We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
During some integration tests of my embedded system, the firmware is being reset multiple times. (Software reset. The power is always on)I would like to run the firmware in debug mode to collect some coverage data during testing.
Now on every reset, the debugger stops at the main() function.
Is there a way to turn this off? This is very annoying since it makes it impossible to run these automated tests in debug mode.
I'm using the ULINK Pro Cortex Debugger.
The article above describes a way how to connect to a running target device without reset, so that you can verify or do some debugging for a running target.
When you do a reset on purpose in your debug session, of course your device is reset. When the option "Run to main()" is disabled, after a reset your program will stop at the first instruction. If the option "Run to main()" is enabled, your program will stop at main().
Are you expecting after you do a reset, your program will "restart" from the point where you did that reset? It is impossible!
You actually described the problem. With (Run to main()) disabled the program stops at first instruction. With (Run to main()) enabled the program stops at main().I'm looking for an option to don't stop at all after a reset.
disable the option "Stop after Reset" should do as you want
www.keil.com/.../ulink2_ctx_debug.htm