:orphan: .. title:: BOARD_ENABLE_CPUNET .. option:: CONFIG_BOARD_ENABLE_CPUNET *Enable nRF53 Network MCU* *Enable nRF53 Network MCU* *Enable nRF53 Network MCU* Type: ``bool`` Help ==== .. code-block:: none 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 ==== .. code-block:: none 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 ==== .. code-block:: none 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 =================== \ :option:`BOARD_BL5340_DVK_CPUAPP ` || \ :option:`BOARD_BL5340_DVK_CPUAPPNS ` || \ :option:`BOARD_NRF5340DK_NRF5340_CPUAPP ` || \ :option:`BOARD_NRF5340DK_NRF5340_CPUAPPNS ` || \ :option:`BOARD_THINGY53_NRF5340_CPUAPP ` || \ :option:`BOARD_THINGY53_NRF5340_CPUAPPNS ` *(Includes any dependencies from ifs and menus.)* Defaults ======== - y if \ :option:`BT ` || \ :option:`NRF_802154_SER_HOST ` - y if \ :option:`BT ` || \ :option:`NRF_802154_SER_HOST ` - y if \ :option:`BT ` || \ :option:`NRF_802154_SER_HOST ` Kconfig definitions =================== At ``/arm/bl5340_dvk/Kconfig:70`` Included via ``Kconfig:8`` → ``Kconfig.zephyr:27`` → ``/Kconfig:57`` Menu path: (Top) → Board Options .. code-block:: kconfig 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_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. ---- At ``/arm/nrf5340dk_nrf5340/Kconfig:69`` Included via ``Kconfig:8`` → ``Kconfig.zephyr:27`` → ``/Kconfig:57`` Menu path: (Top) → Board Options .. code-block:: kconfig 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_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. ---- At ``/arm/thingy53_nrf5340/Kconfig:72`` Included via ``Kconfig:8`` → ``Kconfig.zephyr:27`` → ``/Kconfig:57`` Menu path: (Top) → Board Options .. code-block:: kconfig 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_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.)*