No board specified for domain 'CPUNET'

[Stefano1984]

Hi all,
I want to program a nRF5340 microcontroller to become a peripheral BLE device. I use the Zephyr with nRF Connect SDK 2.7.0 and VSCode as IDE.
I have a custom electronic board so I created a new board with the "Create a new board" wizard.
Everything was going well until I moved on to the BLE part.
In particular, I receive the following error:

No board specified for domain 'CPUNET'. This configuration is typically defined in myProjectPath/boards/ ... /nrf5340_ah_board/Kconfig

So there is something missing regarding the core network of the nRF5340.

Can anyone help me and solve my problem?
I checked and the Kconfig file does not exist.
Yet the wizard to create a new board is not complicated and there are not many settings to set.

At this point I wonder: is it possible to create a board from scratch or is it better to take an existing board and create an overlay file?

Is it too complicated to set up a custom board by yourself? Shouldn't the automatic procedure do it all?

Thanks.

[Einar Thorsrud]

Hi,

The Create new board wizard does not work well with the nRF5340, and also does not work well with hardware model 2 yet. The recomended approach for making your custom nRF5340 board files is to copy out the DK files and adjust to your custom board. (There is an exercise demonstrating it here, but it has unfortunately not ben updated for the latest SDK versions).

[jhellen]

I have the same problem, I can either select cpuapp as target or cpunet as target. My board default configuration files match the DK version. Wat do I need to do to enable the net core? I'm using the Using the project in a cmake envrironment, 

Anyone any idea?

[Einar Thorsrud]

 Hi,

Can you elaborate? Note that you cannot select multiple targets for a single build (though with sysbuild, additional images can be built for other cores). So when you make an appliction for the app core that rely on the radio, sysbuild (or previously the parent/child image support), will be used to automatically build the corresponding network core image, as is the case when you build relevant examples for the DK. The approach will be the same for custom boards.

[jhellen]

I'm trying to add some BLE parts to the project that  I already build using the app target. As long as I don't add BLE config parts it builds and runs ok. As soon as I add various BLE config tags to the prj.conf file I get the following errors/warnings (two examples) :

1) 

# Bluetooth

#CONFIG_BT_CTLR=y

CONFIG_BT=y             # Enable bluetooth

CONFIG_BT_CENTRAL=y     # Central Role support

CONFIG_BT_GATT_CLIENT=y # Interact with other BLE devices that expose GATT services (heart rate service)

CONFIG_BT_SCAN=y        # Enable scanning for nearby devi

Result:

CMake Error at C:/ncs/v2.7.0/nrf/cmake/multi_image.cmake:208 (message):
No board specified for domain 'CPUNET'. This configuration is typically
defined in
C:/source/repo/OEMCPETModule/trunk/firmware/BLEController/boards/Relitech/nRF5340_CPET/Kconfig
Call Stack (most recent call first):
C:/ncs/v2.7.0/nrf/cmake/multi_image.cmake:178 (add_child_image_from_source)
C:/ncs/v2.7.0/nrf/samples/CMakeLists.txt:148 (add_child_image)

2) 

# Bluetooth

CONFIG_BT_CTLR=y

CONFIG_BT=y             # Enable bluetooth

CONFIG_BT_CENTRAL=y     # Central Role support

CONFIG_BT_GATT_CLIENT=y # Interact with other BLE devices that expose GATT services (heart rate service)

CONFIG_BT_SCAN=y        # Enable scanning for nearby devices

CONFIG_BT_SMP=y         # security management

Result:

warning: Experimental symbol BT_LL_SW_SPLIT is enabled.

warning: ENTROPY_NRF5_RNG (defined at drivers/entropy/Kconfig.nrf5:14) has direct dependencies !ENTROPY_NRF_FORCE_ALT && DT_HAS_NORDIC_NRF_RNG_ENABLED && ENTROPY_GENERATOR with value n, but is currently being y-selected by the following symbols:
- BT_LLL_VENDOR_NORDIC (defined at subsys/bluetooth\controller\Kconfig.ll_sw_split:8), with value y, direct dependencies SOC_COMPATIBLE_NRF && !n && !n && BT_LL_SW_SPLIT && BT_CTLR && BT_HCI && BT (value: y), and select condition SOC_COMPATIBLE_NRF && !n && !n && BT_LL_SW_SPLIT && BT_CTLR && BT_HCI && BT (value: y)
Parsing C:/ncs/v2.7.0/zephyr/Kconfig
Loaded configuration 'C:/source/repo/OEMCPETModule/trunk/firmware/BLEController/boards/Relitech/nRF5340_CPET/nRF5340_CPET_nrf5340_cpuapp_defconfig'
Merged configuration 'C:/source/repo/OEMCPETModule/trunk/firmware/BLEController/prj.conf'
Merged configuration 'C:/source/repo/OEMCPETModule/trunk/firmware/BLEController/prj_debug.conf'

error: Aborting due to Kconfig warnings

Hope this make sense somehow, me, ignorant as I am, missing some vital information.