This section describes the debugging facilities for a virtualization facility when a selected microcontroller incorporates that facility.
When specifying contexts for debugging in CS+, debugging with the focus on specific virtual machines (referred to as guests) is enabled.
Select the contexts for debugging in the Select Contexts on Debug target dialog box. The following describes the behavior of the facilities of CS+ when contexts for debugging are selected. The operation of each facility depends on the core (PE) selected as the target for debugging.
The operation of a program varies with the setting for the [Skip contexts on not debug target] property in the [Hardware-assisted Virtualization] category on the [Debug Tool Settings] tab page of the Property panel
If any break source condition is satisfied and stops the execution of the program, the program is still stopped if the current context has been selected as a target for debugging. If the program was stopped in a context that is not selected as a target for debugging, execution of the program is automatically continued until it makes a transition to a context for debugging and execution only stops after the transition is completed.
If the execution of the program is stopped, the program will be stopped regardless of the context.
Selecting [Yes] enables confirming the operation of the program with the focus only on the contexts for debugging.
For hardware break events, trace events, point trace events, timer measurement events, and performance measurement events, only those generated within the contexts for debugging are detected.
The whole memory and all I/O registers are available for display regardless of the contexts for debugging.
Register values in the context where execution was stopped are displayed.
However, when the program is stopped in a context other than one that is a target for debugging, [?] is displayed except for the following registers.
PC, R3 (SP), R28, and R31 (LP)
Only the history of execution in the contexts for debugging is collected.
The timestamps, however, include the execution times of contexts other than those for debugging.
Information on the context is displayed as part of the trace data in the Trace panel.
The following setting is required to show information on the context.
Select [Yes] for the [Trace the transition information of CPU operation mode] property in the [Trace] category on the [Debug Tool Settings] tab page of the Property panel.
For run-break timer events, times in all contexts are measured regardless of the context for debugging.
For timer measurement events, times in all contexts are measured regardless of the context for debugging when measurement proceeds after an event condition has been satisfied.
Performance is only measured in the contexts for debugging.
All contexts are measured regardless of the context for debugging.