Compiling OpenOCD v06 Linux

This guide will compile OpenOCD 0.6.0 for Ubuntu 10.04 with the LibFTDI driver library, for use with the TinCanTools Flyswatter, Flyswatter2, and Flyswatter3. Version 0.6.0 is the version of OpenOCD currently in development. For instructions on compiling with the most recent release code, see Compiling OpenOCD Linux.


OpenOCD 0.6.0 vs the 0.5.0 Release

This guide uses the most recent version of the OpenOCD source currently in development. Unlike the 0.5.0 release the development version includes support for the Flyswatter2 and Flyswatter3, so you won’t need to download or apply a patch before compiling. However, the development code is subject to change at any time. If you encounter problems with this option, try the OpenOCD 0.5.0 instructions in Compiling OpenOCD Linux instead.


Installing Packages

You will need to install several packages to compile and run OpenOCD. Open a terminal window (Applications menu > Accessories > Terminal) and type:

sudo apt-get install libtool autoconf texinfo libusb-dev

If you prefer to compile libusb yourself, you can find the source at


Downloading and Compiling libFTDI

libFTDI is an open source library that enables you to talk to FTDI chips like: FT232BM, FT245BM, FT245R, FT2232C, FT2232D and FT2232H. You will need libFTDI to compile OpenOCD. Download libftdi-0.19.tar.gz from: and extract it to your home directory (/home/USERNAME, replacing USERNAME with your username).

Navigate to home/USERNAME/libftdi-0.19/src, and copy ftdi.h to your /usr/include directory. Then create a symbolic link to ftdi.h in /usr/local/include. In the terminal window:

cd ~/libftdi-0.19/srcsudo cp ftdi.h /usr/includecd /usr/local/includesudo ln -s /usr/include/ftdi.h ftdi.h

Return to your libftdi-0.19 directory and compile.

cd ~/libftdi-0.19./configuremakesudo make install

This will install the necessary library files to /usr/local/lib. Navigate to /usr/lib and create symbolic links to the new files.

cd /usr/libsudo ln -s /usr/local/lib/libftdi.a libftdi.asudo ln -s /usr/local/lib/ libftdi.lasudo ln -s /usr/local/lib/ ln -s /usr/local/lib/ libftdi.sosudo ln -s /usr/local/lib/


Downloading OpenOCD

Git is version control software distributed with Ubuntu. You can use git to download the current development code from the OpenOCD git repository at In the terminal window, navigate to your home directory and make sure you don’t already have a directory there named openocd/. (Downloading with git will create a directory called openocd/ containing the OpenOCD source. If you already have a directory called openocd/ either rename it or navigate to a different directory before you proceed.) Then download OpenOCD with the following command:

cd ~git clone git://

There should now be a folder in your home directory called openocd/.


Compiling OpenOCD

In the terminal window, navigate to the new folder containing the OpenOCD source and compile as follows.

cd ~/openocdsudo ./bootstrapsudo ./configure --enable-maintainer-mode --disable-werror --enable-ft2232_libftdisudo makesudo make install

Navigate to /home/USERNAME/openocd/src to find the openocd binary. You will need superuser privileges (the sudo command) to run OpenOCD.


Preparing to Run OpenOCD

You can run openocd from /home/USERNAME/openocd/src, but you may encounter problems with configuration files. For a more in-depth discussion of these issues, see OpenOCD Config File Paths. This guide recommends that you create a new directory containing OpenOCD and its config files.

Create a new directory in /home/USERNAME called openocd-bin, and copy the openocd binary and the contents of /home/USERNAME/openocd/tcl to the new directory. You can do this from the terminal window with the collowing commands:

cd ~mkdir openocd-bincd ~/openocd/tclcp -r * ~/openocd-bincd ~/openocd/srccp openocd ~/openocd-bin

openocd-bin should now contain the following files and subdirectories:


You can now run OpenOCD from /home/USERNAME/openocd-bin. To get started running OpenOCD, see Running OpenOCD on Linux.

Leave a Reply

Your email address will not be published. Required fields are marked *