• Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 292 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.

x-loader and sys_boot for OMAP 35x

burchmere
Intellectual 930 points

Just posted this under an older thread, but I'm afraid it will get kind of lost there so re-posting here.

Does anyone know the background on why x-loader was written the way it was for handling the sys_boot[4:0] value and determining how to boot from there?  As the thread above shows, the code in omap3evm.c/get_mem_type() only allows booting from MMC1 (assuming OneNAND flash) if sys_boot[4:0] = 0x03 or 0x06.  But 0x03 is shown as "reserved" in the TRM, and why not allow 0x0D, 0x0E, 0x0F, 0x10, 0x11, 0x12, and 0x18?  They all include MMC1 as a boot source.

I'm in the midst of modifying the code and feel like I'm missing something about how x-loader works.

 

  • TI__Mastermind 41665 points

    Your post isnt lost, however I do not have a good answer for this one, this is something I will have to ask around internally to see if I can get some feedback from the developer.

    My initial suggestion would be to modify and rebuild X-Loader to accept some other boot modes and than see what happens, my suspicion is this was just put in there based on what the developer wanted to use for the MMC boot, not because the other modes are actually precluded from functioning properly with X-Loader (though this is just a guess).