Debugging the Startup Code With Eclipse and GDB
Debugging the Startup Code With Eclipse and GDB
Learn more about debugging embedded applications.
Join the DZone community and get the full member experience.
Join For FreeBy default, when debugging an embedded application, the target usually stops at main():
That's usually fine, but what if I want to debug the code out of reset?
I'm using the Eclipse-based NXP MCUXpresso IDE 10.3 in this article, but same or similar things apply to most modern gdb + Eclipse-based IDEs.
Why does the application stop at main? This is because the debugger has set a temporary breakpoint on the main symbol (or function):
Temporary Breakpoint
This is confirmed by the Log in the Debugger Console view:
Temporary Breakpoint in Debugger Console
So what happens is:
- Debugger downloads the binary
- Debugger sets a temporary breakpoint at main
- Debugger issues a reset to the target followed by a 'run'
- The target will stop at the temporary breakpoint
Obviously, a simple way to debug the startup code is to set a breakpoint in the startup code itself:
Breakpoint on ResetISR
Another way is to inspect and change the debugger launch configuration. Because this might be different for each debug configuration, I'll show it for LinkServer, Segger, and PEMicro.
LinkServer
The LinkServer (CMSIS-DAP, LPC-Link2) connection does not have a dedicated 'run' setting. To debug the startup code, I have to change the 'main' to the 'ResetISR' Symbol. To revert back, change the symbol back to 'main'.
Stop on Startup at
Segger
With the GNU Mcu Eclipse plugins, the settings are as shown below and easy to change:
GnuMcuEclipseSegger
To do startup code debugging, disable the 'Continue' option.
P&E (PEMicro)
The screenshot below shows the setting for P&E to set the temporary breakpoint and the 'run on reset' setting, which is easy to find and change:
PEMicro Launch Config
To start debugging from the reset vector, simply disable the 'Run on reset' option.
Summary
In order to debug the startup code with Eclipse and GDB, I could set a breakpoint in the reset routine, or better, I can change the setting in the Eclipse CDT launch configuration to halt in the ResetISR (or whatever the reset function name is).
Happy Startuping!
Additional Links
- MCUXpresso IDE: http://www.nxp.com/mcuxpresso/ide
- GNU MCU Eclipse plugins: https://gnu-mcu-eclipse.github.io/
Like This Article? Read More From DZone
Published at DZone with permission of Erich Styger , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}