Help¶

This option enables releasing the Network ‘force off’ signal, which as a consequence will power up the Network MCU during system boot. Additionally, the option allocates GPIO pins that will be used by UARTE of the Network MCU. Note: GPIO pin allocation can only be configured by the secure Application MCU firmware, so when this option is used with the non-secure version of the board, the application needs to take into consideration, that the secure firmware image must already have configured GPIO allocation for the Network MCU.

Direct dependencies¶

BOARD_NRF5340PDK_NRF5340_CPUAPP || BOARD_NRF5340PDK_NRF5340_CPUAPPNS || BOARD_NRF5340DK_NRF5340_CPUAPP || BOARD_NRF5340DK_NRF5340_CPUAPPNS

(Includes any dependencies from ifs and menus.)

Default¶

y if BT || NRF_802154_SER_HOST

Kconfig definition¶

At <Zephyr>/boards/arm/nrf5340dk_nrf5340/Kconfig:33

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:27 → <Zephyr>/boards/Kconfig:48

Menu path: (Top) → Board Options

config BOARD_ENABLE_CPUNET
    bool "Enable nRF53 Network MCU"
    default y if BT || NRF_802154_SER_HOST
    depends on BOARD_NRF5340PDK_NRF5340_CPUAPP || BOARD_NRF5340PDK_NRF5340_CPUAPPNS || BOARD_NRF5340DK_NRF5340_CPUAPP || BOARD_NRF5340DK_NRF5340_CPUAPPNS
    help
      This option enables releasing the Network 'force off' signal, which
      as a consequence will power up the Network MCU during system boot.
      Additionally, the option allocates GPIO pins that will be used by UARTE
      of the Network MCU.
      Note: GPIO pin allocation can only be configured by the secure Application
      MCU firmware, so when this option is used with the non-secure version of
      the board, the application needs to take into consideration, that the
      secure firmware image must already have configured GPIO allocation for the
      Network MCU.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)