Keil Logo

Debug

The Debug section, consisting of three groups, controls caching, downloading, and device resetting options that are applied each time a debugging session is started.

Target Driver Setup - Debug Options

Cache Options improve the µVision Debugger performance by caching target memory areas into the PC memory. By default, these options are enabled to get maximum performance.

  • Cache Code informs the debugger that the downloaded program code will not change. When this option is set, µVision never reads the program code from the target system. Disable this option if you are using self-modifying code, or if you suspect that your program code is being overwritten.
  • Cache Memory determines whether memory displays are updated during a program stop. When this option is set, the debugger does not update memory displays until the next single step, procedure step, or go command. Disable this option, if you want to see the actual memory content (e.g. the data content of memory mapped peripherals) when the debugger is halted.

Download Options control the application downloading process.

  • Verify Code Download compares the content of the target memory with the application program loaded in the debugger for each new debug session. Enable this option to ensure program correlation between the image loaded in target system and the image loaded in the µVision debugger. This prevents debugging the wrong code when working with various targets or more instances of µVision.

  • Download to Flash downloads code to all memory regions. When disabled, the debugger does not download code to the memory address ranges defined in the dialog Programming Algorithm. Enable the option if the application is loaded into RAM and the Flash algorithm is defined for the same address range. By default, this option is disabled. Refer to the knowledgebase article µVision Debugger: Error 57:Illegal Address in Debugger Output Window.

Misc Options

  • Use Reset at Startup when enabled, issues a CPU Reset to the target when the debugger is started. When disabled, the debugger just stops the CPU at the currently executed instruction. This allows you to start a debugging session and debug a program that is currently executing on your target.

    Refer to Start Sequence for more information.

  Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings

Privacy Policy Update

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.