Migration from SDK v2.7.0 to v2.8.0 (and v2.9.0) failing

We have a project that includes a custom board definition and out of tree driver with folder structure as follows:

Our project builds successfully with SDK v2.7.0 and toolchain v2.7.0

Upgrading the toolchain so we have SDK v2.7.0 and toolchain v2.9.0 works fine.

 

Upgrading the SDK so we have SDK v2.9.0 and toolchain v2.9.0 fails to build the application.

We see this at the end of the build output in the terminal:

As can be seen, the drivers in the src folder (which are referenced from the board definition) are not being found.

If we roll the SDK back to v2.7.0 the same project builds ok again so this is definitely a difference between v2.7.0 and what follows.

Please note we also tried with v2.8.0 with the same result as v2.9.0 so wherever I have mentioned v2.9.0 I also tried the same with v2.8.0

So, the breaking change seems to have occurred between v2.7.0 and v2.8.0 and the breaking change remains in v2.9.0 

Parents
  • Hi,

    Can you show your build commands when using different NCS versions?

    Have you tried to use --no-sysbuild option when building with west in NCS v2.8.0 and v2.9.0? Do you see any difference in the result?

    Best regards,
    Dejan

  • I have tried --no-sysbuild and the build still fails in anything later than v2.8.x and v2.9.x

    Generated Build Commands Shown Below...


    Toolchain: v2.9.1

    SDK: v2.7.0

    Status: OK

    Build Command:


    Toolchain: v2.9.1

    SDK: v2.9.1

    Status: FAILS

    Build Command:


    Toolchain: v2.9.1

    SDK: v2.9.1 (NO SYSBUILD)

    Status: FAILS

    Build Command:

  • Hi,

    Can you provide full build log when using NCS v2.9.0 (and NCS v2.8.0 if build log is different)?

    Best regards,
    Dejan

Reply Children
  • I can copy the truncated output form the terminal but where will I find the full logs?

    Terminal Output for SDK v2.7.0

    Terminal Output for SDK v2.9.1 - Build system Default (Sysbuild) selected in VS Code

    The issues seems top start at:

    Terminal Output for SDK v2.9.1 - No Sysbuild selected in VS Code

  • Hi,

    Can you upload your CMakeLists.txt file and CMakeOutput.log file?

    Best regards,
    Dejan

  • Also, with sdk v2.9.1 (no sysbuild) I get a CMakeError.log file.

    For some reason this system fails when I upload it but its content is:

  • Hi,

    Have you kept the same CMakeLists.txt file both in NCS both v2.7.0 and v2.9.1?

    There is no drivers/proprietary/ folder in your directory structure, but it is used in your CmakeLists.txt as ${CMAKE_CURRENT_SOURCE_DIR}/drivers/proprietary. Can you elaborate on this?

    Have you tried to include 


    in your CMakeLists.txt?

    Best regards,
    Dejan