• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 99 subscribers
  • Views 275 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.

OMAP 3530 wake-up problem after 36 hours

imran erguler
Prodigy 40 points

Hi community

I am having a problem with wakeup of 3530. After boot of the device, the device intentionally enters suspend mode. Then it can wake and suspend in any order and many times without a problem. However after ~36 hours, the device can not wake after sleep. I think it should be related to a timer or counter in OMAP, but  I dont know how?

 

Thanks

  • 0
    TI__Genius 16690 points

    What's the wake up events you are using to wake up the device ? What is your OS ?

  • 0 in reply to kshin
    Prodigy 40 points

    I found the problem:  The period of the Sync_32 timer is about 36.4 hours (It runs with 32 kHz and a counter register with 32 bits, i.e. it increments with 32768 per second. Hence, 2^32/32768 = 131072 seconds= 36.4 hours).  The problem arises, if suspend time  <  wake time.

    Let suspend time be t1 and wake time be t2. Suppose the device has not been waken up for more than 36.4 hours. In a wake attempt, since counter restarts and t2 < t1,  suspend time  <  wake time problem occurs.

    In pm_34xx.c, I commented out omap_enable_system_timer() and omap_disable_system_timer() and the error has seen no more. One can deal with to provide an exact solution