Migration guide for nRF Connect SDK v2.7.0

This document describes the changes required or recommended when migrating your application from nRF Connect SDK v2.6.0 to nRF Connect SDK v2.7.0.

Required changes

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

Samples and applications

This section describes the changes related to samples and applications.

Applications using the dfu_application.zip file

For all applications using the dfu_application.zip file generated by the nRF Connect SDK build system:

  • Make sure that your DFU host tools support the dfu_application.zip file with the new format version (1). If the tools do not support the new format version and you cannot update them, you can manually align the content of the zip archive generated with format version 1 to version 0:

  • Build your application in the same configuration with the nRF Connect SDK v2.6 release to obtain a reference file dfu_application.zip with format version 0.

  • Manually align the content of the dfu_application.zip file generated with format version 1:

    • Align the properties described in the manifest.json file. Make sure to update all of the fields that are used by the selected DFU host tool.

    • Rename the binary files that are included in the zip archive to match the file names used by the updated manifest. The binary file content is interoperable across nRF Connect SDK releases.

Samples and applications using short-range radio

All samples and applications built for multi-core SoCs were migrated to use IPC radio firmware as the default image for the network core (on nRF5340) or the radio core (on nRF54H20).

The samples previously built for those cores are no longer used in the default builds: Bluetooth: HCI IPC, nRF IEEE 802.15.4: Serialization RPMsg, nRF5340: Multiprotocol RPMsg, and Bluetooth: Host for nRF RPC Bluetooth Low Energy.

nRF5340 Audio applications

Wi-Fi

  • Wi-Fi: Shell sample:

    • The parameters of the connect and ap enable commands have been updated. Check the updated parameters using the -h help option of the command.

Serial LTE Modem (SLM)

The AT command parsing has been updated to utilize the Custom AT commands library. If you have introduced custom AT commands to the SLM, you need to update the command parsing to use the new library. See the Extending the application page for more information.

Peripheral samples

Matter

With the inheritance of Zephyr’s Sysbuild (System build) in the nRF Connect SDK Sysbuild, some changes are provided to the Matter samples and applications:

  • CONFIG_CHIP_FACTORY_DATA_BUILD Kconfig option is deprecated and you need to use the SB_CONFIG_MATTER_FACTORY_DATA_GENERATE Kconfig option instead to enable or disable creating the factory data set during building a Matter sample. To enable factory data support on your device, you still need to set the CONFIG_CHIP_FACTORY_DATA to y.

  • Factory data output files are now located in the <application_name>/zephyr/ directory within the build directory.

  • CONFIG_CHIP_FACTORY_DATA_MERGE_WITH_FIRMWARE Kconfig option is deprecated in sysbuild and you need to use the SB_CONFIG_MATTER_FACTORY_DATA_MERGE_WITH_FIRMWARE Kconfig option instead to enable or disable merging the factory data HEX file with the final firmware HEX file.

  • SB_CONFIG_MATTER_OTA Kconfig option has been added to enable or disable generating Matter OTA package during the building process.

  • CONFIG_CHIP_OTA_IMAGE_FILE_NAME Kconfig option is deprecated and you need to use the SB_CONFIG_MATTER_OTA_IMAGE_FILE_NAME Kconfig option instead to define Matter OTA output filename.

Note

If you want to build a sample without using sysbuild, you need to use the old Kconfig options.

Libraries

This section describes the changes related to libraries.

MQTT helper library

For applications using the MQTT helper library:

  • The CONFIG_MQTT_HELPER_CERTIFICATES_FILE is now replaced by CONFIG_MQTT_HELPER_CERTIFICATES_FOLDER. The new option is a folder path where the certificates are stored. The folder path must be relative to the root of the project.

    If you are using the MQTT helper library, you must update the Kconfig option to use the new option.

  • When using the CONFIG_MQTT_HELPER_PROVISION_CERTIFICATES Kconfig option, the certificate files must be in standard PEM format. This means that the PEM files need not be converted to string format anymore.

FEM abstraction layer

For applications using FEM abstraction layer:

Modem library

For applications using Modem library integration layer:

  • The option CONFIG_NRF_MODEM_LIB_TRACE_BACKEND_UART_ZEPHYR is now deprecated. To enable the UART trace backend, use the nrf91-modem-trace-uart snippet instead, or add a similar configuration in application overlays. The snippet is located in snippets/nrf91-modem-trace-uart/.