4.6.2. Format of the Association file

An Association file consists of a number of distinct lines, each separated by newline characters. Each line consists of a number of distinct elements separated by semi-colons.

Table 4.3 lists all the elements required (or potentially required) to configure the associations that are required to obtain trace from a system.

Table 4.3. Element names and descriptions

Element nameDescription
NameA unique name for the component in this list.
TypeA type identifier for the specified component. This must match the name of the RVI template for the component.
PortnUsed only for components that are trace sinks. Indicates that this component can get input from the component specified as connected to it using a Port. When specifying a Port, each Port element tag must be suffixed with a number starting at 0, for example “Port0=Cortex-R4;Port1=Cortex-A8;”.
TraceOutputUsed only for components that are trace sources. Indicates that this component can output into the component specified as a TraceOutput. Where more than one TraceOutput must be specified, each TraceOutput element tag must be suffixed with a number starting at 0, for example “TraceOutput0=ETB;TraceOutput1=TPIU;”.
CoreUsed to link a component to a core.
ETMUsed to link a component to an ETM.

Note

Although the format of an Association file takes the form shown in the examples that follow, you must use the Trace Associations... button to create your Associations as described in CoreSight Association files.

Example: CoreSight DK11

Figure 4.30 shows the CoreSight topology diagram for CoreSight DK11.

Figure 4.30. CoreSight system topology diagram - CoreSight DK11


The Association file for this is:

Name=ARMCS-DP;Type=ARMCS-DP;Name=ARM1136JFS-JTAG-AP;Type=ARM1136JFS-JTAG-AP;ETM=ETM11;Name=ETM11;Type=CSETM11;TraceOutput0=ETB;TraceOutput1=TPIU;Core=ARM1136JFS-JTAG-AP;Name=ETB;Type=CSETB;Port0=ETM11;Name=TPIU;Type=CSTPIU;Port0=ETM11;

The Association file’s content is now described.

Name=ARMCS-DP;Type=ARMCS-DP;

This line specifies the first device in the list is the ARM CoreSight Debug port. Any CoreSight components that are connected by the Debug Port associated with this template must follow this device.

Name=ARM1136JFS-JTAG-AP;Type=ARM1136JFS-JTAG-AP;ETM=ETM;

This line specifies that an ARM1136JF-S core is connected to a JTAG-AP on the preceding ARMCS-DP. The ETM=ETM11 section states that the core has an associated ETM called “ETM11”.

Name=ETM11;Type=CSETM11;TraceOutput0=ETB;TraceOutput1=TPIU;Core=ARM1136JFS-JTAG-AP;

This line specifies that an ETM is accessible using the preceding ARMCS-DP.

TraceOutput0=ETB signifies that this ETM can output into the component named “ETB”.

TraceOutput1=TPIU signifies that this ETM can output into the component named “TPIU”.

Core=ARM1136JFS-JTAG-AP signifies that the source for trace captured by this ETM is the ARM1136JFS-JTAG-AP device.

Name=Funnel;Type=CSTFunnel;

This line specifies that a CoreSight Trace Funnel is accessible using the preceding ARMCS-DP.

Name=ETB;Type=CSETB;Port0=ETM11;

This line specifies that a CoreSight ETB is accesible using the preceding ARMCS-DP.

Port0=ETM11; indicates that the source of trace that is stored in this ETB is the component named “ETM11”.

Name=TPIU;Type=CSTPIU;Port0=ETM;

This line specifies that a CoreSight TPIU is accessible using the preceding ARMCS-DP.

Port0=ETM indicates that the source of trace that is stored in this ETB is the component named “ETM11”.

Note

Although the funnel is located between the trace sources and trace sinks, it is not necessary to include it in the Association’s map. The funnel can be used to control the flow of trace through the system dynamically. The purpose of the Association file is to describe a static view of the trace flow through the system.

Copyright © 2002, 2004-2008 ARM Limited. All rights reserved.ARM DUI 0155J
Non-Confidential