| |||
| Home > Changes to RealView Debugger > CoreSight support | |||
RealView Debugger provides support for development systems that contain CoreSight components. The following CoreSight components are supported:
CoreSight Debug components:
A Debug Access Port (DAP) for connecting a Debug Interface unit to the target, and comprises a JTAG Debug Port (JTAG-DP) and JTAG Access Port (JTAG-AP).
An Embedded Cross Trigger (ECT) to specify cross triggering between multiple targets, and comprises Cross Trigger Interface (CTI) and Cross Trigger Matrix (CTM).
CoreSight Trace components:
Sources generate trace data, and include the Embedded Trace Macrocell™ (ETM) and AHB Trace Macrocell (HTM).
Sinks are the end points for trace data on the SoC, and include the Embedded Trace Buffer™ (ETB™) and Trace Port Interface Unit (TPIU).
Links provide connection, triggering, and flow of trace data, and include the Trace funnel.
Control and access components configure, access, and control the generation of trace, and include DAP and ECT. They do not generate or process trace data.
In this release, you can collect trace only from one ETM trace source in a multiple trace source system. Trace capture from an HTM is not supported in this release.
CoreSight components, except for the CTM, are visible in the Connect to Target window for connections through a RealView ICE unit. The Configuration grouping shows a basic relationship between the CoreSight components and the runnable targets.
You can connect to a CoreSight component in the same way that you connect to a target processor. However, all execution-related features are disabled and the Code window shows a limited view as follows:
the register view in the Register pane
the memory view in the Memory pane, if appropriate.