TI BLE-Stack 3.01.01.58 Release Notes
Table of Contents
Introduction
The BLE-Stack 3.01.01.58 is a set of sample applications, tools and protocol stack libraries that enable engineers to develop embedded Bluetooth® 4.2 LE single-mode standalone or network processor applications on the SimpleLink™ CC2640R2F Bluetooth low energy (BLE) wireless MCU.
BLE-Stack 3.01.01.58 is production release and a maintenance update to BLE-Stack 3.1.0
Key features of BLE-Stack 3.01.01.58 :
- Fully qualified, royalty-free Bluetooth 4.2 protocol stack with support for all single-mode BLE roles: Peripheral, Central, Broadcaster and Observer
- Support for all Bluetooth 4.2 LE features including Secure Connections, Data Length Extension and Privacy 1.2
- Integrated BLE Host and Controller supporting System-on-chip (SoC) standalone or network processor dual-device configurations
- Full integration with TI-RTOS for real-time scheduling, automatic power management and utilizing peripheral device drivers
- Multi-role support for up to eight simultaneous connections in any supported role configuration
- Flexible Over-the-Air Download (OAD) device firmware upgrade options using on-chip or off-chip memory
- Support for developing applications on all QFN and WCSP CC2640R2F device package options
- Includes BT SIG adopted profiles for HID over GATT (HOGP), Glucose and Heart Rate as well as custom TI Audio and firmware update (OAD) profiles
- Support for automatic code generation of any adopted or custom Bluetooth GATT profile with TI’s plugin for Bluetooth Developer Studio (BDS)
- Ability to support additional sample applications using the CC2640R2 BLE Sample Applications Plugin
- Microstack configuration for broadcast-only applications
- Free code development option with Code Composer Studio™ (CCS) v7.3
Additional information about TI’s Bluetooth low energy solutions can be found at www.ti.com/ble
BLE-Stack Documentation
The SimpleLink CC2640R2 SDK allows easier product development by combining the TI-RTOS and BLE protocol stack in one unified SDK. All BLE-Stack sample applications are based off the TI-RTOS Kernel. Key documents needed for BLE application development include:
What’s New
- Updated CoreSDK component
Installation and Usage
- To build the sample applications with this SDK a supported IDE and toolchain must be installed (refer to Dependencies below)
- Install the simplelink_cc2640r2_sdk_1_50_00_58.exe package on a Windows® 7 SP1, Windows 8.1 or Windows 10 machine with Administrator privileges
- The default install path is C:\ti\simplelink_cc2640r2_sdk_1_50_00_58 and is referenced as $BLE_INSTALL$ in the documentation
- 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
Fixed Issues
- Incorrect Stack image version is reported for a successful on-chip Stack-only OAD upgrade
- ATT_FindInfoReq causes GATT_DB_OFF_CHIP enabled HostTest to crash
- Refer to CoreSDK release note for specific updates to the RF Driver
Upgrade and Compatibility Information
The BLE-Stack 3.01.01.58 maintains BLE API compatibility with BLE-Stack 3.1.0. Changes to SDK directory structure and TI-RTOS drivers may require updates to existing applications developed with BLE-Stack 3.1.0.
The CC2640R2 SDK uses a new directory & file format which differs from BLE-Stack 2.2.x and earlier SDK releases. Existing applications developed with earlier SDKs require porting to this release; however, most BLE APIs remain the same thus reducing the effort required to migrate to this release.
Operating System Support
The BLE-Stack sample applications in the CC2640R2 SDK are supported on the Microsoft Windows® 7 SP1, Windows 8.1 or Windows 10 build platform.
Dependencies
The BLE-Stack sample applications were built & tested with the following Integrated Development Environments (IDEs) and tools on Windows 7 SP1 and Windows 10 build platforms. All Bluetooth low energy applications must be developed using the components, such as the CoreSDK, within this SDK or with approved plugins. Using an IDE or toolchain version not listed below may result in compatibility issues with this SDK release.
- IAR Embedded Workbench: EWARM-8.11.2
- TI Code Composer Studio: CCS-7.03.00.00019
- C Compiler for ARM: 16.09.03.LTS
- XDCTools: 3.50.03.33
Note: Earlier IDE/toolchain versions are not supported and compatibility with newer versions of supported IDEs is not assured.
Device Support
This release supports single-mode Bluetooth 4.2 LE on the following SimpleLink wireless MCUs:
Note: This SDK does not support SimpleLink CC2640/CC2650/CC1350 devices or development kits with these devices.
Development Board Support
This release supports Bluetooth low energy applications on the following development kit: CC2640R2 LaunchPad
Known Issues and Limitations
- Number of simultaneous connections may be limited when attempting concurrent LE Secure Connections pairings. Suggested workaround is to perform LE Secure Connections pairing on an individual connection basis
- L2CAP Connection Oriented Channels are not available in multi-role configurations
- Central-role applications may have issues when discovering or connecting to non-bonded peer devices that Advertise with RPAs
- SignCounter can become out of sync with multiple connections and re-pairing
- Scan may not be started during a connection
- OAD target consistently fails to advertise after OAD reset is issued and a supervision timeout has occurred under a specific scenario. The scenario includes removing USB cable and reconnecting it to target after all images have been downloaded
- Non Connectable Advertisements cannot be done at 100ms intervals while in a connection. Workaround is to adjust TGAP_CONN_ADV_INT_MIN after the connection is formed
- Multi Role incorrectly setting gapRole_AdvEnabled when enabling non-connectable ADV
- GATT procedures that require encryption may incorrectly return Insufficient Authentication after LE Secure Connection Authentication Stage 2 completes. Workaround is to repeat the GATT procedure after Phase 3 / Transport Specific Key Distribution completes.
- BTool: Responses to connection parameter updates must manually sent within 30 seconds using HCI_LERemoteConnectionParameterRequestReply under the Adv.Commands -> HCI menu
- LE Secure Connections pairing failures observed with Nexus 5 running Android 6.0.1 build M4B30Z due to the Nexus device not sending the pairing confirm. Workaround is to use non-MITM pairing method (JustWorks).
- Link Layer Connection Parameters Request Procedure is disabled on most peripheral applications to improve connection parameter request compatibility with smart phone devices. L2CAP LE Signaling will be used instead. Define USE_LL_CONN_PARAM_UPDATE in application project to override this behavior
- RTOS Object Viewer (ROV) in IAR is not available when using autosized heap configuration. See the TI BLE Wiki for workaround
- Some BLE API doxygen links might not be functional
- Post-release updates to Known Issues will be posted on the TI BLE Wiki
Validation
TI BLE-Stack 3.01.01.58 was tested using the following components:
- TI Code Generation Tools for ARM: 16.09.03.LTS
- XDCTools: 3.50.03.33
- CC2640R2 LaunchPad
Refer to the TI BLE Wiki How to certify your product page for details regarding Bluetooth certification and how to reduce Bluetooth certification time by using TI’s Qualified Design ID (QDID).
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.