Post Go back to editing

Problem flashing u-boot from Yocto Linux ADSP-SC5xx 2.0 beta to SC589-EZKIT


We are attempting to install the u-boot associated with the beta release of Yocto Linux for adsp-sc5xx 2.0 on an sc589-ezkit following the instruction found at  The only difference is that we are installing the u-boot LDR file from an SD card rather than using TFTP.

We connect to the board using an ICE-1000 as described in the instructions using our old u-boot (version 1.0, u-boot 2015) and are able to access the u-boot command line via the serial UART as expected.  We then issue the following sequence of commands to install the new u-boot (version 2.0, u-boot 2020) which is on the SD card:

sc # ext2load mmc 0 0xc2000000 /boot/u-boot-sc589-ezkit.ldr;
485712 bytes read in 102 ms (4.5 MiB/s)
sc # sf probe 2:1;
SF: Detected W25Q128BV with page size 256 Bytes, erase size 4 KiB, total 16 MiB
sc # sf erase 0 0x80000;
SF: 524288 bytes @ 0x0 Erased: OK
sc # sf write 0xc2000000 0 ${filesize};
SF: 485712 bytes @ 0x0 Written: OK
sc # save
Saving Environment to SPI Flash...
SF: Detected W25Q128BV with page size 256 Bytes, erase size 4 KiB, total 16 MiB
Erasing SPI flash...Writing to SPI flash...done
sc # reset
resetting ...

After this point the Red "FLT" LED immediately turns on and the serial console becomes unresponsive.  The only way to access the board is to re-connect the ICE-1000 and use it to connect in debug mode again.

Other information that may or may not be helpful:

  • We have made no modifications to u-boot, it is exactly as provided in the 2.0 beta repo.
  • We are able to flash the old 1.0 (2015) u-boot to SPI using the exact method above on this board with no difficulty at all.
  • We are able to run the new 2.0 (2020) u-boot on this board from the ICE-1000 debugger.
  • With the old 1.0 u-boot installed in the SPI flash we are able to run the new 2.0 (dunfell-compatible) ADI Linux on this board.

Please let us know if you have any ideas about what might be going wrong or if you need any further information.  We are very excited about the Yocto Linux 2.0 release and are looking forward to getting it working.

  • Hi JMB,

    Have you tried using the TFTP method, does that too fail?

    Will try to replace my u-boot with the new one and let you know.


    Prasanth R

  • Hi Prasanth,

    Thanks for your reply.

    We were actually able to get it working late yesterday evening using the SD card and I was just about to post here when I saw your message.  I will describe what worked for us just for the edification of others.

    The issue appears to be that we cannot flash SPI to the 2.0 U-Boot if we are running the 1.0 U-Boot environment, either from the JTAG or from our old installation of 1.0 currently on the SPI flash (something we have been able to do previously with different versions of 1.0 U-Boot).  We needed to be running the 2.0 U-Boot on the JTAG in order to flash the SPI to 2.0 U-Boot successfully.

    The reason we had been attempting this from the 1.0 U-Boot on the JTAG was that a) we have some devices running the 1.0 U-Boot on their SPI flash and we would have liked to be able to upgrade them without the JTAG , and b) initially we were not able to run ext2load from the 2.0 U-Boot on the JTAG (we got a command not recognized error).  To my embarrassment I do not know exactly what part of the environment I changed but yesterday evening I became able to run ext2load from the 2.0 U-Boot on the JTAG; at that point I was able to successfully flash the SPI to 2.0 from the SD card and get it to restart properly.

    If you can think of any way we would be able to upgrade from 1.0 U-Boot to 2.0 U-Boot it would be much appreciated but otherwise I think we can chalk this up to user error on my part.

    Thanks for your time,