Attachments (0)
Nordic Case Info
  • Case ID: 338843
Options

Migration Issues from Zephyr 2.6.1 to 2.9.0: Configuration Problems and Deprecation Warnings

Andrea Verdecchia

I am migrating from the 2.6.1 development environment to 2.9.0 but am unable to compile due to some configuration issues.

My prj.conf configuration file is as follows:

When I compile, I get the following warnings:

Can someone help me understand the configuration changes? Specifically, what do the last two warnings mean?

  • 0

    Hi

    In NCS 2.7 we changed to HWM2 to align with Zephyr 

    Highlights from NCS 2.7

    This release introduces significant, potentially breaking, changes to the SDK:

    All samples and applications in the SDK have been migrated. Consult respective documentation as additional or changed parameters might be needed to build them successfully. Applications that are outside of the SDK and use custom-defined boards should not be affected by these changes. However, modifications might still be required as per the migration procedure described in Migration guide for nRF Connect SDK v2.7.0. nRF Connect for VS Code users migrating to the latest version of the SDK might be affected.

    All samples and applications in the SDK are built with sysbuild by default. Applications that are outside the SDK are not built with sysbuild by default.

    The deprecated methods are scheduled for removal after the next release. We recommend transitioning to the alternatives as soon as possible. Consult migration guides for Migrating to the current hardware model and Migrating from multi-image builds to sysbuild. Exercise caution when migrating production environments to the latest SDK.

    Have you seen our migration guide for going from hardware model 1 to model 2 which can be found here? 

    Regards

    Runar

  • 0 in reply to runsiv

    Thank you for the suggestions. However, I think the issue is not with upgrading from SDK 2.6.1 to 2.7.0 because if I set SDK 2.7.0 in the NCS of my VS Code, I can compile the project without any issues and continue its development. So, I tried upgrading from SDK 2.7.0 to SDK 2.8.0, and in this case, I encountered the same problem I faced when directly upgrading from 2.6.1 to 2.9.0. Therefore, I believe the issue is not with upgrading to 2.7.0 but rather with 2.8.0. The compilation gives me the following output:

    I really can't figure out what it could be. Any other suggestions?

  • +1 in reply to Andrea Verdecchia

    can you try to build using the command --no-sysbuild.  Since you are using the old HW1 you should not be using sysbuild either. 

    I would also suggest taking a look at the Migration note for NCS 2.8. Are you using Zephyr Bluetooth Controller or our Softdevice? It would also be interesting to have a look at your prj.conf

    Regards

    Runar

  • 0 in reply to runsiv
    runsiv said:
    can you try to build using the command --no-sysbuild.

    I tried compiling with SDK 2.8.0 and the --no-sysbuild option, and I no longer have any errors. Even when compiling with SDK 2.9.0, the errors are gone. It seems the issue has been resolved. However, I now have two questions:

    1. What does not using sysbuild imply?
    2. What should I change to use sysbuild?
  • +1 in reply to Andrea Verdecchia

    1. I would recommend just reading the migration note for sysbuild as it explains it better then what I can do. 

    2. You will need to convert over to HWM2 as I mentioned in my first reply. This is something that you will have to do in the future if you plan to upgrade to a new version of NCS for your application. I'm not sure when we will remove support for HWM1 but normally we remove something after 3 versions. 

    Regards

    Runar

1 2
Terms of service