CC3235S: No Wakeup from Hibernate Slow Clock 32KHz Wakeup

Hi,

Your code for putting the device in hibernate and waking up from the slow clock appears to be correct:

PRCMHibernateWakeupSourceEnable(PRCM_HIB_SLOW_CLK_CTR);
PRCMHibernateIntervalSet(32768); // should set up the HIB timer for x amount of ticks, 32,768 per second
PRCMHibernateEnter();

To verify, I used the power_management example to put the device in hibernate mode. The application calls powerShutdown(), which then calls Power_shutdown(). I edited powerShutdown() in platform.c by adding the lines of code above to enter hibernate and have the device wake up based on the slow clock, and commented out Power_shutdown(), as shown at the bottom of the code snippet below:

void powerShutdown(uint32_t shutdownTime)
{
#ifdef CC32XX
    Power_NotifyObj hibSignal;
#endif

#ifdef __MSP432P401R__
#if 0
    Power_registerNotify(&hibSignal, PowerMSP432_ENTERING_SHUTDOWN,
                         preHibConfig,
                         (uintptr_t)NULL);
    if(shutdownTime != MAX_INT)
    {
        /* config gpio to wakeup from hib */
    }
    /*
     *    PowerMSP432_SHUTDOWN_0 => PCM_LPM35_VCORE0
     *    PowerMSP432_SHUTDOWN_1 => PCM_LPM45
     */
    Power_shutdown(PowerMSP432_SHUTDOWN_0,0);
#else
    if(shutdownTime != MAX_INT)
    {
        if(shutdownTime >= 1000)
        {
            sleep(shutdownTime / 1000);
        }
        usleep((shutdownTime % 1000) * 1000);
    }
#endif
#elif CC32XX
    Power_registerNotify(&hibSignal, PowerCC32XX_ENTERING_SHUTDOWN,
                         preHibConfig,
                         (uintptr_t)NULL);
    //Power_shutdown(0,shutdownTime);
    PRCMHibernateWakeupSourceEnable(PRCM_HIB_SLOW_CLK_CTR);
    PRCMHibernateIntervalSet(32768);
    PRCMHibernateEnter();
#endif
}

The hibernate and wakeup also worked when I added the same lines of code to the buttonled example.

Are PRCMCC3200MCUInit() and Power_init() the first functions executed by your application code? They are typically called by Board_init().

Best regards,

Jesse

Also, just an FYI, the CC32xx Power Management documentation you had linked above is for the older gen 1 CC3200. Here's the link to the CC3x3x Networking Subsystem Power Management document

Thank you for the suggestion and your link.

I modified power_measurement precisely as you did, but did not achieve your result. When the device goes into Hibernate, I never see another print statement ever again. I should see the Banner print again after Hib Wake (because of MCU rebooting), and I also put a UART print in after shutdown() just in case.

By not seeing the UART Prints, I am assuming this means I am not waking. However, when I run the program again, I do see that the Wake Reason is HibWake, its just that the debugger / CCS woke it up, not my Slow Clock.

So what does this mean? What could be different about my situation?

I am using the Launchpad with default jumpers set. Is there some sort of prep that I missed?

SDK 5.20.00 (I'm not updating because I have a complex project this is for that has issues on other SDKs. I'll debug that later, but for now 5.20 is staying).

I did confirm that PRCMCC3200MCUInit() and Power_Init() are being called in Board_Init().

Your time and effort is appreciated.

Tom

Jesse,

This solved my issue thank you. After the Debugger was cut off / disconnected, My "burned" image was being ran, which was just a bunch of NOPs I put in.

Short story, the previous image was an AWS project that tested MQTT client, so when I left it unattended while not in debug, guess how many MQTT publishes I found on my AWS MQTT test client!  So I burned in an image that didn't puke out MQTT messages every 2-3 seconds, my NOP image.

Thanks for the info, I can't believe something that simple was my problem. In the future, is there a way to get my CCS-Created Debugged images to "Stick" without using Image Creator feature in UniFlash?

I see there are two ways to use UniFlash. I have success using the Image Creator feature, but it's slow. I try using Auto-Detect (Top Option), but my image verification always fails, so I just give up and use Image Creator.

I want my images to stay when the debugger is disconnected, but Image Creator takes a hot minute to flash. Maybe this is my only option. 

When working on 16 bit MSP430 projects, I don't have this issue, so this is a result of my CC3235S ignorance I suppose.

Thanks again.

Tom

Thank you for all your help. I, and others appreciate it.