What is a .DTB file?
DTB describes a device’s hardware layout for the Linux kernel to read at boot.
- Did you know
- Device trees let one Linux kernel boot on many different ARM boards.
- The device-tree idea came from the Open Firmware used on PowerPC and SPARC machines before spreading to ARM Linux.
- A DTB is compiled from a human-readable .dts source file by the device-tree compiler, dtc.
- What Analyser reads
- Inspect virtual-machine descriptors (VMware .vmx, VirtualBox .vbox, OVF/OVA), disc images (Nero .nrg, Alcohol .mds/.mdf, CloneCD), embedded firmware (Intel HEX, Motorola S-record, UF2, ELF/AXF, Device Tree Blobs, U-Boot uImage), partition tables (MBR/GPT with GUIDs), Linux filesystem superblocks (ext2/3/4, SquashFS, cramfs, romfs) and Windows imaging (WIM/ESD) - reading headers directly, no upload. The two generic suffixes are handled on their bytes rather than their name: a .bin opens in the raw-binary inspector (magic-byte guess, entropy profile, hex and ASCII dump) and names itself when the signature proves a raw BIN/CUE disc image or a Mega Drive cartridge dump, while a .out is read as either the ELF executable a compiler left behind or the plain-text log a batch job dumped. Either one is re-routed automatically when its bytes turn out to be a real format.
- Depth of analysis
- .DTB is an identification-grade format: Analyser recognises it from its bytes and decodes the header metadata it carries, rather than opening it in a full viewer. Formats that do get a full viewer are marked "Full" on the formats page.
- Open a .DTB file
- Drag a .DTB file onto the Analyser home page (or tap to pick one). It is identified entirely in your browser - nothing is uploaded, there is no account, and it works offline once installed.