• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 431 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.

EMIF booting with 4430 on Pandaboard

Vince Yee
Prodigy 120 points
Other Parts Discussed in Thread: 4430

I'm getting data abort or prefetch exceptions when trying to boot from an LPDDR2-NVM PoP on the pandaboard (customized board).  I've configured everything correctly on the board, SYS_BOOT is configured to boot from EMIF through resistor stuffing on the pandaboard.  The X-Loader MLO code has been burned onto the LPDDR2-NVM using Trace32.

I can step through the code and see the ROM copy the MLO into the 4430 internal RAM, then when all of a sudden i would get the data abort/prefetch exception.  The trace registers show everything is fine up until the CHSETTINGS found.  It does not seem to get to the CHSETTING execute portion of ROM code.  

Is there something I am missing?  any insight would be helpful. 

thanks,

Vincent

  • 0
    TI__Expert 8055 points

    Vincent,

    Are you trying to include a Configuration Header in your MLO?  (The CH is optional for XIP type booting, such as with LPDDR2-NVM.)  If so, does your Configuration Header match the format described in section 27.4.8.2 of the OMAP4430 TRM?

    Regards,
    Gina 

  • 0 in reply to Gina Glaser
    Prodigy 120 points

    Hi Gina,

    Correct, I have looked at that section multiple times.  I've tried various settings, with and without CH.  The one confusing part for me is, DMM LISA Map 0, is this for the DDR ram that is set at 0x80000000?  Currently, the LPDDR2-NVM does have the DDR ram on it as well, so I would think the default settings would be ok, since I just need access to the NVM, which the ROM sets up to look at 0xC0000000. 

    I will try w/o the CH header again, maybe I have some other configuration that is incorrect.  I will also try with the default CHRAM configuation that came with the x-loader build i have.

    thanks.

  • 0 in reply to Vince Yee
    Prodigy 120 points

    Does the CHSETTINGS valid need to be set?  Also same for the CHRAM?  The setting is currently disabled in the MLO that works with MMC boot.  

    thanks.

    Vincent

  • 0 in reply to Vince Yee
    TI__Expert 8055 points

    Vince,

    The CH can be void, meaning that it contains only a CHSETTINGS item for which the Valid field is 0.

    Have you removed the GP device header from the MLO?  The header contains the size and destination address for non-XIP memory (SD card, eMMC, etc) and is not needed for XIP memory boot such as in your case.

    Regards,
    Gina 

  • 0 in reply to Gina Glaser
    Prodigy 120 points

    Hi Gina,

    Yes, we have removed the GP header, and now it works.  The main issue was in the X-loader code where they hard coded the GP header offset, with comments that did not reflect that.

    thanks,

    Vincent