UBootImages < DULG

%SECTION0{name=UBootImages}% U-Boot Image Formats

U-Boot operates on "image" files which can be basically anything,
preceeded by a special header; see the definitions in
_include/image.h_ for details; basically, the header defines the
following image properties:

   * Target Operating System (Provisions for <nop>OpenBSD, <nop>NetBSD, <nop>FreeBSD,
     4.4BSD, Linux, SVR4, Esix, Solaris, Irix, SCO, Dell, NCR,
     <nop>LynxOS, pSOS, QNX, RTEMS, <nop>U-Boot, ARTOS, Unity OS, Integrity;
     Currently supported: Linux, <nop>NetBSD, <nop>VxWorks,
     QNX, RTEMS, ARTOS, Unity OS, Integrity).

   * Target CPU Architecture (Provisions for Alpha,
     ARM, AVR32, <nop>BlackFin,
     IA64,
     M68K, Microblaze, MIPS, MIPS64, NIOS, NIOS2, [[PowerPC][Power Architecture]]®,
     IBM S390,
     <nop>SuperH, Sparc, Sparc 64 Bit, Intel x86;
     Currently supported:
     ARM, AVR32, <nop>BlackFin,
     M68K, Microblaze, MIPS, MIPS64, NIOS, NIOS2, [[PowerPC][Power Architecture]]®,
     <nop>SuperH, Sparc, Sparc 64 Bit, Intel x86).

   * Compression Type (Provisions for uncompressed, gzip, bzip2, lzo; Currently
     supported: uncompressed, gzip, bzip2, lzo).

   * Load Address

   * Entry Point

   * Image Name

   * Image Timestamp
The header is marked by a special Magic Number, and both the header
and the data portions of the image are secured against corruption by
CRC32 checksums.
5.12. U-Boot Standalone Applications		1. Abstract		5.14. U-Boot Advanced Features
Prev		Home		Next