Package U-Boot

U-Boot uses Flat Image Tree (FIT) as a standard file format for packaging images that it it reads and boots. Documentation about FIT is available at doc/uImage.FIT

U-Boot also provides binman for cases not covered by FIT. Examples include initial execution (since FIT itself does not have an executable header) and dealing with device boundaries, such as the read-only/read-write separation in SPI flash.

• Introduction
  • What it does
  • Features
  • Motivation
  • Terminology
  • Relationship to FIT
  • Relationship to mkimage
• Using binman
  • Example use of binman in U-Boot
  • Example use of binman for x86
  • Installing binman
  • Running binman
  • Enabling binman for a board
  • Access to binman entry offsets at run time (symbols)
  • Access to binman entry offsets at run time (fdt)
  • Map files
  • Passing command-line arguments to entries
• Image description format
  • Sections and hierachical images
  • Image Properties
  • Hashing Entries
  • Expanded entries
  • Compression
  • Automatic .dtsi inclusion
• Updating an ELF file
• Entry Documentation
  • Binman Entry Documentation
• Managing images
  • Listing images
  • Extracting files from images
  • Replacing files in an image
  • Logging
• Bintools
• Bintool Documentation
  • Binman bintool Documentation
• Technical details
  • Order of image creation
  • External tools
  • External blobs
  • Code coverage
  • Error messages
  • Concurrent tests
  • Debugging tests
  • Running tests on non-x86 architectures
  • Writing new entries and debugging
  • Building sections in parallel
  • Collecting data for an entry type
  • History / Credits
  • Design notes
  • To do