SWRA793A October   2023  – November 2023 CC2340R5 , CC2340R5-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1 Introduction
  5. 2 Certification and Qualification
    1. 2.1 Bluetooth Qualification
    2. 2.2 Regional Compliance
  6. 3 Reference Examples
    1. 3.1 CC2340 Chipsets
    2. 3.2 Flash and RAM Allocation
  7. 4 Software Stack
    1. 4.1 BLE5-Stack Configurations
    2. 4.2 Software Offering
    3. 4.3 Supported PHYs
    4. 4.4 Supported Features
    5. 4.5 Multi-Connection
    6. 4.6 Coexistence (Planned)
  8. 5 Security
  9. 6 Performance and Test Data
    1. 6.1 Connection
    2. 6.2 Advertising
    3. 6.3 Stability Testing
    4. 6.4 Interoperability
  10. 7 Tools and Development Support
    1. 7.1  SmartRF Packet Sniffer 2
    2. 7.2  Smart RF Studio 8
    3. 7.3  Energy Trace
    4. 7.4  Code Composer Studio
    5. 7.5  SimpleLink Connect App
    6. 7.6  Uniflash
    7. 7.7  Antenna Reference Designs
    8. 7.8  Design Review Service
    9. 7.9  SysConfig
    10. 7.10 BTool
    11. 7.11 GitHub
    12. 7.12 SimpleLink Academy
  11. 8 Known Limitations
  12. 9 References
  13. 10Revision History

6.3 Stability Testing

TI Bluetooth LE stack is tested for stability in several configurations as part of our extensive stability testing on device and connected system level. In general, TI Bluetooth LE stack is tested in several test scopes which are listed below.

Advertise Stability (1M Phy) using simple_peripheral and Multirole examples:

  • Maintain legacy set for 48 hours.
  • Maintain Advertising set with RPA/public address for 48 hours.
  • Run Connect and Disconnect operations for 48 hours.
  • Run Pairing & Bonding operation for 48 hours.

Scan Stability (1M PHY) using host_test:

  • Run Scanning for 48 hours.
  • Run Scan operations for different windows size.
  • Run Continuous Scan operation for 48 hours.
  • Run scan operations while in connection for 48 hours.

Connection Stability (1M, 2M and Coded PHYs) with Peripheral, Central and Multirole devices:

  • Maintain 1 Secure Connection (2 for multirole) for 48 hours.
  • Run GATT Read and Write connection for 48 hours.
  • Run GATT Read and Write operations for 48 hours.
  • Run Connection parameter update operations for 48 hours.

BLE Profiles (1M, 2M and Coded PHYs) running the data_stream example:

  • Maintain secure connection for 24 hours.
  • GATT operations for 24 hours.
  • MTU exchange operations for 24 hours.