ULINK2 User's GuideIntroduction Hardware Description Setup ULINK2 Connecting ULINK2 Installing Drivers Configure µVision for Debugging ARM Devices Debug Driver Configuration ULINK USB-JTAG Adapter JTAG Device Chain Debug Cortex-M Debugging Debug Driver Configuration ULINK USB-JTAG/SW Adapter SW Device JTAG Device Chain Debug Known Limitations Trace Configuration Trace Port Timestamps PC Sampling Trace Events ITM Stimulus Ports Pack Options Setup Flash Programming Flash Download Configuration Download Function RAM for Algorithm Programming Algorithm Creating New Algorithms Supplied Algorithms Analog Devices AMD Atmel Intel Luminary Micro Macronix NXP (founded by Philips) OKI SST STMicroelectronics Toshiba TI Using ULINK2 Configure Cortex-M Devices for Tracing µVision Windows Troubleshooting Guide Appendix
Connect & Reset Options
Connect & Reset Options control the instructions executed while connecting to target.
Connect - controls the operations that are executed when the µVision debugger connects to the target device. The drop-down has the following options:
Reset after Connect (if enabled) performs a reset operation as defined in the Reset drop-down list (see below) after connecting to the target. When disabled, the debugger just stops the CPU at the currently executed instruction after connecting the target. Refer also to Start Sequence for details.
Reset controls the reset operations performed by the target device. The available options vary with the selected device and supported debug description that can be enabled in Pack Options.
Stop after Reset permanently enables the Cortex-M Reset Vector Catch. This stops the CPU when running through the reset vector (e.g. because of pressing the reset button on the board, issuing a reset from uVision while the target is running; reset caused by a watchdog timer).
Stop after Bootloader stops the CPU after executing the bootloader instructions and is available only for some devices.
Log Debug Accesses writes target debug accesses and information about debug components detected in the device ROM table into a text file. The following accesses are logged:
The text file ULINK2_DebugLog_xxxx.log is created in the current project folder, where xxxx is a sequential number. The file limit is 100MB. If this limit is reached during a single debug session, then a new file is created.
Cache Options improve the µVision debugger performance during target debugging by caching target memory areas into 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 when the application includes self-modifying code or 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 execution of the next single step, procedure step, or go command. Disable this option to display the actual memory content (for example, the content of memory mapped peripherals) when the debugger is halted.
Download Options control the downloading of code to the target system when starting a debugging session.
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 Range defined in the dialog Programming Algorithms. 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.
of your data.