Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

  • State
  • Replies 2 replies
  • Subscribers 40 subscribers
  • Views 78 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

CC3235MODASF: Device comes out of hibernate at random times

Kent Middlekauff
Prodigy 50 points
Part Number: CC3235MODASF

Tool/software:

Once the firmware puts the device into Hibernate, the device exits Hibernate after anywhere from 164 microseconds to 30 seconds. This occurs randomly, around 1 in 1000 times. When this occurs, PRCMSysResetCauseGet() returns PRCM_HIB_EXIT (7) and PRCMHibernateWakeupCauseGet() returns 0.

The firmware does this before entering Hibernate mode. 

PRCMHibernateWakeUpGPIOSelect(PRCM_HIB_GPIO13 , PRCM_HIB_FALL_EDGE);
PRCMHibernateWakeUpGPIOSelect(PRCM_HIB_GPIO17 , PRCM_HIB_FALL_EDGE);
PRCMHibernateIntervalSet((32768 * 2));
PRCMHibernateWakeUpGPIOSelect(PRCM_HIB_GPIO11 , PRCM_HIB_FALL_EDGE);
PRCMHibernateWakeUpGPIOSelect(PRCM_HIB_GPIO4 , PRCM_HIB_FALL_EDGE);
PRCMHibernateWakeupSourceEnable(PRCM_HIB_GPIO4 | PRCM_HIB_GPIO13 | PRCM_HIB_GPIO17 | PRCM_HIB_GPIO11 | PRCM_HIB_SLOW_CLK_CTR);
uint32_t hibReg = HibRegRead();
Display_printf(gDisplayHandle, "HibReg %x Hibernate Now!\n", hibReg);
Display_printf(gDisplayHandle, 0, 0, "vvvvvvv");
PRCMHibernateEnter();

With this code we usually see the device exit Hibernate after 2 minutes, and PRCMSysResetCauseGet() returns PRCM_HIB_EXIT (7) and PRCMHibernateWakeupCauseGet() returns PRCM_HIB_WAKEUP_CAUSE_SLOW_CLOCK (2).

Do you have any ideas about how to fix/troubleshoot this issue?

  • 0
    TI__Guru 60435 points

    Hi,

    I would expect to get either 0x2 for slow clock wakeup or 0x4 for GPIO wakeup.

    0x0 means that it woke up unexpectingly.

    I am less familiar with this area in the code (and really harder to debug it as the device is in hibernate).

    I will try to check internally.

    Shlomi

  • 0 in reply to Shlomi Itzhak
    TI__Guru 60435 points

    Hi,

    In the code, you can see that it returns 0 according to the following condition:

      if( (HWREG(0x00000400) & 0xFFFF) >= 2 )

      {

          return ((PRCMHIBRegRead((OCP_SHARED_BASE + OCP_SHARED_O_SPARE_REG_8))>>2)&0x7);

      }

      else

      {

          return(0);

      }

    Browsing through the code, this condition refers to the ROM version of the device and means it is earlier than ES2.0.

    It does not correlate with the fact that it works most of the times so I would assume the ROM version is OK.

    In this case, since it is not due to slow clock (wakeup does match the period set), I would assume this is due to GPIO.

    Maybe you can try to rule out some GPIOs since many GPIOs are included as wakeup sources and see if it makes any difference.

    Shlomi