ARM DS-5 Using the Debug Hardware Configuration Utilities

Configuring CoreSight systems6.5 About trace associationsTrace associations are stored in the debug hardware configuration file (.rvc). However, you cansave the associations in a separate file, if you want to provide the associations to other usersusing a similar development platform.Trace associations are required to describe the associations between the processors and thetrace-related devices in complex CoreSight systems. Examples of such associations are:• processor outputs into an ETM• ETM outputs into an ETB• ETM input from a particular processor• CoreSight ETM outputs into a Trace Port Interface Unit (TPIU)• TPIU input from a particular trace source• ETB input from a particular trace source.Your debug tools use the associations in the debug hardware configuration file to determine thecomponents that must be programmed for tracing a specific source in the systemAssociations have direction, and some are bi-directional. You must configure associationscorrectly to enable your debugger to associate trace output with the source of generated trace.NoteAlthough a trace association might be created for a non-CoreSight system, do not modify it.6.5.1 See alsoConcepts• 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• Format of trace associations on page 6-8.ARM DUI 0498F Copyright © 2010-2012 ARM. All rights reserved. 6-6ID021112Non-Confidential