This is second part of ongoing tutorial on setting up GCC + Eclipse + OpenOCD environment for use with the SAME54 Xplained pro board on latest Ubuntu system. In order to be able to follow this blog entry you must already have the gcc-arm toolchain and openOCD configured When we talk about debugging it is important to know that the actual "debugger" or emulation hardware is "on chip" and is called the "on chip debug" (OCD) hardware. While there are other methods to debug your embedded code using DDD, Kgdb, & Gdb on Ubuntu in this post will see debugging using Eclipse. Prerequisite - Download and install the latest version of Eclipse (open-source integrated development environment). Compile and install openOCD
Tag: openocd
ARM Cortex-M4 HOWTO Debug Under Ubuntu
With SAME54 board and using OpenOCD will debug the LED Flasher example. This post assumes that basic setup is ready using GNU-ARM Embedded Tool chain and OpenOCD. Basic gdb with OpenOCD To Begin with connect the SAME54 explained pro board and start the OpenOCD server using telnet telnet localhost 444>reset halt Then it is time for gdb to use GDB via openocd there are couple of options like, gdb, ddd, insight and kdgb. Will start with gbd $arm-none-eabi-gdb --eval-command="target remote localhost:3333" AtmelStart.elf This will start gdb with remote debugging and you can see following message Type "apropos word" to search for commands related to "word"… Reading symbols from AtmelStart.elf… Remote debugging using localhost:3333 main () at ../led_switcher_main.c:55 55