nRF Connect SDK v3.2.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:

    • Integration of Matter 1.5.0 with dedicated sample for closures:

      • Better closures - Supporting different motion types (sliding, rotating, opening), configurations (single/dual panels, nested mechanisms), and improved safety features (through precise position reporting).

      • Soil sensors - Introducing soil sensors that enable Matter-based valves and irrigation systems to optimize water use for plants.

      • Energy management - Providing real-time data on energy prices, carbon data, and advanced smart metering, thereby improving tracking, enabling grid coordination, and supporting EV charging features.

    • Introduced the Matter Quick Start app as part of nRF Connect for Desktop. This tool allows you to set up and configure Matter accessory devices and evaluate Matter samples without installing the nRF Connect SDK and setting up the development environment.

  • Bluetooth®:

    • Support for Bluetooth Core version 6.2.

    • LE Shorter Connection Intervals feature and sample.

    • LE Frame Space Update feature.

    • Central-only and Peripheral-only library variants for the nRF54H Series devices.

    • See the changelogs of MPSL and Softdevice Controller for the full list of improvements and changes.

  • Bluetooth Mesh:

  • Wi-Fi®:

  • Cellular and Non-Terrestrial Networks (NTN):

  • nRF Desktop:

    • Support for the nRF54H20 DK that is based on the new IronSide SE architecture.

Added the following features as experimental:

  • Matter:

  • Wi-Fi:

    • nRF70 Series Wi-Fi connectivity stack on the nRF54LM20A SoC, using the nRF7002 EBII.

    • Wi-Fi Direct operation mode on the nRF7002 DK, with support for Wi-Fi Direct added to the Wi-Fi: WFA QuickTrack control application.

  • nRF54L Series:

    • This is the first release of nRF Connect SDK that brings experimental support for the nRF54LV10 DK and the nRF54LV10A SoC.

    • Protocols with experimental support include:

      • Bluetooth LE, including Channel Sounding

      • 2.4 GHz proprietary

    • All standard SoC peripherals are supported.

    • Device Firmware Update (DFU) and bootloader support.

    • PSA Crypto APIs (HW accelerated) for cryptographic operations and key storage.

    • Trusted Firmware-M providing secure processing environment.

    • Out-of-the-box support across many standard SDK samples.

  • Device Firmware Update (DFU) and Firmware Over-the-Air (FOTA):

    • Single slot DFU support for the nRF54H20 SoC and the nRF54L Series.

    • Encrypted DFU support using ECIES on the nRF54L15, nRF54LM20, and nRF54LV10 SoCs.

    • Support for DFU using external flash on the nRF54H20 SoC.

Improved:

  • System-Off mode can now be used in devices running TF-M.

  • Bluetooth:

    • The Quality of Service (QoS) channel survey feature now supports incremental channel surveying, allowing scheduling with smaller or shorter timeslots.

    • MPSL and Softdevice Controller :

      • The Scheduler can now manage events that are scheduled less than 100 microseconds apart.

      • Timeslot events can now run for longer than 128 seconds.

    • Reduced code size for nRF52 and nRF53 Series devices.

Deprecated:

  • The Matter over Wi-Fi support on the nRF5340 SoC combined with nRF7002. It is recommended to switch to using the nRF54LM20A SoC (in combination with the nRF7002 EBII), which provides a significantly larger amount of available non-volatile memory for Matter over Wi-Fi applications.

Removed:

Release tag

The release tag for the nRF Connect SDK manifest repository (https://github.com/nrfconnect/sdk-nrf) is v3.2.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.2.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.2.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.

Known issues

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

Migration notes

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

Changelog

The following sections provide detailed lists of changes by component.

IDE, OS, and tool support

Board support

  • Added support for the nRF7002-EB II Wi-Fi shield for use with the nRF54LM20 DK board target.

Bootloaders and DFU

Developing with nRF91 Series

Developing with nRF54L Series

Developing with nRF54H Series

Developing with Thingy:91

Security

Mbed TLS

  • Updated to version 3.6.5.

Trusted Firmware-M

  • Updated:

    • The TF-M version to 2.2.0.

    • Documentation to clarify the support for TF-M on devices emulated using the nRF54L15 DK:

      • nRF54L05 does not support TF-M.

      • nRF54L10 supports TF-M experimentally.

  • Removed several documentation pages from the Trusted Firmware-M reference documentation section not relevant to the understanding of the TF-M integration in the nRF Connect SDK. The section now includes only pages that provide background information about TF-M design that are relevant for the nRF Connect SDK.

Protocols

Bluetooth LE

  • Added:

    • The bt_nrf_conn_set_ltk() API. This API allows you to set a custom Long Term Key (LTK) for a connection. You can use it when two devices have a shared proprietary method for obtaining an LTK.

    • Support for the Frame Space Update feature. This feature allows the time between connection events to be negotiated, allowing for shorter or longer spacing to improve throughput for various applications.

    • Support for the Shorter Connection Intervals (SCI) feature. This feature introduces a range of connection intervals below 7.5 ms, providing faster device responsiveness for high-performance HID devices, real-time HMI systems, and sensors. SCI extends the connection interval range to span from 375 μs to 4.0 s, and defines the resolution to be a multiple of 125 μs. The minimum supported connection interval depends on the current device and controller capabilities. For more information, see the SoftDevice Controller documentation.

Bluetooth Mesh

Enhanced ShockBurst (ESB)

Matter

  • Added:

  • Updated to use the CONFIG_PICOLIBC Kconfig option as the C library instead of CONFIG_NEWLIB_LIBC, in compliance with Zephyr requirements.

  • Deprecated the Matter over Wi-Fi samples that are using nRF5340 SoC (nRF7002 DK and nRF5340 DK with the nRF7002 EK shield attached). This is mainly due to the very limited non-volatile memory space left for application code. As an alternative, it is recommended to use the nRF54LM20A SoC in combination with the nRF7002-EB II shield, which provides a significantly greater amount of available non-volatile memory for Matter over Wi-Fi applications.

  • Removed the CONFIG_CHIP_SPI_NOR and CONFIG_CHIP_QSPI_NOR Kconfig options.

Matter fork

The Matter fork in the nRF Connect SDK (sdk-connectedhomeip) contains all commits from the upstream Matter repository up to, and including, the v1.5.0.0 tag.

  • Added:

    • Support for the following new device types:

      • Irrigation System

      • Soil Sensor

      • Closure

      • Closure Panel

      • Closure Controller

      • Meter Reference Point

      • Electrical Energy Tariff

      • Electrical Meter

      • Electrical Utility Meter

      • Camera

      • Floodlight Camera

      • Video Doorbell

      • Snapshot Camera

      • Chime

      • Camera Controller

      • Doorbell

      • Intercom

      • Audio Doorbell

    • Full support for operation over TCP transport to Data Transport, which enables more efficient and reliable transmission of large messages.

    • The new code-driven approach for the Matter Data Model and Cluster configuration handling. This approach assumes gradually replacing the configuration based on the ZAP files and the ZAP-generated code, and handling the configuration in the source code. For example, to enable a specific cluster or its attribute, the new model requires calling a dedicated delegate and registering the cluster in a source code. The code-driven approach is not yet fully implemented for all the available clusters, but the coverage will be increasing and it is used for the newly created clusters. The new model is meant to be backward compatible with the previous configuration based on the ZAP files and the ZAP-generated code, until the code-driven approach is fully implemented for all the available clusters. See the Migration guide for nRF Connect SDK v3.2.0 for more information.

    • The zap-sync command to synchronize the ZAP and zcl.json files after updating the ZAP tool version.

    • The check to all ZAP tool west commands that verify whether ZAP tool sandbox permissions are correctly set. In case of detecting incorrect permissions, the command prompts the user to accept automatically updating the permissions to required ones.

  • Updated the zap-append command to accept --clusters argument instead of new_clusters argument.

  • Removed dependencies on Nordic DK-specific configurations in Matter configurations. See the Migration guide for nRF Connect SDK v3.2.0 for more information.

Thread

Wi-Fi®

Applications

  • Removed the Serial LTE modem application. Instead, use Serial Modem, an nRF Connect SDK add-on application.

Matter bridge

  • Added:

    • Support for the nRF54LM20 DK working with both Thread and Wi-Fi protocol variants. For the Wi-Fi protocol variant, the nRF54LM20 DK works with the nRF7002-EB II shield attached.

    • The matter_bridge list command to show a list of all bridged devices and their endpoints.

  • Updated:

    • The application to store a portion of the application code related to the nRF70 Series Wi-Fi firmware in the external flash memory by default. This change breaks the DFU between the previous nRF Connect SDK versions and the upcoming release. To fix this, you need to disable storing the Wi-Fi firmware patch in external memory. See the migration guide for more information.

    • By moving code from samples/matter/common/src/bridge to applications/matter_bridge/src/core and applications/matter_bridge/src/ble directories.

    • The Identify cluster implementation in the application to use the code-driven approach instead of the zap-driven approach.

    • The default number of Bluetooth Low Energy connections that can be selected using the Kconfig configuration from 10 to 8 for the Matter bridge over Thread configuration.

nRF5340 Audio

nRF Desktop

  • Added:

    • Support for the nrf54h20dk/nrf54h20/cpuapp board target configurations, aligned with the IronSide SE architecture. These configurations use the MCUboot bootloader in direct-XIP mode and a merged image slot that combines both the application and radio core images. They provide the same feature set as the SUIT-based configuration released in nRF Connect SDK v3.0.0. Support for the nrf54h20dk/nrf54h20/cpuapp board target in the nRF Desktop application has been removed in nRF Connect SDK v3.1.0, because the nRF54H20 configurations relied on the SUIT solution, also removed in the same release. For guidance on how to migrate an nRF Desktop application from SUIT to IronSide SE, see the nRF Desktop section in the Migration guide for nRF Connect SDK v3.2.0.

    • Support for the DTS-based memory layout in the Device Firmware Upgrade module when using the MCUboot bootloader.

    • Experimental support of the ram_load and release_ram_load configuration variants for the nrf54lm20dk/nrf54lm20a/cpuapp board target. These variants use the MCUboot bootloader in its experimental RAM load mode and support firmware updates using the Device Firmware Upgrade module. Bootloader configurations in this mode retain the same security features as direct-xip variants, including hardware cryptography, signature type, and public key storage.

      The MCUboot RAM load mode is used to improve the USB HID report rate by executing the application code from the RAM.

      For more details on the MCUboot RAM load mode, see the MCUboot RAM load mode section in the nRF Desktop documentation.

    • Experimental support for the MCUboot RAM load mode in the Device Firmware Upgrade module.

  • Updated:

    • The memory layouts for the nrf54lm20dk/nrf54lm20a/cpuapp board target to make more space for the application code. This change in the partition map of every nRF54LM20 configuration is a breaking change and cannot be performed using DFU. As a result, the DFU procedure fails if you attempt to upgrade the application firmware based on one of the nRF Connect SDK v3.1 releases.

    • The application and MCUboot configurations for the nrf54lm20dk/nrf54lm20a/cpuapp board target to use the CRACEN hardware crypto driver instead of the Oberon software crypto driver. The application image signature is verified with the CRACEN hardware peripheral.

    • The MCUboot configurations for the nrf54lm20dk/nrf54lm20a/cpuapp board target to use the KMU-based key storage. The public key used by MCUboot for validating the application image is securely stored in the KMU hardware peripheral. To simplify the programming procedure, the application is configured to use the automatic KMU provisioning. The KMU provisioning is performed by the west runner as a part of the west flash command when the --erase or --recover flag is used.

    • Application configurations to avoid using the deprecated Kconfig options CONFIG_DESKTOP_HID_REPORT_EXPIRATION and CONFIG_DESKTOP_HID_EVENT_QUEUE_SIZE. The configurations rely on Kconfig options specific to HID providers instead. The HID keypress queue sizes for HID consumer control (CONFIG_DESKTOP_HID_REPORT_PROVIDER_CONSUMER_CTRL_EVENT_QUEUE_SIZE) and HID system control (CONFIG_DESKTOP_HID_REPORT_PROVIDER_SYSTEM_CTRL_EVENT_QUEUE_SIZE) reports have been decreased to 10.

    • Application configurations integrating the USB legacy stack (CONFIG_DESKTOP_USB_STACK_LEGACY) to suppress build warnings related to deprecated APIs of the USB legacy stack (CONFIG_USB_DEVICE_STACK). The configurations enable the CONFIG_DEPRECATION_TEST Kconfig option to suppress the deprecation warnings. The USB legacy stack is still used by default.

    • MCUboot configurations that support serial recovery over USB CDC ACM to enable the CONFIG_DEPRECATION_TEST Kconfig option to suppress deprecation warnings. The implementation of serial recovery over USB CDC ACM still uses the deprecated APIs of the USB legacy stack (CONFIG_USB_DEVICE_STACK).

    • Configurations of the nrf52840dongle/nrf52840 board target to align them after Zephyr introduced the bare board variant. The application did not switch to the bare board variant to keep backwards compatibility.

    • HID transports (HID Service module, USB state module) to use the early hid_report_event subscription (APP_EVENT_SUBSCRIBE_EARLY). This update improves the reception speed of HID input reports in HID transports.

    • The Motion module implementations to align internal state names for consistency.

    • The Motion module implementation that generates simulated motion. Improved the Zephyr shell (CONFIG_SHELL) integration to prevent potential race conditions related to using preemptive execution context for shell commands.

    • The motion_event to include information if the sensor is still active or goes to idle state waiting for user activity (motion_event.active). The newly added field is filled by all Motion module implementations. The HID provider mouse module uses the newly added field to improve the synchronization of motion sensor sampling. After the motion sensor sampling is triggered, the provider waits for the result before submitting a subsequent HID mouse input report.

    • The default value of the CONFIG_SOC_FLASH_NRF_RADIO_SYNC_MPSL_NORMAL_PRIORITY_TIMEOUT_US Kconfig option to 0. This is done to start using high MPSL timeslot priority quicker and speed up non-volatile memory operations.

    • The number of preemptive priorities (CONFIG_NUM_PREEMPT_PRIORITIES). The Kconfig option has been increased to 15 (the default value in Zephyr). The priority of 10 is used by default for preemptive contexts (for example, CONFIG_BT_GATT_DM_WORKQ_PRIO and CONFIG_BT_LONG_WQ_PRIO). The previously used Kconfig option value of 11 leads to using the same priority for the mentioned preemptive contexts as the lowest available application thread priority (used for example, by the log processing thread).

    • Application image configurations to explicitly specify the LED driver used by the LEDs module (CONFIG_CAF_LEDS_GPIO or CONFIG_CAF_LEDS_PWM). Also, disabled unused LED drivers enabled by default to reduce memory footprint.

    • The HID forward module to allow using the module when configuration channel support (CONFIG_DESKTOP_CONFIG_CHANNEL_ENABLE) is disabled in the application configuration.

    • The Keys state utility to rely on runtime assertions, ensuring that the initialization function is called only once and other APIs of the utility are called after the utility has been initialized. This is done to align the utility with other application utilities.

    • The Device Firmware Upgrade module and the Device Firmware Upgrade MCUmgr module to handle the nrf54h20dk/nrf54h20/cpuapp board target with the IronSide SE architecture and the MCUboot bootloader.

    • The HID state module:

      • Now allows for the delayed registration of HID report providers. Previously, subscribing to a HID input report before the respective provider had been registered triggered an assertion failure.

      • The HID state power manager module now skips submitting the keep_alive_event if the POWER_MANAGER_LEVEL_ALIVE power level is enforced by any application module through the power_manager_restrict_event. This is done to improve performance.

      • The documentation for the module and default HID report providers now has a simplified getting started guide for updating HID input reports used by the application or introducing support for a new HID input report.

      • Fixed issues related to selective HID report subscription. This resolves the known issue NCSDK-35718.

  • Removed:

nRF Machine Learning (Edge Impulse)

  • Updated:

    • The application to change the default libc from the Newlib to the Picolibc to align with the nRF Connect SDK and Zephyr.

    • By changing the number of preemptive priorities (CONFIG_NUM_PREEMPT_PRIORITIES) from 11 to default value 15 from Zephyr. The priority of 10 is used by default for some preemptive contexts (for example, CONFIG_BT_LONG_WQ_PRIO). The previously used Kconfig option value of 11 led to using the lowest available application thread priority for the mentioned preemptive contexts, which at the same time is used, for example, by the log processing thread.

  • Removed support for the thingy53/nrf5340/cpuapp/ns board target.

Thingy:53: Matter weather station

  • Updated the application to use the code-driven approach for the Identify cluster implementation instead of the zap-driven approach.

Samples

This section provides detailed lists of changes by sample.

Bluetooth samples

Bluetooth Mesh samples

Bluetooth Fast Pair samples

  • Bluetooth Fast Pair: Locator tag sample:

    • Updated:

      • The memory layout for the nrf54lm20dk/nrf54lm20a/cpuapp board target to make more space for the application code. This change in the nRF54LM20 partition map is a breaking change and cannot be performed using DFU. As a result, the DFU procedure fails if you attempt to upgrade the sample firmware based on one of the nRF Connect SDK v3.1 releases.

      • The application and MCUboot configurations for the nrf54lm20dk/nrf54lm20a/cpuapp board target to use the CRACEN hardware crypto driver instead of the Oberon software crypto driver. The Fast Pair subsystem still uses the Oberon software library. The application image signature is verified with the CRACEN hardware peripheral.

      • The MCUboot configuration for the nrf54lm20dk/nrf54lm20a/cpuapp board target to use the KMU-based key storage. The public key used by MCUboot for validating the application image is securely stored in the KMU hardware peripheral. To simplify the programming procedure, the samples are configured to use the automatic KMU provisioning. The KMU provisioning is performed by the west runner as a part of the west flash command when the --erase or --recover flag is used.

  • Bluetooth Fast Pair: Input device sample:

    • Updated the application configuration for the nrf54lm20dk/nrf54lm20a/cpuapp board target to use the CRACEN hardware crypto driver instead of the Oberon software crypto driver. The Fast Pair subsystem still uses the Oberon software library.

Cellular samples

Cryptography samples

  • Added:

    • Support for the nrf54lv10dk/nrf54lv10a/cpuapp and nrf54lv10dk/nrf54lv10a/cpuapp/ns board targets to all samples (except Cryptography tests).

    • Support for the nrf54h20dk/nrf54h20/cpuapp board target to the Crypto: Persistent key usage sample, demonstrating use of Internal Trusted Storage (ITS) on the nRF54H20 DK.

    • Support for the nrf54lm20dk/nrf54lm20a/cpuapp/ns board target in all supported cryptography samples.

    • Support for the nrf54lm20dk/nrf54lm20a/cpuapp board target in the following samples:

    • The Crypto: KMU usage with CRACEN sample.

  • Updated documentation of all samples for style consistency. Lists of cryptographic features used by each sample and sample output in the testing section have been added.

  • Crypto: PSA TLS sample:

    • Updated sample-specific Kconfig configuration structure and documentation.

DECT NR+ samples

  • nRF91x1: DECT NR+ Shell sample:

    • Added the dect perf command client - Listen Before Talk (LBT) support with configurable LBT period and busy threshold.

    • Updated:

      • PCC and PDC printings improved to show SNR and RSSI-2 values with actual dB/dBm resolutions.

      • dect perf command - Improved operation schedulings to avoid scheduling conflicts and fix to TX the results in server side.

      • dect ping command - Improved operation schedulings to avoid scheduling conflicts.

DFU samples

  • Added:

    • The DFU Multi-image sample to demonstrate how to use the DFU target library.

    • The A/B with MCUboot sample to demonstrate how to implement the A/B firmware update strategy using MCUboot.

    • The Minimal Bluetooth LE SMP firmware loader sample that provides a minimal configuration for firmware loading using SMP over Bluetooth LE. This sample is intended as a starting point for developing custom firmware loader applications that work with the MCUboot bootloader.

    • The Single-slot DFU with MCUboot sample to demonstrate how to maximize the available space for the application with MCUboot using firmware loader mode (single-slot layout).

    • The MCUboot with encryption enabled sample demonstrating how to build MCUboot with image encryption enabled.

Enhanced ShockBurst samples

IronSide SE samples

  • Added the Secondary boot sample that demonstrates how to build and boot a secondary application image on the nRF54H20 DK.

Matter samples

  • Added:

    • The Matter: Temperature Sensor sample that demonstrates how to implement and test a Matter temperature sensor device.

    • The Matter: Contact sensor sample that demonstrates how to implement and test a Matter contact sensor device.

    • The Matter: Closure sample that demonstrates how to implement and test a Matter closure device.

    • The matter_custom_board toggle paragraph in the Matter advanced configuration section of all Matter samples that demonstrates how add and configure a custom board.

    • Support for the Matter over Wi-Fi on the nRF54LM20 DK with the nRF7002-EB II shield attached to all Matter over Wi-Fi samples.

    • Enabled deprecated warnings for all Matter over Wi-Fi samples that are using nRF5340 SoC.

  • Updated:

    • All Matter over Wi-Fi samples and applications to store a portion of the application code related to the nRF70 Series Wi-Fi firmware in the external flash memory by default. This change breaks the DFU between the previous nRF Connect SDK versions and the nRF Connect SDK v3.2.0. To fix this, you need to disable storing the Wi-Fi firmware patch in external memory. See the migration guide for more information.

    • All Matter samples that support low-power mode to use the RAM power-down feature with the nRF54LM20 DK. This change resulted in decreasing the sleep current consumption by more than 2 µA.

    • All Matter samples to use the code-driven approach for the Identify cluster implementation instead of the zap-driven approach.

  • Matter: Door lock sample:

Networking samples

Trusted Firmware-M (TF-M) samples

  • TF-M Hello World sample:

    • Added:

      • Support for the nrf54lv10dk/nrf54lv10a/cpuapp/ns board target.

      • Support for the nrf54lm20dk/nrf54lm20a/cpuapp/ns board target.

  • TF-M secure peripheral partition

    • Added support for the nrf54lm20dk/nrf54lm20a/cpuapp/ns board target.

Wi-Fi samples

Other samples

  • Added the Multicore idle test with firmware relocated to radio core TCM sample to demonstrate how to relocate the firmware to the TCM memory at boot time. The sample also uses the radio_loader sample image (located in nrf/samples/nrf54h20/radio_loader), which cannot be tested as a standalone sample, to relocate the firmware from the MRAM to the TCM memory at boot time.

  • nRF Profiler sample:

    • Added a new testing step demonstrating how to calculate event propagation statistics. Also added the related test preset for the calc_stats.py script (nrf/scripts/nrf_profiler/stats_nordic_presets/nrf_profiler.json).

  • Application Event Manager profiling tracer sample:

    • Added a new testing step demonstrating how to calculate event propagation statistics. Also added the related test preset for the calc_stats.py script (nrf/scripts/nrf_profiler/stats_nordic_presets/app_event_manager_profiler_tracer.json).

  • Event Manager Proxy sample:

    • Added experimental support for the nRF54LV10A SoC.

  • IPC service sample:

    • Added experimental support for the nRF54LV10A SoC.

Drivers

This section provides detailed lists of changes by driver.

nrfx

Flash drivers

  • Added a Kconfig option to configure timeout for normal priority MPSL request (CONFIG_SOC_FLASH_NRF_RADIO_SYNC_MPSL_NORMAL_PRIORITY_TIMEOUT_US) in MPSL flash synchronization driver (nrf/drivers/mpsl/flash_sync/flash_sync_mpsl.c). After the timeout specified by this Kconfig option, a higher timeslot priority is used to increase the priority of the flash operation. The default timeout has been reduced from 30 milliseconds to 10 milliseconds to speed up non-volatile memory operations.

Libraries

This section provides detailed lists of changes by library.

Binary libraries

  • LwM2M carrier library:

    • Updated the glue layer to manage PDN connections using the PDN management functionality in the LTE link control library when the CONFIG_LTE_LC_PDN_MODULE Kconfig option is enabled, or direct AT commands otherwise.

    • Removed the dependency on the deprecated PDN library.

Bluetooth libraries and services

Security libraries

  • Trusted storage library:

    • Updated the API documentation to be based on headers in subsys/trusted_storage/include/psa instead of include/.

    • Removed the internal_trusted_storage.h and protected_storage.h files from the include/ folder as these files had duplicates in the subsys/trusted_storage/include/psa folder.

Modem libraries

  • Added the NTN library to provide helper functionality for Non-Terrestrial Network (NTN) usage.

  • Removed:

    • The AT command parser library. Use the AT parser library instead.

    • The AT parameters library.

    • The Modem SLM library. Use the library from Serial Modem instead.

  • LTE link control:

    • Added:

      • Support for environment evaluation.

      • Support for NTN NB-IoT system mode.

      • eDRX support for NTN NB-IoT.

      • Support for new modem events LTE_LC_MODEM_EVT_RF_CAL_NOT_DONE, LTE_LC_MODEM_EVT_INVALID_BAND_CONF, and LTE_LC_MODEM_EVT_DETECTED_COUNTRY.

      • Description of new features supported by mfw_nrf91x1 and mfw_nrf9151-ntn in receive only functional mode.

      • Sending of the LTE_LC_EVT_PSM_UPDATE event with tau and active_time set to -1 when registration status is LTE_LC_NW_REG_NOT_REGISTERED.

      • New registration statuses and functional modes for the mfw_nrf9151-ntn modem firmware.

      • Support for PDP context and PDN connection management. The functionality is available when the CONFIG_LTE_LC_PDN_MODULE Kconfig option is enabled.

      • Support for also disabling the default modules that are enabled by default. This is useful when the application only needs a subset of the functionality provided by the library and to reduce the size of the application image. To disable a module, set the corresponding CONFIG_LTE_LC_<MODULE_NAME>_MODULE Kconfig option to n.

    • Updated:

      • The type of the lte_lc_evt.modem_evt field to lte_lc_modem_evt.

      • Replaced modem events LTE_LC_MODEM_EVT_CE_LEVEL_0, LTE_LC_MODEM_EVT_CE_LEVEL_1, LTE_LC_MODEM_EVT_CE_LEVEL_2 and LTE_LC_MODEM_EVT_CE_LEVEL_3 with the LTE_LC_MODEM_EVT_CE_LEVEL modem event.

      • The order of the LTE_LC_MODEM_EVT_SEARCH_DONE modem event, and registration and cell related events. See the migration guide for more information.

    • Fixed an issue where band lock, RAI notification subscription, and DNS fallback address are lost when the modem has been put into LTE_LC_FUNC_MODE_POWER_OFF functional mode.

  • Modem library integration layer:

    • Added the nrf_modem_lib_trace_peek_at() function to the nrf_modem_lib_trace_backend interface to peek trace data at a byte offset without consuming it. Support for this API has been added to the flash trace backend.

    • Updated the PDN functionality to use the PDN management in the LTE link control library instead of the PDN library.

    • Removed the deprecated CONFIG_NRF_MODEM_LIB_TRACE_BACKEND_UART_ZEPHYR Kconfig option.

  • AT parser:

    • Fixed an issue where an unquoted string parameter in the middle of a response would not be parsed correctly.

  • PDN library:

    • Deprecated the library. Use the PDN management functionality in the LTE link control library instead.

Libraries for networking

  • Added missing brackets that caused C++ compilation to fail in the following libraries:

  • Updated the following libraries to use the new SEC_TAG_TLS_INVALID definition for checking whether a security tag is valid:

  • Removed the Download client library. Use the Downloader library instead.

  • nRF Cloud device provisioning library:

    • Added a blocking call to wait for a functional-mode change, relocating the logic from the app into the library.

    • Updated:

      • Made internal scheduling optional. Applications can now trigger provisioning manually using the CONFIG_NRF_PROVISIONING_SCHEDULED Kconfig option.

      • Moved root CA provisioning to the modem initialization callback to avoid blocking and ensure correct state during startup.

      • Expanded the event handler to report additional provisioning events, including failures.

      • Made the event handler callback mandatory to ensure the application is notified of failures and to prevent silent errors.

      • Unified the device-mode and modem-mode callbacks into a single handler for cleaner integration.

      • Updated the documentation and sample code to reflect the changes.

    • Fixed multiple bugs and enhanced error handling.

  • nRF Cloud REST library:

  • Firmware over-the-air (FOTA) updates library:

    • Fixed occasional message truncation notifying that the download is complete.

  • nRF Cloud Logging library library:

    • Updated by adding a missing CONFIG prefix.

  • nRF Cloud library:

    • Added the nrf_cloud_obj_location_request_create_timestamped() function to make location requests for past cellular or Wi-Fi scans.

    • Updated:

      • By refactoring the folder structure of the library to separate the different backend implementations.

      • Handling of ports, which led to confusing log messages with byte-inversed values.

  • Downloader library:

    • Fixed an issue where HTTP download would hang if the application had not set the socket receive timeout and data flow from the server stopped. The HTTP transport now sets the socket receive timeout to 30 seconds by default.

Other libraries

Scripts

Integrations

This section provides detailed lists of changes by integration.

Google Fast Pair integration

  • Removed the Fast Pair TinyCrypt cryptographic backend (CONFIG_BT_FAST_PAIR_CRYPTO_TINYCRYPT), because the TinyCrypt library support has been removed from Zephyr. You can use either the Fast Pair Oberon cryptographic backend (CONFIG_BT_FAST_PAIR_CRYPTO_OBERON) or the Fast Pair PSA cryptographic backend (CONFIG_BT_FAST_PAIR_CRYPTO_PSA).

Memfault integration

  • Added a metric tracking the unused stack space of the Bluetooth Long workqueue thread, when the CONFIG_MEMFAULT_NCS_BT_METRICS Kconfig option is enabled. The new metric is named ncs_bt_lw_wq_unused_stack.

  • Updated:

  • Removed a metric for tracking the unused stack of the Bluetooth TX thread (ncs_bt_tx_unused_stack). This thread has been removed in Zephyr v3.7.0.

sdk-nrfxlib

See the changelog for each library in the nrfxlib documentation for additional information.

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 support for S2RAM resume on nRF54H20 devices. MCUboot acts as the S2RAM resume mediator and redirects execution to the application’s native resume routine.

  • Updated KMU mapping to BL_PUBKEY when MCUboot is used as the immutable bootloader for nRF54L Series devices. You can restore the previous KMU mapping (UROT_PUBKEY) with the SB_CONFIG_MCUBOOT_SIGNATURE_KMU_UROT_MAPPING Kconfig option.

Zephyr

The Zephyr fork in nRF Connect SDK (sdk-zephyr) contains all commits from the upstream Zephyr repository up to and including 911b3da1394dc6846c706868b1d407495701926f, 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 911b3da139 ^0fe59bf1e4

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

git log --oneline manifest-rev ^911b3da139

Note

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

Documentation