CONFIG_BT_ASSERT

Custom Bluetooth assert implementation

Type: bool

Help

Use a custom Bluetooth assert implementation instead of the
kernel-wide __ASSERT() when CONFIG_ASSERT is disabled.

Help

Use a custom Bluetooth assert implementation instead of the
kernel-wide __ASSERT() when CONFIG_ASSERT is disabled.

Direct dependencies

BT_RPC_STACK || (BT_HCI && BT)

(Includes any dependencies from ifs and menus.)

Defaults

y
y

Kconfig definitions

At <Zephyr>/subsys/bluetooth/common/Kconfig:241

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:33 → <Zephyr>/modules/Kconfig:6 → <nRF>/doc/_build/kconfig/Kconfig.modules:2 → <nRF>/Kconfig.nrf:92 → <nRF>/subsys/Kconfig:10 → <nRF>/subsys/bluetooth/Kconfig:38 → <nRF>/subsys/bluetooth/rpc/Kconfig:195

Menu path: (Top) → Modules → nrf (/home/runner/work/sdk-nrf/sdk-nrf/ncs/nrf) → Nordic nRF Connect → Bluetooth Low Energy → BLE over nRF RPC

config BT_ASSERT
    bool "Custom Bluetooth assert implementation"
    default y
    depends on BT_RPC_STACK
    help
      Use a custom Bluetooth assert implementation instead of the
      kernel-wide __ASSERT() when CONFIG_ASSERT is disabled.

At <Zephyr>/subsys/bluetooth/common/Kconfig:241

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:44 → <Zephyr>/subsys/Kconfig:9 → <Zephyr>/subsys/bluetooth/Kconfig:179

Menu path: (Top) → Sub Systems and OS Services → Bluetooth

config BT_ASSERT
    bool "Custom Bluetooth assert implementation"
    default y
    depends on BT_HCI && BT
    help
      Use a custom Bluetooth assert implementation instead of the
      kernel-wide __ASSERT() when CONFIG_ASSERT is disabled.

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