Version 0.11.0-1 is a new major release; it updates to the latest upstream major release.

The xPack OpenOCD is the xPack distribution of OpenOCD.

There are separate binaries for Windows (Intel 32/64-bit), macOS (Intel 64-bit) and GNU/Linux (Intel 32/64-bit, Arm 32/64-bit).


The binary files are available from GitHub releases.


The full details of installing the xPack OpenOCD on various platforms are presented in the separate Install page.

Easy install

The easiest way to install OpenOCD is with xpm by using the binary xPack, available as @xpack-dev-tools/openocd from the registry.

To install the latest version available, use:

xpm install --global @xpack-dev-tools/openocd@latest --verbose

To install this specific version, use:

xpm install --global @xpack-dev-tools/openocd@0.11.0-1.1


The xPack OpenOCD generally follows the official OpenOCD releases.

The current version is based on:

  • OpenOCD version 0.11.0, the development commit f342aac08 from March 7, 2021.


There are no functional changes.

Compared to the upstream, the following changes were applied:

  • a configure option was added to configure branding (--enable-branding)
  • the src/openocd.c file was edited to display the branding string
  • the contrib/60-openocd.rules file was simplified to avoid protection related issues.

Bug fixes

  • none


  • none

Known problems

  • none

Shared libraries

On all platforms the packages are standalone, and expect only the standard runtime to be present on the host.

All dependencies that are build as shared libraries are copied locally in the same folder as the executable.


On GNU/Linux the binaries are adjusted to use a relative path:

$ readelf -d | grep runpath
 0x000000000000001d (RPATH)            Library rpath: [$ORIGIN]

In the GNU search strategy, the DT_RPATH has the highest priority, higher than LD_LIBRARY_PATH, so if this later one is set in the environment, it should not interfere with the xPack binaries.

Please note that previous versions, up to mid-2020, used DT_RUNPATH, which has a priority lower than LD_LIBRARY_PATH, and does not tolerate setting it in the environment.


Similarly, on macOS, the binaries are adjusted with otool to use a relative path.


The original documentation is available in the share/doc folder.

Supported platforms

Binaries for Windows, macOS and Intel/Arm GNU/Linux are provided.

The binaries were built using the xPack Build Box (XBB), a set of build environments based on slightly older distributions, that should be compatible with most recent systems.

  • Intel GNU/Linux: all binaries were built with GCC 9.3, running in an Ubuntu 12 Docker container
  • Arm GNU/Linux: all binaries were built with GCC 9.3, running in an Ubuntu 16 Docker container (added in mid-2020)
  • Windows: all binaries were built with mingw-w64 GCC 9.3, running in an Ubuntu 12 Docker container
  • macOS: all binaries were built with GCC 9.3, running in a separate folder on macOS 10.10.5.


The scripts used to build this distribution are in:

  • distro-info/scripts

For the prerequisites and more details on the build procedure, please see the README-MAINTAINER page.

Travis tests

The first set of tests were performed on Travis, by running a simple script to check if the binaries start on a wide range of platforms and distributions:


The binaries were testes on Windows 10 Pro 32/64-bit, Intel Ubuntu 18 LTS 64-bit, Intel Xubuntu 18 LTS 32-bit and macOS 10.15.

Install the package with xpm.

The simple test, consists in starting the binaries only to identify the STM32F4DISCOVERY board.

.../xpack-openocd-0.11.0-1/bin/openocd -f board/stm32f4discovery.cfg

A more complex test consist in programming and debugging a simple blinky application on the STM32F4DISCOVERY board. The binaries were those generated by simple Eclipse projects available in the xPack GNU Arm Embedded GCC project.


The SHA-256 hashes for the files are:








Download analytics

Credit to Shields IO for the badges and to Somsubhra/github-release-stats for the individual file counters.