This repository redistributes TI's SimpleLink Low Power F3 Software Development Kit (LPF3 SDK), a comprehensive software package for developing 2.4 GHz applications. The LPF3 SDK is one of many within the SimpleLink Low Power ecosystem.
The LPF3 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
- ProprietaryRF 2.4 GHz stack
- TI Drivers
Note: The Zigbee stack and examples are in early access for the 8.20 F3 SDK, and are not recommended for production.
This is version 8.20.00.119 of the LPF3 SDK. This release includes:
- Bluetooth Low Energy 5.4 support
- Bluetooth Advertisement Extension and Periodic Advertisement Qualification
- Early access to Zigbee Stack; not recommended for production
- CC2340R53 support
More details, including supported devices, IDEs, and toolchains are provided in the LPF3 8.20.00.119 SDK release notes.
Although TI also offers this SDK via a classic installer, we made it available as a Git repository to cater to various use cases:
- Smaller download size: By omitting documentation (in the docs/
directory) and examples (in the examples/ directory), the size of the SDK
can be reduced.
- The documentation is available online in the TI Developers Zone; just be sure to browse the appropriate version.
- Examples are provided in separate repositories, as noted below.
- CI/CD tooling integration: Using Git instead of installers can ease integration with CI/CD tooling pipelines.
- Increased visibility and change tracking: Git improves the ability to identify changes that may affect (or not!) your application.
- Simplified workflow for rebasing: Git makes it simpler for you to rebase your changes to new releases.
At the base of the SDK, you will find imports.mak; this file is used by the build system to find your installed dependencies. Please update imports.mak with full paths to where you have these dependencies installed on your system.
Notably for Windows users, the Windows variant of some tools may be required.
For example, the SYSCONFIG_TOOL
will need to have a .bat extension.
Refer to the comments in imports.mak for details on setting variables, and the release notes for recommended versions. Also see the Resources section below for download locations.
With a few exceptions (libraries without sources), the SDK is provided without
prebuilt libraries. To build the SDK libraries (after editing imports.mak as
described above!), navigate to the root of the SDK (the same directory where
imports.mak resides) and run GNU make
.
Assuming it is on your path, you can simply:
make
To clean/rebuild:
make clean
make
At this point, the libraries will be built and installed into the appropriate locations throughout the SDK.
Dependency download locations:
- SysConfig (SYSCONFIG_TOOL)
- This is also included with CCS
- TI CLANG Compiler (TICLANG_ARMCOMPILER)
- ARM Gnu Toolchain (GCC_ARMCOMPILER)
- CMake
- GNU make
- This is also included with CCS in the ccs/utils/bin/ directory (and
called
gmake
).
- This is also included with CCS in the ccs/utils/bin/ directory (and
called
Please consider creating a post on TI's E2E forum.