Skip to main content

Devicetree-to-C generator

Test status PyPI version Documentation status Supported Python versions

Dtoc converts a devicetree binary (.dtb) into C code, so that a program can use the devicetree’s data without parsing it at run time. U-Boot uses it to give SPL and TPL their devicetree data when they are too small to include libfdt, with the OF_PLATDATA options. It:

  • generates a C struct for each devicetree compatible string, holding the node’s properties with suitable C types;

  • generates the platform data for each node, along with a U_BOOT_DRVINFO() record which binds it to its driver;

  • scans the U-Boot source tree for drivers, so that each node is matched to its driver, including driver aliases and parent drivers;

  • can instead instantiate the devices and uclasses at build time, so that U-Boot does not need to bind them at run time (OF_PLATDATA_INST).

It also provides Python libraries for reading and changing devicetrees (dtoc.fdt and dtoc.fdt_util), which binman uses too.

Installation

Install the latest release from PyPI:

pip install dtoc

The dtoc command is then on your path. It needs the devicetree compiler (dtc) to compile devicetree source files.

Quick start

Generate the C files for an SPL devicetree, scanning a U-Boot tree for drivers:

dtoc -d u-boot-spl.dtb -p spl --source-dir ~/u-boot \
    -c out -C out/include all

U-Boot’s build runs dtoc like this for each phase which uses OF_PLATDATA. See the documentation linked below for the files it writes and the other options.

Documentation

Full documentation is hosted on Read the Docs:

https://dtoc.readthedocs.io/

How U-Boot uses the generated code is described in its documentation, under Compiled-in Device Tree / Platform Data.

Development

Run the test suite from a checkout:

pip install -r requirements.txt
pip install -e .[test]
dtoc -t

Most tests generate code for U-Boot’s sandbox drivers. Set UBOOT_SRC to a U-Boot source tree to include them; otherwise they are skipped. dtoc -T checks that the tests cover all of the code.

Metadata

Release files for dtoc 0.5.4

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

Source distribution (sdist)

Source distribution for dtoc 0.5.4
File Size Uploaded Provenance Actions
dtoc-0.5.4.tar.gz 77.5 kB With provenance Details for dtoc-0.5.4.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for dtoc 0.5.4
File Interpreter ABI Platform Actions
dtoc-0.5.4-py3-none-any.whl Python 3 none any Details for dtoc-0.5.4-py3-none-any.whl

Total release size: 168.7 kB

Release files / dtoc-0.5.4.tar.gz

Download URL dtoc-0.5.4.tar.gz
Size 77.5 kB
Tags Source
SHA-256 checksum
How to use checksums
8e9585fa4e766bc9f0e4af72475a67269a4abcf1b70f835aaa5eec4408856895
BLAKE2b-256 checksum
How to use checksums
6887a9ac2c03be4718e733cd4b1623f76f8fdb79a9afcc572a957cd80a0d398d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 13, 2026.

Transparency log

Release files / dtoc-0.5.4-py3-none-any.whl

Download URL dtoc-0.5.4-py3-none-any.whl
Size 91.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4c74fdf55b71161cde343e5572b222674dbd19e316f22c4ec7c15c69548b5c78
BLAKE2b-256 checksum
How to use checksums
6f4f183f237d8f428e32a0e55918ba3ed0a5446ff49789dfc572f12d0e5936ce
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 13, 2026.

Transparency log

Security for dtoc 0.5.4

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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for dtoc-0.5.4.tar.gz

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 Nov 13, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

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