The ARM1176JZF-S Development Chip integrated on the PB1176JZF-S can be configured as a traditional or a CoreSight JTAG system based design. To capture ETM trace on the PB1176JZF-S, the system must be configured as a Coresight system by placing a jumper on J1. Coresight components are accessed by specifying a DAP-AP (Debug Access Port) and an address.

This FAQ explains how to configure RealView Debugger (RVD) and RealView ICE (RVI) for external trace on the PB1176JZF-S using the Trace Port Interface Unit (TPIU).

In this case, an RealView Trace (RVT) unit is required.

The following software must be installed in order to perform trace on the PB1176JZF-S:

• RealView Development Suite (RVDS) v3.1 or later
• RVDS v3.1 Installer Patch
• RVDS v3.1 Patch
• RVI v3.1 or later

To obtain the Installer Patch and the Patch for RVDS v3.1, please visit the ARM technical support web pages:

http://www.arm.com/support/downloads/RVDS_31.html

It is important to do this installation in the following order:

1. RVDS v3.1
2. RVDS v3.1 Installer Patch
3. RVDS v3.1 Patch
4. RVI v3.1 or later

If you have installed RVI v3.2 software, you should update the RVI firmware to version 3.2 using the RVI Update tool.

An Association File to link the devices is needed. A working example association file is available here:

PB1176TraceTPIU_associations.txt

Save this file in a local directory.

The Association File PB1176TraceTPIU_associations.txt contains the following text:

Name=DAP;Type=ARMCS-DP;
Name=ARM1176JZF-JTAG-AP_1;Type=ARM1176JZF-JTAG-AP;ETM=CSETM;
Name=ETB;Type=CSETB;Port0=CSETM;
Name=CSETM;Type=CSETM;Core=ARM1176JZF-JTAG-AP_1;TraceOutput0=TPIU;TraceOutput1=ETB;
Name=TPIU;Type=CSTPIU;Port0=CSETM;

Also available in PDF:

• RVDS 3.1 Downloads
• RealView ICE Downloads
• PB1176TraceTPIU_associations.txt
• How do I configure RVI to debug cores behind a JTAG-AP in CoreSight systems?
• How do I produce a trace Association file to describe my CoreSight systems to RVD/RVIv3.1?