µVISION DEBUGGER: Connect to a running target without hardware reset
Information in this knowledgebase article applies to:
Sometimes I want to connect to an application that is running on my target board to analyze the memory and variables in the current context. But the debugger issues a hardware reset when it starts and the current status of my application is lost.
How can I connect to a running application on my target hardware without a hardware reset?
The µVision Debugger normally resets the target hardware to ensure a consistent startup behavior. Several debugger options influence the startup behavior.
If you disable all of the following options no hardware reset is performed at debugger start:
If all the options shown in the picture below are disabled, the debugger starts without performing a hardware reset.
With these options disabled, the debugger starts, and the target hardware stops at the current location of the program counter. This allows you to analyze the memory and register content.
Because Options For Target - Debug - Load Application at startup is disabled, the debugger does not have any application program and debug information. To load this information into the debugger, use the LOAD debugger command with the option NORESET or INCREMENTAL.
You may automate this LOAD using an Initialization File under Options For Target - Debug. For example, the following debug command loads the program and debug information of the current application, where %L is the linker output file name for the project:
LOAD %L INCREMENTAL
of your data.