TI BLE5-Stack 2.02.00.01 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™ CC13x2 and CC26x2 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.00.01 has been Bluetooth 5.2 qualified and is available for production use.
Key features of BLE5-Stack 2.02.00.01:
- Bluetooth 5.2 qualified release for production
- Enables development for Bluetooth Mesh applications.
NEW in BLE Stack version 2.02.00.01 (SDK version 4.40.04.xx): The Bluetooth Mesh Profile 1.0.1 is now 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
- Secure Over-the-Air Download (OAD) firmware upgrade support for updating device firmware wirelessly
- 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 CC13x2 and CC26x2 Software Development Kit (SDK) allows easier product development by combining TI-RTOS and the BLE protocol stack in one unified SDK. All BLE5-Stack sample applications are based off the TI-RTOS Kernel. Key documents needed for BLE application development include:
Installation and Usage
- To build the sample applications with this SDK a supported a supported IDE must be installed (refer to Dependencies below)
- Install the simplelink_cc13x2_26x2_sdk_4_40_04_xx installer package on a supported host operating system build machine with Administrator privileges
- The default install path for Windows is C:\ti\simplelink_cc13x2_26x2_sdk_4_40_04_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-2966 | [MESH] Added support for BLE Mesh |
| BLE_AGAMA-2961 | [MESH] Qualified Mesh Profile solution |
| BLE_AGAMA-2958 | Support Periodic Advertisement feature |
| BLE_AGAMA-2957 | Support Connectionless AoA feature |
| BLE_AGAMA-2950 | Scheduler Improvements - Connections Scheduling Fairness & Connection Priority Support |
| BLE_AGAMA-2817 | Add Authenticated Pairing Only mode |
| BLE_AGAMA-1785 | Expand multirole maximum number of connections to 16 |
Fixed Issues
| ID | Summary |
|---|---|
| SCCM-64 | Corrected the security payload offset calculation in the image header for Off-Chip OAD |
| SCCM-63 | Enforced the program entry address to be within the OAD image range for On-Chip and Off-Chip OAD |
| SCCM-62 | Corrected the input parameter size for hash calculation to 32-bit for Off-Chip OAD |
| SCCM-61 | Add protections against zero image length and zero hash value for Off-Chip OAD |
| SCCM-60 | Enabled authentication of the persistent application image type for On-Chip OAD |
| BLE_AGAMA-3015 | [MESH] Simple Mesh Node & Peripheral examples pairing fails |
| BLE_AGAMA-2913 | [MESH] IAR Bluetooth LE Mesh examples have a few compilation warnings |
| BLE_AGAMA-2887 | Enabling co-ex for host test causes ICall_abort |
| BLE_AGAMA-2802 | Update persistent app projects to allow for authentication |
| BLE_AGAMA-2732 | Connection dropped with two Android master devices where second continuously reconnects |
| BLE_AGAMA-2715 | Invalid Adv Handle Returned by function llDmmSetThreshold |
| BLE_AGAMA-2638 | [AoA - PHY tests] The LE Test packet interval in LE Direct Test Mode is not spec compliant |
| BLE_AGAMA-2636 | [AoA - PHY tests] The IQ reports stops being sent by the device |
| BLE_AGAMA-2635 | [AoA - PHY tests] The Tx tests fail if payload length less to 38 bytes |
| BLE_AGAMA-2615 | Unable to re-start advertisement with multi role when connected to another Peripheral and using filter accept list |
| BLE_AGAMA-2613 | Fixed issue where file ti_ble_config.h always includes simple_gatt_profile |
| BLE_AGAMA-2546 | [GATT Builder] No error raised if several Callback functions have the same name |
| BLE_AGAMA-2513 | Device stops advertising when more than 5 connections are present |
| BLE_AGAMA-2500 | Under certain conditions, device becomes unresponsive after receiving connection request |
| BLE_AGAMA-2497 | Fixed buffer overflow bug in the OAD implementation |
| BLE_AGAMA-2479 | Fixed comments in ATT_HANDLE_VALUE_NOTI definition (att.h) |
| BLE_AGAMA-2344 | Occasional duplicate advertisement on the same channel |
| BLE_AGAMA-2061 | [Stability] Simple Peripheral fails to maintain more than 2 connections for more than 3H |
| BLE_AGAMA-1674 | Added API descriptions for items in out-of-band (OOB) pairing |
Known Issues and Limitations
| ID | Summary |
|---|---|
| BLE_AGAMA-3027 | [MESH] LPN provisioning and configuration is not always successful |
| BLE_AGAMA-3017 | [MESH] LPN/Friend is disconnecting and reconnecting sporadically |
| BLE_AGAMA-2947 | [MESH] Simple Mesh Node + Peripheral examples don't support proxy service & Provisioning over GATT |
| BLE_AGAMA-2918 | [MESH] [IOP] Instability trying to connect to provisioning/proxy services with devices running BlueZ |
| BLE_AGAMA-2917 | [Build] Persistent Application failed to compile in debug configuration due to memory limitation with all platforms |
| BLE_AGAMA-2914 | [MESH] BLE Mesh Examples do not have TICLANG Support |
| BLE_AGAMA-2861 | [MESH] LPN sending redundant ADV packets causing increased Power Consumption |
| 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-2094 | [GATT Builder] Missing characteristics attributes (Indication, Primary/Secondary, Authentication/Authorization) |
| 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 | [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-1652 | [RTLS] AoA multiple connection: When>4 slaves are connected, the passive node sometimes fails to track some of the connections. |
| 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.00.01 only supports SimpleLink CC13x2 and CC26x2 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.
Please note that Angle of arrival (AoA) has not yet gone through PHY qualification.
Qualification
The Bluetooth low energy software stack (BLE-Stack) for CC13x2_26x2 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.
Operating System Support
- Microsoft Windows® 7 SP1, Windows 8.1 or Windows 10
- Ubuntu 14.04 64-bit, Ubuntu 16.04 64-bit
- macOS Mojave
Dependencies
The BLE5-Stack sample applications were built & tested with the Integrated Development Environments (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 versions of the following Integrated Development Environments (IDEs) and tool chains listed in the top-level SDK release notes:
- Code Composer Studio using the TI C Compiler for Arm
- IAR Embedded Workbench for Arm
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.