Help

Enabling this setting will include an ANT-only network stack to run on the network core to communicate over nRF RPC with the application core. The application core does not have access to the radio peripheral.

This setting conflicts with CONFIG_BT since dual protocol samples (ANT and BLE) are built on the on the default network core sample (typically hci_rpmsg, see NCS_INCLUDE_RPMSG_CHILD_IMAGE for details) with additional configurations to enable ANT.

Direct dependencies

SOC_NRF5340_CPUAPP && ANT_NP && !BT && SOC_SERIES_NRF53X && ANT

(Includes any dependencies from ifs and menus.)

Default

y if ANT_NP && !BT

Symbols selected by this symbol

PARTITION_MANAGER_ENABLED
BOARD_ENABLE_CPUNET

Kconfig definition

At samples/Kconfig:12

Included via Kconfig:37

Menu path: (Top) → ANT Wireless

config ANT_INCLUDE_NP_CHILD_IMAGE
    bool "Include ANT NP sample on netcore"
    default y if ANT_NP && !BT
    select PARTITION_MANAGER_ENABLED
    select BOARD_ENABLE_CPUNET
    depends on SOC_NRF5340_CPUAPP && ANT_NP && !BT && SOC_SERIES_NRF53X && ANT
    help
      Enabling this setting will include an ANT-only network stack to run on
      the network core to communicate over nRF RPC with the application core.
      The application core does not have access to the radio peripheral.

      This setting conflicts with CONFIG_BT since dual protocol samples (ANT
      and BLE) are built on the on the default network core sample (typically
      hci_rpmsg, see NCS_INCLUDE_RPMSG_CHILD_IMAGE for details) with
      additional configurations to enable ANT.

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