TI BLE5-Stack 2.02.04.00 Release Notes
Table of Contents
- Introduction
- BLE5-Stack Documentation
- Installation and Usage
- What’s New
- Fixed Issues
- Known Issues and Limitations
- Upgrade and Compatibility Information
- Qualification
- Operating System Support
- Dependencies
- Device Support
- Development Board Support
- Validation
- Versioning
- Technical Support and Product Updates
Introduction
The BLE5-Stack is a set of sample applications, tools, APIs and protocol stack libraries that enable engineers to develop Bluetooth ® 5 standalone or network processor LE applications on the SimpleLink™ CC13xx and CC26xx family of wireless MCUs.
This Bluetooth 5 (BLE5-Stack) release includes qualification for Bluetooth 5.2 in addition to support for the existing core specifications (4.0, 4.1, 4.2) in addition to core specification 5.0 and 5.1 LE features such as: Direction Finding (AoA - Connected and Connectionless CTE), High Speed Mode (2 Mbps PHY), Long Range (LE Coded 125kbps and 500kbps PHYs), Advertisement Extensions (AE), Periodic Advertisements, Privacy 1.2.1 and Channel Selection Algorithm #2.
As with all Bluetooth core specifications that support the Low Energy (LE) feature, devices implementing the LE feature of Bluetooth 5 are backward compatible with Bluetooth 4.2, 4.1 and 4.0 LE capable devices.
BLE5-Stack 2.02.04.00 has been Bluetooth 5.2 qualified and is available for production use.
Key features of BLE5-Stack 2.02.04.00:
- Our new devices CC13x1x, CC26x1x, CC1352P7, CC2652R7 and CC2652RSIP are supported in the examples provided
- Bluetooth 5.2 qualified release for production
- Bluetooth Mesh Profile 1.0.1 is also qualified
- Supports the following Bluetooth 5 LE features: High Speed Mode (2 Mbps PHY), Long Range (LE Coded 125 kbps and 500 kbps PHYs), Advertisement Extensions (AE), Periodic Advertisements, Privacy 1.2.1 and Channel Selection Algorithm #2
- Supports the following Bluetooth 5.1 LE features: Direction Finding (AoA - Connected and Connectionless CTE)
- Support for all Bluetooth 4.2 LE features including LE Secure Connections and Data Length Extension (DLE)
- Integrated BLE Host and Controller supporting System-on-chip (SoC) standalone or network processor dual-device configurations
- Project Zero sample application demonstrates typical peripheral role operations such as controlling LEDs, identifying button states and sending strings of data from a smartphone to the LaunchPad™
- Standalone Peripheral, Broadcaster and Central sample applications to jump start development
- Full integration with TI-RTOS for real-time scheduling, automatic power management and utilizing peripheral device drivers
- Free code development option with Code Composer Studio™ (CCS)
- All example applications now utilize the BLE5-Stack in ROM to maximize application flash memory availability
- Simple_central supports up to 32 concurrent connections
- Secure Boot and Secure Over-the-Air Download (OAD) firmware upgrade support for updating device firmware wirelessly
Additional information about TI’s Bluetooth Low Energy solutions can be found at www.ti.com/ble
BLE5-Stack Documentation
The SimpleLink CC13xx and CC26xx Software Development Kit (SDK) allows easier product development by combining TI-RTOS and the BLE protocol stack in one unified SDK. Key documents needed for BLE application development include:
Installation and Usage
- To build the sample applications with this SDK a supported Integrated Development Environment (IDE) must be installed (refer to Dependencies below)
- Install the simplelink_cc13xx_cc26xx_sdk_5_40_00_xx installer package on a supported host operating system build machine with Administrator privileges
- The default install path for Windows is C:\ti\simplelink_cc13xx_cc26xx_sdk_5_40_00_xx
- Changing the default install path and/or drive letter may require updating project variables. Do not use a space in the install path
- It is recommended to make a backup of the installation in order to revert modifications to the SDK
What’s New
| ID | Summary |
|---|---|
| BLE_AGAMA-3631 | Add multi_role example for CC2651P3 device |
| BLE_AGAMA-3588 | Added RCOSC support to Project Zero |
| BLE_AGAMA-3538 | Update SysConfig to support Authentication pairing only feature and OOB pairing |
Fixed Issues
| ID | Summary |
|---|---|
| BLE_AGAMA-3716 | GapAdv_enable/disable sometimes creates null pointer access |
| BLE_AGAMA-3634 | [Mesh][AE][Stability] Mesh nodes with AE fail to send/receive messages after certain amount of messages are being transferred in the network |
| BLE_AGAMA-3633 | [RTLS] Passive and connection monitor might fail to monitor one of the links when running 8 central responders topology |
| BLE_AGAMA-3626 | SysConfig does not update the field “Complete Local Name” when changing the device name |
| BLE_AGAMA-3617 | Resolving list does not overwrite LRU entry when GAPBOND_LRU_BOND_REPLACEMENT is enabled |
| BLE_AGAMA-3613 | [MESH] [AE] Low reliability in multi-hop scenarios vs. Legacy Adv. |
| BLE_AGAMA-3591 | [Mesh][eRPC] Source mesh node with AE support gets stuck when sending many roundtrip messages in a row |
| BLE_AGAMA-3590 | Secondary task gets interrupted by connections even when priority is set to high |
| BLE_AGAMA-3581 | [Mesh][eRPC] (CC2652R7) Mesh LPN using eRPC is stuck after mesh init and static provisioning |
| BLE_AGAMA-3533 | [Mesh] Input/output OOB string value fails for PB-ADV (Input/Output OOB number value is working) |
| BLE_AGAMA-3390 | [Mesh][eRPC] Callback server raise the wrong model index number when running 2 vendor model on the same element |
| BLE_AGAMA-3361 | Sysconfig board migration tool does not allow to migrate to CC2642 |
Known Issues and Limitations
| ID | Summary |
|---|---|
| BLE_AGAMA-3752 | Using host_test, GapScan_enable returns with GAP_EVT_INSUFFICIENT_MEMORY under certain test conditions |
| BLE_AGAMA-3747 | [MESH][AE][eRPC] ~100% missing packets more than 3 hops while GATT Bearer is enabled |
| BLE_AGAMA-3606 | [Mesh][Stability] Messages might stop after ~3 hours in a network with more than ~20 nodes |
| BLE_AGAMA-3597 | [Mesh] LPN might fail to maintain friendship with ble.scanLatency < 10, when Display module is enabled |
| BLE_AGAMA-3556 | [Mesh][IOP] LPN fails to configure after provisioning over PB-GATT with BlueZ |
| BLE_AGAMA-3543 | [Build] Simple Mesh and Peripheral OAD onchip example fail to compile with GATT Bearer for CCS/TICLANG due to memory limitation |
| BLE_AGAMA-3540 | [RTLS Agent] RTLS Agent sometimes shows exception when there are huge amount of data to be processed in the PC |
| BLE_AGAMA-3486 | Device asserts upon connection when HeapMem and HeapTrack is used |
| BLE_AGAMA-3391 | [Mesh][eRPC] Limitation - Mesh node with eRPC unable to transmit messages > 221B |
| BLE_AGAMA-3388 | [Mesh] Relay fails to transmit segmented message without re-transmission (relay re-transmit = 0) |
| BLE_AGAMA-3383 | Mesh stack delay work API is limited to a maximum delay of uint32 maximum value (42,949,672 milliseconds) |
| BLE_AGAMA-3381 | Simple Peripheral example application spinlocks while pairing, when compiled with IAR in Debug configuration |
| BLE_AGAMA-3258 | [Build] Agama Lite examples fail to build for Debug configuration, due to insufficient RAM |
| BLE_AGAMA-3193 | [OAD] In all the OAD examples, the OAD doesn't work for BAW/704k device when working with TI's SimpleLink Starter Mobile Application |
| BLE_AGAMA-3169 | Connecting twice to the same device causing wrong count of connections and a memory leakage |
| BLE_AGAMA-3107 | [CLAOA] parsing errors when trying to parse CL_AOA_RESULT_RAW events when using periodic interval smaller than 300ms |
| BLE_AGAMA-3077 | [RTLS] CTE reception on the 2M PHY do not meet spec requirements |
| BLE_AGAMA-3076 | [RTLS] CTEs sent on the 2M PHY do not meet spec requirements |
| BLE_AGAMA-3024 | [MESH] [IOP] Mesh DUT is not publishing its mesh supported roles (Unable to config Mesh node) with iPhone |
| BLE_AGAMA-2917 | [Build] Persistent Application failed to compile in debug configuration due to memory limitation with all platforms |
| BLE_AGAMA-2845 | [CLAOA] Scanner shows only one IQ report when advertiser sends multiple CTE in one periodic train with 2M PHY |
| BLE_AGAMA-2266 | Central not able to find peer device advertising Extended ADV with aux offset bigger than 16.3ms |
| BLE_AGAMA-2245 | [Simple Peripheral] Number of connections shows zero after a connection if the previous connections were unsuccessful |
| BLE_AGAMA-2033 | [RTLS] Passive Application is not functioning well in Debug configuration. WA: Change the optimization in Debug configuration to High (as in Release) |
| BLE_AGAMA-2010 | [Multi-Sensor] Updating Report Interval Have no effect |
| BLE_AGAMA-1970 | [LPSTK][Multi-Sensor] Some of the Multi Sensor services fail to initiate or open when loading up |
| BLE_AGAMA-1675 | IOP: Device fails to pair with Meizu Pro 7 |
| BLE_AGAMA-1435 | [Multi-Sensor] Accelerometer Service Disappears After First Connection |
| BLE_AGAMA-1416 | OAD offchip examples needs additional reset to load Factory Image |
| BLE_AGAMA-546 | Central applications do not receive timeout when connection fails |
| BLE_AGAMA-139 | When using multi-role, the random address will display in the serial terminal, instead of the “Work With” selection |
| BLE_AGAMA-80 | The NVS Driver is now used for bond storage. It is not possible to retain OSAL_SNV contents when upgrading from earlier BLE5 1.1.x releases. |
Upgrade and Compatibility Information
The BLE5-Stack 2.02.04.00 only supports SimpleLink CC13xx and CC26xx devices with silicon revision E. No support for previous silicon revisions or LaunchPad™ development kits using earlier silicon revisions. If you’re unsure of the revision number of your device, please see the Package Symbolization and Revision Identification section of the Errata Note.
As a supplier of Bluetooth® Low Energy (BLE) solutions with a focus on interoperability and broad market adoption, we recommend to transition from proprietary Real Time Localization Toolbox (RTLS) software examples to the new RTLS software examples based on the Bluetooth 5.1 specification. These examples are included in this software development kit. For further information please contact your local TI sales representative.
Qualification
The Bluetooth low energy software stack (BLE5-Stack) for CC13xx_CC26xx BLE-enabled wireless MCUs uses Bluetooth Qualified Components, which allow customers to substantially reduce the testing required to meet Bluetooth end product listing (EPL) qualification requirements while providing flexibility to the device configuration. Bluetooth SIG rules specify that Qualified Components have a validity period of three (3) years at which time they may not be available for new End Product Listings (EPLs). For information on the applicable QDID’s for this release, please refer to the application report SWRA601 - How to Qualify Your Bluetooth Low Energy Product.
As mentioned in the Known Issues and Limitations section, the Bluetooth low energy software stack (BLE5-Stack) for CC13xx_CC26xx CTE reception and transmission for AoA on the 2M PHY is not fully compliant with the Bluetooth specifications. As a consequence, AoA enabled projects cannot be qualified to operate on the 2M PHY.
Operating System Support
Please refer to the SDK release notes.
Dependencies
The BLE5-Stack sample applications were built & tested with the IDEs and listed in the top-level SDK release notes.
Note: Earlier IDE/toolchain versions are not supported and compatibility with newer versions of supported IDEs is not assured.
Device Support
This release supports development of single-mode Bluetooth LE applications on 2.4 GHz and multi-band wireless MCUs listed in the top-level SDK release
Development Board Support
This release supports development of single-mode Bluetooth LE on 2.4 GHz and multi-band wireless MCU development kits listed in the top-level SDK release notes
Validation
The BLE5-Stack sample applications were built & tested with the IDE’s and toolchains mentioned in the SDK release notes.
Versioning
This product follows a version format, M.mm.pp.bb, where:
- M is a 1 digit major number,
- mm is a 2 digit minor number,
- pp is a 2 digit patch number,
- bb is a 2 digit incrementing build counter.