Software maturity levels
The nRF Connect SDK supports its various features and components at different levels of software maturity. The tables on this page summarize the maturity level for each feature and component supported in the nRF Connect SDK.
Software maturity categories
The following categories are used in the tables to classify the software maturity of each feature and component:
- Supported
The feature or component is implemented and maintained, and is suitable for product development.
- Not supported
The feature or component is neither implemented nor maintained, and it does not work.
- Experimental
The feature can be used for development, but it is not recommended for production. This means that the feature is incomplete in functionality or verification and can be expected to change in future releases. The feature is made available in its current state, but the design and interfaces can change between release tags. The feature is also labeled as experimental in Kconfig files and a build warning is generated to indicate this status.
See the following table for more details:
Supported |
Experimental |
Not supported |
|
|---|---|---|---|
Technical support |
Customer issues raised for features supported for developing end products on tagged nRF Connect SDK releases are handled by technical support on DevZone. |
Customer issues raised for experimental features on tagged nRF Connect SDK releases are handled by technical support on DevZone. |
Not available. |
Bug fixing |
Reported critical bugs and security fixes will be resolved in both |
Bug fixes, security fixes, and improvements are not guaranteed to be applied. |
Not available. |
Implementation completeness |
Complete implementation of the agreed features set. |
Significant changes may be applied in upcoming versions. |
A feature or component is available as an implementation, but is not compatible with (or tested on) a specific device or series of products. |
API definition |
The API definition is stable. |
The API definition is not stable and may change. |
Not available. |
Maturity |
Suitable for integration in end products. A feature or component that is either fully complete on first commit, or has previously been labelled experimental and is now ready for use in end products. |
Suitable for prototyping or evaluation. Not recommended to be deployed in end products. A feature or component that is either not fully verified according to the existing test plans or currently being developed, meaning that it is incomplete or that it may change in the future. |
Not applicable. |
Verification |
Fully verified according to the existing test plans. |
Incomplete verification |
Not applicable. |
For the certification status of different features in a specific SoC, see its Compatibility Matrix in the Nordic Semiconductor TechDocs.
API deprecation
The Deprecated status is assigned to API that has gone through all maturity levels, but is being phased out. The deprecated API will be removed in one of future releases, no earlier than two releases after the deprecation is announced and only when the code has transitioned to not using the deprecated API. The experimental API can be removed without deprecation notification. Following Zephyr’s guidelines for API lifecycle, the API documentation informs about the deprecation and attempts to use a deprecated API at build time will log a warning to the console.
Application support
The following subsections indicate the software maturity levels of the support for applications.
Note
Features not listed are not supported.
nRF5340 Audio
The following table indicates the software maturity levels of the support for the nRF5340 Audio applications.
Application |
Description |
Limitations |
Maturity level |
|---|---|---|---|
Broadcasting audio using Broadcast Isochronous Stream (BIS) and Broadcast Isochronous Group (BIG). Play and pause emulated by disabling and enabling stream, respectively. |
The following limitations apply:
|
Experimental |
|
Receiving broadcast audio using BIS and BIG. Synchronizes and unsynchronizes with the stream. |
The following limitations apply:
|
Experimental |
|
One Connected Isochronous Group (CIG) with two Connected Isochronous Streams (CIS). Transmitting unidirectional or transceiving bidirectional audio using CIG and CIS. |
The following limitations apply:
|
Experimental |
|
One CIG with one CIS stream. Receiving unidirectional or transceiving bidirectional audio using CIG and CIS. Coordinated Set Identification Service (CSIS) is implemented on the server side. |
The following limitations apply:
|
Experimental |
Protocol support
The following table indicates the software maturity levels of the support for each protocol:
| Bluetooth |
| Bluetooth Mesh |
| LTE |
| Matter |
| Sidewalk |
| Thread |
| Wi-Fi |
| Zigbee |
Amazon Sidewalk features support
The following table indicates the software maturity levels of the support for each Amazon Sidewalk feature:
| Sidewalk - OTA DFU over Bluetooth LE |
| Sidewalk File Transfer (FUOTA) |
| Sidewalk Multi-link + Auto-connect |
| Sidewalk on-device certification |
| Sidewalk over BLE |
| Sidewalk over FSK |
| Sidewalk over LORA |
Bluetooth features support
The following table indicates the software maturity levels of the support for each Bluetooth feature:
| Bluetooth LE Peripheral/Central |
| Connectionless/Connected CTE Transmitter |
| LE Coded PHY |
| LLPM |
Thread features support
The following table indicates the software maturity levels of the support for each Thread feature:
| Thread + nRF21540 (GPIO) |
| Thread - Full Thread Device (FTD) |
| Thread - Minimal Thread Device (MTD) |
| Thread 1.1 |
| Thread 1.2 - CSL Receiver |
| Thread 1.2 - Core |
| Thread 1.2 - Link Metrics |
| Thread 1.3 - Core |
| Thread FTD + Bluetooth LE multiprotocol |
| Thread MTD + Bluetooth LE multiprotocol |
| Thread Radio Co-Processor (RCP) |
| Thread TCP |
Matter features support
The following table indicates the software maturity levels of the support for each Matter feature:
| Matter - OTA DFU over Bluetooth LE |
| Matter Intermittently Connected Device |
| Matter commissioning over Bluetooth LE with NFC onboarding |
| Matter commissioning over Bluetooth LE with QR code onboarding |
| Matter commissioning over IP |
| Matter over Thread |
| Matter over Wi-Fi |
| OTA DFU over Matter |
Zigbee feature support
The following table indicates the software maturity levels of the support for each Zigbee feature:
| OTA DFU over Zigbee |
| Zigbee (Sleepy) End Device |
| Zigbee + Bluetooth LE multiprotocol |
| Zigbee + nRF21540 (GPIO) |
| Zigbee Coordinator |
| Zigbee Network Co-Processor (NCP) |
| Zigbee Router |
Wi-Fi feature support
The following table indicates the software maturity levels of the support for each Wi-Fi feature:
| Bluetooth LE Co-existence |
| Monitor Mode |
| Promiscuous Mode |
| STA Mode |
| Scan only (for location accuracy) |
| SoftAP Mode |
| TX injection Mode |
Security Feature Support
The following sections contain the tables indicating the software maturity levels of the support for the following security features:
Trusted Firmware-M
PSA Crypto
nRF Secure Immutable Bootloader
Hardware Unique Key
Trusted storage
Trusted Firmware-M support
| Full build |
| Minimal Build |
PSA Crypto support
| PSA Crypto APIs |
nRF Secure Immutable Bootloader
| Immutable Bootloader as part of build |
Hardware Unique Key
| Key Derivation from Hardware Unique Key |
Trusted storage
| Trusted storage implements the PSA Certified Secure Storage APIs without TF-M |
Power management device support
The following table indicates the software maturity levels of the support for each power management device:
| nPM1100 |
| nPM1300 |
| nPM6001 |