Debug

The Debug section controls caching, download, and device reset options applied each time a debug session starts.

The Connect & Reset Options controls how the µVision debugger establishes a connection to the target device.

The Connect selection controls what happens when the µVision debugger connects to the target device.

• Connect — Normal just stops the CPU at the currently executed instruction after connecting.
• Connect — with Pre-reset applies a hardware reset(HW RESET) before connecting to the device.
• Connect — under Reset holds the hardware reset(HW RESET) signal active while connecting to the device. You may use this option when the user program mistakenly disables the JTAG/SW interface.

The Reset selection controls how the target device performs a reset operation.

• Reset — HW RESET performs a hardware reset by asserting the hardware reset (HW RESET) signal.
• Reset — SYSRESETREQ performs a software reset by setting the SYSRESETREQ bit. Both the Cortex-M core and the on-chip peripherals are reset.
• Reset — VECTRESET performs a software reset by setting the VECTRESET bit. Only the Cortex-M core is reset. The on-chip peripherals are not reset. For some Cortex-M devices, VECTRESET is the only way they may be reset.
• Reset — Autodetect selects one of the reset methods based on the target device. If Autodetect detects an unknown device, it uses the SYSRESETREQ method.

The Reset after Connect option, if enabled, tells the µVision debugger to perform a reset operation after connecting to the target. If disabled, the debugger just stops the CPU at the currently executed instruction after connecting.

The Cache Options improve the performance of the µVision Debugger during target debugging by caching target memory areas in the PC memory. By default, caching 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 executes. 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.

The Download Options control the downloading of code to the target system when the debugger starts.

• Verify Code Download compares the content of the target memory with the application program loaded in the Debugger.
• Download to Flash downloads code to all memory regions. When disabled, the debugger does not download code to the Memory Address Ranges defined under Flash Download Setup.