CONFIG_BOARD_ENABLE_CPUNET

Enable nRF53 Network MCU

Enable nRF53 Network MCU

Enable nRF53 Network MCU

Type: bool

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.

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.

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.

Kconfig definitions

At <Zephyr>/boards/arm/bl5340_dvk/Kconfig:70

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:35 → <Zephyr>/boards/Kconfig:60

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_BL5340_DVK_CPUAPP || BOARD_BL5340_DVK_CPUAPP_NS
    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.

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

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:35 → <Zephyr>/boards/Kconfig:60

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_NRF5340DK_NRF5340_CPUAPP || BOARD_NRF5340DK_NRF5340_CPUAPP_NS
    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.

At <Zephyr>/boards/arm/thingy53_nrf5340/Kconfig:72

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:35 → <Zephyr>/boards/Kconfig:60

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_THINGY53_NRF5340_CPUAPP || BOARD_THINGY53_NRF5340_CPUAPP_NS
    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.)