August 25th 2009
boote) -- use bootable u-boot images instead (bootm)While we would love to test every environment out there that you may use, we'll document the platforms we actively develop and test on. Refer to the documentation for setting up your system.
Development is actively done with:
Testing is actively done with the same software on SUSE systems, but for all supported boards.
File names generally take the form u-boot-<board>-<boot mode>-<version>.filetype.
Each board has one tarball which contains all of the release images for that board. For information on which file to use, see the binaries and boot modes pages. Additionally, a u-boot.elf and init.elf file are included to facilitate booting via JTAG.
All files are raw binary. That means you use them as is. They are most certainly not in the hex or srec format. Alternative file formats are no longer provided as part of the release. If you really need such a file, you will need to convert it yourself.
| File | Description |
|---|---|
| u-boot-2008.10-2009R1.tar.bz2 | Source code package |
| u-boot-bf518f-ezbrd-2009R1.tar.bz2 | bf518f-ezbrd images |
| u-boot-bf526-ezbrd-2009R1.tar.bz2 | bf526-ezbrd images |
| u-boot-bf527-ezkit-2009R1.tar.bz2 | bf527-ezkit images |
| u-boot-bf533-ezkit-2009R1.tar.bz2 | bf533-ezkit images |
| u-boot-bf533-stamp-2009R1.tar.bz2 | bf533-stamp images |
| u-boot-bf537-srv1-2009R1.tar.bz2 | bf537-srv1 images |
| u-boot-bf537-stamp-2009R1.tar.bz2 | bf537-stamp images |
| u-boot-bf538f-ezkit-2009R1.tar.bz2 | bf538f-ezkit images |
| u-boot-bf548-ezkit-2009R1.tar.bz2 | bf548-ezkit images |
| u-boot-bf561-ezkit-2009R1.tar.bz2 | bf561-ezkit images |
| u-boot-cm-bf527-2009R1.tar.bz2 | cm-bf527 images |
| u-boot-cm-bf533-2009R1.tar.bz2 | cm-bf533 images |
| u-boot-cm-bf537e-2009R1.tar.bz2 | cm-bf537e images |
| u-boot-cm-bf548-2009R1.tar.bz2 | cm-bf548 images |
| u-boot-cm-bf561-2009R1.tar.bz2 | cm-bf561 images |
| u-boot-tcm-bf537-2009R1.tar.bz2 | tcm-bf537 images |
sspi commandbootldr commandgo on external memory by putting it into self refreshethaddr handling with environment and network driversmii command-f{function,data}-sections and link with --gc-sections for optimized outputclkin_hz to the kernel by default for complete u-boot clock handlingnboot skip bad blocks by default
Please refer to the Das U-Boot section of the Blackfin documentation wiki for more information:
http://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot