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

OMAP3530: global warm reset after wakeup from OFF mode

Nicolas Vassal
Prodigy 180 points

Hello Omap experts,

I have developped a piece of software that enable the IO daisy chain and put Omap in OFF mode. When the expected IO is toggled the device wakeup... Classic scenario.

Here some points about this software:

> Stand alone environment, No OS!

> Code running in DDR. ROM code restoration feature is used to restore device hardware when wakeup from OFF mode.

> For first execution (after power on reset) the device load software from SDCard.

I'm able to run successfully this test on an EVM board. After each wakeup from OFF mode, the Omap ROM code jumps to the correct location.

I have an issue when I run this software on a Beagleboard. Looks like the ROM code restoration does not complete successfully
and I get a global warm reset. Also, if I dump PRM_RSTST register I see that bit 3 is set ... which corresponds to security violation.

Anyone would have an idea on the root cause of this issue?

thanks to everyone who spend a little time on this.

Regards,
Nicolas.

 

  • 0
    Prodigy 180 points

    hi again,

    some more precise details to narrow a little bit the problem:

    > just before going to OFF, I set the configuration informations in wakeup memory as explained in chapter 25.5 "Wakeup booting by ROM code". The "Public restoration pointer" field points to the start symbol of my application.

    > On EVM board, when device wakeup from OFF mode, the ROM code jumps directly to my application, as expected.

    > On beagleboard the ROM code seems not able to jumps to my application directly and do instead a boot from NAND (default settings for beagleboard).

    Does anyone know what kind of problem can prevent the ROM code to jump to the address set in "Public restoration pointer" field?

    Thanks!!

     

    Regards,

    Nicolas.