Build errors that have just appeared

RE: Build errors that have just appeared

helsing — Fri, 29 Jul 2022 21:41:27 GMT

HI Loren,

Migrating from one SDK version to another is likely to cause these type of errors. As my colleague put it in another ticket:

[quote user="Markus Schellenberger"]

Unfortunately, there is no straight forward guide for a migration process like that. You have to go through each library / Kconfig set your application is using and modify accordingly. The release notes for each release might be a help as they give you guidance on what has changed.

Alternatively, if your application is based on a sample provided by us, taking it as a reference from the SDK version migrating to and then adding custom functionality step by step could be another approach.

[/quote]

Updated link to the release notes and migration notes.

RE: Build errors that have just appeared

Loren Rogers — Thu, 28 Jul 2022 21:04:55 GMT

Hi Helsing.

I installed 1.9.1 I was getting the following build error:

$ west -v build -b nrf9160dk_nrf9160_ns
ZEPHYR_BASE=C:/ncs/v1.9.1/zephyr (origin: env)
-- west build: generating a build system
cmake version 3.20.5 is OK; minimum version is 3.13.1
Running CMake: 'C:\ncs\v1.9.1\toolchain\opt\bin\cmake.EXE' '-DWEST_PYTHON=C:\ncs\v1.9.1\toolchain\opt\bin\python.exe' '-BC:\dev\halo-unity\build' '-SC:\dev\halo-unity' -GNinja -DBOARD=nrf9160dk_nrf9160_ns
-- Application: C:/dev/halo-unity
-- Zephyr version: 2.7.99 (C:/ncs/v1.9.1/zephyr), build: v2.7.99-ncs1-1
-- Found Python3: C:/ncs/v1.9.1/toolchain/opt/bin/python.exe (found suitable exact version "3.8.2") found components: Interpreter
-- Found west (found suitable version "0.12.0", minimum required is "0.7.1")
-- Board: nrf9160dk_nrf9160_ns, Revision: 0.7.0
-- Cache files will be written to: C:/ncs/v1.9.1/zephyr/.cache
-- Found dtc: C:/ncs/v1.9.1/toolchain/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (C:/ncs/v1.9.1/toolchain/opt)
-- Found BOARD.dts: C:/ncs/v1.9.1/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160_ns.dts
-- Found devicetree overlay: C:/dev/halo-unity/boards/nrf9160dk_nrf9160_ns.overlay
-- Generated zephyr.dts: C:/dev/halo-unity/build/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: C:/dev/halo-unity/build/zephyr/include/generated/devicetree_unfixed.h
-- Generated device_extern.h: C:/dev/halo-unity/build/zephyr/include/generated/device_extern.h
-- Including generated dts.cmake file: C:/dev/halo-unity/build/zephyr/dts.cmake
Parsing C:/dev/halo-unity/Kconfig
Loaded configuration 'C:/ncs/v1.9.1/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160_ns_defconfig'
Merged configuration 'C:/dev/halo-unity/prj.conf'
Merged configuration 'C:/dev/halo-unity/boards/nrf9160dk_nrf9160_ns.conf'
-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: 'C:\ncs\v1.9.1\toolchain\opt\bin\cmake.EXE' '-DWEST_PYTHON=C:\ncs\v1.9.1\toolchain\opt\bin\python.exe' '-BC:\dev\halo-unity\build' '-SC:\dev\halo-unity' -GNinja -DBOARD=nrf9160dk_nrf9160_ns

I uninstalled ALL toolchains, and resinstalled 1.9.1. Still getting the same error as above. I have NO CLUE as to what is failing as there is 0 apparent messages/files.

Please help me.

/Loren

RE: Build errors that have just appeared

Loren Rogers — Thu, 28 Jul 2022 12:56:57 GMT

Hi Helsing!

I am 100% sure I was building with 1.7.1. I will install 1.8.1 and give it a shot. In the meantime, what about those KConfig options not found for 2.0.0 (e.g. MBEDTLS_VANILLA_BACKEND)? And the other warnings?

RE: Build errors that have just appeared

helsing — Thu, 28 Jul 2022 10:32:44 GMT

Have you tried v1.8.1?

RE: Build errors that have just appeared

helsing — Thu, 28 Jul 2022 10:21:50 GMT

Hello Loren,

I searched for 'TFM_SECURE_UART1' in the Kconfig reference and was not able to find anything for nRF Connect SDK v1.7.1. However, if I search in v1.8.0 and later I am able to find it. Is ther any chance your code was written for v1.8.1?