...
Create a Debug Configuration using JTAG and GDB
Before starting a Debug configuration we have to make sure that the GDB hardware debug plugin in Eclipse is installed. To install it go to Help - Install New Software
Use the filtering option to find the GDB plugin and select the GDB Hardware Debugging option.
This will require you to restart eclipse.
Before starting a debug configuration GDB server needs to be started. This is a tool provided by Segger and can be started by executing Segger J-link GDB server from the segger application menu.
The following screen will allow you to configure the target chip and the connection features.
After that press OK and the following screen will appear.
Now that GDB is running and we have the GDB server plugin installed in Eclipse we can create a configuration to debug our CC2538 platform.
To do so, create a Debug Configuration as follows (click on the little arrow in the side of the little bug on the menu panel in eclipse):
Make sure to select the Standard GDB Hardware Debugging Launcher (click select if this is not the case)
In the Debugger tab configure the debugger as follow (choose the location of the arm-none-eabi-gdb script)
Configure the startup tab as follows:
The code to put in the box is the following one.
| Code Block |
|---|
target remote localhost:2331
monitor interface jtag
monitor speed 5000
monitor endian little
monitor flash download = 1
monitor flash breakpoints = 1
monitor reset |
Click Apply to save the settings and Debug to start the debugging session.
Debugging
Finally, that everything is configured we can just lunch our debug session. Make sure first that:
- the JTAG is connected to the board
- the Segger GDB Server app is running
If you look at the GDB Server app all Color labels MUST be green.
And that's all folks!!