Everything
2.1 Overview

The basic debugging sequence for programs using CS+ is as follows:

(1)

Start CS+

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

Remark

For details on how to start CS+, see "CS+ Project Operation".

(2)

Set a project

Create a new project, or load an existing one.

Remark

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

(3)

Create a load module

Create a load module by running a build after setting of the active project and the build tool to be used.

Remark

For details on "Create a load module" with CC-RL, see "CS+ Project Operation".

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

Select the debug tool to be used in a project.

(6)

Configure operating environment of the debug tool

Configure the operating environment of the debug tool selected in steps (5).

Connect the debug tool to CS+ to start communication.

Download the load module created in steps (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 by using the operation method corresponding to a purpose.

If you wish to stop the program at the arbitrary position, set a breakpoint/break eventNote before executing the program (see "2.8.3 Stop the program at the arbitrary position (breakpoint)", "2.8.4 Stop the program at the arbitrary position (break event)", or "2.8.5 Stop the program with the access to variables/SFRs").

Note

These functions are implemented by setting events to the debug tool used.
See "2.15.7 Notes for setting events", when you use events.

Stop the program currently being executed.

Note that if a breakpoint or a break event has been set in steps (10), the program execution will be stopped automatically when the set break condition 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.15.7 Notes for setting events", 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 file, Motorola S-record file, binary file, and 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".