Install or Update an SDK#
Objective#
Install a new Software Development Kit (SDK) by using Silicon Labs Tool (SLT).
Installing an SDK#
You can install an SDK by defining package dependencies in a recipe file (recommended) or by installing a specific SDK version directly.
Install Using a Recipe File (Recommended)
The
pkg.sltrecipe file defines the packages and versions that your project depends on. Instead of installing each package individually, define the dependencies once inpkg.slt, and let SLT install and manage them together.Create a file named
pkg.slt:version = "0" [dependency] simplicity-sdk = "~"Note: The
~version specifier instructs SLT to install the latest compatible version instead of an exact version.Install a Specific SDK Version
To install a specific SDK version by using a recipe file, specify the SDK version in the
pkg.sltfile.version = "0" [dependency] simplicity-sdk = "2025.6.0"You can also install a specific SDK version directly.
slt install simplicity-sdk/2025.12.1
Step 1. Update Package Information#
slt update -a
This command updates installed packages.
Step 2. Install the New SDK Version#
Install a Single Package#
slt install <package-id>
Install Using a Recipe File#
slt install -f <recipe_file>.slt
Step 3. Verify the Installed SDK#
slt list
Additional Installation Examples#
Install the latest Simplicity SDK:
slt install simplicity-sdkInstall a specific version:
slt install simplicity-sdk/2025.12.1Install with the check-updates flag:
slt install simplicity-sdk/2025.12.1 --check-updatesInstall all packages from the default recipe file:
slt installInstall from a custom recipe file:
slt install -f myrecipe.sltInstall from a lock file (exact versions):
slt install -f pkg.lockNon-interactive mode for Continuous Integration/Continuous Delivery (CI/CD):
slt install -f pkg.slt --non-interactive
Package Installation Location#
By default, SLT installs packages in the following directories.
~/.silabs/slt/installs/ ├── conan/p/ ← SDKs and SDK extensions always here └── archive/ ← Some tools installed here
Note: Share the generated
pkg.lockfile to ensure that all team members use the same package versions. This approach makes builds reproducible across CI/CD environments.