What it is
The Devicetree Specification defines how to describe a board’s hardware as a tree, so boot software and the operating system can discover CPUs, memory, buses, and peripherals from data instead of a single hard-coded board file. Each node names a component and carries properties: a compatible string that identifies the programming model, register addresses, interrupt routing, clocks, and references (phandles) to other nodes. Authors write the tree as source text, compile it into a flat binary blob, and firmware passes that blob through the boot chain.
The format comes from Open Firmware practice on earlier PowerPC and SPARC systems. It is now the usual hardware description for Arm and RISC-V application processors. The specification fixes the data format and the base semantics. Operating systems implement their own driver models on top of that data.
Who it applies to
The document matters on high-performance controllers — cockpit and driver-assistance computers — where an application processor runs a rich operating system. Hardware engineers produce the description of the silicon and the stuffed board. Bootloader engineers carry the blob into the kernel. Driver and hardware-abstraction authors consume nodes to probe devices.
Microcontroller ECUs whose configuration is generated as AUTOSAR basic-software settings follow a different path. Use this specification where the software image must adapt to a board from a hardware description passed at boot.
What it covers
The base specification standardizes shape and encoding. Bindings for individual devices, keyed by compatible, spell out the properties a given part requires and are published alongside the operating system or in separate binding collections.
| Topic | Role in daily work |
|---|---|
| Nodes and properties | Name each CPU, bus, and peripheral and attach its parameters |
Addresses and ranges |
Place a device on its bus and translate those addresses toward the CPU |
| Standard nodes | Describe CPUs, memory, reserved regions, aliases, and chosen boot parameters |
compatible |
Give the driver a stable string to match |
| Binary blob | Give firmware a compact form to hand over without the source text |
A typical source split puts the SoC in a shared include and the board’s population, pin choices, and enabled devices in a board file. Overlays can patch a base tree for a plug-in or a hardware variant when the boot design supports them.
How it fits with other documents
IEEE 1275 is the Open Firmware ancestor of the tree model. The Devicetree Specification stands on its own so an embedded boot chain can pass a flattened blob without a full Open Firmware client interface.
The bootloader and the operating system agree on where the blob lives and which version of the board it describes. Binding documents are the companion specs a driver author implements. The base specification leaves a vendor’s register-level properties to those bindings. ACPI is the hardware-description mechanism typical of PCs, and a platform’s boot design picks one primary description. AUTOSAR Classic ECU configuration remains the configuration path for microcontroller basic software. A POSIX or Adaptive AUTOSAR stack on the application processor still boots on top of the tree the firmware provided.
In practice
Review the tree with the schematic and store it with the board revision. An incorrect address, a swapped interrupt, or a node enabled for an unpopulated part produces a driver that touches the wrong device or never starts. Keep the silicon description stable, and record board straps, stuffed options, and pin routing in the board file. When a respin changes wiring, ship a new blob or a reviewed overlay rather than special cases inside the driver.
Agree on one blob for lab boards, development images, and production images. Driver code should follow compatible, apply a documented default when an optional property is absent, and leave board differences in the tree so the same software build can serve more than one hardware variant.