User manual

DVP and EMU2 (HDS2) emulator features UM0036
246/385 Doc ID 7705 Rev 11
Figure 179 and Figure 180 show all of the trace columns for each STVD version. You can
preselect which of these columns are displayed (see Show/hide columns).
The trace fields contain the following information:
● Symbol Bar: This column contains icons such as source line markers and/or
bookmarks .
Note: When a source line marker occurs, the fields described hereafter are used to display source
line information such as the name of the source file, the line of source code, and the
instruction call.
● Record: Trace record numbering starts at 1, which corresponds to the earliest cycle to
be recorded, and ends at the latest cycle recorded (for the EMU2 emulator, the
maximum is generally 1024 cycles, for the DVP2 the maximum is 256, and for DVP3
the maximum is 512).
Take, for example, the case of the EMU2 emulator’s trace. If you have an application
that runs for 2048 cycles before there is a break, and the maximum size of the trace
buffer is 1024 cycles, cycles 1024 to 2048 are recorded in the trace buffer, but they will
be numbered 1 to 1024 in the Record column.
● Address: The memory location accessed.
● Data: The hexadecimal value on the data bus
● Hexadecimal: The instruction in hexadecimal format, if this is a Fetch instruction cycle.
● Disassembly: The instruction in assembly language mnemonics, if this is a Fetch
instruction cycle.
● Symbolic: The instruction in assembly language mnemonics with symbolic operands,
if this is a Fetch instruction cycle.
● Memory: The type of memory access (either read/write/fetch or invalid).
● Sig: The value of the EMU2 emulator front panel input signals (Analyser probe).
● S2: The value of the EMU2 emulator S2 input signal (see emulator documentation).
● Event: The name of the Logical Analyser event that has been matched on this cycle
(Event 1, Event 2, Event 3 or blank for none).
● TRIGIN: The value of the TRIGIN signal (input pin located on the DVP).
● Probe: The values of the signals output from the probe pins located on the DVP.
8.4 Using hardware testing
The hardware test function enables you to check that the emulator is still working online and
has not suffered a hardware problem. If problems occur during debugging (such as bad
debugger responses and unexpected behavior), you should check for hardware problems
using the Hardware Test function, and if any are detected, contact your STMicroelectronics
sales representative.
Caution: Be careful when performing a hardware test while an application is open. The opened
application may be corrupted by the hardware testing process. If you find that your
application has been corrupted, simply close the application, and reopen it.
The Hardware Test dialog box is accessible either by clicking on (the Hardware Test
icon) in the Emulator toolbar, or from the main menu by selecting Debug
Instrument>Hardware Test.