Actions
Forum Thread Details
  • State Not Answered
  • Replies 4 replies
  • Subscribers 355 subscribers
  • Views 588 views
  • Users 0 members are here
Related

SD Init failed

Former Member

Hello I am trying to boot from SD and i have done that successfully before on same SD card. what happening is this following message from fsbl code .


Boot mode is SD
SD_INIT_FAIL
FSBL Status = 0xa009

This Boot Mode Doesn't Support Fallback

So please any help what I can should do ?

  • 0

    Hi,

      Perhaps you are doing this already, but first load a known good BOOT.BIN file for the target you are using on the SD card.  You can download any of the reference designs on this site for your target to obtain one.  Note that the file must be named BOOT.BIN, or the BOOTROM code in the Zynq will not be able to locate it and you will get the error you are seeing.

    If you have done this, then try using a different SD card, formatted FAT32, with your BOOT.BIN file loaded.

    Ron

  • 0 in reply to Former Member

    hello thanks for your reply,
    I have started new project and formatted the SD to FAT32 and got the same error. I also tried the previous project which its BOOT file worked and it ran successfully. I also got the error from Sd.c and it is as follows :
    Boot mode is SD
    SD: rc= 00000000
    SD: Unable to open file BOOT.BIN: 3
    SD_INIT_FAIL
    FSBL Status = 0xa009

    do I need to do something more.

  • 0 in reply to Former Member

    SOLVED
    IT WAS voltage bank problem
    I should put voltage bank 1.8 V while I was putting it 3.3V in the MIO design. So I think SD need 1.8 V not 3.3V to work

  • 0 in reply to Former Member

    I've had the same error message ("SD: Unable to open file BOOT.BIN: 3") with Vivado 2016.4; I don't think it's specific to outdated tool versions therefore, as some solutions on Zedboard.org, xilinx.com and elsewhere suggest.

    The cause in my case (pins are for Zedboard - check your schematic for other boards):

    The WP and CD pins had been moved to other locations than they should be on this board (MIO47 for CD, MIO46 for WP). They can be corrected in Vivado by clicking on the ZYNQ7 PS block, in the "MIO Configuration" section of the "Re-customize IP" dialog. They are specified for "SD 0", which should selected already.

    In my case, this happened because the "CAN 0" module had been selected, too, by default and it occupied MIO46 and MIO47; you'll have to uncheck it to be able to (re-assign) those pins. Curiously, when I did the whole things from scratch, CAN0 did not get selected and everything was assigned fine. I suspect this seeming randomness might cause the experience that another version solved it.

    Re-export HW to SDK afterwards, of course, and make sure FSBL is re-built with that update.

    - Ruedi