CoIDE User Guide for FRDM-KL25Z

12/2/2012 6:48 PM V1.0 Completed

Website:

http://www.coocox.org

Forum:

http://forum.coocox.org

Technical: master@coocox.com
Market:

market@coocox.com

Catalog
1

CoIDE Quick Start............................................................................................................... 5

General Introduction ....................................................................................................... 16

2.1

2.1.1

Terminology Note ............................................................................................. 16

2.1.2

CoIDE Features ................................................................................................. 17

2.2

Support Devices ................................................................................................ 17

2.2.2

Supported Adapters ......................................................................................... 18

Requirement for CoIDE ............................................................................................ 18

Preparation ...................................................................................................................... 19
3.1

Set GCC Compiler ..................................................................................................... 19

3.1.1

ARM GCC Introduction ..................................................................................... 19

3.1.2

Set GCC in CoIDE ............................................................................................... 20

3.2
4

Support list ............................................................................................................... 17

2.2.1

2.3
3

New Concepts .......................................................................................................... 16

Install the adapter .................................................................................................... 22

User Interface .................................................................................................................. 23

4.1

Menus and Actions................................................................................................... 23

4.1.1

File Menu Actions ............................................................................................. 23

4.1.2

Edit Menu Actions ............................................................................................ 23

4.1.3

View Menu Actions ........................................................................................... 23

4.1.4

Project Menu Actions ....................................................................................... 24

4.1.5

Flash Menu Actions .......................................................................................... 24

4.1.6

Debug Menu Actions ........................................................................................ 24

4.1.7

Search Menu Actions ........................................................................................ 25

4.1.8

Help Menu Actions ........................................................................................... 25

4.2

Toolbar ..................................................................................................................... 26

4.2.1

Editor Toolbar Actions ...................................................................................... 26

4.2.2

Debug Toolbar Actions ..................................................................................... 27

4.3

Editor View ............................................................................................................... 28

4.3.1

Breakpoint ........................................................................................................ 28

4.3.2

Components ..................................................................................................... 28

4.3.3

Console ............................................................................................................. 28

4.3.4

Configuration .................................................................................................... 30

4.3.5

Editor ................................................................................................................ 34

4.3.6

Help................................................................................................................... 35

4.3.7

Help Contents ................................................................................................... 36

4.3.8

Outline .............................................................................................................. 37

4.3.9

Peripheral ......................................................................................................... 38

4.3.10

Project Explorer ................................................................................................ 39

4.3.11

Repository......................................................................................................... 40

4.3.12

Search ............................................................................................................... 40

4.4

Debug View .............................................................................................................. 42

4.4.1

Breakpoints ....................................................................................................... 42

4.4.2

Debug................................................................................................................ 43

4.4.3

Disassembly ...................................................................................................... 44

4.4.4

Expressions ....................................................................................................... 46

4.4.5

Memory ............................................................................................................ 47

4.4.6

Peripherals view (CoAssistant) ......................................................................... 49

4.4.7

Registers ........................................................................................................... 50

4.4.8

Semihosting view .............................................................................................. 52

4.4.9

Variables ........................................................................................................... 52

Project Management ....................................................................................................... 55

5.1

Create Project........................................................................................................... 55

5.2

Manage Target/Groups/Files and Switch Chip ........................................................ 59

5.2.1
5.3

Target List Management in the Multi-configuration ........................................ 59

Project configuration................................................................................................ 62

5.3.1

Change device................................................................................................... 62

5.3.2

Compile configuration ...................................................................................... 64

5.3.3

Link configuration ............................................................................................. 65

5.3.4

Output configuration ........................................................................................ 67

5.3.5

User configuration ............................................................................................ 68

5.3.6

Debugger configuration .................................................................................... 69

5.3.7

Download configuration ................................................................................... 70

5.4

Build project ............................................................................................................. 71

5.5
6

Debug .............................................................................................................................. 74
6.1

Introduction ............................................................................................................. 74

6.1.1

Enter debug mode ............................................................................................ 74

6.1.2

Debug execution control .................................................................................. 74

6.1.3

Set breakpoints ................................................................................................. 74

6.1.4

Single step......................................................................................................... 74

6.1.5

Debug Example ................................................................................................. 75

6.2

Open project ............................................................................................................ 72

How to use debug views .......................................................................................... 78

6.2.1

Disassembly view .............................................................................................. 79

6.2.2

Memory view .................................................................................................... 80

6.2.3

Variables view ................................................................................................... 81

Component and Examples............................................................................................... 83

7.1

Components ............................................................................................................. 83

7.1.1

Add Components .............................................................................................. 83

7.1.2

Refresh and Update Components .................................................................... 87

7.2

Examples .................................................................................................................. 89

7.2.1

Viewing example .............................................................................................. 89

7.2.2

Adding code snippet ......................................................................................... 93

1 CoIDE Quick Start

1.

Launch CoIDE, and select the manufacturer, e.g. Freescale.

2.

Select your target chip, e.g. MKL25Z128VLK4, and then the Help view on the right side
of CoIDE will show corresponding information of the chip.

3.

Check/Select the components which you want to use, e.g. xGPIO component, CoIDE will
ask you to create a new project.

4.

After clicking "Yes", CoIDE will pop up a window for you to specify where to save the
project.

5.

Select an English path, e.g. the "workspace" folder under the CoIDE installation path,
and then create a new folder such as "test" to save your project.

6.

Save the project with specified project name, e.g. "Freescale".

7.

After clicking "Save", CoIDE will create a project for you, containing manually-selected
component code in step 3, auto-selected components code depended on by manuallyselected component (e.g. the startup component), as well as a main.c file.

8.

Click xGPIO component in the Repository view, detailed descriptions of GPIO

component will show in the Help view.

9.

The Components view shows all selected components and the example number of each
component. Click a component and its Example window will popup.

10. Click view to view the example (e.g. Blinky) and add to add it to your project.

11. Click Yes to confirm adding the example to the default path.

12. CoIDE will add the Blinky.c file to the project, and the Blinky function to the main
fuction.

13. Click Build button to compile and link the program.

14. Click Configuration button to open the configuration window.

15. Select CMSIS-DAP as the adapter in the Debugger page.

16. Click Download button to download code to flash.

17. Click Debug button to start debugging.

18. If debugging is launched successfully, CoIDE will enter the debug mode.

19. The default debug UI only shows several debug windows, you can open the other debug
windows through view menu.

20. Set breakpoints in the c code window or the Disassembly window.

21. Use the debug functions like single stepping via the tool bar or debug menu.

2 General Introduction
CoIDE is a new, free and highly integrated software development environment for ARM
Cortex MCU based microcontrollers, which includes all the tools necessary to develop highquality software solutions in a timely and cost effective manner.

2.1 New Concepts

CoIDE consists of a component-based network platform and an Eclipse-based development
environment. The component-based network platform can quickly obtain resources to build
applications, share your resources and exchange ideas. The Eclipse-based development
environment provides many features for code editing, code browsing, compiling, linking,
debugging, project management, etc.
Features:

2.1.1

Free to use
Full functional IDE
Component-oriented development platform
Internet-based, efficient integration of network resources
Integrates CoOS
Peripheral registers
Terminology Note

2.1.1.1 Component
In CoIDE, any reusable code can be called as a component, including OS, drivers, examples,
middle layer software and so on. It is easy to understand and use by providing useful
functions, and most importantly, can work correctly. Each component has its corresponding
code snippets, usage, documentation and comments.
2.1.1.2 Dependence
If component A calls the content of component B (known as Compilation Dependence), or
component A cannot correctly execute without component B (known as Application
Dependence). We call component A depends on component B. When you check component
A, CoIDE will automatically check the dependence components of component A. One
component can depend on several components. It can be depended by multiple
components, too.
2.1.1.3 Code Snippet
Code Snippet is also known as example code, it is an extension of component. If the
component is object-oriented, the code snippet will be application-oriented. For example, a
PIO driver can be known as a component, a function using PIO driver to achieve LED flashing
can be known as a code snippet. The code snippet is generally very short, but the features
are not restricted. It can be automatically inserted into the code.

2.1.2

CoIDE Features

CoIDE can be used for code editing, code browsing, compiling, linking, debugging, project
management; it also can be used to obtain components, to share components and to
exchange ideas.
2.1.2.1 Component Network
Component Network contains a large amount of free components, the components are
provided by CooCox and CooCox users. CooCox has provided RTOS, flash manager,
embedded database, protocol stack and other components, which are all free and open.
Everyone can use these components and upload their own components.
2.1.2.2 Component Oriented Programming
In embedded application development, if there is no suitable libraries, development work
will become very complicated. Once you have the suitable libraries, anything will be
manipulated in your hands. CooCox CoIDE Component Network contains a large amount of
free components, users can choose suitable components according to your own needs, and
use the component code snippets to build application will become more quickly. With a
large number of components and detailed component documentation, programming will be
as simple as building block.
2.1.2.3 Component Documentation
Each component has a detailed documentation (displayed in the Help View), including
component description, component dependency relationship, component source files, usage
of the component, comments and so on. CoIDE automatically generates documentation for
source files. If the code comment style is consistent with Doxygen, the documentation will
be very detailed. Moreover, the detailed documentation allows you to use the component
more quickly.
2.1.2.4 Interaction
In order to help users to solve the problems encountered in development process, CoIDE
provides a powerful interaction function. In CooCox CoIDE, everything can interact, such as
chip, component, peripheral, register, code snippet and so on; users can even ask questions
directly to solve their problems.
2.1.2.5 Development Environment
CoIDE is based on the Eclipse development platform, it has the following features:

Integrated CDT editor: You can edit and browse the code; it is a full-featured editor.
Integrated GCC ARM Embedded: Using gcc tool chain, which is efficient and stable.
A clear interface: Menus and toolbar are simple, clear and easy to use.
GUI Setting: Dialogs for all settings.

2.2 Support list

2.2.1

Support Devices

CooCox CoIDE mainly supports ARM Cortex M series. Until now, CooCox has supported
Cortex-M4, Cortex-M3, Cortex-M0 and Cortex-M0 plus chips from Atmel, Energy Micro,

Freescale, Holtek, NXP, Nuvoton, ST and TI. For the entire support list, you can go to:
http://www.coocox.org/CooCox_CoIDE.htm
Here we list the Freescale chips that are supported by the newest version of CoIDE (v 1.6.2):

MKL04Z16VFK4, MKL04Z16VFM4, MKL04Z16VLC4, MKL04Z16VLF4, MKL04Z32VFK4,

MKL04Z32VFM4, MKL04Z32VLC4, MKL04Z32VLF4, MKL04Z8VFK4, MKL04Z8VFM4,
MKL04Z8VLC4,
MKL05Z16VFK4, MKL05Z16VFM4, MKL05Z16VLC4, MKL05Z16VLF4, MKL05Z32VFK4,
MKL05Z32VFM4, MKL05Z32VLC4, MKL05Z32VLF4, MKL05Z8VFK4, MKL05Z8VFM4,
MKL05Z8VLC4,
MKL14Z32VFM4, MKL14Z32VFT4, MKL14Z32VLH4, MKL14Z32VLK4, MKL14Z64VFM4,
MKL14Z64VFT4, MKL14Z64VLH4, MKL14Z64VLK4,
MKL15Z128VFM4, MKL15Z128VFT4, MKL15Z128VLH4, MKL15Z128VLK4,
MKL15Z32VFM4, MKL15Z32VFT4, MKL15Z32VLH4, MKL15Z32VLK4, MKL15Z64VFM4,
MKL15Z64VFT4, MKL15Z64VLH4, MKL15Z64VLK4,
MKL24Z32VFM4, MKL24Z32VFT4, MKL24Z32VLH4, MKL24Z32VLK4, MKL24Z64VFM4,
MKL24Z64VFT4, MKL24Z64VLH4, MKL24Z64VLK4,
MKL25Z128VFM4, MKL25Z128VFT4, MKL25Z128VLH4, MKL25Z128VLK4,
MKL25Z32VFM4, MKL25Z32VFT4, MKL25Z32VLH4, MKL25Z32VLK4, MKL25Z64VFM4,
MKL25Z64VFT4, MKL25Z64VLH4, MKL25Z64VLK4

2.2.2

Supported Adapters

Here we list the adapters, which support Freescales M0plus series.

Adapter

Available Devices

CoLinkEx

Atmel, Energy Micro, Freescale, TI, NXP, Nuvoton, ST, Holtek

Open-SDA

Freescale

2.3 Requirement for CoIDE

System requirements:

Windows XP SP3/Windows Vista/Windows 7

Hardware requirements:

A debugging Adapter such as CoLinkEx, Open-SDA, etc.

Software requirements:

GCC ARM Embedded (see: Set GCC Compiler)

3 Preparation
3.1 Set GCC Compiler
Before you use CoIDE to start your project, you need to configure the GCC compiler and
debugger at first.
CooCox suggests you to choose ARM GCC Compiler as the compiler since it is from ARM
official. If you want to know more details about ARM GCC, please click here. In addition, you
can also choose other GCC compilers such as CodeSourcery GCC.
3.1.1

ARM GCC Introduction

Features:

All GCC 4.6 features, plus latest mainline features

Cortex-M0/M1/M3 support
Cortex-M4 with hard float multilib support
Cortex-R4/R5 with hard float multilib support
Fixed point fraction support

Download link: https://launchpad.net/gcc-arm-embedded/+download

Note:
As CoIDE support different GCC compilers, you need to pay attention to the following points
when you switch between the compilers:

The different compilers have different C libraries, for example: ARM GCC have base C
Library and Semihosting Library, Retarget Library. However, CodeSourcery GCC only has
the base C Library. See: Project Configuration
ARM GCC and CodeSourcery GCC use different link.ld when they compile the same
project. CoIDE will generate different link.ld when you create the project, so it is
strongly recommended of you to set the GCC compiler before you start.
If you want to use ARM GCC to compiler the project you created under CodeSourcery
GCC, you need to delete the Build.xml, link.ld, memory.ld. Then check a component
and reconfigure the project after set the GCC.

3.1.2

Set GCC in CoIDE

1.

After launched CooCox CoIDE, click "Select Toolchain Path" under the Project menu.

2.

Click the Browse button, select the folder that contains the arm-none-eabi-gcc.exe and
the other GCC execute files.

3.

For example, select the bin folder.

4.

Click OK button to save the setting.

3.2 Install the adapter

If you are using OpenSDA, you need to do the following steps:
1. Download the CMSIS-DAP firmware for OpenSDA.
2. Update the OpenSDA with the new firmware.
3. Install the Microsoft Visual C++2010 SP1 Redistributable Package according to the
operating system.
4. Select CMSIS-DAP as the adapter in CoIDE.
You can view the detailed operation guide in document: How_to_use_OpenSDA.pdf. The
document can be get from http://www.coocox.org/Freescale.html or the CD:/Document/

4 User Interface
4.1 Menus and Actions

4.1.1

File Menu Actions

Name

Description

Shortcut

New File

Create a new file.

Ctrl + Shift + N

Save

Save the content of the current editor. Disabled if the editor does
not contain unsaved changes.

Ctrl + S

Save As...

Save the content of the current editor under a new name.

Save All

Save the content of all editors with unsaved changes. Disabled if

no editor contains unsaved changes.

Exit

Exit CoIDE.

4.1.2

Ctrl + Shift + S

Edit Menu Actions

Name

Description

Shortcut

Undo

Undo your operations.

Ctrl + Z

Cut

Cut a code snippet or a file.

Ctrl + X

Copy

Copy a code snippet or a file.

Ctrl + C

Paste

Paste the code snippet or a file to a place.

Ctrl + V

4.1.3

View Menu Actions

Name

Description

Repository

Open Repository View.

Configuration

Open the current project configuration page (Open builder.xml of

the current project in Editor).

Project

Open Project View

Components

Open component platform

Help

Open Help View.

Outline

Open Outline View.

Peripherals

Open Peripherals View.

Breakpoints

Open Breakpoints View.

Default layout

Resume to the default layout.

Shortcut

4.1.4

Project Menu Actions

Name

Description

New Project

Shortcut

Create a new Project and close the current project.

Open Project... Show a dialog that can be used to select an existing project.
Close Project

Close the current project.

Select
Select the GCC Toolchain you want to use.
Toolchain path
Build the currently selected project. This is an incremental build, meaning
Build
that the builder analyzes the changes since the last time of build and
minimizes the number of changed files.

Ctrl +
R

Rebuild

Rebuild all files of the current project.

Clean

Clean the intermediate files that generated by building.

Upload
Component

Open the Login dialog box, you can upload Component after login with
CooCox account.

Upload Board

You can upload development board after login with CooCox account.

Upload
Example

You can upload component examples after login with CooCox account.

4.1.5

Flash Menu Actions

Name

Description

Program Download

Download program to Flash.

Flash Erase

Erase Flash.

4.1.6

F7

Shortcut

Debug Menu Actions

Name

Description

Shortcut

Debug

To debug the current project.

Ctrl+F5

Toggle Breakpoint

To set a breakpoint at the current line.

Ctrl +Shift+ B

Toggle Line Breakpoint

To set a breakpoint at one line in the function.

Toggle Method Breakpoint

To set a breakpoint at the entry of current function.

Toggle Watch Breakpoint

To set a Watch Breakpoint.

Skip All Breakpoints

Skip all the Breakpoints when debugging.

Remove All Breakpoints

Delete all the Breakpoints.

Breakpoint Type

Breakpoint Type

4.1.7

Search Menu Actions

Name

Description

Search...

Execute a C/C++ or file search.

File...

Execute a file search.

4.1.8

Shortcut
Ctrl + H

Help Menu Actions

Name

Description

Help Contents CoIDE Users' Guide.

About CoIDE

Display CoIDE version number and license information.

Shortcut

4.2 Toolbar
4.2.1

Editor Toolbar Actions

Icons

Name

Description

New Project

Create a new Project and close the current project.

Create New File

Create a new file.

Save

Build

Save the content of the current editor. Disabled if

the there is no changed.
Build the currently selected project. This is an
incremental build, meaning that the builder
analyzes the changes since the last time of build
and minimizes the number of changed files.

Shortcut

Ctrl + S

F7

Rebuild

Rebuild all files of the current project.

Ctrl + R

Start Debug.

Debug the current project.

Ctrl + F5

Download Code
to Flash

Download program to flash.

Flash Erase

Erase the full chip.

Configuration

Configure the project.

Target Manage

Manage the Targets in the project

Repository

Open Repository View.

Open Element

Open the Search dialog box.

Ctrl +Shift +T

Search

Open the Search dialog box.

Ctrl + H

Toggle Mark
Occurrences

Turns mark occurrences on and off in the C/C++

editor.

Next Annotation

Go to the next annotation.

Ctrl +.

Previous
Annotation

Go to the previous annotation.

Ctrl + ,

Last Edit Location

Go to the location where you have modified last

time.

Ctrl + Q

Back to...

Go back to the previous position.

Alt + Left

Forward to...

Forward to next position.

Alt + Right

Alt+Shift+0

4.2.2

Debug Toolbar Actions

Icons

Name

Description

Shortcut

Instruction Stepping Select the instruction stepping mode command

Mode
to step the instruction.
Select the Reset command to reset the
Reset CPU
debugging.
Select the Run command to resume execution
Run
F5
of the currently suspended debug target.
Select the Suspend command to halt execution
Suspend
of the currently selected thread in a debug
F9
target.
Ends the selected debug session and/or
Terminate
Ctrl + F5
process.
Select to execute the current line, including
Step Into
any routines, and proceed to the next
F11
statement.
Select to execute the current line, following
Step Over
F10
execution inside a routine.
Select to continue execution to the end of the
Step Out
current routine, then follow execution to the
Ctrl + F11
routine's caller.
Run To Line

Select to continue execution to current line.

Open Element

Open the Search dialog box.

Ctrl +Shift +T

Search

Open the Search dialog box.

Ctrl + H

Toggle Mark
Occurrences

Turns mark occurrences on and off in the

C/C++ editor.

Next Annotation

Go to the next annotation.

Previous Annotation Go to the previous annotation.

Ctrl + R

Alt+Shift+0
Ctrl +.
Ctrl + ,

Last Edit Location

Go to the location where you have modified

last time.

Ctrl + Q

Back to...

Go back to the previous position.

Alt + Left

Forward to...

Forward to next position.

Alt + Right

4.3 Editor View

4.3.1

Breakpoint

This view shows the information of breakpoints set by user in the code.
4.3.2

Components
This view displays all the components of the
current project selection. If you click a
component in this view:

4.3.3

The Help view will display the

properties of the clicked component,
such as the component source files,
source files documents, dependent
components, usage and comments.
The Code Snippet View will display all
code snippets of the component.
The Project View will highlight the
component source files.

Console

This view shows the output of the execution of your program and enables you to enter input
for the program.

Console View Toolbar:

Icon Command

Description

Pin Console

Force the Console view to remain on top of other

views in the window area.

Display Selected Console

If multiple consoles are open, you can select the one

to display from a list.

Open Console

Open new console view.

Clear Console

Clear the console.

Scroll Lock

Toggle the Scroll Lock.

Show Console When

Standard Out Changes

Show console when standard out changes.

Show Console When

Standard Error Changes

Show console when standard error changes.

4.3.4

Configuration

Click the Configuration button to enter the configuration view.

The Configuration view is departed into seven parts, contain the configuration for the
project. It has Device, Compile, Link, Output, User, Debugger, Download pages.

1.

The following pictures show the different pages: The Device configuration

2.

The compile configuration

3.

The link configuration

4.

The output configuration

5.

The user configuration

6.

The debug configuration

7.

The download configuration

4.3.5

Editor

The C/C++ editor provides specialized features for editing C/C++ related files.

The most common way to invoke the C/C++ editor is to open a file from the Project Explorer
by clicking the file (single or double-click depending on the user preferences).
The C/C++ editor just have the context menu (right click your mouse in the editor view, the
context menu will be presented) and key binding actions.

4.3.6

Help

This view displays all information about the selected component, it always include the
following issues:
1.
2.
3.
4.

Component name, overview and other information

API Reference, the reference of the APIs, which link to the Doxygen Documents
generated by CoIDE.
Source files: Source files of the component.
Dependency: Other components depended by the component.

4.3.7

Help Contents

You can open the Help Contents through the Help Menu, which shows the help for use
CoIDE.

Toolbar
Icon

Name

Description

Availability

Go Back

Go back to the previous position.

Toolbar

Go Forward to

Forward to the next position.

Toolbar

Home
Show in table of
content

Go to the home page of the Help

content.
Show the page position in the
table of content view.

Toolbar
Toolbar

Bookmark Document Add a bookmark.

Toolbar

Print Page

Print the current page.

Toolbar

Print Topics

Print the topics.

Context menu

Search Topics

Search the topics.

Context menu

Collapse All

Collapse all the topics.

Context menu

Link with contents

Link with the contents.

Context menu

Show Result
Categories

Show the categories of the search

results.

Search Results
View

4.3.8

Show Result
Description
Delete Selected
Bookmark

Show the description of the search Search Results

results.
View
Delete the selected bookmark.

Bookmark View

Delete All Bookmark

Delete the entire bookmark.

Bookmark View

Outline

The Outline view will show the outline when

you open a source file in the edit view. It can
show all the includes, definitions, macros,
functions in the source file you opened.
You can click the icons or the characters
behind to go to the related values in the edit
view.

Outline view toolbar icons:

The table below lists the icons displayed in the Outline view toolbar.
Icon

Description

Icon

Description
Filters

Sort items alphabetically

Link With Editor

Hide Fields

Group Includes

Hide Static Members

Group Macros

Hide Non-Public Members

Group Methods

Hide Inactive Elements

Group Namespaces

Outline view menu

Outline view icons:

The table below lists the icons displayed in the Outline view.
Icon

Description

Icon

Description

Class

Include

Namespace

Method private

Macro Definition

Method protected

Enum

Method public

Enumerator

Struct

Variable

Type definition

Field private

Union

Field protected

Function

Field public

4.3.9

Peripheral

This view shows the information of peripheral register.

Click on the corresponding register to get the register detailed information view:

4.3.10 Project Explorer

This view displays all files of the file system under your project
directory, including C source files (*.c, *.h), assembly source files
(*.s), project configuration files (build.xml), linker script files
(*.ld), library files (*.a), etc. In this view you could do the
following operations:

Open files in the editor view

Open project configuration interface
Close the current project
Create new projects, files, or folders
Manage existing files (copy, paste, delete, move or rename)

4.3.11 Repository

This view displays all available components in the project. The before the component
shows this component has been checked into the project. By checking or unchecking the
before components to add or delete the components.
4.3.12 Search
The Search view only shows when you have searched something in the project.

The type of the selected C/C++ element defines which search context menus are available.
The C/C++ editor does not constrain the list of available C/C++ searches based on the
selection.
Search view Toolbar:
Icon

Command
Next

Description
Navigate to the next search result.

Previous

Navigate to the previous search result.

Remove the Selected

Matches

Removes user selected matches from the search

console.

Remove All Matches

Clear the search console.

Run the Current Search

Again

Run the current search again.

Terminate

Terminate the current search.

Show Previous Searches

Show the list of previously runs searching, which

can be re-selected.

Pin the Search View

Force the search view to remain on top of other

views in the window area.

Menu

List two selectable view layouts for search

results: Flat and Hierarchical.

Minimize Console

Minimize the Console view.

Maximize Console

Maximize the Console view.

4.4 Debug View

4.4.1

Breakpoints

The Breakpoints View lists all the breakpoints you have set in your workspace. Only up to six
breakpoints can be toggled if you are debugging in flash with Cortex-M3 series' chips, for
Cortex-M0, the number is four. Otherwise, warnings will be presented at runtime.
You can double-click a breakpoint to find its location in the editor (if applicable). You can
also enable or disable breakpoints, delete them, add new ones.

The commands available in the Breakpoints View are listed below.

Command

Name

Description

Availability
Context
menu and
view action
Context
menu and
view action

Remove Selected
Breakpoints

Only remove the selected breakpoint(s).

Remove All Breakpoints

Remove all breakpoints.

Show Breakpoints
Supported by Selected
Target

Display the breakpoints supported by the

selected target board.

View action

Go to File

Go to the corresponding location of the

breakpoint in the java editor.

Context
menu and
view action

Skip All

Set all breakpoints to be skipped.

View action

Expand All

Expand all the sub items in the view.

View action

Collapse All

Collapse all the sub items in the view.

View action

Link with View

Change if the breakpoints should be linked

to the Debug View.

View action

Add Event
Breakpoint(C/C++)...

Add event breakpoint.

View action

Add Watchpoints
(C/C++)...

Add watchpoints (Not supported by the

current version. It will be supported in the
future versions.)

View action

Show full paths

Show the full paths of the breakpoints.

View action

Group By...

Allow you to select an alternate grouping

View action

for your breakpoints or create your own.

Select default Working
Sets...
Deselect Default
Working Set
Working Sets...
Enable
Disable

4.4.2

Select the default working set so that the

new breakpoints will be added into this
working set.
Deselect the default working set so that
the new breakpoints will not be added into
any working set.

View action

View action

Open the working sets dialog.

View action

Change the selected breakpoint(s) to be

enabled.
Change the selected breakpoint(s) to be
disabled.

Context
menu
Context
menu
Context
menu
Context
menu
Context
menu
Context
menu
Context
menu
Context
menu

Select All

Select all the breakpoints in the view.

Copy

Copy the selected breakpoints to the

system clipboard.

Paste

Paste copied breakpoints into the view.

Import Breakpoints...

Open the import breakpoints wizard.

Export Breakpoints...

Open the export breakpoints wizard.

Breakpoint Properties...

Open the breakpoints properties dialog.

Debug

1.
2.

The Debug view shows the target debugging information in a tree hierarchy.
The number beside the thread label is a reference counter, not a thread identification
number.

3.

The CDT displays stack frames as child elements. It displays the reason for the
suspension beside the thread, (such as end of stepping range, breakpoint hit, and signal
received). When a program exits, the exit code is displayed.

Debug view context menu commands

command

Name
Remove All
Terminated

Description
Clear all terminated processes in Debug view.

Use Step Filters

Copy Stack
Find...

Open the debug view element-searching dialog.

Step Into

Select to execute the current line, including any routines, and

proceed to the next statement.

Step Over

Select to execute the current line, following execution inside a

routine.

Step Return
Instruction
Stepping Mode
Resume
Suspend
Terminate

Select to continue execution to the end of the current routine, then

follow execution to the routines caller.
Activate to enable instruction stepping mode to examine a
program as it steps into disassembled code.
Select the Resume command to resume execution of the currently
suspended debug target.
Select the Suspend command to halt execution of the currently
selected thread in a debug target.
End the selected debug session and/or process. The impact of this
action depends on the type of the item selected in the Debug view.

Terminate and
Relaunch

Select the Terminate and Relaunch command to terminate the

selected debug target and then relaunch it.

Restart

Select the Restart command to restart the remote debug target.

Disconnect

Select the Disconnect command to disconnect the connection to

the debug target.

Relaunch

This command relaunches the selected debug target.

Edit...

Open the launch configuration dialog, allowing you to make

changes.

Edit Source
Lookup...

Open the source lookup dialog, allowing you to make changes.

Lookup Source

Select to force a source lookup to take place.

Terminate and
Remove
Terminate/Discon
nect All
Properties

4.4.3

Toggle step filters on/off. When on, all step functions apply step
filters.
Copy the selected stack of suspended threads as well as the state
of the running threads to the clipboard.

Terminate the selected debug target and removes it from the view.
Terminate all active launches in the view.
Open the Properties for window showing the process properties.

Disassembly

The Disassembly View shows the loaded program as assembler instructions mixed with
source code for comparison. The currently executing line is indicated by an arrow marker
and highlighted in the view. You can do the following tasks in the Disassembly view.

Set breakpoints at the start of any assembler instruction

Enable and disable breakpoints and set their properties

Step through the disassembly instructions of your program

Jump to specific instructions in the program

Disassembly view context menu commands

Command

Name

Description

Availability

Copy

Copy the selected content into the clipboard.

Context menu

Select All

Select all the content.

Context menu

Show Source

Show the assembly and its corresponding source

code

Context menu
and View action

Show Symbols

Show function label and symbols

Context menu

Preferences

Parameter selection.

Context menu

Run To Line

Resume program execution until the specific line is

reached. This is a convenient way to suspend
execution at a line without setting a breakpoint.

Context menu

Move to Line

Jump to the line selected in the Disassembly view.

Context menu

Resume At Line

Resume program execution from the line selected in

Context menu
the Disassembly view.

4.4.4

Refresh View

Refresh Disassembly view.

View action

Go to Current
Program
Counter(Home)

Jump to the current program execution.

View action

Link with Active

Debug Context

Display the current operating position of the code

View action

Open New View Open a new Disassembly view.

View action

Pin to Debug
Context

View action

Expressions

An expression is a snippet of code that can be evaluated to produce a result. The context for
an expression depends on the particular debug model. Some expressions may need to be
evaluated at a specific location in the program so that the variables can be referenced. You
can view information about expressions in the Expressions view.
You can inspect expressions from a scrapbook page, a stack frame of a suspended thread,
and other places. The Expressions View opens automatically when an item is added to the
view. When debugging a C/C++ program, data that contains variables can be expanded to
show the variables and the fields of the variables.

There are many commands available in the Expressions View:

Command

Name

Description

Availability

Show Type Name

Configure columns to display type names.

View action

Show logic
structure

Show logic structure of the Expressions.

View action

Collapse All

Collapse all the Expressions.

View action

Add Watch
Expression

Allow you to add a watch expression.

Remove

Remove the currently selected expression(s)

from the view.

Context menu and

view action
Context menu and
view action

Remove All

Remove all of the expressions from the view.

Context menu and

view action

Open New View

Open a new Expressions view.

View action

Pin to Debug
Context

4.4.5

View action

Refresh

Refresh.

View action

Select All

Select all the variables in the view.

Context menu

Copy Expressions

Copy the selected expressions and variables

to the system clipboard.

Context menu

Find...

Open the search dialog to find elements in

the variables view.

Context menu

Disable

Disable a currently enabled expression.

Context menu

Enable

Enable a currently disabled expression.

Context menu

Edit Watch
Expression

Allow you to edit existing watch expression.

Context menu

Reevaluate
Expression

Reevaluate the currently selected expression.

Context menu

Format

Select a format type. Choices include: Binary,

Decimal, Natural, and Hexadecimal.

Context menu

Memory

The Memory view of the Debug perspective lets you monitor and modify your process
memory. Memory can be displayed in different predefined data formats -- memory
renderings. The CoIDE supports five rendering types -- hexadecimal (default), ASCII, signed
integer and unsigned integer.

The Memory view can display and modify the value of selected memory address. The
Rendering pane can be configured to display more than two renderings simultaneously.
Memory view toolbar icons:
The table below lists the icons displayed in the Memory view toolbar.
Command

Name

Description

New Tab

Click to create a new memory view..

Go

Shows the Memory value of the selected address.

Import

Import memory view from different kinds of files.

Export

Export memory to different kinds of files.

Open New View

Open a new Memory view.

Pin to Debug Context

Default Rendering

Select default rendering.

Find/Replace

Find or replace value from the Rendering pane.

Find next

Find next one after the command: Find/Replace.

Clear Expressions

Clear the contents of the address input box.

Memory view context menu:

The context menu inside the Memory view includes:
Name

Description

Panes

Enable or disable the showing of the Address, Binary, and Text portions of the
rendering view.

Endian

Toggle between the Little (default) and Big Endian display of memory.

Text

Choose the character encoding used to convert memory values into text for display.
Choices include: ISO-8859-1 (default), US-ASCII, or UTF-8.

Cell Size

Specify the cell size used to display values in the Binary column. Choices include 1, 2,
4 (default), and 8 bytes.

Radix
Columns

Specify the radix used to display the values in the Binary column. Choices include
Hex, Decimal Signed, Decimal Unsigned (default), Octal, and Binary.
Specify the number of columns in the Binary column.

Update Mode Select the update mode of the Rendering pane: Always, On Breakpoints, or Manual.
Copy

Copies the selected portion (address, content or binary number) of the Rendering
pane to the clipboard.

Reset To Base
Reset the Rendering pane to the original base address.
Address
Refresh

Refresh the Rendering pane.

4.4.6

Peripherals view (CoAssistant)

The Peripherals View can be used to view and modify the value of Peripherals' registers.
Values that have changed are highlighted in the Peripherals view when your program stops.

It shows the register list and views the value of these registers. Register that have changed
are highlighted in in the Peripherals view.

Click the name of Register to open the detail information view. In this view, you can get the
description, RW access, address offset and the reset value of the register. You can modify
the value of register when you debug a project.

4.4.7

Registers

The Registers view of the Debug perspective lists

information about the registers in a selected stack
frame.
You can view information about the registers in a
selected stack frame. Values that have changed are
highlighted in the Registers view when your
program stops.

Registers view toolbar icons:

The table below lists the icons displayed in the Registers view toolbar.
Command

Name

Description

Show Type Name

Configure columns to show type names(unavailable when columns

are displayed).

Show logic
structure

Show logic structure of the registers.

Collapse All

Collapse all the registers.

Open New View

Open a new Registers view.

Pin to Debug
Context
Refresh

Refresh

Layout

Provides multiple layout options for the Registers view.

Registers view context menu commands:

The Registers view context menu commands include:

Command

Name

Description

Select All

Select all the editor content.

Copy Registers

Copy the register names and contents to the clipboard.

Enable

Enable the selected register.

Disable

Disable the selected register.

Format
Find...

Select a format type. Choices include Binary, Decimal, Natural,

and hexadecimal.
Open the Find dialog, which allows you to find specific
elements within the view.

Change Value...

Open the Set Value dialog to change the selected registers

value.

Add Register Group

Open the Register Group dialog, which allows you to define a

register group that is shown in the Registers view.

Restore Default
Register Groups

Restore the original register groups.

Add Watchpoints
(C/C++)...

Add watchpoints (Not supported by the current version. It will

be supported in the future versions.)

Watch

Convert the selected register into a watch expression.

4.4.8

Semihosting view

Semihosting view is used to show the information of the host computer and the ARM input
and output communication when running debug.

Semihosting view toolbar icons:

The Semihosting view toolbar commands include:
Command

Name

Description

Clear Console

Clear Console view content.

Scroll Lock

Toggle the Scroll Lock.

Show semihosting info

Show semihosting information.

Semihosting view context menu commands:

The Semihosting view context menu commands include:
Command

4.4.9

Name

Description

Cut

Cut the selected content.

Copy

Copy the selected content to the system clipboard.

Paste

Paste the content in the clipboard.

Select All

Select all the content.

Find/Replace

Find or replace specific element from the Rendering pane.

Open Link

It always is in an invalid state.

Clear

Clear all the content.

Scroll Lock

Toggles the Scroll Lock.

Variables

The Variables View displays information about the variables associated with the stack frame
selected in the Debug View. When debugging a C/C++ program, data that contains variables
can be expanded to show the variables and the fields the variables contain.
You can view information about the variables in a selected stack frame in the Variables view.
When execution stops, the changed values are by default highlighted . Like the other debug-

related views, the Variables view does not refresh as you run your executable. A refresh
occurs when execution stops.
Variables view

There are many commands available in the Variables View:

Command

Name

Description

Availability

Show Type Name

Configure columns to show type names.

View action

Show logic structure

Show logic structure of the Variables.

View action

Collapse All

Collapse all the Variables.

View action

Add Global Variables

Add Global Variables.

Context menu and

view action

Remove Global
Variables

Remove Global Variables.

Context menu and

view action

Remove All Global

Variables

Remove All Global Variables.

Context menu and

view action

Open New View

Open a new Variables view.

View action

Pin to Debug Context

View action

Select All

Select all the variables in the view.

Context menu

Copy Variables

Copy the selected variables to the system

clipboard.

Context menu

Enable

Enable a currently disabled variable.

Context menu

Disable

Disable a currently enabled variable.

Context menu

Cast To Type

Cast To Type

Context menu

View Memory

Allow you to create a memory monitor for

the selected variable.

Context menu

Format

Select a format type. Choices include Binary,

Decimal, Natural, and hexadecimal.

Context menu

Find...

Open the search dialog to find elements in

the variables view.

Context menu

Change Value...

Allow you to change the value for the

underlying selected variable.

Context menu

Add
Watchpoints(C/C++)

Add Watchpoints(C/C++).

Context menu

Watch

Allows you to create a watch expression for

the selected variable.

Context menu

5 Project Management
5.1 Create Project
To create an embedded project using CoIDE, you only need to perform the following steps:
1. Select Project > New Project.

2.

Select any folder as a project file save directory, and fill in the name of the project file
(for example: GPIO_Test)

3.

Select a chip. For example, select ''MKL25Z128VLK4''.

4.

Click "Finish". CoIDE automatically generates GPIO_Test.coproj file and one

configuration: "GPIO_Test".

5.

Check a component. For example, select 'GPIO'. CoIDE will automatically check the
components, which are depended by the checked component.

6.

You can review the result in Component View.

7.

You can also click Drivers to view the Driver pages and add the driver components to
your project.

5.2 Manage Target/Groups/Files and Switch Chip

5.2.1

Target List Management in the Multi-configuration

There is one default configurations target after creating project: Flash configuration target.

Click Target Manage button to manage configuration

list. You can modify the configuration name, increase
configuration, delete configuration, and move the
order of configuration, set as current target and so on.
Click OK to confirm.

In the project view, select the parent directory in which you want to create the Group (If you
do not select the parent directory, the default is the root directory of the project), select Add
Group in context menu:

Group edit box pops up, and you can add the Group.

Click Add Files menu item, you can add a link file to the project view:

Click the new file menu item, you can create a new file, as it is shown in the following figure
after clicking ''Save'' you can create a file and add the file to the project view as a link file.

Double click the file name in Project view to open and edit it.

5.3

Project configuration

Click Configuration button

to enter project configuration view.

Configuration area is divided into seven different configuration items: Device, Compile, Link,
Output, User, Debugger and Download. The first five configurations are building and linking
configurations, the last two are debugging/programming configurations.
5.3.1

Change device

In the newest version of CoIDE, we supported change device function.

However, the new chip may be not compatible with component files or other
configuration you checked in the old chip, so there may be errors or warnings, the user
needs to consider carefully and modify appropriately.
1.

Click ''Device'' in context menu in project view to switch project chip.

2.

Select the target file you need to switch, and then click change device.

3.

CoIDE will popup a dialog for you to confirm the change.

4.

Click OK, then CoIDE will show you the following view. Peripherals view and all the
other views will be related to the new chip.

5.3.2

1)

Compile configuration

Option area:

a)

2)

FPU select MCU type: Not use FPU, FPU soft and FPU hard (Note: If you select the
FPU hard, you need to enable FPU module in the code)
b) Optimization Select the level of optimization(None(-O0), Optimize(-O1), Optimize
More(-O2), Optimize Most(-O3), Optimize Size(-Os))
Include paths area:
Add / Remove header files path
The added path will be relative to the current path of the project file to do deal.

3)

Defined Symbols area:

Add / Remove pretreatment (macro definition) Symbol

4)

Misc Controls area:

User can edit (add) user-defined compile commands.

5)

Compile Control String area:

Show compile commands (do not edit)

5.3.3

Link configuration

1) Options area:
a)

Use Memory Layout from Memory Window (Checked by default)

Check: Memory Areas will be available; Scatter File will be unavailable.

Mean to use memory Areas memory data, and use IDE default link file (such as link.ld).
Uncheck: Memory Areas will be unavailable; Scatter File will be available.
The system will add default link.ld/arm-gcc-link.ld and the memory.ld file in the directory of
the project file, at the same time, the link file path is filled into the Scatter File area, and user
can select a custom link file in the Scatter File area.
b)

Discard unused sections

Allow recovery of unused input section. Segment that contains the entrance symbol, and all
the segments of undefined symbols in the command line will be retained. Segment that
contains a dynamic object reference symbol will also be retained. Check this option to
reduce code size.
c)

Select Discard unused sections to discard useless section

Library select list

Select link library: Not use C Library, Use base C Library, Semihosting, Retarget
2) Linked Libraries area:
Add/remove library file.
Library is collection of a series of procedures, external function and variables. It is integrated
to an application program by the compiler and linker during compilation, and made into a
target file and an executable file that can run independently. The CoIDE library is the GCC
library.
3) Memory Areas area
The memory area only available when check Use Memory Layout from Memory Window)
a)
b)

Select: Debug in Flash (default), Debug in RAM

In Memory Areas area, customize start address and size for IROM and IRAM:
IROM and IRAM start address and size is automatically changed according to your
choice, or you can manually modify these values.
In Start line customize IROM and IRAM start address; in Size line customize IROM and
IRAM size.

4) Scatter File area

Scatter File area (available when uncheck Use Memory Layout from Memory Window, at
the same time system in project file directory provides a default link file)
In the area user can specify a custom link file path.
5) Misc Controls area
Edit link command area, users can add custom link command.
6) Linker Control String area
Cannot be edit, display the link commands information.

5.3.4

Output configuration

The configuration area of output files after build project.

The files generated after build will be output to the directory made up of Path of
Executable+/+ Name of Executable.
1)
2)
3)
4)

Name of Executable: Specify the folder of the output files, the default is the
configuration name of the current project configuration;
Path of Executable: Specify the output file path
Create Executable(.elf) :: Generate .elf executable files, by check / uncheck decide
whether to generate the HEX or BIN file
Create Library(.a): Generate .a library file

5.3.5

User configuration

Customize IDE implementation program before and after build.

In Before Build/Rebuild area customize implementation program before Build/Rebuild, in

After Build/Rebuild area customize implementation program after Build/Rebuild.
You can directly output commands, or import .bat or .exe files. After configuration, you need
build or rebuild the project.

5.3.6

Debugger configuration

1) Hardware area
a)

Adapter: CoIDE supports Colink, CoLinkEx, Nu-Link, ST-Link, J-Link and Stellaris-ICDI
debug adapter.

b)

Port: CoIDE supports SWD and JTAG debug modes.

c)

Max Clock (Hz): You can select the clock frequency 2M, 1M, 500K, 300K and 100K.

2) Startup area
Need to check or uncheck Run to main.
3) Advance area
a)

Reset Mode: There are three reset modes: HW RESET, VECTRESET and SYSRESETREQ.

b)

Semihosting Enable: Check to enable Semihosting function.

c)

CacheRom Enable: Check to enable ROM cache.

4) TargetInfo area
Target Info area displays the host name and port number.

5) J-link Info area

In Adapter configuration items of the Hardware area, some special link such as J-Link
Adapter has the peculiar configuration items, as shown below. It displays J-link debugger
configuration information.

5.3.7

Download configuration

1)
2)
3)
4)
5)
6)
7)

Auto Download Before Debugging: automatically download programs before

debugging.
Verify After Download: verify programs after download.
Erase Full Chip: erase the full chip before download.
Erase Effected: erasing the affected sectors before download.
Do not Erase: do not erase the chip before download.
Programming Algorithm Will display Programming Algorithm file.
Add..., Remove and default are used to configure Flash algorithm file.

5.4 Build project

To build a project using CoIDE, you only need to perform the following steps:
1. Select Project > Build. If necessary, you can select Rebuild to recompile your project or
select Clean to clean-up the project has been compiled.

2.

View compile information in the Console window.

5.5 Open project

To open an existing project using CoIDE, you only need to perform the following steps:
1. Select Project > Open Project....

2.

Find the project files with suffix of ''.coproj'' or ''.cob''.

3.

View the opened project.

6 Debug
6.1 Introduction
6.1.1

Enter debug mode

You can click the Debug button to start debug. After launching debug successfully,
CoIDE will come into debug mode.
The debug mode has a quiet different interface from edit mode, to learn more, you can go
to Chapter 4.4 Debug View
6.1.2

Debug execution control

The debug execution controls are superseded by breakpoints. For example, if you attempt to
step over a function and the program hits a breakpoint, it pauses, regardless of whether the
function is completed. You can control your debug execution in various ways, but they all
rely on a core set of debug controls.
To control the debug session, you can use the buttons in the toolbar of debug mode.
Reference: Chapter 4.2.2 Debug Toolbar Actions
6.1.3

Set breakpoints

A breakpoint can be set on an executable line of the program. If the breakpoint is enabled
when you debug, the execution will suspend before the code of that line is executed.
To add a breakpoint point, you could double-click the marker bar located in the left margin
of the C/C++ Editor beside the line of code where you want to add a breakpoint. A dot
will display in the marker bar and in the Breakpoints View, along with the name of the
associated file.
6.1.4

Single step

CoIDE support two kinds of step modes: C code step and instruction step. C code step is the
default option.
C code step means step in c code area, while the instruction step means step each assembler
instructions.
To activate the instruction step mode, you just need to click the Instruction Stepping Mode
option ( ) on the Debug view toolbar. Then when you click the step button ( ), the
Debugger switches to the instruction stepping mode, the Disassembly view will be opened
automatically. If you want to switch back to c code step mode, click the Stepping Mode
option ( ) again.

6.1.5 Debug Example

1. Click Debug button to start debugging.

2.

After launching debug successfully, CoIDE will come into debug mode.

3.

Set a breakpoint by double clicking the marker bar.

4.

Step in C code

5.

Step in instruction step

6.

End debug

6.2 How to use debug views

The initial debug UI only shows a few debug windows, you can open the other debug
windows through view menu.

6.2.1

Disassembly view

The Disassembly view lets you examine your program as it steps into disassembled code.
This is useful when the instruction pointer enters a function for which it does not have the
source. To open the Disassembly view, select View > Disassembly menu.

6.2.2

Memory view

To open the Memory view, select View > Memory menu. Input the memory address you
want to view, for example 0x20000000, then press Enter or click the Go button.

Then you can view the memory space.

6.2.3

Variables view

1.

To open the Variables view select View > Variables menu. Click Add Global Variables to
add a global variable.

2.

Check the global variables you want to add, then click OK button.

3.

Right click on the variable and select the Change Value item to change the value of the
variable.

4.

Input the new value of the variable and click the OK button.

7 Component and Examples

7.1 Components
In CooCox CoIDE, the reusable code is called component. A component can be a library, a
collection of source files and so on. It must provide useful functions, be easy to understand
and use, and most importantly, can work correctly. Each component has its corresponding
code snippets, usage, documentation and comments.
7.1.1
1.

Add Components

When you have created a project and selected a chip, CoIDE will show you a Repository
View, which lists all the components that fit for the chip.

2.

Check the Component you want to add to your project.

3.

CoIDE will add the component and the dependent components to your project
automatically.

4.

You can also click the Driver page to view and add driver components, etc.

5.

Click the components name to view the help documents.

6.

You can view the Doxygen documents for the component by click the related links in
help view.

7.

For the driver component, we have more documents that guide you to use.

7.1.2

Refresh and Update Components

1.

Click "Refresh Component List" button in the right corner of Repository View.

2.

CoIDE will pop up a dialog to remind you which components can be downloaded or
updated.

3.

The right side of repository view shows the components can be updated (or
downloaded) with the state Update (or Download).

4.

Click Update to download the components, and then it shows Available.

7.2 Examples
CoIDE integrates many infrastructure components, in order to allow users to use these
components more easily, each component can be corresponded to multiple sample code
fragments, you can view them and add them to your project, you also could upload your
own examples to the internet.
7.2.1
1.

Viewing example

Click the component which shows "with x example(s)" in the Component View of CoIDE.

2.

The example view will appear and display all the code snippets of the selected
component.

3.

Click view link of the example you are interested in.

4.

The code snippet will display in the code editor viewer.

5.

You can click "More Example for xxx" to view more example for the selected chip.

6.

Other examples will show in more example view based on the component classification.

7.

Click the example name can open the example in the edit view.

7.2.2

Adding code snippet

1.

Click add link of the example you are interested in.

2.

A dialog will pop up to tell you where the example will be located. Click "yes".

3.

The code snippet will be automatically added to the project.