1. What is a DTB?

DTB stands for Device Tree Blob.

In the context of Linux on embedded devices (like routers, IoT devices, or Android phones), the hardware configuration can vary wildly even for the same CPU. To handle this without compiling a unique kernel for every single hardware variant, Linux uses a Device Tree.

• The Source (.dts): A human-readable text file describing the hardware (e.g., "This machine has a Wi-Fi chip on SPI bus 2, address 0x3000").
• The Blob (.dtb): The compiled binary version of that file. This is the "firmware" piece you load onto the device.

What is DTB Firmware? Deconstructing the Acronyms

To understand DTB firmware, we must first break down the two halves of the phrase.

Check for integrity

fdtdump myboard.dtb | head -20

3. Corrupted DTB Storage

Symptom: U-Boot loads the DTB, but the kernel reports "Bad device tree blob" or "Invalid magic number." Cause: The DTB stored in flash or eMMC has become corrupted, or the firmware loaded the wrong size. Fix: Re-flash the DTB. Check the DTB magic number:

hexdump -C my-board.dtb | head -n 1

Valid DTB starts with d0 0d fe ed (little-endian magic).

DTB: Device Tree Blob

The Device Tree is a data structure that describes the hardware components of a computer system. It lists CPUs, memory addresses, interrupt controllers, UARTs, I2C buses, GPIO pins, and peripheral devices. The Device Tree Blob (DTB) is the compiled, binary version of the Device Tree Source (DTS) file. The Linux kernel reads this blob at boot time to understand what hardware it is running on.

DTB firmware, therefore, refers to the practice of storing, loading, and passing the Device Tree Blob to the kernel via the firmware or bootloader. It is not a separate type of firmware; rather, it is a critical data payload that the firmware delivers to the operating system.

Step 1: Obtain the Device Tree Source

The kernel source contains DTS files for thousands of boards. For a custom board, you might write your own my-board.dts.

/dts-v1/;
/ 
    model = "My Custom Board";
    compatible = "my,board";
    memory@0 
        device_type = "memory";
        reg = <0x0 0x80000000 0x0 0x20000000>; /* 512MB at 0x80000000 */
    ;
    chosen 
        bootargs = "console=ttyS0,115200 root=/dev/mmcblk0p2";
        stdout-path = "serial0:115200n8";
    ;
    serial@ff130000 
        compatible = "ns16550a";
        reg = <0x0 0xff130000 0x0 0x1000>;
        interrupts = <0 22 4>;
        clock-frequency = <24000000>;
    ;
;

Common tools & commands

• dtc — compile/ decompile Device Trees
• fdtdump / dtc -I dtb -O dts — inspect DTBs
• mkimage (U-Boot) — wrap DTB for bootloader
• fw_printenv/fw_setenv — for environments where DTB path is set in boot variables