• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 41 subscribers
  • Views 894 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.

PRCMHibernateWakeupCauseGet returns wrong value

Peter Archer
Intellectual 330 points

After a hibernation wakeup, calling this function fails to return either of the possible reasons for the wakeup - PRCM_HIB_WAKEUP_CAUSE_GPIO or PRCM_HIB+WAKEUP_CAUSE+SLOCK_CLOCK.  Regardless of the cause, and I've tried with both, it always returns a zero value, which is not defined.  PRCMHibernateWakeupCauseGet() is called immediately after PRCMSysResetCauseGet() and determined that it is indeed a PRCM_HIB_EXIT code.

Peter

  • 0
    TI__Expert 5025 points

    Hi Peter,

    This is a limitation in our current silicon and there are no direct ways of getting the wakeup cause from HIBernation.

    Please consider if you could use some indirect means of determining the wake source depending on your usecase. For instance, the elapsed duration in HIBernation can be approximately determined by saving the last SlowClockCount and deducting it from the current value after the wakeup. If this is close to the value set as HIBernate duration, the source can be Slow clock wakeup.

    Best regards,

    Naveen.

     

  • 0 in reply to Naveen Narayanan
    Intellectual 330 points

    Naveen,

    Thanks!  It's no big deal; I was just using it to include in informational log messages.  I just wanted TI to be aware of the issue in case they weren't

    Peter

  • 0 in reply to Peter Archer
    Prodigy 175 points

    Hello,

    I am also seeing this issue with the production silicon. Any idea when will be a new revision that solves this problem?

    Cheers,

    Daniel Campora