Debugging on OpenMote-CC2538 with J-Link (using nemiver)
After trying for several days to get debugging working in Eclipse, I was told that it would be easier to use nemiver. I tried it and worked on the first try without any problems. This post will show the easy steps necessary to debug the code running on the OpenMote hardware.
My setup is the following: a linux pc (running Arch Linux), the SEGGER J-Link EDU, the OpenMote-CC2538 and the OpenBase to connect the mote to the pc. Also an ARM-JTAG-20-10 adaptor was used to connect the J-Link to the JTAG on the OpenBase.
The first thing to do is start the J-Link GDB Server which you can download from the SEGGER website. I am using V4.96f as I faced some problems introduced in V5.02b, but these issues should have already been fixed so the latest version should also work.
The J-Link GDB server will be listening to new GDB connections on port 2331 by default.
In another terminal we can then start the GDB session, but how easy this is depends on whether you are using the OpenMote firmware or not to write your program.
Using the firmware
When your program is written with the OpenMote firmware you just have to execute the nemiver target in the Makefile. So after running “make” to build the program, running “make nemiver” will do everything for you: start the nemiver debugger, flash your program to the OpenMote and break at the beginning of your program.
Without the firmware
First create a file (name it e.g. cc2538_gdb.gdb) with the following contents:
Secondly we setup the GDB connection and upload your program to the J-Link GDB server. The command to run is the ARM GDB, the debugger for the ARM GCC compiler that you used to compile the binary. On Arch Linux this program is called arm-none-eabi-gdb but it may have a different name in other linux distributions (e.g. in Ubuntu the package is called gdb-arm-none-eabi). The parameter to the “--command” option is the file you just created and the “program.elf” is the binary that you should have build.
Finally you can start nemiver and start debugging your program.