Migration notes for nRF Connect SDK v3.5.0 (Working draft)

This document describes the changes required or recommended when migrating your application from nRF Connect SDK v3.4.0 to nRF Connect SDK v3.5.0.

Required changes

The following changes are mandatory to make your application work in the same way as in previous releases.

Build and configuration system

This section describes the changes related to the build and configuration system.

  • Device Firmware Update (DFU) support for the nRF70 Series firmware patch has been removed, together with the following Kconfig options:

    • SB_CONFIG_DFU_MULTI_IMAGE_PACKAGE_WIFI_FW_PATCH

    • SB_CONFIG_DFU_ZIP_WIFI_FW_PATCH

    • CONFIG_NRF_WIFI_FW_PATCH_DFU

    If your application enabled any of these options, remove them. The nRF70 Series firmware patch is no longer allocated a separate MCUboot update slot. If you set the SB_CONFIG_MCUBOOT_UPDATEABLE_IMAGES Kconfig option or a static partition layout explicitly for a firmware-patch build, reduce the number of updatable images by one and remove the now-unused update-slot partitions. Storing the nRF70 Series firmware patch in external flash using the SB_CONFIG_WIFI_PATCHES_EXT_FLASH_XIP or SB_CONFIG_WIFI_PATCHES_EXT_FLASH_STORE Kconfig option is not affected.

Samples and applications

This section describes the changes related to samples and applications.

Bluetooth Fast Pair samples

  • The Bluetooth Fast Pair: Locator tag and Bluetooth Fast Pair: Input device samples no longer support the nRF52 and nRF53 Series devices. The following board targets have been removed from both samples:

    • nrf52dk/nrf52832

    • nrf52840dk/nrf52840

    • nrf5340dk/nrf5340/cpuapp

    • nrf5340dk/nrf5340/cpuapp/ns

    Additionally, the following board targets have been removed from the Bluetooth Fast Pair: Locator tag sample:

    • nrf52833dk/nrf52833

    • thingy53/nrf5340/cpuapp

    • thingy53/nrf5340/cpuapp/ns

    If your application is based on one of these samples and targets an nRF52 or nRF53 Series device, continue using the nRF Connect SDK v3.4.0 release or migrate your design to a supported nRF54L Series device.

Libraries

This section describes the changes related to libraries.

  • Location library:

    • The library now always uses the chosen zephyr,wifi node to find the used Wi-Fi device. If your application uses the deprecated ncs,location-wifi node, you need to change it to use the zephyr,wifi node instead:

      chosen {
        zephyr,wifi = &mywifi;
};

Drivers

This section describes the changes related to drivers.