Changelog for nRF Connect SDK v3.2.0-preview3

This changelog reflects the most relevant changes from the latest official release.

Known issues

Known issues are only tracked for the latest official release. See known issues for nRF Connect SDK v3.1.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

Board support

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

Build and configuration system

No changes since the latest nRF Connect SDK release.

Bootloaders and DFU

  • Added an option to restore progress after a power failure when using DFU multi-image with MCUboot.

Developing with nRF91 Series

No changes since the latest nRF Connect SDK release.

Developing with nRF70 Series

No changes since the latest nRF Connect SDK release.

Developing with nRF54L Series

No changes since the latest nRF Connect SDK release.

Developing with nRF54H Series

No changes since the latest nRF Connect SDK release.

Developing with nRF53 Series

No changes since the latest nRF Connect SDK release.

Developing with nRF52 Series

No changes since the latest nRF Connect SDK release.

Developing with Thingy:91 X

No changes since the latest nRF Connect SDK release.

Developing with Thingy:91

Developing with Thingy:53

No changes since the latest nRF Connect SDK release.

Developing with PMICs

No changes since the latest nRF Connect SDK release.

Developing with Front-End Modules

No changes since the latest nRF Connect SDK release.

Developing with custom boards

No changes since the latest nRF Connect SDK release.

Developing with coprocessors

No changes since the latest nRF Connect SDK release.

Security

  • Added:

    • CRACEN and nrf_oberon driver support for nRF54LM20 and nRF54LV10. For the list of supported features and limitations, see the Supported cryptographic operations in the nRF Connect SDK page.

    • Support for disabling Internal Trusted Storage (ITS) on nRF54L series devices when using CONFIG_TFM_PARTITION_CRYPTO with Trusted Firmware-M (TF-M) through the CONFIG_TFM_PARTITION_INTERNAL_TRUSTED_STORAGE Kconfig option.

    • Support for AES in counter mode using CRACEN for the nRF54LM20 DK.

    • Experimental support for TF-M on the nRF54LV10A SoC.

    • Experimental support for NSIB and MCUBoot on the nRF54LV10A SoC.

    • Experimental support for KMU on the nRF54LV10A SoC.

    • Experimental support for compression and encryption on the nRF54LV10A SoC.

  • Updated:

    • The Security page with a table that lists the versions of security components implemented in the nRF Connect SDK.

    • The Secure storage in the nRF Connect SDK page with updated information about the secure storage configuration in the nRF Connect SDK. Also renamed the page from “Trusted storage in the nRF Connect SDK.”

Protocols

No changes since the latest nRF Connect SDK release.

Bluetooth® LE

No changes since the latest nRF Connect SDK release.

Bluetooth Mesh

  • Updated the NLC profile configuration system:

DECT NR+

No changes since the latest nRF Connect SDK release.

Enhanced ShockBurst (ESB)

Gazell

No changes since the latest nRF Connect SDK release.

Matter

Matter fork

nRF IEEE 802.15.4 radio driver

No changes since the latest nRF Connect SDK release.

Thread

Wi-Fi®

No changes since the latest nRF Connect SDK release.

Applications

No changes since the latest nRF Connect SDK release.

Connectivity bridge

No changes since the latest nRF Connect SDK release.

IPC radio firmware

No changes since the latest nRF Connect SDK release.

Matter bridge

  • 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 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.

nRF5340 Audio

nRF Desktop

  • 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 will fail 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 were 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 the bare variant of the board was introduced in Zephyr. The application did not switch to the bare board variant to keep backwards compatibility.

    • The HID state module to allow for delayed registration of HID report providers. Before the change was introduced, subscribing to a HID input report before the respective provider was registered triggered an assertion failure.

    • 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 HID state power manager module to skip 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 of the HID state module and default HID report providers to simplify getting started with updating HID input reports used by the application or introducing support for a new HID input report.

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.

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

Serial LTE modem

  • Updated to use the new SEC_TAG_TLS_INVALID definition as a placeholder for security tags.

Thingy:53: Matter weather station

No changes since the latest nRF Connect SDK release.

Samples

This section provides detailed lists of changes by sample.

Bluetooth samples

Bluetooth Mesh samples

  • Added external flash settings support for the nrf52840dk/nrf52840 board targets in all Bluetooth Mesh samples.

  • Bluetooth Mesh: Device Firmware Update (DFU) distributor sample:

    • Added:

    • Support for external flash memory for the nrf52840dk/nrf52840 and the nrf54l15dk/nrf54l15/cpuapp as the secondary partition for the DFU process.

    • Support for external flash settings for the nrf52840dk/nrf52840 board targets.

    • Updated the FILE_SUFFIX make variable to use more descriptive suffixes for external flash configurations. The new suffixes are _dfu_ext_flash for external flash DFU storage and _ext_flash_settings for external flash settings storage.

  • Bluetooth Mesh: Device Firmware Update (DFU) target sample:

    • Added:

      • Support for external flash memory for the nrf52840dk/nrf52840 and the nrf54l15dk/nrf54l15/cpuapp as the secondary partition for the DFU process.

      • Support for external flash settings for the nrf52840dk/nrf52840 board targets.

    • Updated the FILE_SUFFIX make variable to use more descriptive suffixes for external flash configurations. The new suffixes are _dfu_ext_flash for external flash DFU storage and _ext_flash_settings for external flash settings storage.

  • Bluetooth Mesh NLC: HVAC Integration (Sensor observer) sample:

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 will fail 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. Note, that 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. Note, that the Fast Pair subsystem still uses the Oberon software library.

Cellular samples

Cryptography samples

  • Added:

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

    • The Crypto: KMU usage with CRACEN sample.

  • Crypto: AES CTR sample:

    • Added support for nrf54lm20dk/nrf54lm20a/cpuapp.

  • Crypto: Persistent key usage sample:

    • Added support for the nrf54h20dk/nrf54h20/cpuapp board target, demonstrating use of Internal Trusted Storage (ITS) on the nRF54H20 DK.

Debug samples

No changes since the latest nRF Connect SDK release.

DECT NR+ samples

No changes since the latest nRF Connect SDK release.

DFU samples

Edge Impulse samples

No changes since the latest nRF Connect SDK release.

Enhanced ShockBurst samples

Gazell samples

No changes since the latest nRF Connect SDK release.

Keys samples

No changes since the latest nRF Connect SDK release.

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_custom_board toggle paragraph in the Matter advanced configuration section of all Matter samples that demonstrates how add and configure a custom board.

  • 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 two uA.

  • Matter: Door lock sample:

    • Added a callback for the auto-relock feature. This resolves the known issue KRKNWK-20691.

Networking samples

NFC samples

No changes since the latest nRF Connect SDK release.

nRF5340 samples

No changes since the latest nRF Connect SDK release.

Peripheral samples

No changes since the latest nRF Connect SDK release.

PMIC samples

No changes since the latest nRF Connect SDK release.

Protocol serialization samples

No changes since the latest nRF Connect SDK release.

SDFW samples

No changes since the latest nRF Connect SDK release.

Sensor samples

No changes since the latest nRF Connect SDK release.

SUIT samples

No changes since the latest nRF Connect SDK release.

Trusted Firmware-M (TF-M) samples

  • TF-M Hello World sample:

    • Added support for the nrf54lv10dk/nrf54lv10a/cpuapp/ns board target.

Thread samples

No changes since the latest nRF Connect SDK release.

Wi-Fi samples

Other samples

  • Added experimental support for the nRF54LV10A SoC in the following samples:

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

  • 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).

Drivers

This section provides detailed lists of changes by driver.

Wi-Fi drivers

No changes since the latest nRF Connect SDK release.

Flash drivers

No changes since the latest nRF Connect SDK release.

Libraries

This section provides detailed lists of changes by library.

Binary libraries

No changes since the latest nRF Connect SDK release.

Bluetooth libraries and services

Common Application Framework

No changes since the latest nRF Connect SDK release.

Debug libraries

No changes since the latest nRF Connect SDK release.

DFU libraries

No changes since the latest nRF Connect SDK release.

Gazell libraries

No changes since the latest nRF Connect SDK release.

Security libraries

No changes since the latest nRF Connect SDK release.

Modem libraries

  • LTE link control library:

    • 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.

    • 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.

  • Modem library integration layer library:

  • PDN library:

    • Fixed:

      • An issue where wrong APN rate control event was sent.

      • An issue where a malformed +CGEV notification was not handled correctly.

Multiprotocol Service Layer libraries

No changes since the latest nRF Connect SDK release.

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:

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

      • By moving root CA provisioning to modem initialization callback to avoid blocking and ensure proper state.

      • By expanding the event handler to report more provisioning events, including failures.

      • By making the event handler callback mandatory to notify the application of failures and prevent silent errors.

      • By unifying the device‐mode and modem‐mode callbacks into a single handler for cleaner integration.

      • The documentation and sample code accordingly.

    • 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 was complete.

  • nRF Cloud Logging library library:

    • Updated by adding a missing CONFIG prefix.

  • nRF Cloud library:

  • 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.

Libraries for NFC

No changes since the latest nRF Connect SDK release.

nRF RPC libraries

No changes since the latest nRF Connect SDK release.

Other libraries

Shell libraries

No changes since the latest nRF Connect SDK release.

sdk-nrfxlib

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

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 was 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).

Edge Impulse integration

No changes since the latest nRF Connect SDK release.

Memfault integration

  • Updated:

  • 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.

  • Removed a metric for the tracking Bluetooth TX thread unused stack ncs_bt_tx_unused_stack. The thread in question was removed in Zephyr v3.7.0.

AVSystem integration

No changes since the latest nRF Connect SDK release.

nRF Cloud integration

No changes since the latest nRF Connect SDK release.

CoreMark integration

No changes since the latest nRF Connect SDK release.

DULT integration

No changes since the latest nRF Connect SDK release.

MCUboot

The MCUboot fork in nRF Connect SDK (sdk-mcuboot) contains all commits from the upstream MCUboot repository up to and including 81315483fcbdf1f1524c2b34a1fd4de6c77cd0f4, 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 0fe59bf1e4b96122c3467295b09a034e399c5ee6, 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 0fe59bf1e4 ^fdeb735017

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

git log --oneline manifest-rev ^0fe59bf1e4

The current nRF Connect SDK main branch is based on revision 0fe59bf1e4 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.

Additions specific to nRF Connect SDK

No changes since the latest nRF Connect SDK release.

zcbor

No changes since the latest nRF Connect SDK release.

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.

Documentation