Devicetree-to-C generator
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:
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.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| dtoc-0.5.2.tar.gz | 76.5 kB | With provenance | Details for dtoc-0.5.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dtoc-0.5.2-py3-none-any.whl | Python 3 | none | any | Details for dtoc-0.5.2-py3-none-any.whl |
Total release size: 166.5 kB
Release files / dtoc-0.5.2.tar.gz
| Download URL | dtoc-0.5.2.tar.gz |
|---|---|
| Size | 76.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0d7ddae1377a3429bee8e0667c1c945011819ec715cf8232eeb14980b9e2784a
|
|
BLAKE2b-256 checksum How to use checksums |
b2dd0f9dad81450ac28bcd358a4ebfa238a9b26e2c0b77cccb3790a4db6c636f
|
| 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 logRelease files / dtoc-0.5.2-py3-none-any.whl
| Download URL | dtoc-0.5.2-py3-none-any.whl |
|---|---|
| Size | 90.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ffbcf45bbf9faa044fabd400379a70794a46251537da4cfc443b293678eca973
|
|
BLAKE2b-256 checksum How to use checksums |
49b1d541043b03b70d35fb0b4fd5d14b80dfa6098719302251d3c6474f52e6e3
|
| 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 logSecurity for dtoc 0.5.2
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.
Attestation for dtoc-0.5.2.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 logA 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.