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]

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