SimpleLink™ Low Power F3 SDK 9.14.00.39 Release Notes

Introduction
Supported Features and Limitations
Documentation
What’s New
Migration to CCS v20+
Operating System Support
Dependencies
Device Support
Versioning
Technical Support and Product Updates

Introduction

The SimpleLink™ Low Power F3 Software Development Kit (SDK) delivers components that enable engineers to develop applications on the Texas Instruments SimpleLink CC23xx and CC27xx family of wireless microcontrollers (MCUs). This software toolkit provides a cohesive and consistent software experience for all SimpleLink CC23xx and CC27xx wireless MCU users by packaging essential software components, such as:

Bluetooth® Low Energy (Bluetooth LE) protocol stack
Zigbee® protocol stack supporting low power wireless mesh networks
Proprietary RF layer
TI Drivers

All of the above are provided in one easy-to-use software package along with example applications and documentation.

The SimpleLink MCU portfolio offers a single development environment that delivers flexible hardware, software, and tool options for customers developing wired and wireless applications. With code reuse across host MCUs, Wi-Fi™, Bluetooth Low Energy, Sub-1GHz devices and more, choose the MCU or connectivity standard that fits your design. A one-time investment with the SimpleLink software development kit allows you to reuse often, opening the door to create unlimited applications. For more information, visit TI SimpleLink Wireless Connectivity.

This is version 9.14.00.39 of the SimpleLink Low Power F3 SDK.

Supported Features and Limitations

LAES & HSM Limitations

The CC27xx family of devices now include a Hardware Security Module (HSM) for cryptographic and key storage features.

For crypto drivers that support the HSM and LAES, a failure in the HSM bootup process will be cached in the driver’s handle or will return a NULL handle (AESGCM, ECC, RNG Drivers). If the user attempts to perform an HSM operation later, it will return an error due to the cached initialization error. LAES operations would continue to function without issue in that case.

For drivers that support running operations on both hardware accelerators, for primarily AES drivers, a switch has been implemented so that the driver knows which engine to use to execute the operation on. This switch is part of the cryptography operation’s key. The key encoding of each key, part of the input parameters to drivers’ APIs, holds the value of the engine-of-choice.

To leverage the HSM hardware accelerator, the user has to call ‘CryptoKeyPlaintextHSM_initKey(..)’ or ‘KeyStore_PSA_initKeyHSM(..)’ API and pass in the plaintext key as well as the key length.
To leverage the LAES hardware accelerator, the user has to call ‘CryptoKeyPlaintext_initKey()(..)’ API and pass in the plaintext key as well as the key length.

NOTE:

Please refer to each driver’s top level header file for driver-specific limitations.
Mass erasing the CC27xx without retaining protected sectors will result in the erasure of the HSM firmware. Please see the Quick Start Guide: Build your first program for the CC27xx device on how to re-flash the HSM firmware.
Starting SDK version 9.10, the crypto drivers are removed from the drivers library and moved into a separate secure drivers library: source/ti/drivers/secure/lib.
Starting SDK version 9.10, if SysConfig generated libraries linker is not used, the secure drivers library will need to be added manually into the respective linker settings.

Documentation

What’s New

Bluetooth® LE Version 6 Qualification
Improvements to Channel Sounding ranginglib Algorithms
Bluetooth® LE Thread Priority Configuration
Zigbee Certification for CC27xx Device Family
Production-ready release for CC2340R53 WCSP including finalized characterized RF settings
New HSM Firmware Version 3.1.1
SDK Support for CC2755R10 WCSP

Refer to the Document Overview for the individual release notes and details for starting development with each SDK component.

Migration to CCS v20+

Starting from 9.10 SDK, CCS v20+ is the only supported CCS IDE. Please see Migration Guide for help migrating from CCS Eclipse IDE to CCS v20+ (Theia).

Documentation and Video collateral can be found here:

For more information on CCS v20+, see the CCS v20+ Users Guide.

Operating System Support

Microsoft® Windows 10/11
Ubuntu 22.04 LTS 64-bit
macOS 13.x

Dependencies

The sample applications included in this SDK were built & tested with the IDEs and listed below:

Compiler Settings: Default CCS configurations (optimization level z)

Note: Earlier IDE/toolchain versions are not supported and compatibility with newer versions of supported IDEs is not assured.

Device Support

This SDK supports the following SimpleLink CC23XX and CC27XX wireless MCUs:

Device	Orderable Part Number (OPN)	LaunchPad	Product Page	Migrate from these examples
CC2340R5RKP	CC2340R52E0RKPR, CC2340R52N0RKPR	LP-EM-CC2340R5	CC2340R5	N/A
CC2340R5RGE	CC2340R52E0RGER, CC2340R52N0RGER	N/A	CC2340R5	LP-EM-CC2340R5
CC2340R5RHB-Q1	CC2340R52E0WRHBRQ1	N/A	CC2340R5-Q1	LP-EM-CC2340R5
CC2340R53RKP	CC2340R53E0RKPR, CC2340R53N0RKPR	LP-EM-CC2340R53	CC2340R5	N/A
CC2340R53RHB-Q1	CC2340R53E0WRHBRQ1	N/A	CC2340R5	LP-EM-CC2340R53
CC2340R53WCSP	CC2340R53E0YBGR	N/A	CC2340R5	LP-EM-CC2340R53
CC2340R22RKP*	CC2340R22E0RKPR, CC2340R22N0RKPR	N/A	CC2340R2	LP-EM-CC2340R5
CC2340R2RGE*	CC2340R21N0RGER	N/A	CC2340R2	LP-EM-CC2340R5
CC2745R10-Q1	CC2745R10E0WRHARQ1, CC2745R10E1WRHARQ1	LP-EM-CC2745R10-Q1	CC2745R10-Q1	N/A
CC2755R10	CC2755R105E0WRHAR	N/A	CC2755R10	LP-EM-CC2745R10-Q1
CC2755R10WCSP	CC2755R105E0YCJR	N/A	CC2755R10	LP-EM-CC2745R10-Q1
CC2744R7-Q1	CC2744R74E0WRHARQ1	N/A	CC2744R7-Q1	LP-EM-CC2745R10-Q1
CC2745R7-Q1	CC2745R74E0WRHARQ1	N/A	CC2745R7-Q1	LP-EM-CC2745R10-Q1
CC2745P10-Q1	CC2745P10E0WRHARQ1	N/A	CC2745P10-Q1	LP-EM-CC2745R10-Q1

Note *CC2340R2x only supports Bluetooth Low Energy stack and PropRF stack examples, and does not support Zigbee stack.

Note Use SysConfig to obtain the proper configuration to migrate the project to target board.

The project configuration for each of the device variants mentioned can be obtained starting from the examples projects included in this SDK and using SysConfig migration GUI.

Examples of migration pathways:

A LaunchPad containing the device that this SDK provides examples for, or
A LaunchPad this SDK provides examples for that can be used to SysConfig-migrate to the device.

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.