SWRA499C June   2016  – September 2019 CC1352P , CC1352R , CC2640 , CC2640R2F , CC2642R , CC2642R-Q1 , CC2650 , CC2652P , CC2652R , CC2652R7 , CC2652RB , CC2652RSIP

 

  1.   Running Bluetooth Low Energy on CC13x2/CC26xx Without a 32 kHz Crystal
    1.     Trademarks
    2. 1 Introduction
    3. 2 Requirements
      1. 2.1 Bluetooth Low Energy (BLE)-Stack Software Versions
      2. 2.2 Constraints
    4. 3 Configuration
      1. 3.1 Hardware Configuration
      2. 3.2 Software Configuration
    5. 4 Performance
      1. 4.1 Current Consumption
    6. 5 Recommendations
    7. 6 References
  2.   Revision History

Introduction

The Bluetooth specification puts a strict requirement on the accuracy of the sleep clocks for Bluetooth Low Energy devices that are intended to enter (and stay) in a connection. The specification requires that devices have a sleep clock accuracy (SCA) that meets ± 500 ppm. For more details on the SCA requirement, see the Sleep Clock Accuracy section in the Bluetooth core specification 4.0, Volume 6. that can be downloaded from the following URL: https://www.bluetooth.com/specifications/adopted-specifications.

This sleep clock accuracy (SCA) requirement is valid for both the master and slave side of the Bluetooth Low Energy connection; however, devices such as Bluetoooth Low Energy beacons do not require such accuracy as the advertising interval is intentionally varied to prevent collisions. The intention of the SCA requirement is to ensure low power consumption while maintaining flexibility in the component selection. The amount of time a slave device must stay in active RX mode, referred to as the receive window, is dependent upon the sleep clock tolerance; a less accurate sleep clock requires the receive window time to be increased, thus, increasing the average current consumption.