2.1 Overview

Following shows the basic sequence of program debugging using CS+.

(1)

Start CS+

Launch CS+ from the [Start] menu of Windows.

Remark

For details on "Start CS+", see "CS+ Project Operation".

(2)

Set a project

Create a new project, or load the existing one.

Remark

For details on "Set a project", see "CS+ Project Operation".

(3)

Create a load module

Once you are finished with the setting of the active project and the build, execute the build to create a load module.

Remark

For details on "Create a load module" with CC-RX, see "CS+ CC-RX Build Tool Operation".

Connect the debug tool (E1, E20, EZ Emulator or Simulator) to be used to a host machine.

Select the debug tool to be used in a project.

Remark

The selectable debug tool differs depending on the microcontroller type to be used in a project.

(6)

Configure the operating environment for the debug tool

Configure the operating environment for the debug tool selected in step (5).

Connect the debug tool to CS+ to start communication.

Download the load module created in step (3) to the debug tool.

Display the contents of the downloaded load module (source files) on the Editor panel or Disassemble panel.

Execute the program using the operation method that matches your purpose.

If you wish to stop the program at the arbitrary position, set a breakpoint/break eventNote before executing the program (see "2.10.2 Stop the program at the arbitrary position (breakpoint)"/"2.10.3 Stop the program at the arbitrary position (break event) [E1] [E20] [EZ Emulator]").

Note

These functions are implemented by setting events to the debug tool used.
See "2.17.7 Points to note regarding event setting", when you use events.

Stop the program currently being executed.

Note that if a breakpoint/break event has been set in steps (10), the program execution will be stopped automatically when the condition of the breakpoint/break event is met.

(12)

Check the result of the program execution

Check the following information that the debug tool acquired by the program execution.

Note

These functions are implemented by setting events to the debug tool used.
See "2.17.7 Points to note regarding event setting", when you use events.

 

Debug the program, repeating steps (9) to (12) as required.

Note that if the program is modified during debugging, steps (3) and (8) also should be repeated.

Remark 1.

Other than the above, you can also check the result of the program execution by using the following functions.

Remark 2.

The acquired information can be saved to a file.

Save the program (the memory contents) to a file in the arbitrary format (e.g. Intel hex format, binary data format, etc.), as required.

Disconnect the debug tool from CS+ to terminate communication.

(15)

Save the project file

Save the setting information of the project to the project file.

Remark

For details on "Save the project file", see "CS+ Project Operation".