• State Not Answered
  • Replies 1 reply
  • Subscribers 86 subscribers
  • Views 113 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 353412
Options
Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs

Migration from nrfSDK1.8.0

Derek Liddle

We are looking to migrate our nrf52833 project to latest toolchain and SDK for build in visual studio.

We use MCU boot, BLE and Zephyr RTOS.

Do we need to follow each migration step for the nrf Connect SDK from V2.0.0 onwards in sequence?

Do we also need to include the multi-image builds and the  hardware migration also?

Is there a specific sequence for the migration you recommend?

Parents
  • 0

    Hi, 

    Do we need to follow each migration step for the nrf Connect SDK from V2.0.0 onwards in sequence?

    Yes, it is recommended to review and apply the migration steps for each major and minor SDK version between your current version and the target version. See Migration guides.

    What is your target version?

    Do we also need to include the multi-image builds and the  hardware migration also?

    Yes, if your project uses multi-image builds or custom hardware definitions, you should follow the relevant migration guides for these areas.

    • Multi-image builds: The method for handling multi-image builds has changed, with Sysbuild replacing the old parent-child image method. This is a significant change starting from SDK v2.7.0, and you should migrate to Sysbuild if you use multi-image builds. 
    • Hardware migration: The board (hardware model) definition method has also changed. If you have a custom board, review the hardware model migration guide.
    What is your application? Does it require mcuboot for DFU?
    Do you build for nRF52833DK or the custom board?
    Is there a specific sequence for the migration you recommend?

    You could:

    1. Update your SDK and toolchain to the latest version using the recommended installation method (e.g., nRF Connect for VS Code or nRF Util).
    2. Review and apply each migration guide in order, starting from your current SDK version up to the latest.
      • For each version, address both required and recommended changes.
      • Pay special attention to breaking changes in the build system, toolchain, MCUboot, BLE, Zephyr RTOS, and any other features you use.
    3. If your project uses multi-image builds or custom hardware, include the relevant migration steps for those features.
    4. Test your project after each major migration step to catch issues early.

    Because the latest version is NCS v3.1.1, there have been so many updates since NCS v1.8.0. It might take a lot of time and effort to migrate to the latest version. Maybe you could consider to start a new project in NCS v3.1.1 to save effort.  

    Regards,
    Amanda H.

Reply
  • 0

    Hi, 

    Do we need to follow each migration step for the nrf Connect SDK from V2.0.0 onwards in sequence?

    Yes, it is recommended to review and apply the migration steps for each major and minor SDK version between your current version and the target version. See Migration guides.

    What is your target version?

    Do we also need to include the multi-image builds and the  hardware migration also?

    Yes, if your project uses multi-image builds or custom hardware definitions, you should follow the relevant migration guides for these areas.

    • Multi-image builds: The method for handling multi-image builds has changed, with Sysbuild replacing the old parent-child image method. This is a significant change starting from SDK v2.7.0, and you should migrate to Sysbuild if you use multi-image builds. 
    • Hardware migration: The board (hardware model) definition method has also changed. If you have a custom board, review the hardware model migration guide.
    What is your application? Does it require mcuboot for DFU?
    Do you build for nRF52833DK or the custom board?
    Is there a specific sequence for the migration you recommend?

    You could:

    1. Update your SDK and toolchain to the latest version using the recommended installation method (e.g., nRF Connect for VS Code or nRF Util).
    2. Review and apply each migration guide in order, starting from your current SDK version up to the latest.
      • For each version, address both required and recommended changes.
      • Pay special attention to breaking changes in the build system, toolchain, MCUboot, BLE, Zephyr RTOS, and any other features you use.
    3. If your project uses multi-image builds or custom hardware, include the relevant migration steps for those features.
    4. Test your project after each major migration step to catch issues early.

    Because the latest version is NCS v3.1.1, there have been so many updates since NCS v1.8.0. It might take a lot of time and effort to migrate to the latest version. Maybe you could consider to start a new project in NCS v3.1.1 to save effort.  

    Regards,
    Amanda H.

Children
No Data
Related
Terms of service