Trace associations consist of a number of distinct elements separated by semi-colons. The following table lists the elements of an association:
Table 4. Trace association file element names and descriptions
| Element name | Description |
|---|---|
Name | A unique name for the component in this list. |
Type | A type identifier for the specified component. This must match the name of the template for the component. |
Port | Used 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;”. |
TraceOutput | Used 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;”. |
Core | Used to link a component to a processor. |
ETM | Used to link a component to an ETM. |
Example trace association fileThe following example is an association file for a system containing a Cortex-R4 processor, a CoreSight TPIU, a CoreSight ETM, a CoreSight ETB, and a CoreSight DAP:
Name=ARMCS-DP;Type=ARMCS-DP;Name=Cortex-R4;Type=Cortex-R4;ETM=ETMR4;Name=ETMR4;Type=CSETM;TraceOutput0=TPIU;TraceOutput1=ETB;Core=Cortex-R4;Name=ETB;Type=CSETB;Port0=ETMR4;Name=TPIU;Type=CSTPIU;Port0=ETMR4;
Note
Although the format of an association file takes the form shown in this example, you must use the Trace Associations... button to create your associations.
- Concepts
- Reference
PDF version