nRF Connect SDK v3.3.0 Release Notes

nRF Connect SDK delivers reference software and supporting libraries for developing low-power wireless applications with Nordic Semiconductor products in the nRF52, nRF53, nRF54, nRF70, and nRF91 Series. The SDK includes open source projects (TF-M, MCUboot, OpenThread, Matter, and the Zephyr RTOS), which are continuously integrated and redistributed with the SDK.

Release notes might refer to “experimental” support for features, which indicates that the feature is incomplete in functionality or verification, and can be expected to change in future releases. To learn more, see Software maturity levels.

Highlights

Added the following features as supported:

  • Matter:

  • Bluetooth®:

    • Quality of Service (QoS) channel survey feature is now supported for production. This feature allows devices to analyze the RF channels and avoid the ones that are more congested, helping to improve the connection quality.

  • Wi-Fi:

  • nRF54L Series:

    • Support for the nRF54LM20B SoC.

  • DECT NR+:

    • Modem firmware v2.0.0 support for star topology network, implementing a subset of MAC and DLC layers for easier networking using NR+.

  • MCUboot:

    • The possibility to update the single slot “Loader.”

    • Single slot DFU switched to the Supported state.

    • RAM Loader mode switched to the Supported state.

Added the following features as experimental:

  • Bluetooth:

    • Direct Test Mode. This mode allows you to test the radio low level interface for RF certification, debugging, and troubleshooting.

    • LE Flushable ACL Data feature and the LE Read and Write Automatic Flush Timeout HCI commands. These allow devices to drop packages from the transmit queue if the timeout expires before they are sent.

  • Wi-Fi:

    • Support for the nRF54LM20B SoC combined with the nRF7002-EB II shield.

  • nRF54L Series:

    • Support for the new nRF54LS05A and nRF54LS05B SoCs.

  • nRF Cloud:

    • CoAP client for uploading diagnostic data over LTE-M/NB-IoT.

    • Battery metrics for nPM1300 or nPM1304 PMICs, including fuel gauge integration and battery voltage heartbeat metric.

Improved:

  • Bluetooth:

    • Introduced separate libraries for nRF54LM and nRF54LV sub-series.

  • Wi-Fi:

    • Updated Zperf to enable Raw TX throughput testing and throughput improvements.

Deprecated:

  • The Partition Manager is a component in the nRF Connect SDK that handles the flash memory partitioning at build time. This functionality is now replaced by Zephyr’s default devicetree-based flash partitioning when multi-image builds are involved. It is recommended that all new designs using Nordic devices, excluding the nRF91 Series devices, are to be built with DTS instead of Partition Manager. Partition Manager will be removed from the nRF Connect SDK by the end of 2026 from the main branch.

    As the first step, in the nRF Connect SDK 3.3.0, DTS is supported in MCUboot and TF-M.

    Samples will be adapted to showcase the new way of allocating partitions within the v3.3.0 branch. Such adaptations will also be reflected in the main for future releases.

Add-on related:

  • nRF Door Lock and Access Control Add-on:

    • The nRF Door Lock and Access Control Add-on provides a complete reference for building Aliro- and Matter-compatible locks and access control readers for both residential and commercial applications. The reference integrates multiple wireless technologies, including Bluetooth Low Energy, Ultra-Wideband (UWB), NFC, Thread, and Wi-Fi. This allows you to choose the appropriate technology for their specific use case.

  • Edge AI Add-on for nRF Connect SDK:

    • Extending the wake words application with a keyword spotting model.

    • Enabled new keyword spotting functionality in Nordic Edge AI Lab.

Release tag

The release tag for the nRF Connect SDK manifest repository (https://github.com/nrfconnect/sdk-nrf) is v3.3.0. Check the west.yml file for the corresponding tags in the project repositories.

To use this release, check out the tag in the manifest repository and run west update. See Install the nRF Connect SDK code and toolchain and Updating the repositories for more information.

For information on the included repositories and revisions, see Repositories and revisions for v3.3.0.

Integration test results

The integration test results for this tag can be found in the following external artifactory:

IDE and tool support

nRF Connect extension for Visual Studio Code is the recommended IDE for nRF Connect SDK v3.3.0. See the Installation section for more information about supported operating systems and toolchain.

Supported modem firmware

See the following documentation for an overview of which modem firmware versions have been tested with this version of the nRF Connect SDK:

Use the latest version of the Programmer app of nRF Connect for Desktop to update the modem firmware. See Programming nRF91 Series DK firmware for instructions.

Migration notes

See the Migration guide for nRF Connect SDK v3.3.0 for the changes required or recommended when migrating your application from nRF Connect SDK v3.2.0 to nRF Connect SDK v3.3.0.

Known issues

Known issues are only tracked for the latest official release. See known issues for nRF Connect SDK v3.3.0 for the list of issues valid for the latest release.

Changelog

The following sections provide detailed lists of changes by component.

IDE, OS, and tool support

Bootloaders and DFU

Developing with nRF54L Series

  • Added:

    • Experimental support for nRF54LS05B.

    • Support for nRF54LM20B.

    • The nRF54L Errata support in nRF Connect SDK page that summarizes the nRF54L Series anomalies and their workarounds that are currently implemented in the nRF Connect SDK.

Developing with nRF54H Series

Security

Mbed TLS

  • Updated to version 3.6.6.

Trusted Firmware-M (TF-M)

  • Added support for the PSA Key Wrapping functions from the PSA Certified Crypto API v1.4.0.

  • Updated:

Protocols

This section provides detailed lists of changes by protocol. See Samples for lists of changes for the protocol-related samples.

Bluetooth LE

  • Updated the Direct Test Mode HCI commands by making them optional through the CONFIG_BT_CTLR_DTM_HCI Kconfig option.

DECT NR+

  • Added DECT NR+ full stack support, including the following features:

    • Connection Manager integration for enabling easy connect for the applications.

    • Network management API for controlling DECT NR+ operations.

    • L2 API implementation enabling IPv6 connectivity, including HAL definition.

    • Enabling Internet connectivity through sink and Border Router (BR) support together with, for example, Serial Modem on a gateway nRF91 LTE device.

    • nRF91x1 DECT modem driver implementing HAL API and interfacing with DECT NR+ modem firmware where the DECT NR+ MAC layer is running.

Enhanced ShockBurst (ESB)

  • Added:

    • Experimental support for concurrent operation of ESB with other radio protocols using the Timeslot feature.

    • The CONFIG_ESB_CLOCK_INIT Kconfig option. When this option is enabled, the esb_init() function automatically starts the required high-frequency clock and applies platform-specific errata workarounds. Applications that manage clocks independently can leave this option disabled (default).

  • Fixed invalid radio configuration for legacy ESB protocol.

Matter

Thread

  • Added:

    • A warning when using precompiled OpenThread libraries with modified Kconfig options related to the OpenThread stack.

    • The otperf tool that is compatible with zperf and iperf for measuring throughput of thread transmissions. For more details, see OpenThread performance measurement.

    • Support for nRF54LM20B SoC in Thread samples.

Wi-Fi

  • Added:

    • Wired Equivalent Privacy (WEP) support for backward compatibility with legacy networks. The support is enabled through the CONFIG_WIFI_NM_WPA_SUPPLICANT_WEP Kconfig option and is not recommended for new deployments.

    • Host helper scripts under the nrf/scripts/wifi_test/ directory for raw TX profiling. The nrf_wifi_gen_raw_tx.py script builds a zperf raw upload shell line and an 802.11 QoS Data template for aggregation-friendly MPDUs. The nrf_wifi_zperf_raw_tx.py script aggregates tshark throughput from a live interface or a PCAP file, reporting rates in Mbps consistent with iperf2 style output.

    • A Performance profiling subsection under Raw IEEE 802.11 packet transmission.

  • Updated:

    • By enabling PSA Crypto support by default for personal security modes.

    • WPA3-SAE support status from experimental to supported and is now enabled by default.

Applications

This section provides detailed lists of changes by application.

High-Performance Framework (HPF)

  • Added support for the nRF54LV10A SoC in HPF GPIO.

Matter bridge

  • Added support for the nRF54LM20B SoC.

  • Updated partitions mapping for the nRF7002 DK in the application. See the migration guide for more information.

  • Removed the onoff_plug snippet from the application. To build the application with the onoff_plug functionality, use the overlay-onoff_plug.conf configuration overlay file.

nRF5340 Audio

  • Added:

    • Dynamic configuration of the number of channels for the encoder based on the configured audio locations. The number of channels is set during runtime using the audio_system_encoder_num_ch_set() function. This allows configuring mono or stereo encoding depending on the configured audio locations, potentially saving CPU and memory resources.

    • High CPU load callback using the Zephyr CPU load subsystem. The callback uses a printk() function, as the logging subsystem is scheduled out if higher priority threads take all CPU time. This makes debugging high CPU load situations easier in the application. The threshold for high CPU load is set in peripherals.c using the CPU_LOAD_HIGH_THRESHOLD_PERCENT macro.

    • CONFIG_SPEED_OPTIMIZATIONS to enable compiler speed optimizations for the application.

    • Support for multiple independent coordinated sets in the unicast client app. When all the devices in a coordinated set are disconnected, the SIRK is cleared, allowing a new unicast group to be formed with a new SIRK without the need to restart the application.

    • SIRK generation based on the username when using the buildprog.py Python script for the nRF5340 Audio unicast client sample. The SIRK is generated using parts of the SHA-256 hash of the username, aiming to obtain a unique but consistent SIRK across runs for the same username. This change allows you to have a unique SIRK without needing to manually generate and input it, simplifying the setup process for the unicast client sample.

  • Updated:

    • The application to switch to the new USB stack introduced in Zephyr 3.4.0. This change requires no action from you. macOS now works out of the box, fixing OCT-2154.

    • Programming script. Devices are now halted before programming. Furthermore, the devices are kept halted until they are all programmed and then started together, with the headsets starting first. This eases sniffing of advertisement packets.

    • The audio data path to now accumulate 10 ms frames instead of processing 1 ms blocks individually, reducing message queue operations by 90% and improving overall system performance. This optimization affects both USB audio input processing and the I2S audio datapath, resulting in more efficient encoder thread operation.

    • The application to improve handling of I2S RX buffer overruns. When an overrun occurs, the most recent block in the current frame is removed to make space for new incoming data.

    • The application to optimize the USB-to-encoder audio processing pipeline to reduce CPU usage. LC3-encoding of sinusoidal input demands more of the CPU than real-world audio input.

    • The application to improve error handling with unlikely() macros for better branch prediction in performance-critical paths.

    • The application to separate the audio clock configuration into a dedicated module. This allows for better organization and potential reuse of the audio clock configuration code between different SoCs that might not have the high-frequency audio clock (HFCLKAUDIO) feature. The new module provides an initialization function for setting up the audio clock and a function for configuring the audio clock frequency.

  • Removed:

    • The Bluetooth controller watchdog from the application. The watchdog was not providing value and the removal allows for easier porting to other platforms that do not have a multi-core architecture.

    • The DFU options from the application. The nRF5340 Audio applications have for some time used standard nRF Connect SDK tools to perform a DFU. Hence, the applications use the same process as other Bluetooth projects. See Bootloaders and DFU for information on how to set up DFU for their requirements.

    • The note about missing support in nRF Connect for VS Code. The section about programming using standard methods now lists the steps for nRF Connect for VS Code and the command line from the Building and running nRF Audio applications document. This is because, with the latest release of nRF Connect for VS Code, you can build and program the nRF5340 Audio application using the nRF Connect for VS Code GUI.

nRF Desktop

  • Added:

  • Updated:

    • The CONFIG_DESKTOP_BT Kconfig option to no longer select the deprecated CONFIG_BT_SIGNING Kconfig option. The application relies on Bluetooth LE security mode 1 and security level of at least 2 to ensure data confidentiality through encryption.

    • The memory map for RAM load configurations of the nRF54LM20 SoC to increase the KMU RAM section size to allow for a secp384r1 key.

    • The default log levels used by the legacy USB stack (CONFIG_DESKTOP_USB_STACK_LEGACY) to enable error logs (CONFIG_USB_DEVICE_LOG_LEVEL_ERR, CONFIG_USB_DRIVER_LOG_LEVEL_ERR). Previously, the legacy USB stack logs were turned off. This change ensures visibility of runtime issues.

    • Application configurations that emit debug logs over UART to use the CONFIG_DESKTOP_LOG_UART Kconfig option instead of explicitly configuring the logger. This is done to simplify the configurations.

    • The memory map for the nRF54H20 SoC to include a secure storage partition and adjust the size of existing partitions.

    • The dependencies of the Constant latency hotfix module to allow using it for nRF54L Series SoC. The CONFIG_DESKTOP_CONSTLAT_ENABLE Kconfig option no longer depends on CONFIG_SOC_SERIES_NRF54L being disabled.

    • The nRF Desktop application configurations for the nrf54l15dk/nrf54l15/cpuapp, nrf54l15dk/nrf54l05/cpuapp, and nrf52833dk/nrf52833 board targets to use the DTS-based memory layout instead of the Partition Manager. The DTS memory layout is defined in the memory_map.dtsi and similar files placed in the project’s board configuration directory. These files are included by the DTS overlay files of the application. The old Partition Manager configurations are still supported. See the nRF Desktop: Memory layout page for more details.

  • Removed the application-specific Kconfig option (CONFIG_DESKTOP_RTT) that enabled RTT for nRF Desktop logging (CONFIG_DESKTOP_LOG) or nRF Desktop shell (CONFIG_DESKTOP_SHELL). nRF Desktop shell automatically enables RTT by default (CONFIG_USE_SEGGER_RTT). You can use the newly introduced application-specific Kconfig option CONFIG_DESKTOP_LOG_RTT for nRF Desktop RTT logging configuration. By default, this option makes the RTT log backend block the message until it is transferred to host (CONFIG_LOG_BACKEND_RTT_MODE_BLOCK) instead of dropping messages that do not fit in up-buffer (CONFIG_LOG_BACKEND_RTT_MODE_DROP). This is done to prevent dropping the newest logs.

nRF Machine Learning (Edge Impulse)

Samples

This section provides detailed lists of changes by sample.

Bluetooth samples

Bluetooth Mesh samples

Bluetooth Fast Pair samples

  • Added experimental support for the nrf54lm20dk/nrf54lm20b/cpuapp and nrf54ls05dk/nrf54ls05b/cpuapp board targets in all Bluetooth Fast Pair samples.

  • Updated:

    • The Fast Pair samples to use the new <bluetooth/fast_pair/...> include paths.

    • The Fast Pair samples to use devicetree (DTS) for defining NVM partitions instead of the deprecated Partition Manager. The Partition Manager configuration is removed from the samples except for a few selected board targets that are used to validate the correctness of the deprecated Partition Manager solution.

      The DTS migration has not been completed for the nRF53 Series DFU configuration with MCUboot in the overwrite mode (for example, the nrf5340dk/nrf5340/cpuapp board target in the Bluetooth Fast Pair: Locator tag sample). This particular configuration is not yet deprecated, as the DTS alternative is not yet available.

  • Bluetooth Fast Pair: Input device sample:

    • Updated the documentation with a note about Android 16 automatic reconnection behavior for bonded HID devices. On Android 16 and later, disconnecting a bonded HID over GATT Profile (HOGP) device might result in an immediate reconnection.

    • Removed support for the nrf5340dk/nrf5340/cpuapp/ns board target. This board target is only available with the deprecated Partition Manager solution as a legacy build configuration (SB_CONFIG_PARTITION_MANAGER=y).

  • Bluetooth Fast Pair: Locator tag sample:

    • Added an experimental application ranging module (CONFIG_APP_RANGING) that uses the Precision Finding feature of the Google Fast Pair Service (GFPS) library with Bluetooth Low Energy Channel Sounding as the ranging technology. The module is enabled by default on board targets with Channel Sounding hardware support. The experimental status is inherited due to its experimental dependencies.

      As of the beginning of the second quarter of 2026, Precision Finding support using Bluetooth Low Energy Channel Sounding as the ranging technology is not publicly available on Android platforms. However, you can experiment with this configuration on Android test devices that provide hardware and software support for Bluetooth Low Energy Channel Sounding (for example, Google Pixel 10) if you satisfy the necessary requirements. For details regarding the requirements, see the note in the Precision Finding documentation section.

    • Updated:

      • The sample to use the new name for the Find Hub Network (FHN) that was previously known as the Find My Device Network (FMDN). Migrated the sample to use the new Kconfig options and the new FHN API header.

      • The motion detector sensor on Thingy:53 target from gyroscope to accelerometer.

      • The location of the Kconfig fragment files from the src subdirectory to the sample root directory.

      • The battery level measurement module by switching to the Fuel Gauge API, allowing for more accurate battery level readings and better support for different battery types. For more information, see the migration guide for Fast Pair Locator Tag sample.

      • The behavior of the RGB LED on the thingy53/nrf5340/cpuapp target. The green LED color no longer indicates running status. Instead, the green flashes of the RGB LED are used to indicate the following:

        • The button actions.

        • The ringing state.

Cellular samples

  • Cellular: nRF Cloud MQTT FOTA and Cellular: nRF Cloud MQTT device message samples:

    • Added support for JWT authentication by enabling the CONFIG_MODEM_JWT Kconfig option. Enabling this option in the prj.conf is necessary for using UUID as the device ID.

  • Cellular: Location sample:

    • Added support for onboarding with nRF Cloud Utils by using AT commands to set up the modem and device credentials.

  • Cellular: Modem Shell sample:

    • Added support for JWT authentication by enabling the CONFIG_MODEM_JWT Kconfig option. Enabling this option is necessary for using nRF Cloud Utils as an onboarding method.

    • Removed JITP from the shell commands and references from the sample documentation.

  • Cellular: nRF Cloud MQTT device message and nRF Cloud multi-service samples:

    • Updated shadow handling by removing the shadow type Accepted and added Transform request event handling. Delta events can now handle error cases using the /shadow/update/delta/trim/err and /shadow/update/delta/full/err topics in nRF Cloud.

Cryptography samples

DECT NR+ samples

  • Added:

    • The nRF91x1: Hello DECT sample for demonstrating the use of the DECT NR+ stack with connection manager and IPv6 connectivity.

    • The nRF91x1: DECT NR+ Shell sample with the utilities for testing the DECT NR+ networking stack and modem features.

  • nRF91x1: DECT NR+ PHY Shell sample:

    • Updated:

      • The dect rf_tool command - Major updates to improve usage for RX and TX testing.

      • Scheduler - Dynamic flow control based on load tier to prevent modem out-of-memory errors.

      • Settings - Continuous Wave (CW) support and possibility to disable Synchronization Training Field (STF) on TX and RX.

DFU samples

Edge Impulse samples

Enhanced ShockBurst samples

  • Added:

    • The Enhanced ShockBurst: Receiver with Bluetooth LE sample that demonstrates how to use the ESB protocol in PRX mode concurrently with the Bluetooth LE LBS service.

    • The Enhanced ShockBurst: Transmitter with Bluetooth LE sample that demonstrates how to use the ESB protocol in PTX mode concurrently with the Bluetooth LE LBS service.

    • Support for the nrf54ls05dk/nrf54ls05b/cpuapp board target in all ESB samples.

    • Support for the nrf54lm20dk/nrf54lm20b/cpuapp board target in all ESB samples.

  • Updated all ESB samples to use the CONFIG_ESB_CLOCK_INIT Kconfig option for automatic HF clock management, removing the manual clock initialization code from the main.c files.

Matter samples

  • Updated:

    • The documentation for all Matter samples and applications to make it more consistent and easier to maintain and read.

    • Partitions mapping for the nRF7002 DK in all Matter samples. See the migration guide for more information.

  • Matter: Light switch sample:

    • Removed the lit_icd snippet from the sample and enabled LIT ICD configuration by default.

  • Matter: Manufacturer-specific sample:

    • Added support for the NRF_MATTER_CLUSTER_INIT macro.

  • Matter: Closure sample:

    • Added support for the Closure Control cluster test event triggers.

  • Matter: Door lock sample:

    • Added:

      • Support for the Thread and Wi-Fi switching section in the nRF54LM20 DK with the nRF7002-EB II shield attached.

      • Lock data storage implementation based on the ARM PSA Protected Storage API, enabled with the CONFIG_LOCK_ACCESS_STORAGE_PROTECTED_STORAGE Kconfig option.

  • Matter: Light bulb sample:

    • Added support for the AWS IoT integration in the nRF54LM20 DK with the nRF7002-EB II shield attached.

Networking samples

  • Azure IoT Hub sample:

    • Updated the sample for the nRF7002 DK to explicitly enable ECDH/ECDSA and RSA certificate support.

  • AWS IoT sample:

    • Updated the sample for the nRF7002 DK to explicitly enable ECDH/ECDSA and RSA certificate support.

  • Download sample:

    • Updated board-specific configuration files to explicitly enable ECDH/ECDSA and RSA certificate support.

  • HTTP Server sample:

    • Updated TLS overlay files to explicitly enable ECDH/ECDSA and RSA certificate support.

  • HTTPS Client sample:

    • Updated the TF-M overlay for the nRF91 Series to explicitly enable ECDH/ECDSA and RSA certificate support.

  • MQTT sample:

    • Updated TLS overlay files to explicitly enable ECDH/ECDSA and RSA certificate support.

NFC samples

Peripheral samples

  • Radio test (short-range) sample:

    • Added:

      • The start_tx_sweep_with_sleep shell command. It allows for running a TX sweep with silent periods between each frequency.

      • The start_tx_sweep_with_sleep_modulated shell command. It allows for running a modulated TX sweep with silent periods between each frequency.

      • The set_channel_sequence shell command. It allows for setting a custom channel sequence for the start_tx_sweep_with_sleep command and start_tx_sweep_with_sleep_modulated commands.

      • The print_channel_sequence shell command. It prints the currently configured channel sequence.

PMIC samples

Protocol serialization samples

Thread samples

Wi-Fi samples

  • Added:

    • The Wi-Fi: P2P sample that demonstrates how to establish a Wi-Fi Peer-to-Peer (P2P) connection using Wi-Fi Direct, supporting both Client (CLI) mode and Group Owner (GO) mode operations.

    • Support for the nrf54lm20dk/nrf54lm20b/cpuapp board target for all Wi-Fi samples.

Other samples

  • CoreMark sample:

    • Added support for the nrf54lm20dk/nrf54lm20b board target.

Drivers

This section provides detailed lists of changes by driver.

  • Added the UART driver documentation.

  • Updated the nrfx_gppi API to now have full support on the application core of the nRF54H20 device. Using DPPI does not require the devicetree configuration.

Wi-Fi drivers

  • Added functionality to optionally insert Wi-Fi idle windows of configurable time (ms) using CONFIG_NRF70_BT_SLOT_TIME after each channel scan. This depends on CONFIG_NRF70_SR_COEX.

  • Updated the Wi-Fi coexistence functionality to be disabled by default. To enable it, use CONFIG_NRF70_SR_COEX=y in the configuration file.

Libraries

This section provides detailed lists of changes by library.

Bluetooth libraries and services

  • Added the DTM 2-wire UART to HCI Converter library that converts DTM 2-wire UART commands into appropriate 2-wire UART events or HCI commands, and subsequent HCI events into 2-wire UART events.

  • Google Fast Pair Service (GFPS) library:

    • Added:

      • Precision Finding support for the Find Hub Network (FHN) extension, enabling distance measurement for FHN accessories using supported ranging technologies. The feature is controlled by the CONFIG_BT_FAST_PAIR_FHN_PF Kconfig option and is experimental.

      • Support for the Fast Pair partition definition using devicetree (DTS) for all supported board targets. Defining the Fast Pair partition using DTS is the recommended approach and replaces the deprecated Partition Manager approach.

    • Updated:

      • The location of the Fast Pair headers and implementation out of the services subdirectory. The headers moved from include/bluetooth/services/fast_pair/ to include/bluetooth/fast_pair/ and the implementation moved from subsys/bluetooth/services/fast_pair/ to subsys/bluetooth/fast_pair/. The deprecated forwarding headers remain at the old paths to provide backward compatibility.

      • The naming of the Find My Device Network (FMDN) extension to Find Hub Network (FHN) to align with the updated Google specification:

        • All public API symbols have been renamed from bt_fast_pair_fmdn_* to bt_fast_pair_fhn_*. The new FHN header is located at include/bluetooth/fast_pair/fhn/fhn.h. Deprecated FMDN API aliases remain available through the include/bluetooth/services/fast_pair/fmdn.h header.

        • All Kconfig options have been renamed from CONFIG_BT_FAST_PAIR_FMDN_* to CONFIG_BT_FAST_PAIR_FHN_*. Deprecated FMDN Kconfig options remain available under the CONFIG_BT_FAST_PAIR_FMDN option tree.

        • The FMDN implementation directory has been renamed from subsys/bluetooth/services/fast_pair/fmdn/ to subsys/bluetooth/fast_pair/fhn/. See the migration guide for details.

  • Bluetooth Mesh provisioning handler for Nordic DKs module:

    • Added support for node reset callback. Applications can now register a callback using the bt_mesh_dk_prov_node_reset_cb_set() function to perform cleanup operations when a node reset occurs.

  • Bluetooth LE scanning library:

    • Fixed a bug where the central would attempt to connect to a non-connectable peripheral if the device had been matched by specified filters.

Security libraries

  • nRF Security library:

    • Updated the header files at subsys/nrf_security/src/drivers/cracen/cracenpsa/include/ with Doxygen documentation.

  • TF-M input/output control (IOCTL) library:

    • Updated a section in the library page about using the TF-M IOCTL API to perform secure memory writes from NSPE.

Modem libraries

Multiprotocol Service Layer libraries

  • Added back the MPSL radio notification API.

  • Fixed:

    • An issue with toggling of the REQUEST and STATUS0 pins when using the nRF700x coexistence interface on the nRF54H20 device.

    • An issue where coexistence pin GPIO polarity settings were ignored when using the nRF700x coexistence interface.

Libraries for networking

  • The FTP client library has been moved to the Zephyr repository (see FTP client).

  • nRF Cloud library:

    • Added:

    • Fixed an issue where CoAP FOTA was affected due to the downloader reading proxy_uri as a C string using strlen() to determine the CoAP option length. It picked up the stale tail, producing a corrupted download URL.

    • Removed:

      • The CONFIG_NRF_CLOUD_MQTT_SHADOW_TRANSFORMS Kconfig option. Transform request is the default method to request AWS shadows, replacing the shadow type Accepted.

      • The topics /shadow/get/accepted/trim, /shadow/get/accepted, and /shadow/get/trim. Requesting shadow updates through them potentially caused the device to disconnect due to a shadow update larger than two KB.

      • The /shadow/update/delta/full topic. It is replaced by /shadow/update/delta/trim. Deltas are now trimmed by default to prioritize smaller shadows.

  • nRF Cloud P-GPS library:

    • Updated the range for the CONFIG_NRF_CLOUD_PGPS_NUM_PREDICTIONS and CONFIG_NRF_CLOUD_PGPS_REPLACEMENT_THRESHOLD Kconfig options to values supported by nRF Cloud.

    • Fixed an issue where preemptive updates were not always performed when expected.

    • Removed the CONFIG_NRF_CLOUD_PGPS_PREDICTION_PERIOD Kconfig choice and related options (CONFIG_NRF_CLOUD_PGPS_PREDICTION_PERIOD_120_MIN and CONFIG_NRF_CLOUD_PGPS_PREDICTION_PERIOD_240_MIN).

Libraries for NFC

  • Updated the NFC library to set the FRAMEDELAYMAX register to the default value when the field is lost. This avoids violating protocol timing, which can lead readers to reject the NFC tag’s response.

  • Tag NDEF Exchange Protocol (TNEP) library:

    • Fixed the BUILD_ASSERT for the waiting time extension count (_n_wait) in the TNEP Tag API. It now uses NFC_TNEP_TAG_MAX_N_WAIT_TIME instead of NFC_TNEP_TAG_MAX_WAIT_TIME, aligning the check with the TNEP 1.0 specification.

    • Removed the unused NFC_TNEP_NDEF_NLEN_SIZE define from the TNEP base API.

nRF RPC libraries

  • Fixed Distance Measurement RPC by initializing RPC after starting the network core.

Other libraries

  • Added:

    • The Accel to angle library for converting three-dimensional acceleration into pitch and roll angles.

    • The nrf_802154_callbacks_dispatcher library for dispatching callbacks from the nRF IEEE 802.15.4 radio driver to the appropriate client. This library is useful if the application needs to use more than one nRF IEEE 802.15.4 radio driver client and each client has different callbacks implementations.

  • Deprecated the Edge Impulse wrapper library. Replaced by Edge Impulse SDK in Edge AI Add-on for nRF Connect SDK.

  • Hardware ID library:

  • Emergency data storage library:

    • Updated the library documentation to use static devicetree partitions instead of the Partition Manager.

    • Removed strict dependency on the Partition Manager. The Partition Manager can still be used with the library, but it is deprecated and not recommended for new designs.

Scripts

This section provides detailed lists of changes by script.

  • Added:

  • Software Bill of Materials script:

    • Added:

      • Sysbuild support for generating individual SBOM for each application.

      • Licence handling of the LLVM toolchain libraries.

    • Updated to support Matter builds by detecting GN external projects and collecting their source files for SBOM generation.

Integrations

This section provides detailed lists of changes by integration.

Google Fast Pair integration

  • Added documentation for the Precision Finding to the Google Fast Pair integration guide, covering the feature overview with supported ranging technologies, prerequisite operations, GATT service interaction with the ranging management workflow, and the Bluetooth Low Energy Channel Sounding helper APIs.

  • Updated:

    • The Google Fast Pair integration guide to reflect the Find My Device Network (FMDN) extension rename to Find Hub Network (FHN), aligning with the updated Google specification.

    • The Google Fast Pair integration guide to recommend devicetree (DTS) as the primary partition definition method and to deprecate the Partition Manager approach. The only exception from these migration recommendations in the context of the Fast Pair sample support is the nRF53 Series DFU configuration with MCUboot in the overwrite mode (for example, the nrf5340dk/nrf5340/cpuapp board target in the Bluetooth Fast Pair: Locator tag sample). This particular configuration is not yet deprecated, as the DTS alternative is not yet available.

Memfault integration

nRF Cloud integration

  • Updated by enabling a transform request for topic prefix and pairing during connection initialization to nRF Cloud in the MQTT finite state machine (FSM).

  • Fixed a hang in the nRF Cloud log backend caused by incorrect error handling. When the semaphore cannot be acquired, the function now returns the original size instead of 0, allowing the logging system to proceed correctly.

MCUboot

The MCUboot fork in nRF Connect SDK (sdk-mcuboot) contains all commits from the upstream MCUboot repository up to and including 8d14eebfe0b7402ebdf77ce1b99ba1a3793670e9, with some nRF Connect SDK specific additions.

The code for integrating MCUboot into nRF Connect SDK is located in the ncs/nrf/modules/mcuboot folder.

The following list summarizes both the main changes inherited from upstream MCUboot and the main changes applied to the nRF Connect SDK specific additions:

  • Added:

    • Deinitialization for the sQSPI flash driver in MCUboot.

    • Support for the nRF54LM20B SoC.

    • Serial recovery support with the Zephyr USB device stack (USB next) on the nRF54LM20 DK.

    • Support for a subset of functions in nrfxlib_crypto using the ocrypto software cryptography implementation (ECDSA P-256, SHA-256) for the nrf54ls05dk/nrf54ls05b/cpuapp board target.

  • Updated:

    • Image UUID support to use devicetree-based configuration.

    • LZMA compression parameters are now configurable to reduce MCUboot size by enabling decompression on the nrf54ls05dk/nrf54ls05b/cpuapp board target.

    • imgtool.py so images can be ordered on demand in the manifest.

    • To allow cleanup of UARTE pins on nRF54L Series SoCs, including UARTE00 and UARTE136.

  • Fixed:

    • Suspend-to-RAM (S2RAM) resume on the nRF54H20 SoC for direct-XIP mode.

    • UUID handling with external flash support.

    • Decompression when the CC310 crypto accelerator is used.

Zephyr

The Zephyr fork in nRF Connect SDK (sdk-zephyr) contains all commits from the upstream Zephyr repository up to and including 93b5f19f994b9a9376985299c1427a1630f6950e, with some nRF Connect SDK specific additions.

For the list of upstream Zephyr commits (not including cherry-picked commits) incorporated into nRF Connect SDK since the most recent release, run the following command from the ncs/zephyr repository (after running west update):

git log --oneline 93b5f19f99 ^911b3da139

For the list of nRF Connect SDK specific commits, including commits cherry-picked from upstream, run:

git log --oneline manifest-rev ^93b5f19f99

The current nRF Connect SDK main branch is based on revision 93b5f19f99 of Zephyr.

Note

For possible breaking changes and changes between the latest Zephyr release and the current Zephyr version, refer to the Zephyr release notes.

Documentation

  • Added notes in relevant areas explaining the current status of the Partition Manager deprecation.

  • Updated the DFU samples to group under the common DFU samples category.

  • Removed references to JITP in different areas of the documentation.