March 13th 2008
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.
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-1.1.6-2008R1.tar.bz2 | Source code package |
| u-boot-bf527-ezkit-para-2008R1.ldr | BF527-EZKit booting LDR out of parallel flash |
| u-boot-bf527-ezkit-spi-2008R1.ldr | BF527-EZKit booting LDR out of SPI/serial flash |
| u-boot-bf527-ezkit-uart-2008R1.ldr | BF527-EZKit booting LDR over UART |
| u-boot-bf533-ezkit-bypass-2008R1.bin | BF533-EZKit executing directly from parallel flash |
| u-boot-bf533-stamp-bypass-2008R1.bin | BF533-STAMP executing directly from parallel flash |
| u-boot-bf533-stamp-spi-2008R1.ldr | BF533-STAMP booting LDR out of SPI/serial flash |
| u-boot-bf537-stamp-bypass-2008R1.bin | BF537-STAMP executing directly from parallel flash |
| u-boot-bf537-stamp-spi-2008R1.ldr | BF537-STAMP booting LDR out of SPI/serial flash |
| u-boot-bf537-stamp-uart-2008R1.ldr | BF537-STAMP booting LDR over UART |
| u-boot-bf548-ezkit-para-2008R1.ldr | BF548-EZKit booting LDR out of parallel flash |
| u-boot-bf548-ezkit-spi-2008R1.ldr | BF548-EZKit booting LDR out of SPI/serial flash |
| u-boot-bf548-ezkit-uart-2008R1.ldr | BF548-EZKit booting LDR over UART |
| u-boot-bf561-ezkit-bypass-2008R1.bin | BF561-EZKit executing directly from parallel flash |
ethaddr)gocplbinfo for viewing the active CPLB tablesbootldr using common Boot ROM functionsotp for accessing on-chip one time programmable memory (found on BF52x and BF54x processors) -- write support is considered broken and will eat your processor as well as your processor's dogicache_dump for dumping the L1 instruction cachemd and cp now work with all on-chip L1 regionsbin2ldr utility and use the ldr-utils package for LDR creationmake <board name> (just drop the _config)#include <asm/mach-common/bits/<peripheral>.hinclude/asm-blackfin/ that were not actually used, as well as many unused definitions in the remaining header filesbf533, bf537, bf548, and bf561 into just blackfinBFIN_BOOT_<MODE>cpu/blackfin/initcode.c-ffixed-P5 compiler flag to common Blackfin config rather than board specific-fomit-frame-pointer by defaultTEXT_BASE and CFG_MONITOR_BASE -- the latter is used everywhere nowemuexcpt instruction whenever the board calls the hang functionbdinfo function for the Blackfin port
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