gdb via Eclipse and OpenOCD

Why?

I've been bringing up a gcc toolchain for ARM, specifically the STM32. So far the toolchain looks good. I'm able to build binaries with it and downloading and debuging via OpenOCD, a STLINK/V2 low cost debugger and gdb works as expected. Gdb as an interface is fine but I find it helps to take advantage of a modern gui while debugging. Eclipse made it easy to configure the build with the cross compiler toolchain and it has a pretty good debugging interface. Some of the benefits of using an IDE are having multiple windows open to view registers and view several source files at once, searching and easily traversing the call stack. I'm not normally a fan of gui apps but sometimes it does help to have several sets of information visible at once during debugging.

Get the right version of Eclipse

I spent several hours trying to get openocd gdb to work with Eclipse Indigo(?) v3.8.1, the version in Ubuntu/Kubuntu 13.04. I even tried with the Zylin plugin. Nothing seemed to work until I spotted some page that mentioned Eclipse Juno and I guessed that something in the Ubuntu 13.04 version of Eclipse might be causing the problems.

Installing the latest Eclipse release, Juno (4.2?) resolved all of the odd behavior such as Eclipse showing the 'run' and 'terminate' buttons but when clicking on 'run' only the terminate button was active, leaving no way to suspend/break into the current execution of the program. In addition even this behavior was broken, sometimes I had to hit 'run' twice for the target to actually start and 'terminate' wasn't consistently terminating the program.

Install the GDB Hardware Debugging plugin

Configure a Debug target

Run->Debug configurations
Create a new 'GDB Hardware Debugging' entry
Select your application by browsing to it (I'd like to use an eclipse variable to fill this in depending on the active configuration but I'm not sure how to yet.)
Select the 'Debug' panel
Set the appropriate instance of 'GDB' in the 'GDB Command' to point at your cross compiler
Disable 'Use remote target'. I chose this route because I wanted to be able to start openocd in the directory of my choice that contained the correct openocd.cfg file. This also makes it easy to add options such as verbose output.
Select the 'Startup' panel
You'll need to put the same kinds commands into the 'Initialization commands' as you would run from a gdbinit/.gdbinit or manually in order to get gdb to connect to the openocd gdb server. For my specific case these are:

set arm abi AAPCS
target remote localhost:3333
monitor reset halt

GDB+Eclipse in action

Comments

UTM (qemu on OSX) only boots into uefi shell after installing Ubuntu 22.10 (solved!)

I've been meaning to try out running Linux and Windows virtual machines on my x86 MacBook Pro using qemu . I've been using Parallels for several years. Parallels is a nice application and works well but I'm always getting bugged to purchase upgrades. Parallels provides free updates on minor version upgrades only, say 13.0 to 13.1. With so many prompts to purchase upgrades it feels like Parallels could release a bit more minor versions and a bit fewer major versions. Rather than just purchase an upgrade to Parallels I figured I'd try out qemu via the UTM application . UTM wraps qemu with a helpful gui and comes as a packages Mac application. And UTM supports both x86 and M1 systems (as qemu also supports these systems). Creating an Ubuntu VM with UTM didn't go as smoothly as with VirtualBox or Parallels but it was the settings I chose that messed me up. Here are two things I ran into when installing Ubuntu on UTM. #1. Configure the qemu instance to use a 'Display...

Debugging an imprecise bus access fault on a Cortex-M3

This information may apply to other cortex series processors but is written from practical experience with the Cortex-M3. Imprecise bus access faults are ambiguous, as noted by the term "imprecise". Compared to precise bus errors, imprecise errors are much trickier to debug and especially so without a deep understanding of arm processors and assembly language. Imprecise and precise flags are found in the BusFault status register, a byte in the CFSR (Configurable Fault Status Register). BusFault status register bits The definition for imprecise and precise bits is: [2] IMPRECISERR Imprecise data bus error: 0 = no imprecise data bus error 1 = a data bus error has occurred, but the return address in the stack frame is not related to the instruction that caused the error. When the processor sets this bit to 1, it does not write a fault address to the BFAR. This is an asynchronous fault. Therefore, if it is detected when the priority of the current pr...

Graco Swing By Me - Battery to AC wall adapter modification

If you have one of these Graco battery powered swings you are probably familiar with the cost of C batteries! The swing takes four of them and they only last a handful of days. I'm not sure if the newer models support being plugged into the wall but ours didn't. If you are a little familiar with electronics and soldering, here is a rough guide on how you can modify yours to plug in! I wasn't sure how exactly to disassemble the swing side where the batteries were. I was able to open up the clamshell a bit but throughout this mod I was unable to determine how to fully separate the pieces. I suspect that there is some kind of a slip plate on the moving arm portion. The two parts of the plastic are assembled and the moving arm portion with the slip plate is slid onto the shaft. Because of the tension in that slip plate it doesn't want to back away, and because of the mechanicals that portion of the assembly doesn't appear accessible in order to free it. I was...

Chris M.

Search This Blog