Everything
2.14.1.3 [Simulator]

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

Figure 2.65

[Trace] Category [Simulator]

(1)

[Use trace function]

Select whether to use trace function.

Select [Yes] to use the trace function (default: [No]).

(2)

[Trace target]

Select the trace target from the following drop-down list.

Debug core only

Collects the trace data regarding the currently selected PE (default).

After collecting the trace data, if you switch PE, the contents of the Trace panel will be updated to the corresponding trace data.

All core

Collects the trace data for all PEs.

After collecting the trace data, the contents of the Trace panel is not changed even if you switch PE.

(3)

Select trace data

Select the type of trace data to be collected from the following properties.

Trace the branch PC and the data access

PC values for the source and destination instructions of branching during program execution and the PC values and information on the data for instructions leading to access-related events that occur during program execution are collected as trace data.

Trace the software trace

Information on trace output instructions to be embedded that were generated during program execution is collected as trace data.

Trace the DBCP

Information on DBCP that were generated during program execution is collected as trace data.

Trace the DBTAG

Information on DBTAG that were generated during program execution is collected as trace data.

Trace the DBPUSH

Information on DBPUSH that were generated during program execution is collected as trace data.

Caution

The trace memory is cleared when you change the setting of these properties.

(4)

[Clear trace memory before running]

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

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.

(5)

[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.

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, the 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.

(6)

[Accumulate trace time]

Select whether to display the trace time with accumulated time.

Select [Yes] to display trace time with accumulated time. Select [No] to display the trace time with differential time (default).

(7)

[Trace memory size[frames]]

Select the trace memory size (trace frame number).

The trace frame is a unit of trace data. One trace frame is used for each operation in fetch/write/read.

Drop down list includes the following trace frame numbers.

4K (default), 8K, 12K, 16K, 20K, 24K, 28K, 32K, 36K, 40K, 44K, 48K, 52K, 56K, 60K, 64K, 128K 192K, 256K, 320K, 384K, 448K, 512K, 576K, 640K, 704K, 768K, 832K, 896K, 960K, 1M, 2M, 3M

(8)

[Rate of frequency division of trace time tag]

Select the frequency division ratio of the counter to be used for time tag display (the [Time] item in the Trace panel) (default: [1/1]).

When the division ratio is set, the number of clocks required for the incrementation of the counter displayed on the time tag of the branch PC and the data access is changed.