xPack OpenOCD v0.11.0-1 released
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).
Download
The binary files are available from GitHub Releases.
Install
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 npmjs.com
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
Compliance
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.
Changes
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
Enhancements
- 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.
DT_RPATH
and LD_LIBRARY_PATH
On GNU/Linux the binaries are adjusted to use a relative path:
$ readelf -d library.so | grep runpath
0x000000000000001d (RPATH) Library rpath: [$ORIGIN]
In the GNU ld.so 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.
@executable_path
Similarly, on macOS, the binaries are adjusted with otool
to use a
relative path.
Documentation
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.
- x86/x64 GNU/Linux: all binaries were built with GCC 9.3, running in an Ubuntu 12 Docker container
- arm64/arm GNU/Linux: all binaries were built with GCC 9.3, running in an Ubuntu 16 Docker container (added in mid-2020)
- x86/x64 Windows: all binaries were built with mingw-w64 GCC 9.3, running in an Ubuntu 12 Docker container
- x64 macOS: all binaries were built with GCC 9.3, running in a separate folder on macOS 10.10.5.
Build
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:
Tests
The binaries were testes on Windows 11 Pro, Intel Ubuntu 22 LTS and macOS 14.5.
Install the package with xpm.
The simple test, consists in starting the binaries only to identify the STM32F4DISCOVERY board.
~/Library/xPacks/@xpack-dev-tools/openocd/0.11.0-1.1/.content/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 the simple Eclipse projects available in the xPack GNU Arm Embedded GCC project.
Checksums
The SHA-256 hashes for the files are:
3e3719fd059d87f3433f1f6d8e37b8582e87ae6a168287eb32a85dbc0f2e1708
xpack-openocd-0.11.0-1-darwin-x64.tar.gz
6ffe37f305e117e21ca2b7a82b10ed06758968472aa39a2573911ae74a67da3e
xpack-openocd-0.11.0-1-linux-arm64.tar.gz
24c5de0839b8c5cb3476d6fb7b9f528daba14b434a00d60ef71d4e4da3131262
xpack-openocd-0.11.0-1-linux-arm.tar.gz
fb38cc36c31eccbfcb824684596fb16dde91f9c9a42a954d9c26e678cc1a5fc1
xpack-openocd-0.11.0-1-linux-ia32.tar.gz
5972fe70a274f054503dd519b68d3909b83f017b5b8dd2b59e84b3b72c9bc3e1
xpack-openocd-0.11.0-1-linux-x64.tar.gz
b556754ee621962d41f89b229115ecf5e067b6ae76e91e210d7f53d657769296
xpack-openocd-0.11.0-1-win32-ia32.zip
ec37f535265ce93953a874b10d07e8578f9814c206d8bce6a241ba7016297e4f
xpack-openocd-0.11.0-1-win32-x64.zip
Download analytics
- GitHub xpack-dev-tools/openocd-xpack
- this release
- all xPack releases
- all GNU MCU Eclipse releases
- individual file counters (grouped per release)
- npmjs.com @xpack-dev-tools/openocd
Credit to Shields IO for the badges and to Somsubhra/github-release-stats for the individual file counters.