SWRA486A August   2015  – April 2017 CC1310 , CC2620 , CC2630 , CC2640 , CC2640R2F-Q1 , CC2650 , CC2650MODA

 

  1.   CC26x0, CC13x0 SimpleLink™ Wireless MCU Power Management Software Development
    1.     Trademarks
  2.   CC26x0, CC13x0 SimpleLink™ Wireless MCU Power Management Software Development
    1. 1 Abbreviations
    2. 2 Power Management Introduction
    3. 3 TI-RTOS Power Modes
      1. 3.1 Active Mode
      2. 3.2 Idle Mode
      3. 3.3 Standby Mode
        1. 3.3.1 Standby Enter Sequence
        2. 3.3.2 Standby Exit Sequence
      4. 3.4 Shutdown Mode
    4. 4 Implementation Considerations
      1. 4.1 Device Initializing
        1. 4.1.1 Low-Level Initializing
        2. 4.1.2 Initializating TI-RTOS
      2. 4.2 Recharging in Standby
      3. 4.3 Operating the DC-DC Converter
      4. 4.4 Configuring Device for External Input Interrupts and Wakeup
        1. 4.4.1 Interrupt and Wakeup from Active, Idle, and Standby
        2. 4.4.2 Wakeup from Shutdown Mode
      5. 4.5 Oscillators
        1. 4.5.1 High-Frequency Oscillators
        2. 4.5.2 Low-Frequency Oscillators
        3. 4.5.3 RC Oscillator Calibration
      6. 4.6 Auxiliary Domain
        1. 4.6.1 Powering on the Auxiliary Domain
        2. 4.6.2 Powering Down the Auxiliary Domain
        3. 4.6.3 Managing the Sensor Controller and the Auxiliary Domain Power
        4. 4.6.4 Sharing Resources Between the Sensor Controller and the Cortex®-M3
      7. 4.7 RTC
        1. 4.7.1 Initializing RTC
        2. 4.7.2 Configuring RTC Compare Events
      8. 4.8 Debugging Through Power Modes
      9. 4.9 Using Peripherals
    5. 5 References
  3.   Revision History

3.3 Standby Mode

In standby mode, the Cortex-M3 waits in deep-sleep for interrupts to wake up after executing the WFI instruction. Before entering standby, power down system resources, including the high-frequency oscillator, radio, peripherals, and auxiliary domain. Many system modules have retention in standby including the Cortex-M3 (see the CC13x0, CC26x0 Technical Reference Manual for details). After waking up from standby, the Cortex-M3 resumes executing programs at the point before entering standby.

Because CC26x0 and CC13x0 devices run on a low-power LDO in standby, most system resources are unavailable in standby. Use the RTC, which runs in standby, to wake up the Cortex-M3. The Cortex-M3 can wake up on any interrupt-enabled, external input pin.

The application must consider the latency associated with entering and exiting when using standby mode.

If the next wakeup is in less than 1 ms, the TI-RTOS implementation does not enter standby. If the application requires exact timing, consider the latency associated with entering and waking up from standby. The TI-RTOS implementation handles this latency by inserting wake-up event four RTC edges (64 µs) earlier than the event to ensure the system powers on in time to service the wake-up event scheduled by the application.

The TI-RTOS standby implementation allows a variation where the cache contents are retained. In standby, the system draws approximately 2 µA more than it does without retaining the cache. System start-up from standby is typically quicker. The main system RAM should always be retained in standby mode. The main system RAM retention is also the default configuration when the device boots up.

The following code for entering and exiting standby is from the TI-RTOS PowerCC26XX.c implementation: C:\ti\tirtos_cc13xx_cc26xx_#_##_##_##\products\tidrivers_cc13xx_cc26xx_#_##_##_##\packages\ti\drivers\power\PowerCC26XX.c.