Trace Debug Tools User Guide 1.3.3. The Trace Debug Tools (TDT)

1.3.3. The Trace Debug Tools (TDT)

TDT retrieves compressed trace data from the trace capture hardware and reconstructs a historical view of processor activity using a stored copy of the binary image that was loaded into the target. The Trace window displays a disassembly of code executed with full symbol information, interleaved with data accesses to memory (see Chapter 6 The Trace Window Display).

In addition to displaying the basic trace information, you can either interleave the captured trace with your source code (C, C++, or Assembly language), or you can synchronize a memory, source, or disassembly window to the Trace window cursor. This enables a rapid understanding of the trace data. See Viewing trace output with source code.

TDT provides a configuration wizard to enable you to set up the trigger and filter logic of the ETM in a manner that does not require a detailed understanding of the ETM logic (see Using the wizard). With the wizard, you can:

Use trace filters to restrict the trace stream that is captured and sent to the trace port. This prevents the buffer being filled with uninteresting and unwanted trace information (see Defining rules and Defining resources).
Set a trigger point to instruct the TPA to stop the trace capture process (see Trigger).
Collect trace information before, after, or about the trigger point (see The Configure ETM dialog box and Trigger).
Set up triggers while the target system is running, and examine trace output without halting the process. This is referred to throughout this guide as nonstop debugging.
Note
You can perform traditional stop and start debugging, which halts the processor when a breakpoint or watchpoint is hit, by using Go and Stop from the Execute menu.

Copyright © 2000-2002 ARM Limited. All rights reserved.	ARM DUI 0118C
Non-Confidential
PDF version

1.3.3. The Trace Debug Tools (TDT)

Note