Forums

What Power Mode are you setting the device to in the CC2430?

Please note that if you are in PM3, none of the clocks in the device will be enabled.  This is indicated in Table 38 in the CC2430 Datasheet available on the CC2430 Product Folder.

I'm setting it at PM3..but in the same specification is it also mentioned "13.13.3 Watchdog and Power Modes, In the two lowest power modes, PM2 and PM3, the watchdog is disabled and reset."

In this case should I not worry about the watchdog timer here as it is disabled during sleep? 

Are there extra steps that are needed when waking up for the watchdog timer (other than the periodic watchdog clear timer)?

Grant

I'm setting it at PM3..but in the same specification is it also mentioned "13.13.3 Watchdog and Power Modes, In the two lowest power modes, PM2 and PM3, the watchdog is disabled and reset."

In this case should I not worry about the watchdog timer here as it is disabled during sleep? 

To my knowledge, implementing what is indicated in Section 13.13.3 of the CC2430 datasheet should be sufficient.  As this section indicates, when the device is in PM2 or PM3, the watchdog timer is not running.  However, it is return to the same state as it was when going from a PM0 or PM1 state to a PM2 or PM3 state, but start counting from zero.

Grant

Are there extra steps that are needed when waking up for the watchdog timer (other than the periodic watchdog clear timer)?

Not that I am aware of.

If that is the case, has it ever been tried to enable the wathcdog timer with the ZStack-1.43-1.2.1 and have POWER_SAVING enabled?

If so, is there a sample application to show how it is done?

I have reconfigured my algorithm and placed the code to enable and clear the watchdog timer in osal_start_system.

Here's my modified osal_start_system:

void osal_start_system( void )
{
#if !defined ( ZBIT )
  for(;;)  // Forever Loop
#endif
  {
   uint8 idx = 0;

   // Enable the watchdog timer before entering the main processing loop
  WatchDogEnable(WDTIMX);   

    Hal_ProcessPoll();  // This replaces MT_SerialPoll() and osal_check_timer().   

    do {
      if (tasksEvents[idx])  // Task is highest priority that is ready.
      {
        break;
      }
    } while (++idx < tasksCnt);

    if (idx < tasksCnt)
    {
      uint16 events;
      halIntState_t intState;

      HAL_ENTER_CRITICAL_SECTION(intState);
      events = tasksEvents[idx];
      tasksEvents[idx] = 0;  // Clear the Events for this task.
      HAL_EXIT_CRITICAL_SECTION(intState);

      events = (tasksArr[idx])( idx, events );
      
     // Reset the watchdog timer after every event processed
      WatchDogEnable(WDTIMX);   
     

      HAL_ENTER_CRITICAL_SECTION(intState);
      tasksEvents[idx] |= events;  // Add back unprocessed events to the current task.
      HAL_EXIT_CRITICAL_SECTION(intState);
    }
#if defined( POWER_SAVING )
    else  // Complete pass through all task events with no activity?
    {
    
   // Reset the watchdog timer before going to sleep
   WatchDogEnable(WDTIMX);   

   osal_pwrmgr_powerconserve();  // Put the processor/system into sleep

   // Reset the watchdog timer after waking up from sleep
   WatchDogEnable(WDTIMX);   
    }
#endif
    }
}

Grant

If that is the case, has it ever been tried to enable the wathcdog timer with the ZStack-1.43-1.2.1 and have POWER_SAVING enabled?

I'm not personally aware, but isn't to say it hasn't been done.  Based on the sample code you provided, it looks reasonable.

One thing you can add to verify if the watchdog timer is actually resetting the device is to add some checks early on in your application code to read the SLEEP Mode Control register.  Bits[4:3] provide status bits which indicate the cause of the last reset.  If the SLEEP[4:3] = 10b, it indicates a watchdog timer reset.

Grant,

I'm curious. Are you still setting a timer (osal_start_timerEx) in your AppInit with your modified osal_start_system? Or are you just effectively configuring and clearing the Watchdog with your 2 calls to WatchDogEnable in your osal_start_system?

Thanks!