User manual

Basic debugging features UM0036
198/385 Doc ID 7705 Rev 11
Peripheral registers display options
Using the display options in the contextual menu, you can customize the display format of
information shown in the Peripheral Registers window:
● Display Item: You can choose to display the value of the selected Peripheral Register
item in either hexadecimal, unsigned integer or binary format.
● Display All: You can choose to display all values of all Peripheral Register items in
either hexadecimal, unsigned integer or binary format.
● Display Address: You can choose to display the address of the peripheral or of each
individual register within the peripheral, or both for all items in the Peripheral Registers
window.
Forced read of status registers
Values of status register items in the Peripheral Registers window are not normally
available—beside each item, you will see the message "Intrusive read" indicating that
reading the value of these registers could intrude upon the normal running of the program,
and give rise to unpredictable results.
However, if you absolutely must know the value of a particular status register item, select the
item with the mouse and right-click to bring up the contextual menu, as shown above. You
will then have access to an additional option -- the Forced Read option. Choosing this
option will allow an intrusive read of the status register. A dialog box will appear as shown in
Figure 148, warning you of the possibility of unpredictable consequences, and giving the
value of the status register.
Figure 148. Forced read warning
Note: The value of the status register is only valid at the moment of the forced read.
5.17 Memory trace window
The Trace window allows you to view recorded hardware cycles that have occurred during
the execution of your application. In addition, different trace recording modes allow you to
control what information is viewed and when.
You can open the Trace window either by clicking on (the Trace window icon) in the View
toolbar, or from the main menu by selecting View>Trace.
The memory trace is implemented differently for the debug instruments that support this
feature. For more information on the trace capabilities, refer to the section specific to your
debug instrument:
● Section 8.3: Trace recording on page 242 for DVP/EMU2
● Section 10.1: Trace recording on page 284 for EMU3
● Section 9.1: Trace recording on page 258 for STice