TI BLE5-Stack 9.10.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
- Dependencies
- Device Support
- Development Board Support
- Versioning
- Product Security Vulnerabilities
- 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™ CC23xx and CC27xx families of wireless MCUs.
Key features overview of BLE5-Stack 9.10.00:
BLE Features | Support Status |
---|---|
Legacy advertising | Supported |
Connection using the LE 1M PHY | Supported |
Pairing and link encryption | Supported |
Bonding | Supported |
Accept list for advertiser | Supported |
Direct Test Mode (DTM) | Supported |
L2CAP Connection Oriented Channels (CoC) | Supported |
Extended advertising | Supported |
LE 2M and Coded PHYs | Supported |
Privacy | Supported |
Adjustable TX Power | Supported |
RSSI Reading | Supported |
Over The Air Download | Supported |
LE Secure Connection | Supported |
Data Length Extension (DLE) | Supported |
Periodic Advertising | Supported |
Periodic Scanning | Supported |
Adaptivity | Supported (China MIIT and EU RED Regulation) |
LE Power Control | Preview (Not yet certified) |
Channel Sounding | Preview (Not yet certified) * |
Direction Finding (AoA) | Not Supported (Planned for a future release) |
- Channel Sounding measurements results are not yet optimized.
The BLE5-Stack provides a set of basic examples designed to accelerate customer product development providing easy-to-use, out-of-the-box demonstrations of the full hardware capabilities.
Available Examples (CC23xx) | Description |
---|---|
basic_ble | Example project where the device can be configured to operate as a Bluetooth LE peripheral, central, or both. |
basic_ble_extctrl | Example that implements connection handover used to control a device running basic_ble device through external commands sent over UART. |
basic_ble_oad_offchip | Same as basic_ble with OAD off-chip functionality to enable wireless firmware updates. |
basic_ble_oad_onchip | Same as basic_ble with OAD on-chip functionality to enable wireless firmware updates. |
basic_ble_profiles | Same as basic_ble with additional custom profiles: Continuous Glucose Monitoring and Glucose Profile & Health Thermometer Profile. |
basic_ble_ptm | Same as basic_ble with Production Test Mode (PTM) functionality. |
basic_dual_image | Same as basic_ble with OAD dual image functionality. |
basic_persistent | Permanently resident application that implements OAD profile. |
ble_controller | Example project that implements the Bluetooth LE controller layer. |
car_node | Example project to support Channel Sounding, BLE Handover, and Connection Monitor Role only available for CC2340R53 device. |
data_stream | Example project which implements data stream profile to enable UART over Bluetooth LE. |
key_node | Example project to support Channel Sounding. |
host_test | Example project which can be used with Bluetooth Tester through UART or SPI. |
Available Examples (CC27xx) | Description |
---|---|
basic_ble | Example project where the device can be configured to operate as a Bluetooth LE peripheral, central, or both. |
basic_ble_extctrl | Example that implements connection handover used to control a device running basic_ble device through external commands sent over UART. |
basic_ble_oad_onchip | Same as basic_ble with OAD on-chip functionality to enable wireless firmware updates. |
basic_ble_profiles | Same as basic_ble with additional custom profiles: Continuous Glucose Monitoring and Glucose Profile & Health Thermometer Profile. |
basic_ble_oad_dual_image | Same as basic_ble with OAD dual image functionality. |
basic_persistent | Permanently resident application that implements OAD profile. |
data_stream | Example project which implements data stream profile to enable UART over Bluetooth LE. |
ble_controller | Example project that implements the Bluetooth LE controller layer. |
car_node | Example project to support Channel Sounding, BLE Handover, and Connection Monitor Role. |
key_node | Example project to support Channel Sounding |
host_test | Example project which can be used with Bluetooth Tester through UART or SPI. |
Examples showcasing support for Apple® Find My® Network are available in the Find My Network Accessory Protocol (FMNAP) Plugin for SimpleLink devices (SIMPLELINK-LOWPOWER-FMNAP). Access to the plugin requires an MFi licence and a myTI account. Access requests should be filled through the online request form.
Additional information about TI’s Bluetooth Low Energy solutions can be found at www.ti.com/ble
BLE5-Stack Documentation
The SimpleLink™ Low Power F3 Software Development Kit (SDK) allows easier product development by combining TI-drivers and the Bluetooth LE protocol stack in one unified SDK. All BLE5-Stack sample applications are based off the FreeRTOS Kernel. 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_lowpower_f3_sdk_9_10_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_lowpower_f3_sdk_9_10_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
- Bluetooth LE Channel Sounding preview.
- Bluetooth LE Connection Monitor with BLE Stack integration for CC23xx and CC27xx devices.
- Bluetooth LE Power Control Preview for CC23XX and CC27xx devices.
- Bluetooth LE Connection Handover with GATT Layer.
- Certification of devices to be compliant with China MIIT (Ministry of Industry and Information Technology) and the EU RED (European Union Radio Equipment Directive) regulations on 2.4GHz.
ID | Summary |
---|---|
BLE_LOKI-2898 | Adaptivity Support on CC23XX and CC27XX devices |
BLE_LOKI-2882 | Integrate and Enable Connection Monitor functionality |
BLE_LOKI-2868 | GATT Battery Service Profile included in Basic BLE Profiles example |
BLE_LOKI-2866 | Support Bluetooth LE migration to CC2340R53-Q1 device |
BLE_LOKI-2825 | Support BLE migration to CC2755P10/CC2755R10 |
BLE_LOKI-2824 | Support BLE migration to CC2745P10-Q1/CC2745R7-Q1 |
BLE_LOKI-2752 | RSSI Monitor |
BLE_LOKI-2734 | BLE Stack Folders Renaming |
BLE_LOKI-2619 | Support Channel Sounding Connection Handover |
BLE_LOKI-2366 | Post Processing Algorithm Integration and Send results over L2CAP |
BLE_LOKI-1981 | Support BLE migration to CC2340R53-WCSP |
BLE_LOKI-1861 | Multiple Antennas |
BLE_LOKI-1839 | Power Control |
BLE_LOKI-1835 | Support GATT Handover |
BLE_LOKI-1791 | Channel Sounding Module |
BLE_LOKI-1444 | Add support for Scanner Role with 50 bonded devices |
BLE_LOKI-1441 | Add support for Innitiator Role with 50 bonded devices |
Fixed Issues
ID | Summary |
---|---|
BLE_LOKI-3096 | Connection Parameter Update from Android is Rejected |
BLE_LOKI-3042 | Add an Health check functionality to validate RPA address or AES failure |
BLE_LOKI-2713 | SysConfig option to enable Flow Control is misleading |
BLE_LOKI-2549 | L2CAP CoC fails to re-establish on reconnection |
BLE_LOKI-2520 | Broken Link on SysCfg (General Configuration / Max Size of PDU) |
BLE_LOKI-2493 | GATT_Indication/GATT_Notification does not check link status if authentication is set to false |
BLE_LOKI-2072 | Incorrect and misleading warning raised when enabling Connectable AE with 2M PHY as secondary PHY in SysConfig |
BLE_LOKI-1703 | SysConfig raises error when setting scan duration and scan period to 0 |
BLE_LOKI-1391 | Commands HCI_EXT_SetFreqTuneCmd and HCI_EXT_SaveFreqTuneCmd do not exist for CC23xx and CC27xx |
Known Issues and Limitations
ID | Summary |
---|---|
BLE_LOKI-3219 | Calling CM Start API with time_delta smaller than the actual value may result in CMR becoming stuck |
BLE_LOKI-3218 | Calling CM Start API with max_num_conn_events greater than 1, results in only 1 CM monitoring attempt |
BLE_LOKI-3214 | CMR does not check whether the access address is already in use by the current monitor session and creates duplicated sessions. |
BLE_LOKI-3209 | Potential Memory Leak while L2CAP Connect and Reconnect |
BLE_LOKI-3208 | BLE Agent GUI not able to calculate time offset correctly when running connection handover demo which causes frequent unsuccessful handover sessions |
BLE_LOKI-3207 | Central Role Heap Allocation Is Not Consistent While Connect and Disconnect with Multiple devices |
BLE_LOKI-3199 | BLE Device Is not identified by the BLE Agent package |
BLE_LOKI-3172 | L2CAP Channel is not established after connection is handed over backwards |
BLE_LOKI-3097 | After changing PHY both devices continue to send Power Reporting events |
BLE_LOKI-3073 | Car Node can only support 1 CS ranging |
BLE_LOKI-2842 | CC23XX and CC27XX family of devices rounds down Tx power values that are not in the power table |
BLE_LOKI-2650 | CC2745R10Q1 Central Role Fails to Switch Connection PHY to Coded While Holding 16 Connections |
BLE_LOKI-2648 | Connection may be unstable with Coded PHY when Access Address has high cross-correlation with the preamble |
BLE_LOKI-2373 | CC2340R5 MAX periodic adv list size is hard coded and can't be configure by SysConfig |
BLE_LOKI-2358 | CC2340R5 Basic MR printed peripheral initial RPA after bond and pair, instead of its Public Address |
BLE_LOKI-2108 | IOS device doesn't find peer running extended ADV with secondary PHY of 1M |
BLE_LOKI-1630 | Extended Advertisement Reports Are Not Filtered When SCAN_PARAM_FLT_DUP is Enabled |
Upgrade and Compatibility Information
The BLE5-Stack 9.10.00 supports the following devices:
- SimpleLink CC2745R10-Q1 devices with silicon revision E
- SimpleLink CC2340R53 devices with silicon revision B
- SimpleLink CC2340R2 devices with silicon revision A
- SimpleLink CC2340R22 devices with silicon revision B
- SimpleLink CC2340R5 devices with silicon revision B
- SimpleLink CC2340R5-Q1 devices with silicon revision B
No support for previous silicon revisions or LaunchPad™ development kits using earlier silicon revision. If you’re unsure of the revision number of your device, please see the Package Symbolization and Revision Identification section of the Errata Note.
The following compilers are supported (see the SDK release notes for specific version numbers):
- TI ARM Clang Compiler
- IAR Embedded Workbench
Qualification
The applicable Design Number for this release is Design Number Q301991 Please take a look at the following application note for further details on How to Certify Your Bluetooth Product.
Dependencies
The correct dependencies for this SDK release must be used to ensure proper functionality of the software and compatibility with the hardware. Using incorrect dependencies will very likely lead to unintended and unexpected behavior. See top-level release notes for overall SDK dependencies.
Device Support
This release supports development of single-mode Bluetooth LE applications on 2.4 GHz 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 wireless MCU development kits listed in the top-level 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.
Product Security Vulnerabilities
- Vulnerability reports and mitigations can be found on https://www.ti.com/PSIRT`