  | |||
  |  | ||
| |||
| Home > Introduction > About the Program Trace Macrocell > The debug environment | |||
| |||
| | ||
| |||
| Home > Introduction > About the Program Trace Macrocell > The debug environment | |||
A software debugger provides the user interface to the PTM. The debugger can configure all the PTM facilities, typically using a JTAG or Serial Wire interface. The debugger also displays the captured trace information.
The PTM compresses the trace information and exports it to a CoreSight trace capture subsystem. The CoreSight trace capture subsystem either:
Exports the trace through a trace port. An external Trace Port Analyzer (TPA) captures the trace information, as shown in Figure 1.1.
Writes the trace directly to an on-chip Embedded Trace Buffer (ETB). When the trace capture is complete, the trace is read out at low speed, typically using a JTAG or Serial Wire interface.
When the trace has been captured the debugger extracts the information from the TPA or ETB and decompresses it to provide a full disassembly, with symbols, of the code that was executed. The debugger can also link this back to the original high-level source code, showing you how the code executed on the target system.
A system that includes an ETB in the CoreSight capture system might not include a trace port and separate TPA. Such a system must download the captured trace data through the Debug Access Port (DAP).
| Copyright © 1999-2002, 2004-2008 ARM Limited. All rights reserved. | ARM IHI 0035A |
 PDF version | |
| Home > Introduction > About the Program Trace Macrocell > The debug environment | |
| |