• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 99 subscribers
  • Views 2627 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

U-Boot will not start after SPL is loaded by NAND.

Chad Graham1
Prodigy 170 points
Other Parts Discussed in Thread: AM3352

Hello,

I am currently having the following issue getting U-boot to boot from NAND. I am capable of booting SPL & U-boot.img via tera term onto the AM3352 processor and after following the instructions located here I have loaded and written the MLO and u-boot.img files into NAND.

When I reset the device I get the following error and then it hangs:

SPL LoadedThe Expected Linux image was not found. Please check your NAND configuration.
Trying to start u-boot now...

I have not loaded a linux image, I'm just trying to get u-boot to load.

Could there be an issue with the storage address of the u-boot.img that the SPL is trying to read from? If I type in boot while in the U-boot prompt (after loaded via tera term), the system resets fine, just not after power is reset.

Thank you

  • 0
    TI__Expert 3010 points

    Hello Chad,

    Are you experiencing this problem on an EVM? Also, are you using on of our EZSDKs to generate your u-boot and kernel images?

    Early next week I will test out loading the images into NAND via UART using the instructions you mentioned and get back to you.

    I also want to mention that a little while ago I tested booting a BeagleBone black from NAND (SPL, u-boot, kernel, and ubifs), and it was able to get it working.  I loaded the images into NAND from and SD card using these instructions: http://processors.wiki.ti.com/index.php/AMSDK_u-boot_User's_Guide#Using_NAND

    I think I also tried tftping the images in u-boot and loading them into nand, and that worked, too.  It might be worth trying to load your images into nand with sd card or tftp if you can.

    Regards,

    Josh

  • 0
    Prodigy 170 points

    I have it working now. The problem was during the nand write of the u-boot.img. The file size specified in the u-boot guide must be specific for whomever was writing that document as the actual size of u-boot may vary. In this case they had specified 0x40000 where our u-boot.img was 0x55000 in length. I would recommend placing a note in the guide specifying that this number could vary and they should look at their own u-boot.img size on disk. 

    Thank you for your time! :)