• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 429 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.

Hijacking the U-Boot sequence on a AM355x

Srinath Balaraman
Prodigy 10 points

I am a newbie at using U-Boot, so please excuse my ignorance here :)

I am using one of the out-of-the-box SD cards to boot Android on an AM355x evaluation board. From that card I am trying to break the autoboot sequence by hitting a key when the countdown begins, and tftp load my own image. The TFTP load goes through smoothly, but when I say "go <addr>", I expect my image to print some messages to the console but I don't see anything. Obviously, my image is not running. I wanted to find out how do I debug this problem to see what happening? 

I would appreciate any help with debugging this problem.

Thanks,

-Srinath

  • 0
    TI__Intellectual 2725 points

    what image are you loading through tftp.

    The Linux image that u-boot rungs normally is uImage which is having a u-boot related wrapper around the original zImage. This wrapper is the header used by u-boot. u-boot decrypts/parses this header, removes the header for uImage (uImage - header = Linux image) then runs this image.

    so in this regard go <addr> wont work in this regard.In such scenario, bootm <addr>  is used.

    kindly try with bootm <addr> and let me know the status.