How to resolve list "GET given empty list CMake" error when porting nRF9151 application to custom board in NCS v2.9?

[Hunter_B]

I have finished developing an application, utilizing the nRF 9151 DK, and I am now working on transferring the firmware to a custom board and testing it. However, when creating a new custom board I am running into this error;

CMake Error at C:/Users/hunte/nrf/sysbuild/CMakeLists.txt:117 (list):
  list GET given empty list
Call Stack (most recent call first):
  cmake/modules/sysbuild_extensions.cmake:583 (nrf_PRE_CMAKE)
  cmake/modules/sysbuild_extensions.cmake:583 (cmake_language)
  cmake/modules/sysbuild_images.cmake:16 (sysbuild_module_call)
  cmake/modules/sysbuild_default.cmake:20 (include)
  C:/Users/hunte/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:75 (include)
  C:/Users/hunte/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  C:/Users/hunte/zephyr/share/sysbuild-package/cmake/SysbuildConfig.cmake:8 (include)
  template/CMakeLists.txt:10 (find_package)

I have been using this lesson, Lesson 3 – Adding custom board support, as a framework for my custom board, though it may use an earlier hardware model and SDK. I am using SDK v2.9 and toolchain v2.9, and I can't  seem to find any resources online that provide a solution to this problem. Is there anything I can do to fix this?

[Øyvind]

Hello, 

Where have you stored your custom board files? Could you provide more of the logs?

I have been using this lesson, Lesson 3 – Adding custom board support, as a framework for my custom board

Could you please provide more information on exactly what steps you have done in Lesson 3?

Thanks

Kind regards,
Øyvind

[Hunter_B]

Hi,

I completed exercise 2 in lesson 3, and upon building the completed exercise I received this error.

Thanks,

Hunter

[Øyvind]

Hi Hunter, just want to to let you know that I'm looking into this. 

Could you please provide full build log including the build command at top?

Thanks.

Kind regards,
Øyvind

[Hunter_B]

Here's the output of my build command.

Fullscreen CMAKE-empty-error_devzone.txt Download

 *  Executing task: nRF Connect: Generate config yarrow_ns for c:\ncs\RefLabs\Yarrow 

Building Yarrow
C:\WINDOWS\system32\cmd.exe /d /s /c "west build --build-dir c:/ncs/RefLabs/Yarrow/build_custom c:/ncs/RefLabs/Yarrow --pristine --board yarrow_ns --sysbuild -- -DNCS_TOOLCHAIN_VERSION=NONE -DCONF_FILE=prj.conf -DEXTRA_CONF_FILE=config/button.conf;config/location.conf;config/queue.conf -DDTC_OVERLAY_FILE=boards/arm/yarrow/app.overlay -DBOARD_ROOT=c:/ncs/reflabs/yarrow"

-- west build: generating a build system
Loading Zephyr module(s) (Zephyr base): sysbuild_default
-- Found Python3: C:/ncs/toolchains/b620d30767/opt/bin/python.exe (found suitable version "3.12.4", minimum required is "3.8") found components: Interpreter 
-- Cache files will be written to: C:/Users/hunte/zephyr/.cache
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: yarrow_ns
Parsing C:/Users/hunte/zephyr/share/sysbuild/Kconfig
Loaded configuration 'C:/ncs/RefLabs/Yarrow/build_custom/_sysbuild/empty.conf'
Merged configuration 'C:/ncs/RefLabs/Yarrow/build_custom/_sysbuild/empty.conf'
Configuration saved to 'C:/ncs/RefLabs/Yarrow/build_custom/zephyr/.config'
Kconfig header saved to 'C:/ncs/RefLabs/Yarrow/build_custom/_sysbuild/autoconf.h'
CMake Error at C:/Users/hunte/nrf/sysbuild/CMakeLists.txt:117 (list):
  list GET given empty list
Call Stack (most recent call first):
  cmake/modules/sysbuild_extensions.cmake:583 (nrf_PRE_CMAKE)
  cmake/modules/sysbuild_extensions.cmake:583 (cmake_language)
  cmake/modules/sysbuild_images.cmake:16 (sysbuild_module_call)
  cmake/modules/sysbuild_default.cmake:20 (include)
  C:/Users/hunte/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:75 (include)
  C:/Users/hunte/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  C:/Users/hunte/zephyr/share/sysbuild-package/cmake/SysbuildConfig.cmake:8 (include)
  template/CMakeLists.txt:10 (find_package)


-- 
   ****************************
   * Running CMake for Yarrow *
   ****************************

Loading Zephyr default modules (Zephyr base).
-- Application: C:/ncs/RefLabs/Yarrow
-- CMake version: 3.21.0
-- Found Python3: C:/ncs/toolchains/b620d30767/opt/bin/python.exe (found suitable version "3.12.4", minimum required is "3.8") found components: Interpreter 
-- Cache files will be written to: C:/Users/hunte/zephyr/.cache
-- Zephyr version: 3.7.99 (C:/Users/hunte/zephyr)
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: yarrow_ns
-- Found host-tools: zephyr 0.17.0 (C:/ncs/toolchains/b620d30767/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.17.0 (C:/ncs/toolchains/b620d30767/opt/zephyr-sdk)
-- Found Dtc: C:/ncs/toolchains/b620d30767/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6") 
-- Found BOARD.dts: C:/ncs/RefLabs/Yarrow/boards/arm/yarrow/yarrow_ns.dts
-- Found devicetree overlay: boards/arm/yarrow/app.overlay
-- Generated zephyr.dts: C:/ncs/RefLabs/Yarrow/build_custom/Yarrow/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/ncs/RefLabs/Yarrow/build_custom/Yarrow/zephyr/include/generated/zephyr/devicetree_generated.h
-- Including generated dts.cmake file: C:/ncs/RefLabs/Yarrow/build_custom/Yarrow/zephyr/dts.cmake

warning: PARTITION_MANAGER_ENABLED (defined at
C:/Users/hunte/nrf\subsys\partition_manager/Kconfig:9) was assigned the value 'n' but got the value
'y'. See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_PARTITION_MANAGER_ENABLED and/or
look up PARTITION_MANAGER_ENABLED 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: PM_SINGLE_IMAGE (defined at C:/Users/hunte/nrf\subsys\partition_manager/Kconfig:164) was
assigned the value 'n' but got the value 'y'. See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_PM_SINGLE_IMAGE and/or look up
PM_SINGLE_IMAGE 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: Deprecated symbol PLATFORM_SPECIFIC_INIT is enabled.


warning: Deprecated symbol POSIX_CLOCK is enabled.


warning: Deprecated symbol NET_SOCKETS_POSIX_NAMES is enabled.


warning: Experimental symbol NET_SOCKETS_SERVICE is enabled.


warning: Experimental symbol NET_CONNECTION_MANAGER is enabled.

Parsing C:/ncs/RefLabs/Yarrow/Kconfig
Loaded configuration 'C:/ncs/RefLabs/Yarrow/boards/arm/yarrow/yarrow_ns_defconfig'
Merged configuration 'C:/ncs/RefLabs/Yarrow/prj.conf'
Merged configuration 'C:/ncs/RefLabs/Yarrow/config/button.conf'
Merged configuration 'C:/ncs/RefLabs/Yarrow/config/location.conf'
Merged configuration 'C:/ncs/RefLabs/Yarrow/config/queue.conf'
Merged configuration 'C:/ncs/RefLabs/Yarrow/build_custom/Yarrow/zephyr/.config.sysbuild'
Configuration saved to 'C:/ncs/RefLabs/Yarrow/build_custom/Yarrow/zephyr/.config'
Kconfig header saved to 'C:/ncs/RefLabs/Yarrow/build_custom/Yarrow/zephyr/include/generated/zephyr/autoconf.h'
-- Found GnuLd: c:/ncs/toolchains/b620d30767/opt/zephyr-sdk/arm-zephyr-eabi/arm-zephyr-eabi/bin/ld.bfd.exe (found version "2.38") 
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: C:/ncs/toolchains/b620d30767/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe
CMake Deprecation Warning at C:/Users/hunte/zephyr/soc/CMakeLists.txt:15 (message):
  

            ---------------------------------------------------------------------
            --- WARNING: Functionality to describe SoCs in HWMv1 is           ---
            --- deprecated and should be replaced with HWMv2, including       ---
            --- boards. HWMv1 SoCs support remains only to ease the migration ---
            --- of out-of-tree SoCs and associated boards. It will not be     ---
            --- possible to build using HWMv1 SoCs at all in future releases. ---
            ---------------------------------------------------------------------


=========== Generating psa_crypto_config ===============
Backup: CONFIG_MBEDTLS_PSA_CRYPTO_SPM: False
Backup: CONFIG_MBEDTLS_PSA_CRYPTO_C: False
Backup: CONFIG_MBEDTLS_PSA_CRYPTO_KEY_ID_ENCODES_OWNER: False
Backup: CONFIG_MBEDTLS_PLATFORM_SETUP_TEARDOWN_ALT: False
Backup: CONFIG_MBEDTLS_THREADING: False
Backup: CONFIG_MBEDTLS_THREADING_ALT: False
=========== Checkpoint: backup ===============
Restore: CONFIG_MBEDTLS_PSA_CRYPTO_SPM: False
Restore: CONFIG_MBEDTLS_PSA_CRYPTO_C: False
Restore: CONFIG_MBEDTLS_PSA_CRYPTO_KEY_ID_ENCODES_OWNER: False
Restore: CONFIG_MBEDTLS_PLATFORM_SETUP_TEARDOWN_ALT: False
Restore: CONFIG_MBEDTLS_THREADING: False
Restore: CONFIG_MBEDTLS_THREADING_ALT: False
=========== End psa_crypto_config ===============
=========== Generating psa_crypto_library_config ===============
Backup: CONFIG_MBEDTLS_PSA_CRYPTO_C: False
Backup: CONFIG_MBEDTLS_PSA_CRYPTO_KEY_ID_ENCODES_OWNER: False
Backup: CONFIG_MBEDTLS_PSA_CRYPTO_SPM: False
Backup: CONFIG_MBEDTLS_USE_PSA_CRYPTO: True
Backup: CONFIG_MBEDTLS_PLATFORM_PRINTF_ALT: False
Backup: CONFIG_MBEDTLS_THREADING: False
Backup: CONFIG_MBEDTLS_THREADING_ALT: False
=========== Checkpoint: backup ===============
Restore: CONFIG_MBEDTLS_PSA_CRYPTO_C: False
Restore: CONFIG_MBEDTLS_PSA_CRYPTO_KEY_ID_ENCODES_OWNER: False
Restore: CONFIG_MBEDTLS_PSA_CRYPTO_SPM: False
Restore: CONFIG_MBEDTLS_USE_PSA_CRYPTO: True
Restore: CONFIG_MBEDTLS_PLATFORM_PRINTF_ALT: False
Restore: CONFIG_MBEDTLS_THREADING: False
Restore: CONFIG_MBEDTLS_THREADING_ALT: False
=========== End psa_crypto_library_config ===============
-- Setting build type to 'MinSizeRel' as none was specified.
-- Configuring done
-- Generating done
-- Build files have been written to: C:/ncs/RefLabs/Yarrow/build_custom/Yarrow
-- Configuring incomplete, errors occurred!
See also "C:/ncs/RefLabs/Yarrow/build_custom/CMakeFiles/CMakeOutput.log".
FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\b620d30767\opt\bin\cmake.EXE' -DWEST_PYTHON=C:/ncs/toolchains/b620d30767/opt/bin/python.exe '-Bc:\ncs\RefLabs\Yarrow\build_custom' -GNinja -DBOARD=yarrow_ns -DNCS_TOOLCHAIN_VERSION=NONE -DCONF_FILE=prj.conf '-DEXTRA_CONF_FILE=config/button.conf;config/location.conf;config/queue.conf' -DDTC_OVERLAY_FILE=boards/arm/yarrow/app.overlay -DBOARD_ROOT=c:/ncs/reflabs/yarrow '-SC:\Users\hunte\zephyr\share\sysbuild' '-DAPP_DIR:PATH=c:\ncs\RefLabs\Yarrow'

 *  The terminal process terminated with exit code: 1. 
 *  Terminal will be reused by tasks, press any key to close it.

Let me know if this is what you had in mind, or if you need something else, thankyou!

[Øyvind]

Hello, and thanks for sharing. I've been trying to reproduce on my side without luck. I followed the steps as described in Lesson 3, and built the AT Client sample with this board.

I added the customer board as described in Option 3: From within VS Code.

Kind regards,
Øyvind

[Hunter_B]

It looks like the build is failing only when I use sysbuild. When I select the no sysbuild option the build succeeds. Could this be the reason you're not able to reproduce the build failure?

[Øyvind]

Yes, I've tried with both sysbuild enabled and disabled, without being to reproduce. 

But if it does work without sysbuild enabled that is good to hear. Have you looked at the configuring sysbuild documentation in order to enable sysbuild?

Kind regards,
Øyvind

[Hunter_B]

I believe sysbuild is enabled, when building with sysbuild for the nrf9151dk board there are no build errors. The errors only occur when using a custom board. Would recommend continuing without using sysbuild?

[Øyvind]

Just pointing out for the awareness: from our documentation

Sysbuild is a higher-level build system that can be used to combine multiple other build systems together. It is a higher-level layer that combines one or more Zephyr build systems and optional additional build systems into a hierarchical build system.

For example, you can use sysbuild to build a Zephyr application together with the MCUboot bootloader, flash them both onto your device, and debug the results.

Sysbuild is enabled by default in our nRF Connect SDK, and i.e. child images are deprecated and is being replaced by Zephyr’s Sysbuild (System build). You can continue to use it until the transition is complete in the nRF Connect SDK and the feature is removed in one of the upcoming nRF Connect SDK releases. For more information, see Sysbuild (System build), Sysbuild images, Using Zephyr samples with sysbuild, and Sysbuild forced options.

As long as you are aware of this, you can move forward without Sysbuild for now but will most likely meet demands at a later stage.

Kind regards,
Øyvind