*
*Home|Chinese|Japanese*About ARM|Forums|Events|News|Employment|Contact Us|Investors*
dotted rule
*ARM - the architecture for the digital worldARM - the architecture for the digital world
search
*
*
***
*MARKETS:PRODUCTS & SOLUTIONS:CONNECTED COMMUNITY:TECHNICAL SUPPORT:DOCUMENTATION*
*
technical support
*Home > Technical Support > FAQs > Development Tool FAQs > How do I produce a trace Association file to describe my CoreSight ...
*
****
*.Technical Support
*
*
*>>Home Page*
*
*.Obtaining Support*
*
*.FAQs*
*
**Development Tool FAQs*
**IP FAQs*
**Embedded Software FAQs*
**Artisan Physical IP FAQs (Login Required)*
*
*.Downloads*
*
*.Documentation*
*
*.Training*
*
*.Where To Buy*
*
*.Keil MCU Tools*
*
*.What's New*
*
*.ARM Newsgroups*
*
*.Active Assist On-site Services*
*
*
*
technical support FAQsask ARM*
*

Technical Support Search
*     (Advanced Search)
  FAQs   Documentation   Downloads   Forums

*

 
downarrowHow do I produce a trace Association file to describe my CoreSight systems to RVD/RVIv3.1?
Applies to: RVD Debug, RVD Trace, RealView Development Suite (RVDS) 3.1, RealView ICE (RVI)

CoreSight systems may contain many trace sources and sinks. To allow RealView Debugger (RVD) to correctly capture ETM trace from a system and associate the trace information with the source that generated it an Association file must be used.

The document Configuring systems using Association files describes:

  • How to write an Association file that describes your CoreSight system
  • How to use Association files in RVD





back to top

*
**
*4 dots*Other ARM Websites
*
shadow *LEGAL STATEMENTshadow