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

This document describes the changes required or recommended when migrating your application from nRF Connect SDK v2.7.0 to nRF Connect SDK v2.8.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.

Serial LTE Modem (SLM)

  • The handling of Release Assistance Indication (RAI) socket options has been updated in the #XSOCKETOPT command. The individual RAI-related socket options have been consolidated into a single SO_RAI option. You must modify your application to use the new SO_RAI option with the corresponding value to specify the RAI behavior. The changes are as follows:

    The SO_RAI_NO_DATA, SO_RAI_LAST, SO_RAI_ONE_RESP, SO_RAI_ONGOING, and SO_RAI_WAIT_MORE options have been replaced by the SO_RAI option with values from 1 to 5.

    Replace the following commands in your application code if they were used previously:

    • AT#XSOCKETOPT=1,50, with AT#XSOCKETOPT=1,61,1 to indicate RAI_NO_DATA.

    • AT#XSOCKETOPT=1,51, with AT#XSOCKETOPT=1,61,2 to indicate RAI_LAST.

    • AT#XSOCKETOPT=1,52, with AT#XSOCKETOPT=1,61,3 to indicate RAI_ONE_RESP.

    • AT#XSOCKETOPT=1,53, with AT#XSOCKETOPT=1,61,4 to indicate RAI_ONGOING.

    • AT#XSOCKETOPT=1,54, with AT#XSOCKETOPT=1,61,5 to indicate RAI_WAIT_MORE.

SUIT DFU for nRF54H20

  • The manifest sequence number is no longer configured through a sysbuild Kconfig option. The values are now read from the VERSION file, used for Application version management in Zephyr and the nRF Connect SDK. This change to the sysbuild Kconfig option requires the following updates in the SUIT templates for your project:

    • Remove from all templates:

      suit-manifest-sequence-number: {{ sysbuild['config']['SB_CONFIG_SUIT_ENVELOPE_SEQUENCE_NUM'] }}
      
    • Add the line that corresponds to the manifest name, that is APP_ROOT_SEQ_NUM for the application root manifest:

      suit-manifest-sequence-number: {{ APP_ROOT_SEQ_NUM }}
      

    If the value of the sequence number was changed in your application, append the following line to the VERSION file:

    APP_ROOT_SEQ_NUM = <N>
    

    For the list of all variables, set through the VERSION, refer to the How to customize the SUIT DFU process.

Nordic Secure Immutable Bootloader (NSIB, B0, or B0n)

Custom printing has been dropped in favor of using the logging subsystem, with output printed out to the default logging device. The CONFIG_SECURE_BOOT_DEBUG Kconfig option has been removed. To disable logging in B0 or B0n, set the CONFIG_LOG option to n. To send logs over RTT instead of UART, apply the following settings:

Libraries

This section describes the changes related to libraries.

AT command parser