TI BLE5-Stack 2.02.09.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.09.00 has been Bluetooth 5.2 qualified and is available for production use.
Key features of BLE5-Stack 2.02.09.00:
- Our new devices CC13x1x, CC26x1x, CC1352P7, CC2652R7, CC26x4x, CC2652xSIP and CC2651RSIPA 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 Bluetooth LE 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)
- 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 Low Power F2 Software Development Kit (SDK) allows easier product development by combining TI-RTOS and the Bluetooth LE protocol stack in one unified SDK. Key documents needed for Bluetooth LE 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_7_40_00_xx installer package on a supported host operating system build machine with Administrator privileges
- Install the simplelink_cc13xx_cc26xx_sdk_7_40_00_xx installer package
- 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
Bluetooth Mesh examples are not supported in this SDK release. Please reference the 6.30.00.84 SDK release to see Bluetooth Mesh examples
| ID | Summary |
|---|---|
| BLE_AGAMA-4505 | [BASIC BLE] [Profiles] Included Glucose Profile support in Basic BLE Profiles on CC13X4 |
| BLE_AGAMA-4129 | [BASIC BLE] [Profiles] Included Health Thermometer Profile support in Basic BLE Profiles on CC13X4 |
Fixed Issues
| ID | Summary |
|---|---|
| BLE_AGAMA-4839 | Critical Section order not optimal in ICall_leaveCSImpl & ICall_enterCSImpl functions |
| BLE_AGAMA-4785 | In rare occasions, DUT does not respond to LLCP Encryption Request |
| BLE_AGAMA-4724 | Extended disconnect/reconnect test sometimes leads to exception in Multirole with one peripheral and two centrals |
| BLE_AGAMA-4723 | Stack generates unexpected RPA |
| BLE_AGAMA-4710 | [Multi-Connection] CC1354P10-1 Fails to save 16th bond as peripheral and 15th bond as central |
| BLE_AGAMA-4585 | Connection handle and timestamp for GAP_CB_PHY_UPDATE may be incorrect when multiple connections are maintained |
| BLE_AGAMA-4580 | Connection Event Report reports incorrect channel |
| BLE_AGAMA-4573 | [CC2642] Peripheral fails to respond to CON_IND when using GAP_ADV_WL_POLICY_WL_ALL_REQ and connected to Central using RPA with Random ID |
| BLE_AGAMA-4559 | Under certain conditions, incorrect channel is calculated for connection event as peripheral |
| BLE_AGAMA-4480 | [Basic Example] Basic Broadcaster Doesn't Advertise |
| BLE_AGAMA-4425 | BLE Stack does not dequeue ATT msg during fuzzing test |
| BLE_AGAMA-4250 | The rtls_coordinator mixes up scanned extended advertisements' device address |
| BLE_AGAMA-3838 | host_test may raise a UTIL_SystemErrorEvent with status INVALID_INTERRUPT_ID when UART data overflow |
| BLE_AGAMA-3169 | Connecting twice to the same device causing wrong count of connections and a memory leakage |
Known Issues and Limitations
| ID | Summary |
|---|---|
| BLE_AGAMA-4855 | [Multi Connect] CC2651P3 Central fails to connect to more than 5 testers with privacy enable |
| BLE_AGAMA-4846 | [Data Stream][Display] display_printf() is fail when try to print data larger then threshold of 300-500 bytes |
| BLE_AGAMA-4837 | [IOP][Android 14][One Plus 11] With privacy enabled, reconnection fails after after Pairing & Bonding |
| BLE_AGAMA-4830 | [SWAT] Scanner failes after receiving an incorrect event type |
| BLE_AGAMA-4484 | multi_role FreeRTOS support removed from CC13XX / CC26XX |
| BLE_AGAMA-4354 | Under some conditions, CREATE_SYNC or AOA_ENABLE are not sent by RTLS Manager |
| BLE_AGAMA-4324 | [Build] -Path Too Long-Error[Ms003] In simple_peripheral_oad_offchip_src_iar |
| BLE_AGAMA-4029 | Updating BLE Scan Response Data Prevents BLE ADV from being sent when using >1 Advertisement set. |
| BLE_AGAMA-4009 | [RTLS] - RTLS tests with multiple responders stopped after several start/stop AOA commands |
| BLE_AGAMA-3896 | [RTLS] In robustness test with multiple responders, Passive sometimes does not respond to AOA start or stop commands |
| BLE_AGAMA-3774 | Under certain conditions the CC2652R1 failed to synchronize to periodic advertising |
| BLE_AGAMA-3752 | [CC2651] Host_test memory limitation using CCS+TI-CLANG |
| 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-3427 | System goes to halAssertHandlerExt when more than LL_MAX_NUM_CTRL_PROC_PKTS are queued |
| BLE_AGAMA-3381 | Simple Peripheral example application spinlocks while pairing, when compiled with IAR in Debug configuration |
| 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-2266 | Central not able to find peer device advertising Extended ADV with aux offset bigger than 16.3ms |
| 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-1675 | IOP: Device fails to pair with Meizu Pro 7 |
| 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.09.00 only supports SimpleLink CC13xx and CC26xx devices with silicon revisions E and F. 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 (LE) 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.2 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 Bluetooth LE-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.