92b4a3a288
We want to know how many copies of UBL/APP have been written. It is necessary to know that we have written multiple copies to avoid two bitflips rendering the device unusable. dvnixload debug1: Reading: [INFO: UBLs written: 0x5] dvnixload debug1: Reading: [INFO: APPs written: 0x4] Related: SYS#438 |
||
---|---|---|
.gitignore | ||
ChangeLog | ||
Makefile | ||
README | ||
TODO | ||
board.h | ||
common.h | ||
crc.c | ||
crc.h | ||
davinci.c | ||
davinci.h | ||
ddr.h | ||
dm644x.c | ||
dm644x.h | ||
gpio.c | ||
gpio.h | ||
nand.c | ||
nand.h | ||
nandboot.c | ||
nor.c | ||
nor.h | ||
norboot.c | ||
uart.c | ||
uart.h | ||
uartboot.c | ||
ubl.c | ||
ubl.lds | ||
util.c | ||
util.h |
README
README for HVUBL This UBL can be used for flashing itself and a 2nd stage bootloader (usually U-boot) in flash memory. It can also be used to flash an arbitrary data image into flash, without a header. It can also be used to run DDR RAM memory testing. To compile HVUBL for the sffsdr board, for example, run: $> make BOARD=sffsdr The Makefile honors the CROSS_COMPILE environment variable to specify the prefix of your ARM gcc toolchain. If it is not set, it defaults to: CROSS_COMPILE=arm-linux- You can override it like this, for example: $> make CROSS_COMPILE=arm-angstrom-linux-gnueabi- BOARD=sffsdr The output file, in ARM ELF format, will be named <ubl.elf>