ARM DS-5 Using the Debug Hardware Configuration Utilities

Configuring CoreSight systems6.7 Format of trace associationsTrace associations consist of a number of distinct elements separated by semi-colons. Thefollowing table lists the elements of an association:Table 6-1 Trace association file element names and descriptionsElement nameNameTypePortnTraceOutputnCoreETMDescriptionA unique name for the component in this list.A type identifier for the specified component. This must match the name of the template for thecomponent.Used only for components that are trace sinks. Indicates that this component can get input from thecomponent specified as connected to it using a Port. When specifying a Port, each Port element tagmust be suffixed with a number starting at 0, for example “Port0=Cortex-R4;Port1=Cortex-A8;”.Used only for components that are trace sources. Indicates that this component can output into thecomponent specified as a TraceOutput. Where more than one TraceOutput must be specified, eachTraceOutput element tag must be suffixed with a number starting at 0, for example“TraceOutput0=ETB;TraceOutput1=TPIU;”.Used to link a component to a processor.Used to link a component to an ETM.6.7.1 Example trace association fileThe following example is an association file for a system containing a Cortex-R4 processor, aCoreSight 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;NoteAlthough the format of an association file takes the form shown in this example, you must usethe Trace Associations... button to create your associations.6.7.2 See alsoConcepts• About trace associations on page 6-6• Setting up a CoreSight trace association file on page 6-11• Defining CoreSight trace associations on page 6-7• CoreSight topology and associations for the CoreSight DK11 on page 6-15• CoreSight topology and associations for the Cortex-R4 FPGA on page 6-17• CoreSight topology and associations for the Cortex-M3 FPGA on page 6-19• CoreSight topology and associations for multiple trace sources on page 6-21.Reference• CoreSight device names and classes on page 5-52• Trace Association Editor dialog box on page 6-9.ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 6-8ID021112Non-Confidential