Changelog for nRF Connect SDK v3.2.0-preview2

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 

Added macOS 26 support (Tier 3) to the table listing supported operating systems for proprietary tools.
Updated:
- The required SEGGER J-Link version to v8.66.
- Steps on the Installing the nRF Connect SDK page for installing the nRF Connect SDK and toolchain together. With this change, the separate steps to install the toolchain and the SDK were merged into a single step.

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 

Updated the title of the page about updating the Thingy:91 firmware using the Cellular Monitor app to Updating the Thingy:91 firmware using nRF Connect for Desktop apps.
Removed the page about updating the Thingy:91 firmware using the Programmer app. Its contents are now available in the app documentation on the Programming Nordic Thingy prototyping platforms page. The Partition layout section has been moved to the Updating the Thingy:91 firmware using nRF Connect for Desktop apps page.

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. 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.
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:
- Introduced individual profile configuration options for better user control.
- Deprecated the CONFIG_BT_MESH_NLC_PERF_CONF and CONFIG_BT_MESH_NLC_PERF_DEFAULT Kconfig options. Existing configurations continue to work but you should migrate to individual profile options.

DECT NR+

No changes since the latest nRF Connect SDK release.

Enhanced ShockBurst (ESB)

Added the ESB Monitor mode feature.

Gazell

No changes since the latest nRF Connect SDK release.

Matter

Added documentation for leveraging Matter Compliant Platform certification through the Derived Matter Product (DMP) process. See Matter Compliant Platform and Derived Matter Product (DMP).
Updated to using the CONFIG_PICOLIBC Kconfig option as the C library instead of CONFIG_NEWLIB_LIBC, in compliance with Zephyr requirements.
Removed the CONFIG_CHIP_SPI_NOR and CONFIG_CHIP_QSPI_NOR Kconfig options.

Matter fork

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

nRF IEEE 802.15.4 radio driver

No changes since the latest nRF Connect SDK release.

Thread

Updated:
- The Sleepy End Device types in Thread documentation to clarify the impact of the SSED configuration on the device’s power consumption and provide a guide for SSED fine tuning of SSED devices.
- The platform configuration to use the CONFIG_PICOLIBC Kconfig opiton as the C library instead of CONFIG_NEWLIB_LIBC, in compliance with Zephyr requirements.

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

Added:
- The Audio application API documentation page.
- The nRF Audio: Application-specific Kconfig options page.
- The API documentation in the header files listed on the Audio applications: API documentation page.
- Ability to connect by address as a unicast client.
Updated:
- The power measurements to be disabled by default in debug builds. To enable power measurements, set the CONFIG_NRF_AUDIO_POWER_MEASUREMENT Kconfig option to y in the applications/nrf_audio/prj.conf file.
- The audio application targeting the nRF5340 DK to use pins P1.5 to P1.9 for the I2S interface instead of P0.13 to P0.17. This change was made to avoid conflicts with the onboard peripherals on the nRF5340 DK.
- The API documentation in the header files listed on the Audio applications: API documentation page.

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.

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

Added the Bluetooth: Bluetooth LE master test app application to demonstrate how to use the Bluetooth LE Test GATT Server and test Bluetooth LE functionality in peripheral samples.
Updated the network core image applications for the following samples from the HCI IPC sample to the IPC radio firmware application for multicore builds:
The IPC radio firmware application is commonly used for multicore builds in other nRF Connect SDK samples and projects. Hence, this is to align with the common practice.
Removed support for the thingy53/nrf5340/cpuapp/ns build target from the following samples:
Disabled legacy pairing in the following samples:
- Bluetooth: Central NFC pairing
- Bluetooth: Peripheral power profiling
Support for legacy pairing remains exclusively for Bluetooth: NFC pairing sample to retain compatibility with older Andorid devices.
Bluetooth: Direct Test Mode sample:
- Updated by simplifying the 2-wire UART polling. This is done by replacing the hardware timer with the k_sleep() function.

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.
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.
Bluetooth Mesh NLC: HVAC Integration (Sensor observer) sample:
- Added polling toggle to Button 1 (Button 0 on nRF54 DKs) to start/stop the periodic Sensor Get loop, ensuring the functionality is available on all supported devices including single-button hardware.
- Updated:
  - To demonstrate the Bluetooth Bluetooth Networked Lighting Control profiles HVAC Integration profile.
  - The following Mesh samples to use individual NLC profile configurations instead of the deprecated options:
  - Button functions. Assignments are shifted down one index to accommodate the new polling toggle. The descriptor action has been removed from button actions but is still available through mesh shell commands.
- Removed support for the nrf52dk/nrf52832, since it does not have enough RAM space after NLC support was added.

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

Added:
- The Cellular: nRF Cloud CoAP cellular location sample to demonstrate how to use the nRF Cloud CoAP API for nRF Cloud’s cellular location service.
- The Cellular: nRF Cloud CoAP FOTA sample to demonstrate how to use the nRF Cloud CoAP API for FOTA updates.
- The Cellular: nRF Cloud CoAP device message sample to demonstrate how to use the nRF Cloud CoAP API for device messages.
Cellular: nRF Cloud REST cellular location sample:
- Added runtime setting of the log level for the nRF Cloud logging feature.
Updated the following samples to use the new SEC_TAG_TLS_INVALID definition:
Cellular: Modem Shell sample:
- Added:
  - Support for environment evaluation using the link enveval command.
  - Support for NTN NB-IoT to the link sysmode and link edrx commands.
nRF Cloud multi-service sample:
- Fixed an issue where sporadically the application was stuck waiting for the device to connect to the internet. This was due to wrong Connection Manager initialization.

Cryptography samples

Added the Crypto: KMU usage with CRACEN sample.
Crypto: AES CTR sample:
- Added support for nrf54lm20dk/nrf54lm20a/cpuapp.

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

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.

Edge Impulse samples

No changes since the latest nRF Connect SDK release.

Enhanced ShockBurst samples

Added the Enhanced ShockBurst: Monitor sample to demonstrate how to use the Enhanced ShockBurst (ESB) protocol in Monitor mode.

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.
Matter: Door lock sample:
- Added a callback for the auto-relock feature. This resolves the known issue KRKNWK-20691.

Networking samples

Added support for the nRF7002-EB II with the nrf54lm20dk/nrf54lm20a/cpuapp board target in the following samples:
- AWS IoT
- CoAP Client
- Download
- HTTP Server
- HTTPS Client
- MQTT
- UDP

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

No changes since the latest nRF Connect SDK release.

Thread samples

No changes since the latest nRF Connect SDK release.

Wi-Fi samples

Removed support for the nRF7002-EB II with the nrf54h20dk/nrf54h20/cpuapp board target from the following samples:

Other 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

GATT Human Interface Device (HID) Service library:
- Updated the report length of the HID boot mouse to 3. The bt_hids_boot_mouse_inp_rep_send() function only allows to provide the state of the buttons and mouse movement (for both X and Y axes). No additional data can be provided by the application.

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

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:
- nRF Cloud P-GPS
- Firmware over-the-air (FOTA) updates
Updated the following libraries to use the new SEC_TAG_TLS_INVALID definition for checking whether a security tag is valid:
- AWS FOTA
- FOTA download
- FTP client
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:
- Deprecated the library. Use the nRF Cloud CoAP library instead.
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:
- Updated by refactoring the folder structure of the library to separate the different backend implementations.
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

nRF Profiler library:
- Updated the documentation by separating out the nRF Profiler host tools documentation.

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 

Added:
- The Enhanced ShockBurst Sniffer scripts for the Enhanced ShockBurst: Monitor sample.
- The documentation page for nRF Profiler host tools. The page also describes the script for calculating statistics (calc_stats.py).

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:
- The CONFIG_MEMFAULT_DEVICE_INFO_CUSTOM Kconfig option has been renamed to CONFIG_MEMFAULT_NCS_DEVICE_INFO_CUSTOM.
- The CONFIG_MEMFAULT_DEVICE_INFO_BUILTIN Kconfig option has been renamed to CONFIG_MEMFAULT_NCS_DEVICE_INFO_BUILTIN.
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.

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:

No changes since the latest nRF Connect SDK release.

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 

Updated:
- The Application integration section in the Emergency data storage library documentation to clarify the EMDS storage context usage.
- The Emergency data storage section in the Bluetooth Mesh NLC: Lightness Controller/Energy Monitor sample documentation to clarify the EMDS storage context implementation and usage.
- The Bluetooth Mesh: Device Firmware Update (DFU) distributor sample documentation to clarify the external flash support.
- The Bluetooth Mesh: Device Firmware Update (DFU) target sample documentation to clarify the external flash support.
- The IronSide SE ABI compatibility page to include information about the new IronSide SE releases.
- The nRF54H20 boot sequence page to include information about the boot sequences with MCUboot and with the secondary firmware.
- The Configuring your application for a custom PCB page to add information about how to transition the nRF54H20 SoC to LCS RoT and how to update IronSide SE.
- The IronSide Secure Enclave page to add information on update placement, reset handling, clearing update status, and multiple UICR fields.