Other notes | CS+ V4.01.00

2.15.7.3 Other notes

-	No events can be set to local variables.

-	Events do not occur during step execution (including return execution) and program execution by selecting [Go to Here] from the context menu.

-	If the location set for an existing event changes to midway in an instruction because the program to debug has been downloaded again, re-set the event using the following method.

-	If debugging information is available: The location setting of events is always moved to the beginning of the source text line.

-	If debugging information is not available: Depends on the [Automatic change method of event setting position] property in the [Download] category on the [Download File Settings] tab of the Property panel.

-	If a change to internal ROM/RAM changes the location the event is set to a non-mapped area, then set events will not occur (they will also not change to Invalid state /Suspended State on the Events panel).

-	If you differentiate function or variable names by leading underscores, then CS+ may misrecognize them, and convert symbols or make break event settings invalid. This applies for cases like when you have two functions, one named "_reset" and the other named "__reset".

If there is code (text sections) to be ROMified, any software break event set for that code will be deleted during copy to RAM. For this reason, no break will occur. Use a hardware break if you are using OCD(JTAG) or OCD(Serial) or IECUBE. Note that if you are using a simulator, execution will not break even if a hardware breakpoint is used, but it will break if the tracer or timer is turned on.

-	For other than [Simulator] Use a hardware break event.

[Simulator]

Execution will not break even if a hardware break event is used, but it will break if the trace function or the timer function is valid (on the [Debug Tool Settings] tab of the Property panel, specify [Yes] with the [Use trace function]/[Use timer function] property on the [Trace]/[Timer] category).

-	For other than [IECUBE] If a software break event is set in a boot-swap area, then a break instruction will be written to the flash ROM. For this reason, a break instruction will remain after the boot swap.

-	[E1][E20][EZ Emulator] Use a hardware break event in a boot-swap area if you wish to.

-	[Simulator] Do not use a break event in a boot-swap area.

For other than [Simulator]

Hardware Break events with access conditions and Point Trace events [IECUBE] cannot be set for 32-bit (4-byte) variables.
Additionally, Hardware Break events with access conditions and Point Trace events [IECUBE] cannot be detected if a single byte of a 16-bit (2-byte) variable is accessed.