Skip to main content

Binman firmware packager

Test status PyPI version Documentation status Supported Python versions

Binman packages firmware. Building firmware should be separate from packaging it: build all the pieces you need, using whatever projects and build systems they require, then use binman to stitch everything together into an image. It:

  • reads an image description from a devicetree and works out what to place where, with padding, alignment, compression and hashing;

  • supports hierarchical images and a large set of entry types, including FIT, CBFS, ARM Trusted Firmware FIP and many SoC-specific formats;

  • lets firmware find other binaries in the image, using linker symbols or the devicetree description of the image;

  • inspects existing images, extracting and replacing their contents and repacking where needed;

  • copes with missing binary blobs and fetches the external tools it needs.

Binman is designed primarily for use with U-Boot and associated binaries such as ARM Trusted Firmware, but is general enough to be used with other projects.

Installation

Install the latest release from PyPI:

pip install binary-manager

The pylibfdt dependency is built from source, so this needs swig, a C compiler and the Python development headers (on Debian and Ubuntu: apt install swig build-essential python3-dev).

The binman command is then on your path.

Quick start

Build an image from the description in a devicetree, taking the input files from the current directory:

binman build -d u-boot.dtb

List the contents of an existing image:

binman ls -i image.bin

Binman runs external tools for some entry types. To install any which are missing:

binman tool -f missing

See binman -H for the complete manual, or the documentation linked below.

Documentation

Full documentation is hosted on Read the Docs:

https://binman.readthedocs.io/

Development

Run the test suite from a checkout:

pip install -r requirements.txt
pip install -e .[test]
binman tool -f missing
binman test

The tests build some small x86 ELF programs, so they need make and a gcc which can produce 32-bit x86 code (gcc-multilib), or set CROSS_COMPILE to a suitable cross-compiler. They also need a recent mkimage from U-Boot, since the expected output tracks its development; pass --toolpath to point binman at a U-Boot tools/ build directory. binman test -T checks that the tests cover all of the code.

The u_boot_pylib and dtoc libraries are vendored from the U-Boot tree, so no surrounding U-Boot source is required.

Metadata

Release files for binary-manager 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for binary-manager 0.1.1
File Size Uploaded
binary_manager-0.1.1.tar.gz 400.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for binary-manager 0.1.1
File Interpreter ABI Platform
binary_manager-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 1.0 MB

Release files / binary_manager-0.1.1.tar.gz

Download URL binary_manager-0.1.1.tar.gz
Size 400.8 kB
Tags Source
SHA-256 checksum
How to use checksums
421f2d50c07ba205e3ef03b5ac2ae838e0ebef9de003b0aa3f13419505f80bf5
BLAKE2b-256 checksum
How to use checksums
7c1ea2da18b15bf0ae3904d37b0cf56a2ca9a4fbc53d580d18dfb613c50164cd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 4, 2026.

Transparency log

Release files / binary_manager-0.1.1-py3-none-any.whl

Download URL binary_manager-0.1.1-py3-none-any.whl
Size 623.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b169fa655e0404f471fa504189a1f1b48a5a8d2205614c08c4da2c60571868eb
BLAKE2b-256 checksum
How to use checksums
46c3889a36cf30a4fc62b2b62b45fd12b453eba3d31aabdf23e8a86d1fd494af
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 4, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files

0.1.0

2 release files

0.0.7

2 release files

0.0.6

2 release files

0.0.5

2 release files

0.0.4

2 release files

0.0.3

2 release files

0.0.2

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page