Before you can capture trace from a CoreSight Embedded Trace Buffer (CoreSight ETB), you must set up RealView Debugger and the DSTREAM or RealView ICE debug interface unit.
The difference between configuring trace capture from a CoreSight
ETB for use with DSTREAM or RealView ICE is the Debug Interface
that you use. The following procedure uses the RealView
ICE Debug Interface as an example.
To capture trace from a CoreSight ETB:
Connect the debug interface unit.
Install the RealView ICE host software.
Note
The RealView ICE host software is included with RVDS, and does not require a separate installation.
Select Start → Programs → ARM → RealView Development Suite v4.1 → RealView Debugger v4.1 to start RealView Debugger.
Configure RealView ICE to identify the processors and CoreSight components on your development platform. You must also configure RealView ICE to access the CoreSight ETB.
Select Registers from the View menu to display the Registers view.
If your development platform has multiple trace sources, then you must configure the CoreSight Trace Funnel to identify the source from which trace is to be captured:
Connect to the
CSTFunnel_target.nSet up the Trace Funnel registers.
Note
If your development platform contains multiple processors and multiple ETMs, only one CoreSight ETM at a time can be chosen as the trace source in this release.
Configure the CoreSight ETB registers:
Connect to the
CSETB_target.nSet up the CSETB registers. Figure B.5 shows an example:
Connect to the target processor on your development platform.
Connect to the TPA.
See also:
RealView ICE and RealView Trace Setting Up the Hardware
RealView ICE Using the Debug Hardware Configuration Utilities
Configuring DSTREAM or RealView ICE to access the CoreSight ETB
the following in the RealView Debugger User Guide:
Creating a Debug Configuration on page 3-10
Connecting to a target on page 3-19.
PDF version