Development Tools

2.9 Select a Core (PE)

This section describes how to select the target core (PE: Processer Element) to be debugged when the selected microcontroller supports multi-core.

CS+ displays information regarding a core (PE) by switching selection between the target cores to be debugged (see "2.9.1 Switching between cores (PEs)"). Multiple panels are not provided to display each PE in a single dedicated panel.

The following shows the behavior of each CS+ function for a microcontroller that supports multi-core.

Note	Selecting an item other than a core (PE) as the target for debugging may cause some facilities to operate in a different way.

(1)	Program execution control

(a)	[Full-spec emulator][E1][E20]

The control method differs 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:

Synchronous execution and synchronous break are available in all PEs in principle.

In step execution, one instruction each is executed in units of instructions.

-	When [Async debug mode] is selected:

Only the PE selected to be debugged is executed and a break is generated.

Caution

Step execution is available only in the currently selected PE.
Step execution in source level units, however, may also proceed on other PEs (PE).

(b)	[Simulator]

Synchronous execution and synchronous break are available in all PEs in principle.

Step execution is performed in synchronization with the operating frequency.

(2)	Event occurrence

All events excluding software break events are set in only the PE selected to be debugged.

However, when setting a software break event in an internal RAM area for which "(Self)" is added to the memory type, it can be set in only an area of the PE that was selected to be debugged.

The Events panel displays a list of events set in all PEs.

Other panels display only events set in the PE selected to be debugged.

(3)	Information of the memory, registers, or variables

(a)	Memory mappings

Memory mappings may differ depending on the currently selected PE.
In this case, switching to another PE displays the corresponding memory mappings in the [Memory] category on the [Debug Tool Settings] tab of the Property panel or the Memory Mapping dialog box.

(b)	Range and values of memory

The same value is displayed or set regardless of which PE is currently selected.
In the Local RAM self area, note that the value in the currently selected PE is acquired and displayed or set.

(c)	Register values (including IOR/PC)

The value in the currently selected PE is acquired and displayed or set.

(d)	Symbols (including watch-expressions/variable names)

The address and value are determined based on the PC value in the currently selected PE (for example, even when a symbol is valid only in a certain PE, its address and value are determined based on the PC value in the currently selected PE).

(e)	Call stack information

The value in the currently selected PE is acquired and displayed or set.

(4)	Other functions

(a)	Collection of execution history of programs

-	[Full-spec emulator][E1][E20] The operation differs depending on the specification of the [Trace target] property in the [trace] category on the [Debug Tool Settings] tab of the Property panel.

-	When [Debug core only] is selected: Trace data regarding the currently selected PE is collected. Therefore, to collect desired trace data, select the target PE before executing the program (if PE is switched after collecting trace data, the display in the Trace panel will not be updated).

-	When [All core] is selected: Trace data is collected in all PEs. After collecting trace data, switching to another PE displays the corresponding trace data in the Trace panel.

-	When core name is selected: Trace data for the selected core name is collected.

-	[Simulator] Trace data regarding the currently selected PE is collected. Therefore, to collect desired trace data, select the target PE before executing the program (if PE is switched after collecting trace data, the display in the Trace panel will not be updated).

(b)	Measurement of execution time of programs

The execution time is measured in all PEs.
After measurement, switching to another PE displays the corresponding measurement time.

(c)	Coverage measurements

The coverage is measured for access in all PEs.
In the Local RAM self area, note that the measurement results will be displayed only for the access in the currently selected PE.

(d)	Performance measurements

The performance is measured in all PEs.
After measurement, switching to another PE displays the corresponding measurement result.