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

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

Menon — Mon, 23 Jun 2025 11:24:36 GMT

Hello,

I'm glad to hear that you were able to get it working. Thank you for sharing the details here — this will definitely help other users who encounter a similar situation.

Kind regards,
Abhijith

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

MPDeveloper89 — Fri, 20 Jun 2025 21:52:09 GMT

Ncs 2.2 and archive board package (suggested in the table above) permit to build successfully the application and flash it in the board.

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

MPDeveloper89 — Fri, 20 Jun 2025 21:22:25 GMT

Hello,

Last update say that:

- using ncs 2.4

- using the last board package available here GitHub - u-blox/u-blox-sho-OpenCPU: Repository with sample code and examples for u-blox Open CPU modules.

I'm surprise to see that issue appear:

Full report here: /cfs-file/__key/communityserver-discussions-components-files/4/log_5F00_build_5F00_3.txt

I try to downgrade to ncs 2.2 and use the archive board package as suggested here:

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

Menon — Mon, 16 Jun 2025 09:11:54 GMT

Hello,

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

Kind Regards,
Abhijith

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

MPDeveloper89 — Sat, 14 Jun 2025 22:13:45 GMT

[quote userid="115767" url="~/f/nordic-q-a/122079/build-failed-using-toolchain-v3-0-2-and-sdks-v3-0-2/538958"]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?[/quote]

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

[quote userid="118444" url="~/f/nordic-q-a/122079/build-failed-using-toolchain-v3-0-2-and-sdks-v3-0-2"]My board is EVK-NORA-B1 User Guide[/quote]

- 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?

[quote userid="115767" url="~/f/nordic-q-a/122079/build-failed-using-toolchain-v3-0-2-and-sdks-v3-0-2/538958"]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.[/quote]

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

Thank you.

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

Menon — Thu, 12 Jun 2025 07:14:03 GMT

[quote user="MPDeveloper89"]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.[/quote]

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

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

MPDeveloper89 — Sat, 07 Jun 2025 13:16:26 GMT

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.

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

Menon — Fri, 06 Jun 2025 14:38:26 GMT

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