nrf5340DK Custom board fails creation via VSCode extension

[adsa]

Hi,

I am starting from the following example: "Bluetooth Low Energy UART service sample", sdk version v2.6.0
I am trying to add a custom board (using VSCode NRF CONNECT extension). The creation works, I get the files in (project-path)/boards/arm/my-custom-board but this configuration is unable to build and I get the following error that I'm unable to understand and fix.

warning: UART_CONSOLE (defined at drivers/console/Kconfig:43) was assigned the value 'y' but got the
value 'n'. Check these unsatisfied dependencies: SERIAL_HAS_DRIVER (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_UART_CONSOLE and/or look up UART_CONSOLE 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: UART_ASYNC_API (defined at drivers/serial/Kconfig:66) was assigned the value 'y' but got
the value 'n'. Check these unsatisfied dependencies: SERIAL_SUPPORT_ASYNC (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_UART_ASYNC_API and/or look up
UART_ASYNC_API 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.


/Users/work/5340-can-ble/can-ble/boards/arm/can_ble_board/can_ble_board_cpuapp_ns_defconfig:12: warning: ignoring malformed line 'UART_CONSOLE=y'

/Users/work/5340-can-ble/can-ble/boards/arm/can_ble_board/can_ble_board_cpuapp_ns_defconfig:13: warning: ignoring malformed line 'UART_ASYNC_API=y'

error: Aborting due to Kconfig warnings
.............<some output that's irrelevant>............
CMake Error at /opt/nordic/ncs/v2.6.0/nrf/cmake/multi_image.cmake:208 (message):
  No board specified for domain 'CPUNET'.  This configuration is typically
  defined in
  /Users/work/5340-can-ble/can-ble/boards/arm/can_ble_board/Kconfig
Call Stack (most recent call first):
  /opt/nordic/ncs/v2.6.0/nrf/cmake/multi_image.cmake:178 (add_child_image_from_source)
  /opt/nordic/ncs/v2.6.0/nrf/samples/CMakeLists.txt:148 (add_child_image)


-- Configuring incomplete, errors occurred!

[Marte Myrvold]

Hi,

Does CAN work when you are not using Bluetooth in v2.9.0?

Can you test the CAN counter sample?

Best regards,
Marte

[adsa]

It worked without Bluetooth in v2.9.0

So, I figured out the problem.
In the app.overlay file I had to define everything. Once more define uarts, iics, etc.
Therefore maybe a more extensive guide on how to user overlays would be nice.
For example, app.overlay seems to be related to the app core. How to I make a overlay for the network core?

[Marte Myrvold]

Hi,

Great to hear that you figured it out!

To make an overlay for the network core, you need to create it in the subdirectory of the network core image. For example, for the peripheral_uart sample this would be inside peripheral_uart/sysbuild/ipc_radio. You can call it app.overlay, or you can name it after the board target, e.g., nrf5340dk_nrf5340_cpunet.overlay.

You can find some information about how to use overlays on the following pages:

• nRF Connect SDK Fundamentals - Devicetree overlays, CMake, and build systems
• Providing CMake options
• Input and output files
• Devicetree HOWTOs

The first link is to a lesson on the topic in our DevAcademy course nRF Connect SDK Fundamentals. The others are to our documentation.

Best regards,
Marte

[adsa]

So, if I understand correctly
app.overlay + prj.conf in top project directory are for the app core
app.overlay + prj.conf in the <project_directory>/sysbuild/ipc_radio are for the network core

I have completed the tutorials on the dev academy and I have read the documentation provided, but it is generally pretty narrow compared to the multitude of possible scenarios when developing real "life size" projects since they combine multiple resources and types of configurations.

[Marte Myrvold]

adsa said:

So, if I understand correctly
app.overlay + prj.conf in top project directory are for the app core
app.overlay + prj.conf in the <project_directory>/sysbuild/ipc_radio are for the network core

That is correct.

The same goes for other images added to the project, such as MCUboot. In that case, app.overlay + prj.conf (or an overlay Kconfig file) in <project_directory>/sysbuild/mcuboot will be applied to the MCUboot image.