*
*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
*
*
****
*.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

*

 
downarrowDo I need any RAM on my target to connect with a debugger? What is the “cache clean code address”? What are the “code sequence address and size”?
Applies to: AXD Debug, JTAG Debug Issues, Multi-ICE, RVD Debug, RealView ICE (RVI)

In every system there should be some RAM, since it is needed to store variables and the stack and heap. However, in some systems only Flash or ROM is mapped in memory at power-up and RAM needs to be enabled by software in the boot code.

With certain targets, in order to perform certain operations, Multi-ICE and RealView ICE need to download a piece of code into memory and make the core execute it. This code must be located in a writable area of memory (RAM) and needs to be accessed only by the JTAG tool.

  • In Multi-ICE, this piece of code is called "cache clean code" and its address is configured in the "Processor Settings" tab of the Multi-ICE connection window.
     
  • In RealView ICE, you can select the address and size of this code in the "Device" window of RVConfig, under the entries "Code Sequence Address" and "Code Sequence Size".

When you connect with a debugger to one of these targets you should ensure that RAM is mapped in memory and that the "cache clean code" or "code sequence" address is mapped correctly. You can run a script from the command line to configure the target's memory map straight after connecting to the target.

For more information please refer to the Multi-ICE and RealView ICE user guides.






back to top

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