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

High-Frequency Oscillators

The CC26x0 and CC13x0 devices boot with the 48-MHz high-speed RC oscillator that clocks the Cortex-M3. When using the radio, switch the main system clock to the high-speed crystal oscillator. The code in Figure 15 shows how to change to the high-speed crystal oscillator (see the functions in driverlib modules osc.h/osc.c).

Figure_15_SWRA486.pngFigure 15. Switching from RCOSC_HF to XOSC_HF

NOTE

The high-speed crystal oscillator does not start immediately and the application can perform other tasks running on the RCOSC_HF while the XOSC_HF starts.

To optimize power consumption, another function gives the application an estimate of the length of the next XOSC_HF startup. The start-up time depends on the following three factors:

  • How long the XOSC_HF has been off
  • The operational parameters of the crystal
  • The frequency of the RCOSC_HF

The OSCHF_GetStartupTime(uint32_t timeUntilWakeupInMs) returns an estimate of the expected XOSC_HF start-up time, depending on how long the XOSC_HF has been off. For example, the application can use this information to schedule wakeups and ensure that the XOSC_HF starts up before using the radio and transmitting a packet.

NOTE

You must enable the RTC for this functionality to work because the oscillator driver uses the RTC to calculate the start-up time.

You must turn off the XOSC_HF before entering standby or shutdown. To turn off the XOSC_HF, call OSCHF_SwitchToRcOscTurnOffXosc().

NOTE

You cannot switch to the RCOSC_HF before you have switched to the XOSC_HF. Aborting a switch to XOSC_HF is not supported.