SimpleLink™ Low Power F3 SDK 8.40.02.01 Release Notes
Table of Contents
Introduction
The SimpleLink™ Low Power F3 Software Development Kit (SDK) delivers components that enable engineers to develop applications on the Texas Instruments SimpleLink CC23xx family of wireless microcontrollers (MCUs). This software toolkit provides a cohesive and consistent software experience for all SimpleLink CC23xx wireless MCU users by packaging essential software components, such as:
- Bluetooth® Low Energy (BLE) 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 100 percent 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 8.40.02.01 of the SimpleLink Low Power F3 SDK.
Supported Features and Limitations
CC23xx
TI Crypto Driver Overview | Support Status | Additional Comment |
---|---|---|
AES-CCM | Supported | |
AES-ECB | Supported | AESECB_oneStepDecrypt, AESECB_setupDecrypt not supported |
AES-GCM | Supported | |
AES-CTR | Supported | |
AES-CBC | Supported | AESCBC_oneStepDecrypt, AESCBC_setupDecrypt not supported |
AES-CTR-DRBG | Supported | |
AES-CMAC | Supported | |
SHA-256 | Supported | |
ECDH | Supported | |
ECIES | Supported | |
RNG | Supported | |
TRNG | Not Supported |
CC27xx
TI Crypto Driver Overview | Support Status | Additional Comment |
---|---|---|
AES-CCM | Supported | LAES + HSM |
AES-ECB | Supported | LAES + HSM |
AES-GCM | Supported | LAES + HSM |
AES-CTR | Supported | LAES + HSM |
AES-CBC | Supported | LAES + HSM |
AES-CTR-DRBG | Not Supported | This is supported via RNG |
AES-CMAC | Supported | LAES + HSM |
ECDH | Supported | HSM |
ECDSA | Supported | HSM |
RNG | Supported | HSM (AES-CTR-DRBG) |
TRNG | Supported | HSM |
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. 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, 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 associated with each key that is included as part of the user-provided data to the driver is where the user can specify which hardware accelerator to use.
- To leverage the HSM hardware accelerator, the user has to call ‘CryptoKeyPlaintextHSM_initKey(..)’ 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:
- 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 CC23xx or CC27xx device on how to re-flash the HSM firmware.
Documentation
What’s New
Certified Zigbee Stack.
Zigbee OTA support.
Minor bug fixes in SCCM.
Refer to the Document Overview for the individual release notes and details for starting development with each SDK component.
Upcoming Migration to CCS Theia
With the release of LPF3 8.40 SDK we are one step closer to fully moving to CCS Theia. Any new developers are recommended to start development with CCS Theia instead of CCS Eclipse. While existing developers can continue developing on CCS Eclipse based IDE we would recommend users of CCS Eclipse to take the time to transition to CCS Theia, see Migration Guide for help migrating from CCS Eclipse IDE to CCS Theia IDE.
Documentation and Video collateral can be found here:
- Getting Started Video
- CCS Academy
- Migration Guide
- CCS User’s Guide
- Getting Started Video
- Quick Tip Videos
Transition Roadmap
Version | Date | CCS IDE support |
---|---|---|
8.10 and 8.20 | 1H 2024 | CCS 12.x is the primary development environment. CCS Theia is also supported, but may have minor feature gaps. |
8.40 | 2H 2024 | Theia-based CCS is the primary development environment. CCS 12.x is deprecated - that is, it’s supported, but not recommended. |
9.10 and later | 2025 | Theia-based CCS (CCS v20+) is the only supported CCS IDE. |
Note: With the CCS v20+ release CCS Theia will be re-branded from “CCS Theia” to just “CCS” (or as Theia-based CCS as shown above).
For more information on CCS Theia, see the CCS Theia Users Guide.
Operating System Support
- Windows® Windows 10
- Ubuntu 20.04 LTS 64-bit
- macOS 13.x
Dependencies
The sample applications included in this SDK were built & tested with the IDEs and listed below:
- TI Code Composer Studio: CCS Eclipse 12.8.1 and CCS Theia 1.5.1
- TI ARM Clang Compiler: 3.2.2.LTS
- SysConfig: 1.22.0
- UniFlash: 8.8.1
- IAR Embedded Workbench: 9.60.3
Compiler Settings: Default CCS configurations (optimization level z)
Note: Earlier IDE/toolchain versions are not supported and compatibility with newer versions of supported IDEs are not assured.
Device Support
This SDK supports the following SimpleLink CC23XX & CC27XX wireless MCUs:
Device | Orderable Part Number (OPN) | LaunchPad | Migrate from these examples |
---|---|---|---|
CC2340R5RKP | CC2340R52E0RKPR, CC2340R52N0RKPR | LP-EM-CC2340R5 | N/A |
CC2340R5RGE | CC2340R52E0RGER, CC2340R52N0RGER | None | LP-EM-CC2340R5 |
CC2340R5RHB-Q1 | CC2340R52E0WRHBRQ1 | None | LP-EM-CC2340R5 |
CC2340R53RKP | CC2340R53E0RKPR, CC2340R53N0RKPR | LP-EM-CC2340R53 | N/A |
CC2340R22RKP* | CC2340R22E0RKPR, CC2340R22N0RKPR | None | LP-EM-CC2340R5 |
CC2340R2RGE* | CC2340R21N0RGER | None | LP-EM-CC2340R5 |
CC2745R10-Q1 | CC2745R10E0WRHARQ1 | None | 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.