OpenOCD - 0.5.0

Upcoming OpenOCD 0.5.0 features RTOS thread awerness for FreeRTOS, eCos or ThreadX. The PandaBoard and OMAP4430 processor are now supported.

I. Building OpenOCD

To compile the latest OpenOCD to use with Bus Blaster dongle:
1. Install MinGW [33]
2. Download and compile libusb-win32
3. Download and compile libftdi
4. Fetch and compile the latest OpenOCD:

$ git clone git://
$ cd openocd/
$ ./bootstrap
$ ./configure --enable-ft2232_libftdi --enable-gw16012 --enable-parport --disable-parport-ppdev
--enable-parport-giveio --enable-presto_libftdi --enable-amtjtagaccel --enable-arm-jtag-ew --enable-jlink --enable-rlink --enable-usbprog --enable-vsllink --enable-usb_blaster_libftdi --enable-maintainer-mode CC="gcc -mno-cygwin"
$ make

II. eCos + STM32 + Eclipse

To try the new thread awerness feature, add -rtos auto to the OpenOCD target configuration, for example, a modify stm32.cfg would include the following entry:

target create $_TARGETNAME cortex_m3 -endian $_ENDIAN -chain-position $_TARGETNAME -rtos auto

Example of an eCos target running 3 threads. When stopping the target in Eclipse, user can access backtrace of every threads in the application and have access to every context.

III. Pandaboard

To connect the Bus Blaster V1 dongle to a Pandaboard, an adapter is required to re-map the JTAG signals correctly. An example is available in the PCB section. According to the OMAP processor mounted on the Pandaboard, it might be required to update the TAPID from the target/omap4430.cfg. TAPID 0x4b95c02f is required for OMAP4430 ES2.2. More information on the JTAG interface are available here.