Development Tools

2.14.1.1 [Full-spec emulator]

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

Caution

Properties in this category cannot be changed during program execution.

Figure 2.61

[Trace] Category [Full-spec emulator]

(1)	[Trace target]

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

The choices of this property vary depending on the mode selected by the [Debug mode] property in the [Multi-core] category on the [Debug Tool Settings] tab of the Property panel.

-	When Sync debug mode is selected:

Debug core only

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

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

All core

Collects the trace data for all PEs.

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

-	When Async debug mode is selected:

core name

Collects the trace data for the selected core name.

This property appears only when the selected microcontroller is a multi-core.

This property can be changed only while all cores are stopped.

Caution

This property can be changed only while all cores are stopped.
This property setting takes effect before user program execution is started.

(2)	Select trace data

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

Trace the branch PC	PC values for source/destination instructions of branching during program execution are collected as trace data.
Trace the data access	Data information on access-related events that occurred during program execution are collected as trace data.
Trace the fetch address of the data access	PC values for instructions of access-related events that occurred during program execution are collected as trace data.
Trace local variable access	Data information on access-related events for accesses to local variables that occurred during program execution is 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 fetch address of the DBTAG	Information on DBTAG that were generated during program execution is collected, along with the values of addresses where the DBTAG instructions were executed.
Trace the DBPUSH	Information on DBPUSH that were generated during program execution is collected as trace data.
Trace the fetch address of the DBPUSH	Information on DBPUSH that were generated during program execution is collected, along with the values of addresses where the DBTAG instructions were executed.

Caution

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

(3)	[Trace priority]

Select which item should be given priority when using the trace function from the following drop-down list.

Speed priority	Traces giving priority to the real-time performance (default).
Data priority	Traces after stopping the execution pipeline of the CPU temporarily so that no data is missed.

Caution

The trace memory is cleared when you change the setting of this property.

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

Caution

The trace memory is cleared when you change the setting of this property.

(6)	[Trace range setting]

Select the range of trace data to be collected from the following drop-down list.

Note, however, that this property can be changed only when connected to the debug tool.

Traces section	Collects the execution history as trace data within the section specified with a trace start event and a trace end event (default).
Traces out of range	Collects the execution history as trace data outside the range specified with a trace start event and a trace end event.

Caution

If this property is changed, then all trace start and trace end events currently being set will become invalid.

Remark

When [Traces out of range] is selected, the range of trace data to be collected will be determined by a lower-limit address and an upper-limit address that are specified with a trace start event and a trace end event.

Caution 1.

For an out-of-range trace event, be sure to specify the start and end addresses.

Caution 2.

Only one section is specifiable for an out-of-range trace event.

(7)	[Trace memory size[frames]]

Specify from the drop-down list the size of trace memory (i.e. the number of trace frames) in this property.

The trace frame is a unit of trace data. One trace frame is used for each operation in fetch/write/read (default: [8K]).

Caution

The trace memory is cleared when you change the setting of this property.

(8)	[Enable trace data complement]

Select whether to enable complement display when displaying the collected trace data in the Trace panel.

By enabling complement display, instructions between branch instructions that cannot be traced by hardware can be displayed.

Select [Yes] to enable complement display (default).

This setting will be applied from the next acquisition of trace data.