Build failed using Toolchain v3.0.2 and sdks v3.0.2

[MPDeveloper89]

Dear All,

I updated Toolchain and SDKs to last version v3.0.2 and I'm going to add build configuration as suggested here How to create and build an application.

My board is  EVK-NORA-B1 User Guide and I followed instruction in paragraph 3.2.3 and downloaded the last board package available in github.

Build configuration is :

 

But build failed (here the entire report-->/cfs-file/__key/communityserver-discussions-components-files/4/1004.build_5F00_log.txt)

Do you idea about this issue? did application creation process change?

Thank you in advance.

MP

[Menon]

Hello,

See also "C:/MPHome/1_Project/09_CustomPrj/button_3_0_2/build/CMakeFiles/CMakeOutput.log".
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\0b393f9e1b\opt\bin\cmake.EXE' -DWEST_PYTHON=C:/ncs/toolchains/0b393f9e1b/opt/bin/python.exe '-Bc:\MPHome\1_Project\09_CustomPrj\button_3_0_2\build' -GNinja -DBOARD=ubx_evknorab10_nrf5340_cpuapp_ns -DCONF_FILE=prj.conf '-DBOARD_ROOT=c:/users/marco/ncs/v1.9.1/zephyr/boards/arm;c:/mphome/1_project/09_customprj/button_3_0_2' '-SC:\ncs\v3.0.2\zephyr\share\sysbuild' '-DAPP_DIR:PATH=c:\MPHome\1_Project\09_CustomPrj\button_3_0_2'

From the shared logs, it looks like the board files are pointing to a different SDK version than the one you are currently building for. Do any BOARD_ROOT entries include paths from different SDK versions (e.g., v1.9.1)?

Kind Regards,

Abhijith

[MPDeveloper89]

Hello,

Thank you for feedback.

I've seen this reference to old SDK and:

- I removed the older SDK version (in the path mentioned It doesn't exsist anymore) but the issue is still present.

- I tried to send manually the west command forcing the -DBOARD_ROOT to last SDK version but issue is there.

- Additionally , I tried to build with a different board and It works even if the path with SDK v1.9.1 is mentioned in the west command.

So, I don't know if can be the root cause but if you have some suggestion to update permanently the command, I 'll do it.

Any other idea?

Thank you in advance.

[Menon]

MPDeveloper89 said:

Additionally , I tried to build with a different board and It works even if the path with SDK v1.9.1 is mentioned in the west command.

Hello,

Sorry, I didn’t fully understand this. Have you tried building with toolchain and SDK version 3.0.2 for any official Nordic board (like the nRF5340 DK)? If so, how did it go? Also, what does the "SDK path" refer to in the west command?

I’m not sure if newer versions of NCS (version > 2.5.0) are compatible with or officially supported by u-blox. I noticed a similar query raised on the u-blox support forum. I would appreciate it if you could check with u-blox whether there have been any changes to the device tree bindings or integration methods when moving to newer SDK versions.

Kind regards,
Abhijith

[MPDeveloper89]

Menon said:

Sorry, I didn’t fully understand this. Have you tried building with toolchain and SDK version 3.0.2 for any official Nordic board (like the nRF5340 DK)? If so, how did it go? Also, what does the "SDK path" refer to in the west command?

Hello,

I'm refering to "target board" in build configuration.

Let me to clarify better:

- using this board and corresponding target board I countered the issue mentioned above

MPDeveloper89 said:

My board is  EVK-NORA-B1 User Guide

- using the same NCS (v3.0.2) with a "target board" as nrf21540dk/nrf52840, no issue appear despite DBOARD is set as follow: DBOARD_ROOT=c:/users/marco/ncs/v1.9.1/zephyr/boards/arm

report -_> /cfs-file/__key/communityserver-discussions-components-files/4/log_5F00_build_5F00_2.txt

Of course, It's strange also because ncs 1.9.1 doesn't exist anymore. Do you know the reason why?

Menon said:

I’m not sure if newer versions of NCS (version > 2.5.0) are compatible with or officially supported by u-blox. I noticed a similar query raised on the u-blox support forum. I would appreciate it if you could check with u-blox whether there have been any changes to the device tree bindings or integration methods when moving to newer SDK versions.

This could explain the issue. I'll try to contact u-blox and build using the old ncs version.

Thank you.

MP

[Menon]

Hello,

Please let me know if there is some important update on this issue.

Kind Regards,
Abhijith