Migration guide for nRF Connect SDK v2.7.0 (Working draft)

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.

• 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 must not be converted to string format anymore.

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

• Radio test (short-range) sample:

  • The CLI command fem tx_power_control <tx_power_control> replaces fem tx_gain <tx_gain> . This change applies to the sample built with the CONFIG_RADIO_TEST_POWER_CONTROL_AUTOMATIC set to n.

Libraries

This section describes the changes related to libraries.

FEM abstraction layer

• For applications using FEM abstraction layer: The function fem_tx_power_control_set() replaces the function fem_tx_gain_set(). The function fem_default_tx_output_power_get() replaces the function fem_default_tx_gain_get().

Recommended changes

The following changes are recommended for your application to work optimally after the migration.

Samples and applications

• For applications using build types (without child images):

  • The CONF_FILE used for Custom build types is now deprecated and is being replaced with the FILE_SUFFIX variable, inherited from Zephyr. You can read more about it in Custom configurations, Providing CMake options, and the related Zephyr documentation.

    If your application uses build types, it is recommended to update the sample.yaml to use the new variable instead of CONF_FILE.

    Note

    The child image Kconfig configuration are not yet compatible with FILE_SUFFIX. Read more about this in the note in Custom configurations.

Matter

• For the Matter samples and applications:

  • All Partition Manager configuration files (pm_static files) have been removed from the configuration directory. Instead, a pm_static_<BOARD> file has been created for each target board and placed in the samples’ directories. Setting the PM_STATIC_YML_FILE argument in the CMakeLists.txt file has been removed, as it is no longer needed.

Libraries

This section describes the changes related to libraries.

No changes since the latest nRF Connect SDK release.