ULINK2 User's Guide
The Debug section controls caching, downloading, and device
resetting options applied each time a debugging session is
Connect & Reset
control the instructions executed while connecting to target.
Connect controls the connection conditions.
Connect — Normal 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. Use this option when
the user program disables the JTAG/SW interface.
Reset controls the RESET operations.
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. The Cortex-M core and on-chip peripherals are
Reset — VECTRESET performs a software reset by setting
the VECTRESET bit. Only the Cortex-M core is reset. The on-chip
peripherals are not affected. For some Cortex-M devices, VECTRESET
is the only way to reset the core. VECTRESET is not supported on
Cortex-M0 and Cortex-M1 cores.
Reset — Autodetect selects one of the above reset
methods based on the target device. The SYSRESETREQ method is used
if an unknown device is detected.
Reset after Connect performs a reset operation after
connecting to the target. If disabled, the debugger stops the CPU at
the currently executed instruction after connecting to target.
Stop after Bootloader stops the CPU after executing the
improve the performance of the µVision Debugger by caching target
memory areas in 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 the application includes self-modifying code or if the
program code might get 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 is executed. Disable
this option to see the actual memory content (for example, the
content of memory mapped peripherals) when the debugger is
control the downloading of code to the target system when the
Verify Code Download compares the content of the target
memory with the application program loaded in the µVision Debugger.
Enable this option to ensure program correlation between the target
system and µ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 Flash Download Setup.
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
Related Knowledgebase Articles