摘：u-boot file format

u-boot
Compiled ELF image

u-boot.bin
u-boot converted to a raw binary

u-boot.hex
u-boot.bin converted to Intel Hex format

u-boot.srec
u-boot.bin converted to Motorola S-records format

u-boot.ldr
u-boot converted to Blackfin Loader format

u-boot.ldr.hex
u-boot.ldr converted to Intel Hex format

u-boot.ldr.srec
u-boot.ldr converted to Motorola S-records format

Which file format you need depends on how you're booting the processor and what tool you're using to do the programming. The u-boot ELF file is never used to boot, only for reference/debugging with the standard toolchain.

If you're booting the processor in “Bypass” mode, then you will need the u-boot.bin file (or one of its derivatives). For every other boot mode, you need the u-boot.ldr file (or one of its derivatives). The u-boot.bin file is also used regardless of boot mode for a quick runtime test (executing via the go command).

If you're using U-Boot to do the programming, then you want the u-boot.bin or u-boot.ldr file. You do not want the hex or srec formats.

If you're using VDSP to do the programming, then you probably want the u-boot.hex or u-boot.ldr.hex file. VDSP can program the raw binary file as well, but many people feel more comfortable with the hex file. Other JTAG programming tools may also require the hex format.

If you want the srec format, you probably don't know what you're doing. Please rethink what you're attempting, read some documentation, or ask for help. If you're 100% sure you need the srec files, they are provided in the rare off-chance.

文章摘自：