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 Reply Children
  • 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.

Related