2010-07-22 02:14:32     What's the correct u-boot upgrade process for SPI (BF518F EZ-BRD)?

Document created by Aaronwu Employee on Sep 25, 2013
Version 1Show Document
  • View in full screen mode

2010-07-22 02:14:32     What's the correct u-boot upgrade process for SPI (BF518F EZ-BRD)?

Chris Eddington (UNITED STATES)

Message: 91544   




The online documentation is not clear so I want to be sure.  Can someone confirm the correct process?


-I just purchased a BF518f ez-brd with a very old version of u-boot (U-Boot 2008.10-00143-g46bf1eb-dirty (ADI-2009R1-pre) (Nov 20 2008 - 21:55:38).


I have downloaded the most recent u-boot images and only a ldr file is available.  I think the correct file is  u-boot-bf518f-ezbrd-spi-2009R1.1-rc1.ldr ?


I can upload this file over the uart and run it with bootldr successfully:


bfin> loady

## Ready for binary (ymodem) download to 0x01000000 at 57600 bps...                                 

C0(STX)/0(CAN) packets, 4 retries

## Total Size      = 0x00027a30 = 162352 Bytes


bfin> bootldr 0x1000000

## Booting ldr image at 0x01000000 ...


U-Boot 2008.10 (ADI-2009R1.1-rc1) (Dec  4 2009 - 03:18:57)

CPU:   ADSP bf518-0.0 (Detected Rev: 0.0) (spi flash boot)

Board: ADI BF518F EZ-Board board


bfin> sf probe 2

SF: Got idcode 20 20 15

2048 KiB M25P16 at 0:2 is now current device



So questions to confirm is:

- is this the right file to program into SPI:  u-boot-bf518f-ezbrd-spi-2009R1.1-rc1.ldr?

- Assuming I reload to 0x1000000 - because it is a loader file (an not a .bin), what is the right commands to program it into the SPI?  Is it  "sf write 0x1000000 0x0 $(filesize)" ?


Many thanks,





2010-07-22 13:22:13     Re: What's the correct u-boot upgrade process for SPI (BF518F EZ-BRD)?

Mike Frysinger (UNITED STATES)

Message: 91602   


the release notes explain the file format:


so there isnt any other file that would match for SPI booting on that board


the wiki shows how to program serial flash:



you can also review the output of 'print update' for the commands we use for automating u-boot updates from the board itself