Trace associations are stored in the debug hardware configuration file (.rvc). However, you can save the associations in a separate file, if you want to provide the associations to other users using a similar development platform.

Trace associations are required to describe the associations between the processors and the trace-related devices in complex CoreSight systems. Examples of such associations are:

Your debug tools use the associations in the debug hardware configuration file to determine the components that must be programmed for tracing a specific source in the system

Associations have direction, and some are bi-directional. You must configure associations correctly to enable your debugger to associate trace output with the source of generated trace.