Jump to content
Setting up an AI agent? ReverseEngineering.wiki skill (works from the command line, no configuration): https://reverseengineering.wiki/skill/rewiki/SKILL.md · setup for every client, including MCP: https://reverseengineering.wiki/llms.txt · REWiki:Connect

Format:FIT image

From ReverseEngineering.wiki
Format
Magic D0 0D FE ED (flattened device tree)
Extensions .itb, .fit
Endianness big
License GPL-2.0+ (U-Boot)
On this wiki Facts · Code · Notes · Topics

U-Boot's Flattened Image Tree (.itb, .fit): a flattened device tree blob whose /images nodes carry kernel, ramdisk and dtb payloads and whose /configurations nodes choose which to boot; hashes and signatures live inside the tree.

Structure

A FIT image is a Format:Flattened device tree blob (so it starts with D0 0D FE ED). Tree layout:

  • /description, /timestamp
  • /images/<name>: properties description, type (kernel, ramdisk, flat_dt, script, firmware, loadable...), arch, os, compression, load, entry, data (payload bytes inline) and a hash-N subnode (algo such as sha256 or crc32, value).
  • /configurations: default plus conf-N nodes naming kernel, ramdisk, fdt (and loadables), optionally with a signature subnode (algo, value, sign-images).

With mkimage -E (external data) the payloads are placed after the tree and the image nodes carry data-offset and data-size (or data-position) instead of data; offsets are relative to the end of the blob rounded to 4 bytes. Unpack with dtc -I dtb -O dts to read the tree and dumpimage/fdtget to extract payloads. Android and many routers (OpenWrt) ship FIT kernels.

Unlike Format:U-Boot legacy uImage, no fixed header exists and several kernels, device trees and ramdisks coexist. The property names above are the FIT_*_PROP strings of U-Boot include/image.h.

External data, precisely (u-boot boot/image-fit.c at 8d534cec, read): if an image node has data-position, that value is used as the offset directly; otherwise data-offset is added to the FDT total size rounded up to 4 bytes ((fdt_totalsize + 3) & ~3). data-size is the length. So data-offset is relative to the aligned end of the tree, data-position is relative to the start of the FIT blob. See Fact:FIT image/behavior/External data position.

Code & repositories

  • https://github.com/u-boot/u-boot @ 8d534cec0cc0109a37c0ded8854da03f1526dc0e · license: GPL-2.0-or-later (declared by the contributor; GitHub's detector did not recognize COPYING)
    U-Boot include/image.h: legacy header, IH_* codes and FIT property names
    Tested on: source read, not run: source read · checked 2026-10-18; last activity 2026-10-16