Build errors that have just appeared

Hello,

When I was building my nrf9160 dk project the beginning of this year (2022), everything was building and working fine.

The project was put on hold until a few weeks ago.

So I installed sdk 1.9.1, and tried to do a build.  I was getting quite a few CONFIG_blahblah not found when attempting to set to y or n.  So I went to sdk 1.7.1 and still getting one CONFIG_blahblah not found.  Please help me with what I am missing.

Thank you very much,

/Loren

Build output for 1.7.1:

C:/dev/halo-unity/boards/nrf9160dk_nrf9160_ns.conf:1: warning: attempt to assign the value 'n' to the undefined symbol TFM_SECURE_UART1
Parsing C:/dev/halo-unity/Kconfig
Loaded configuration 'C:/ncs/v1.7.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'

error: Aborting due to Kconfig warnings

CMake Error at C:/ncs/v1.7.1/zephyr/cmake/kconfig.cmake:268 (message):
command failed with return code: 1
Call Stack (most recent call first):
C:/ncs/v1.7.1/zephyr/cmake/app/boilerplate.cmake:554 (include)
C:/ncs/v1.7.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
C:/ncs/v1.7.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:35 (include_boilerplate)
CMakeLists.txt:6 (find_package)


-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: 'C:\ncs\v1.7.1\toolchain\opt\bin\cmake.EXE' '-DWEST_PYTHON=C:\ncs\v1.7.1\toolchain\opt\bin\python.exe' '-BC:\dev\halo-unity\build' '-SC:\dev\halo-unity' -GNinja -DBOARD=nrf9160dk_nrf9160_ns

Build output for 2.0.0 (Similar with 1.9.1)

warning: MBEDTLS_SSL_MAX_CONTENT_LEN (defined at C:/ncs/v2.0.0/zephyr/modules/mbedtls/Kconfig:69,
modules\mbedtls\Kconfig:69) was assigned the value '8192' but got the value ''. Check these
unsatisfied dependencies: ((MBEDTLS_BUILTIN && MBEDTLS) || (MBEDTLS_BUILTIN && MBEDTLS && 0)) (=n).
See docs.zephyrproject.org/.../kconfig.html and/or look
up MBEDTLS_SSL_MAX_CONTENT_LEN in the menuconfig/guiconfig interface. The Application Development
Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual
might be helpful too.


warning: CJSON_LIB (defined at C:/ncs/v2.0.0/nrf/modules/cjson/Kconfig:7) was assigned the value 'y'
but got the value 'n'. Check these unsatisfied dependencies: ((NEWLIB_LIBC &&
NEWLIB_LIBC_FLOAT_PRINTF) || EXTERNAL_LIBC) (=n). See
docs.zephyrproject.org/.../kconfig.html and/or look up CJSON_LIB in the
menuconfig/guiconfig interface. The Application Development PrimeParsing C:/dev/halo-unity/Kconfig
Loaded configuration 'C:/ncs/v2.0.0/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'
r, Setting Configuration Values,
and Kconfig - Tips and Best Practices sections of the manual might be helpful too.


warning: Experimental symbol HTTP_CLIENT is enabled.


warning: Experimental symbol NET_SOCKETS_SOCKOPT_TLS is enabled.


warning: Experimental symbol NET_SOCKETS_OFFLOAD is enabled.


C:/dev/halo-unity/prj.conf:29: warning: attempt to assign the value 'y' to the undefined symbol MBEDTLS_VANILLA_BACKEND

error: Aborting due to Kconfig warnings

CMake Error at C:/ncs/v2.0.0/zephyr/cmake/modules/kconfig.cmake:290 (message):
command failed with return code: 1
Call Stack (most recent call first):
C:/ncs/v2.0.0/zephyr/cmake/modules/zephyr_default.cmake:121 (include)
C:/ncs/v2.0.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:51 (include)
C:/ncs/v2.0.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:76 (include_boilerplate)
CMakeLists.txt:6 (find_package)


-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\v2.0.0\opt\bin\cmake.EXE' '-DWEST_PYTHON=C:\ncs\toolchains\v2.0.0\opt\bin\python.exe' '-BC:\dev\halo-unity\build' '-SC:\dev\halo-unity' -GNinja -DBOARD=nrf9160dk_nrf9160_ns

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

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

  • 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

  • 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:

    Albrecht Markus Schellenberger said:

    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. 

    Updated link to the release notes and migration notes.

Reply
  • 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:

    Albrecht Markus Schellenberger said:

    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. 

    Updated link to the release notes and migration notes.

Children
No Data
Related