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

  • The nRF Connect SDK v3.4.0 is based on Zephyr 4.4, Mbed TLS 4.1.0, and TF-M 2.3.

    This release has long-term support (LTS) for a period of five years. During this period, patch releases will provide updates for security vulnerabilities and critical bug fixes. These patch releases should not contain breaking changes unless security fixes require them.

    For more information about LTS scope and maintenance, see Long-term support releases.

  • The nRF Connect SDK v3.4.0 and its patch releases are the last nRF Connect SDK releases that include support for nRF52 Series devices. The nRF52 Series devices are considered feature complete, and support for them will be removed from samples and applications in the development branch.

Added the following features as experimental:

  • PMIC:

    • The following battery health features have been added to Nordic’s fuel gauge algorithm and the fuel gauge sample:

      • State-of-health tracking

      • Cycle count tracking

      • Automatic battery replacement detection

  • Bluetooth®:

    • HID Shorter Connection Intervals (SCI) support on both the HID device side (CONFIG_BT_HIDS_SCI) and the HID host side (CONFIG_BT_HOGP_SCI). This feature lets a Bluetooth LE HID host negotiate sub-7.5 ms connection intervals with a Bluetooth LE HID device for lower input latency in high-performance HID applications.

Deprecated:

  • Deprecated features will not be removed from the LTS branch. It is recommended that all new designs using Nordic devices exclude deprecated features for active development and deployment.

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

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

Toolchain:

  • The nRF Connect SDK toolchain is now based on the Zephyr SDK v1.0.1, with GCC as the recommended compiler.

Release tag

The release tag for the nRF Connect SDK manifest repository (https://github.com/nrfconnect/sdk-nrf) is v3.4.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.4.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.4.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 notes for nRF Connect SDK v3.4.0 for the changes required or recommended when migrating your application from nRF Connect SDK v3.3.0 to nRF Connect SDK v3.4.0.

Known issues

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

  • Updated the Thingy:91 and Thingy:91 X devicetree partitions to match the Partition Manager partitions.

Build and configuration system

  • Removed the internal Haltium and Lumos platform abstractions from the Nordic SoC integration. All references to NRF_PLATFORM_HALTIUM and NRF_PLATFORM_LUMOS have been replaced with explicit checks for SOC_SERIES_NRF54H, SOC_SERIES_NRF92, SOC_SERIES_NRF54L, or SOC_SERIES_NRF71.

    • Renamed Kconfig options and headers:

      • SB_CONFIG_NRF_HALTIUM_GENERATE_UICR to SB_CONFIG_NRF_GENERATE_UICR.

      • The HALTIUM_PLATFORM_PSA_KEY_ID() macro to NRF_PLATFORM_PSA_KEY_ID() (in include/psa/nrf_platform_key_ids.h).

      • haltium_power.h to soc_power.h.

      • haltium_pm_s2ram.h to soc_pm_s2ram.h.

    • Deprecated Kconfig options and headers:

    See Migration notes for nRF Connect SDK v3.4.0 for migration instructions.

    The deprecated symbols, headers, and macros remain available with a deprecation warning and are scheduled for removal in a future release.

  • Consolidated the previously per-SoC soc_power.c and soc_pm_s2ram.c sources for the nRF54H and nRF92 Series in a single shared location under zephyr/soc/nordic/common/.

Bootloaders and DFU

  • Added support for the new LCS API to control bootloader behavior. When this API is enabled, the bootloader can skip signature verification in early LCS states and abort the boot process in the decommissioned state.

  • Fixed DTS support for nRF5340 network core images when b0n was enabled.

  • Reworked the signing procedure for MCUboot images in sysbuild projects that use DTS-defined partitions. Signed images now include the expected image address in the image header and the rom-fixed-flag value, which MCUboot uses to match each image candidate with the correct image target. The signing procedure for images used with MCUboot direct-XIP mode remains unchanged.

Developing with nRF91 Series

Developing with nRF54L Series

Developing with nRF54H Series

  • Updated MCUboot to support MRAM write protection for up to four images.

Security

  • Added:

  • Updated:

    • Renamed IronSide Secure Element to IronSide Secure Enclave.

    • IronSide SE to version 23.7.0+30. For more information, see nRF54H20 IronSide SE binaries changelog.

    • Oberon PSA Crypto from v1.5.4 to v2.0.0. The new version aligns with TF-PSA-Crypto v1.1.0.

    • How the CONFIG_NRF_SECURITY and CONFIG_PSA_CRYPTO Kconfig options interact with each other. CONFIG_NRF_SECURITY is now promptless and auto-enabled indirectly by CONFIG_PSA_CRYPTO.

    • Approach to store keys in the KMU so that AEAD algorithms with non-default (shortened) tag lengths are supported.

    • The Supported cryptographic operations in the nRF Connect SDK page:

      • The page now lists both nRF54LS05A and nRF54LS05B in the support tables.

      • The CRACEN support status for nRF54LV10A for most of the algorithms changed from Experimental to Supported.

      • The Side-channel countermeasures section now includes information for nRF54H20.

  • Fixed:

    • Issues with incorrect support status on the Supported cryptographic operations in the nRF Connect SDK page:

      • The CONFIG_PSA_WANT_ALG_GCM Kconfig option is now correctly listed as unsupported for SoCs with Arm CryptoCell CC310.

      • The tables for supported AES key wrapping algorithms for nRF54L Series devices now list the nRF54LS05 device (not supported in the CRACEN driver; experimental in the nrf_oberon driver).

      • The post-quantum cryptography algorithms for nrf_oberon under Key types and key management are now correctly listed as experimental instead of supported.

      • The SPAKE2+ for Matter is now correctly listed as supported instead of experimental.

      • The WPA3-SAE hash-to-element algorithm is now correctly listed as a KDF algorithm, not a PAKE algorithm.

      • The SHA-256/192 and SHAKE hashing algorithms are now correctly listed as not supported in the CRACEN driver and experimental in the nrf_oberon driver. The only exception is the SHAKE256 512 bits algorithm, which is supported in both the CRACEN and nrf_oberon drivers.

  • Removed the CONFIG_NRF_SECURITY_ADVANCED Kconfig option.

Security libraries

Mbed TLS

Trusted Firmware-M (TF-M)

  • Updated to version 2.3.0.

Protocols

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

Bluetooth LE

Bluetooth Mesh

  • Added:

    • The Configuring sysbuild and partitions guide on how to configure DFU for Bluetooth Mesh samples.

    • Recommendations for sizing the persistent storage partitions to handle continuous storage of the replay protection list.

Wi-Fi®

  • Added the nordic-wifi-enterprise snippet to be used for Wi-Fi enterprise. For more information, see the Migration notes for nRF Connect SDK v3.4.0.

  • Updated the hostap_crypto library to use a single backend, CONFIG_HOSTAP_CRYPTO_ALT_PSA, for all modes. The older CONFIG_HOSTAP_CRYPTO_ALT_LEGACY_PSA backend has been removed.

  • Removed support for DES-encrypted private keys in Wi-Fi Enterprise (EAP-TLS) following the update to Mbed TLS 4.1.0/TF-PSA-Crypto 1.1.0 in the nRF Connect SDK. TF-PSA-Crypto no longer implements DES ciphers, therefore PKCS#8 client keys encrypted with DES-EDE3-CBC cannot be decrypted during the TLS handshake (including the FreeRADIUS rsa2k test certificates). Use zephyr/samples/net/wifi/test_certs/rsa2k_no_des, re-encrypt credentials with AES (PBES2), or use unencrypted keys when provisioning enterprise credentials. See the Wi-Fi Management documentation for details.

Applications

This section provides detailed lists of changes by application.

Connectivity bridge

  • Updated to use devicetree (DTS) for defining NVM partitions instead of the deprecated Partition Manager.

High-Performance Framework (HPF)

  • Added support for the nRF54LV10A SoC in HPF MSPI.

nRF Audio (formerly nRF5340 Audio)

  • Renamed the application to nRF Audio from nRF5340 Audio.

  • Added:

    • The CONFIG_BT_AUDIO_BROADCAST_BASE_PRINT Kconfig option to print the contents of the BASE when it is received. This option is intended for debugging purposes. It is only valid for the broadcast sink application.

    • CONFIG_LTO to enable link-time optimization for the application. It improves application performance and reduces code size.

  • Updated:

    • The call to hci_vs_sdc_iso_read_tx_timestamp() so that, when sending ISO data, it is performed at regular intervals instead of every SDU interval. This change reduces the frequency of application-controller time synchronization, while significantly reducing processing overhead.

    • The group creation in the unicast client application so that it waits until all connected devices have finished discovery.

    • The unicast server (headset) now exposes its source endpoint as default. This means that the unicast client (gateway) can choose whether to enable it or not.

    • The buildprog.py script no longer supports the -u (user name) option. Use the -cn (custom name) option instead. The custom name is now used for both unicast and broadcast. Changing this parameter requires a pristine build. The option is intended as a convenience argument. Set names through configuration options for persistent configuration.

nRF Desktop

  • Updated:

    • The application configurations to use devicetree (DTS) for defining non-volatile memory partitions instead of the deprecated Partition Manager. This includes configuration of main application image and other sysbuild images built together with it (for example bootloader).

    • The application configurations to change the non-volatile memory self-protection mechanism in the MCUboot image on the nRF54L board targets (CONFIG_SOC_SERIES_NRF54L). The CONFIG_NCS_MCUBOOT_DISABLE_SELF_RWX Kconfig option is used instead of the CONFIG_FPROTECT to disable read, write, and execute from the memory area that holds the MCUboot bootloader. This is done to improve the protection of the MCUboot immutable bootloader code.

nRF Machine Learning (Edge Impulse)

Samples

This section provides detailed lists of changes by sample.

Bluetooth samples

Bluetooth Mesh samples

  • Bluetooth Mesh: Light sample:

    • The partition layout for the nrf5340dk/nrf5340/cpuapp/ns board target is not backward compatible with the previous versions of the sample. This affects builds with support of point-to-point Device Firmware Update (DFU) over the Simple Management Protocol (SMP).

    • Updated the approach to build the sample with point-to-point Device Firmware Update (DFU) over the Simple Management Protocol (SMP). There are no overlay-dfu.conf and sysbuild-dfu.conf files anymore. DFU support is enabled as a suffixed configuration.

  • Bluetooth Mesh NLC: Lightness Controller/Energy Monitor sample:

    • The partition layout for the nrf5340dk/nrf5340/cpuapp/ns board target is not backward compatible with the previous versions of the sample. This affects builds with support for the EMDS.

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

    • The partition layout for the nrf54l15dk/nrf54l15/cpuapp, nrf54l15dk/nrf54l10/cpuapp, and nrf54lm20dk/nrf54lm20a/cpuapp board targets is not backward compatible with the previous versions of the sample.

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

    • The partition layout for the nrf54l15dk/nrf54l15/cpuapp, nrf54l15dk/nrf54l10/cpuapp, and nrf54lm20dk/nrf54lm20a/cpuapp board targets is not backward compatible with the previous versions of the sample.

Bluetooth Fast Pair samples

  • Updated the DTS overlays of the Fast Pair samples to use the new zephyr,mapped-partition compatible property for each partition node. The change aligns the board target overlays with the layout produced by the Partition Manager-to-DTS helper script (scripts/pm_to_dts.py). See the Google Fast Pair guide to learn how to align the DTS partition map in your project using the new property.

  • Removed the remaining nrf54h20dk/nrf54h20/cpuapp board target configurations from the Fast Pair samples. Removed references to the nrf54h20dk/nrf54h20/cpuapp board target from the Fast Pair sample documentation, including descriptions of nRF54H-specific solutions such as the legacy SUIT DFU integration. Support for this target was already dropped during the IronSide SE migration in the nRF Connect SDK v3.1.0 release.

  • Bluetooth Fast Pair: Locator tag sample:

    • Added initial support for the nRF54L15 TAG (nrf54l15tag/nrf54l15/cpuapp board target). The nrf54l15tag/nrf54l15/cpuapp board target is a complete prototyping platform in a compact form factor. It features the nRF54L15 SoC with additional sensors, RGB LED, button, and a battery. The sample on this board target can closely represent a final product based on the nRF54L15 SoC.

    • Updated:

      • UI thread handling for reference board targets with a speaker by moving the speaker control into the common indication thread. The signaling is now done using the Events API.

      • The configuration of the non-volatile memory self-protection mechanism in the MCUboot image on the nRF54L board targets. The CONFIG_NCS_MCUBOOT_DISABLE_SELF_RWX Kconfig option now replaces the CONFIG_FPROTECT, which is associated with the Hardware flash write protection library. The new mechanism uses a dedicated RRAMC region to disable read, write, and execute access to the MCUboot partition right before jumping to the application image.

    • Fixed the ringing status indications with the green LED flashes for reference board targets. A ringing status indication was often skipped during the motion detection event.

Cellular samples

  • Removed:

    • All nRF Cloud REST samples as the nRF Cloud REST library has been removed.

    • Usage of nRF Cloud logging in samples as the feature is being sunset.

    • The Cellular: nRF Cloud multi-service sample.

  • Crypto: PSA TLS sample:

    • Updated the TLS version support section after the Mbed TLS v4.1.0 update.

  • Cellular: GNSS sample:

    • Updated to use the nRF Cloud CoAP library instead of the removed nRF Cloud REST library.

  • Cellular: Modem Shell sample:

    • Added devicetree overlays for data throughput testing.

    • Updated to use the nRF Cloud CoAP library instead of the removed nRF Cloud REST library.

Cryptography samples

DFU samples

Edge Impulse samples

Matter samples

  • Updated the Matter: Window covering sample to use the Thread Sleepy End Device (SED) device type by default. You can now enable the Thread Synchronized Sleepy End Device (SSED) device type as an optional feature.

  • Removed:

    • Support for the nRF7002 DK and nRF5340 DK used with the nRF7002 EK shield from all Matter samples, as this configuration was deprecated in the nRF Connect SDK v3.2.0. The removal is mainly due to the very limited non-volatile memory available for application code. As an alternative, use the nRF54LM20A or nRF54LM20B SoC with the nRF7002-EB II shield. This combination provides significantly more non-volatile memory for Matter over Wi-Fi applications.

    • The implementation of the Matter Door lock sample has been relocated to the nRF Door Lock and Access Control Add-on. The add-on is an extensible solution offering additional features and expanded integration capabilities. It enables the development of not only Matter-compliant door locks, but also those supporting Aliro and hybrid Matter and Aliro combined functionalities, thereby facilitating the design of versatile smart lock solutions.

    • The AWS IoT integration variant from the Matter: Light bulb sample.

Networking samples

  • Removed Partition Manager for all Wi-Fi targets from the following samples:

    Flash and SRAM partitions are supplied using devicetree overlays instead.

  • MQTT sample:

    • Added the CONFIG_PSA_WANT_ECC_SECP_R1_384 Kconfig option to the TLS overlay files, which is required by the CA certificate of mqtt.nordicsemi.academy.

    • Updated the default MQTT broker from test.mosquitto.org to mqtt.nordicsemi.academy because of recurring instability in the previous broker.

  • Azure IoT Hub sample:

    • Added support for the nRF54LM20 DK with the nRF7002-EB II shield.

Peripheral samples

  • IEEE 802.15.4 PHY test tool sample:

    • Removed unused functions from the rf_proc.c file and the rf_proc.h header file.

  • Radio test (short-range) sample:

    • Added:

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

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

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

      • print_channel_sequence shell command that prints the currently configured channel sequence.

      • set_channel_sequence_hopping_mode shell command that allows for setting the hopping mode for the channel sequence.

      • Support for pin debugging of radio events on nRF54L Series devices.

    • Updated the start_duty_cycle_modulated_tx command to accept an optional argument specifying the number of packets to transmit. If no additional argument is provided, the command works as before.

    • Fixed an issue where the start_duty_cycle_modulated_tx command would not work correctly on nRF52 Series devices if the command was triggered more than once.

PMIC samples

Wi-Fi samples

  • Added the Wi-Fi: nRF Cloud sample, refactored from the former Cellular: nRF Cloud multi-service sample. This sample targets the nRF7002 Wi-Fi companion IC, using Wi-Fi as the transport instead of LTE.

Drivers

This section provides detailed lists of changes by driver.

  • Fixed an issue where the low power UART can fail after a reset if the reset occurs during transmission.

Libraries

This section provides detailed lists of changes by library.

Binary libraries

  • LwM2M carrier library:

    • Added support for building without Partition Manager. This requires an lwm2m_carrier partition to be defined in the devicetree.

Bluetooth libraries and services

Modem libraries

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

  • Location library:

    • Fixed an issue where cloud location requests were not sent when cellular profile 1 was active.

  • Modem library integration layer library:

    • Added support for building for the nRF91 board without Partition Manager. This requires cpuapp_cpucell_ipc_shm_ctrl, cpuapp_cpucell_ipc_shm_heap, and cpucell_cpuapp_ipc_shm_heap partitions to be defined in the devicetree. Use a separate cpucell_cpuapp_ipc_shm_trace partition for modem tracing instead of splitting the cpucell_cpuapp_ipc_shm_heap partition.

  • Modem information library:

    • Fixed a bug where supplying a very large buffer would cause a buffer overflow internally due to incorrect format string usage.

Libraries for networking

  • Azure FOTA library:

    • Fixed a potential NULL-pointer dereference that occurred when the device twin JSON parsers used the jobId, fwUpdateStatus, currentFwVersion, pendingFwVersion, host, and path fields without verifying that the JSON nodes were strings.

  • nRF Cloud device provisioning library:

    • Removed dependency on the LTE link control library. The AT monitor library is now used for tracking network connectivity status.

  • nRF Cloud library:

    • Added the CONFIG_NRF_CLOUD_SEND_DEVICE_INFO_BOOTLOADER_VERSION Kconfig option to include the active MCUboot (B1) fw_info version as bootloaderVersion in deviceInfo.

    • Updated by changing the default device ID source from CONFIG_NRF_CLOUD_CLIENT_ID_SRC_IMEI to the device UUID. On an nRF9160 device the default is now CONFIG_NRF_CLOUD_CLIENT_ID_SRC_INTERNAL_UUID, which reads the UUID from the JWT iss claim and preserves compatibility with field devices provisioned through older nrfcloud-utils flows. On the nRF91x1 and future SoCs, the default is CONFIG_NRF_CLOUD_CLIENT_ID_SRC_MDM_DEVICE_UUID, which reads the UUID using AT%DEVICEUUID without pulling in CONFIG_MODEM_JWT. Each option is constrained to its target SoC at the Kconfig level. See the Migration notes for nRF Connect SDK v3.4.0 for the impact on existing devices that relied on the previous IMEI default.

    • Deprecated the CONFIG_NRF_CLOUD_CLIENT_ID_SRC_IMEI and CONFIG_NRF_CLOUD_CLIENT_ID_SRC_HW_ID Kconfig options. Use the default UUID source for new applications.

    • Fixed:

      • An issue where PEM private keys with CRLF line endings could not be decoded correctly for JWT signing used in nRF Cloud CoAP authentication.

      • A DTLS socket option setup to inspect errno after setsockopt() failures instead of comparing the return value to EOPNOTSUPP or EINVAL, which could mishandle unsupported options during DTLS configuration.

      • The DTLS handshake timeout configuration on native (non-modem) sockets by using TLS_DTLS_HANDSHAKE_TIMEOUT_MIN and TLS_DTLS_HANDSHAKE_TIMEOUT_MAX instead of the modem-only TLS_DTLS_HANDSHAKE_TIMEO option, avoiding handshake failures when connecting to nRF Cloud over Wi-Fi.

      • The internal CoAP client socket descriptor not being updated immediately after a new DTLS socket was connected, which could leave client->cc.fd stale during reconnect and interfere with CoAP polling, receive, and retransmit paths.

    • Removed:

      • The nRF Cloud Alerts library. As part of the migration to nRF Cloud powered by Memfault, the nRF Cloud Alerts feature is now redundant. Memfault’s Trace Events feature replaces the Alerts feature, as it provides equivalent functionality for event reporting, and it also adds enhanced debugging capabilities that were not available with Alerts.

      • The nRF Cloud REST library.

      • The nRF Cloud logging library.

  • nRF Cloud P-GPS library:

    • Updated:

    • Fixed:

      • An issue that caused predictions to be stored into an incorrect index in the flash memory, leading to an error when the affected predictions were used.

      • An issue where the library tried to use predictions that had not yet been flushed to the flash memory, leading to a prediction validation error.

      • An issue where the library kept trying to use corrupted predictions.

  • nRF 802.15.4 callbacks dispatcher library:

    • Updated the status from experimental to supported.

  • MQTT helper library:

    • Fixed an issue where the library could overflow the broker address buffer if an IPv6 address was returned by the DNS resolver while the CONFIG_NET_IPV6 Kconfig option was disabled.

Other libraries

  • nRF Profiler library:

    • Added sending CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC through the info RTT channel as part of the system description. This enables support for the nRF54L Series SoCs (CONFIG_SOC_SERIES_NRF54L) by providing accurate hardware clock information to the profiler host tools. The hardware clock frequency varies between different SoCs, and the host tools require this information to correctly interpret the received timestamps. This change breaks the backward compatibility between the library and host tools due to modifications in the info RTT channel string layout. The nRF Profiler event descriptions are now sent within the <ev_info_start> and <ev_info_stop> markers. System configuration details are now sent within the <sys_config_start> and <sys_config_stop> markers. The system configuration details are formatted as a list of key-value data, for example, key1,value1. Subsequent entries are separated by newlines. The value returned by the sys_clock_hw_cycles_per_sec() function is sent using the sys_clock_hw_cycles_per_sec key.

  • Removed the deprecated Edge Impulse wrapper library. The library has been replaced by the Edge Impulse SDK in Edge AI Add-on for nRF Connect SDK.

sdk-nrfxlib

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

Scripts

This section provides detailed lists of changes by script.

  • Software Bill of Materials script:

    • Added:

      • License handling of the LLVM toolchain libraries.

      • Support for HEX-only softdevice sysbuild domains.

      • Updated the SPDX License List database to version 3.28.0.

  • nRF Profiler host tools script:

    • Updated the scripts to use hardware clock information from SoC to enable accurate conversion from hardware clock cycles to seconds. Refactored the parser to support the new RTT communication layout, including the handling of <ev_info_...> and <sys_config_...> data markers.

    • Fixed the ms_per_timestamp_tick parameter (defined in the rtt_nordic_config.py) to accurately align with the system clock’s frequency of the nRF52, nRF53, and nRF91 Series SoCs.

Integrations

This section provides detailed lists of changes by integration.

Edge Impulse integration

Memfault integration

  • Added:

    • Devicetree support for the internal flash coredump backend (CONFIG_MEMFAULT_NCS_INTERNAL_FLASH_BACKED_COREDUMP). The backend now locates its storage from a fixed partition labeled memfault_coredump_partition when Partition Manager is disabled, while continuing to support Partition Manager when enabled.

    • The Flash-backed coredump storage snippet that supplies a board-specific partition overlay for flash-backed coredump storage on common DKs and Thingy:91 or Thingy:91 X.

  • Updated Memfault to version 1.40.0. See the Memfault firmware SDK changelog for details.

nRF Cloud integration

  • Added a memfaultEn control key in the Device Shadow, enabling dynamic enable/disable of Memfault chunk uploads at runtime. This is done through Device Shadow updates. A new control variable is used.

MCUboot

The MCUboot fork in the 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:

  • Fixed a possible infinite loop in the bootloader information sharing procedure when the Kconfig options CONFIG_BOOT_SHARE_DATA_BOOTINFO and CONFIG_MCUBOOT_HW_DOWNGRADE_PREVENTION are enabled. Iterating boot-info security counters could spin forever if the boot_nv_security_counter_get() function failed for an image index (for example, backends that expose only one NV counter when CONFIG_BOOT_IMAGE_NUMBER is greater than one).

  • The following non-PSA Crypto implementations were deprecated:

    • CONFIG_BOOT_ECDSA_NRF_OBERON

    • CONFIG_BOOT_ECDSA_TINYCRYPT

    • CONFIG_BOOT_ECDSA_CC310

    • CONFIG_BOOT_ED25519_TINYCRYPT

    • CONFIG_BOOT_ED25519_MBEDTLS

    Use their PSA Crypto counterparts instead.

  • Updated image matching to use the explicit image address when CONFIG_MCUBOOT_CHECK_HEADER_LOAD_ADDRESS is enabled. MCUboot now uses the ih_load_address field of the image header instead of the reset vector address, allowing it to match an incoming image to the correct partition even when the image is encrypted. The new method is enabled by default when MCUboot is built with DTS partitioning. Firmware must be signed with the imgtool.py sign --rom-fixed <partition_address> parameter, which is handled by the nRF Connect SDK signing procedures.

Zephyr

The Zephyr fork in the nRF Connect SDK (sdk-zephyr) contains all commits from the upstream Zephyr repository up to and including 684c9e8f32e4373a21098559f748f06915f950c9, 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 684c9e8f32 ^93b5f19f99

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

git log --oneline manifest-rev ^684c9e8f32

The current nRF Connect SDK main branch is based on revision 684c9e8f32 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

  • Added the release.yaml file with device classification support overview.

  • Updated the VERSION file to follow the common version format structure. The common version file format structure is extended with a VERSION_METADATA field for nRF Connect SDK.

Documentation

Updated: