*
*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 > What are the restrictions on the type of image I can profile with ...
*
****
*.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

*

 
downarrowWhat are the restrictions on the type of image I can profile with RealView Profiler?
Applies to: Profiling, RealView Development Suite (RVDS) 3.1 Professional, RealView Profiler (RVP) 1.0

RVP does not currently support systems which use remapping (for example, with an MMU). The profiler is primarily targeted at single threaded applications, although this may change in the future.

The profiler does not support images generated with ADS. Supported build tools are RVCT 2.2 and later and GCC 3.4 and later.

Profiling images without debug information is supported, but in this case the profiler will not be able to relate the instruction stream to the source code. Profiling without symbolic information (a plain binary file) is not supported.






back to top

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