Everything
2.11.1.1 [IECUBE]

This trace operation can be configured in the [Trace] category on the [Debug Tool Settings] tab in the Property panel.

Figure 2.117

[Trace] Category [IECUBE]

(1)

[Clear trace memory before running]

Select whether to clear (initialize) the trace memory before tracing starts in this property.

Select [Yes] to clear the memory (default).

Remark

You can forcibly clear the trace memory when clicking the button in the toolbar in the Trace panel.

(2)

[Operation after trace memory is full]

Select the operation after the trace memory is full with the collected trace data, from the following drop-down list.

The trace memory size is 128K frames (fixed).

Non stop and overwrite to trace memory

Continues overwriting the older trace data after the trace memory is full (default).

When the [Clear trace memory before running] property is set to [Yes], at the time of a resumption, trace data is collected after clearing the trace memory.

Stop trace

When the trace memory is full, CS+ stops writing trace data (the program does not stop execution).

Stop

When the trace memory is full, CS+ stops writing trace data and the program stops execution.

(3)

[Rate of frequency division of trace time tag]

Specify the frequency division ratio of the counter to be used for time tag display (i.e. display of the [Time] item in the Trace panel) (default: [1/1(4ns/0.3min)]).

Remark

Values in "()" on the drop-down list indicate the resolution and the maximum measurement time.

Caution

An error occurs in trace time tag due to the following causes:

-

When the RAM monitor function is used during user program execution

-

When a hardware or software breakpoint is set during user program execution

-

When a value is written to memory using the DMM function during user program execution

Caution

Information on access to the SFRs and memory by the DMAC is also output with information on data to which access is normal.