:orphan:

.. title:: CONFIG_BT_CTLR_DEBUG_PINS

.. kconfig:: CONFIG_BT_CTLR_DEBUG_PINS

CONFIG_BT_CTLR_DEBUG_PINS
#########################

*Bluetooth Controller Debug Pins*

Type: ``bool``

Help
====

.. code-block:: none

    Turn on debug GPIO toggling for the BLE Controller. This is useful
    when debugging with a logic analyzer or profiling certain sections of
    the code.

Direct dependencies
===================

(\ :kconfig:`BOARD_NRF51DK_NRF51422 <CONFIG_BOARD_NRF51DK_NRF51422>` || \ :kconfig:`BOARD_NRF52DK_NRF52832 <CONFIG_BOARD_NRF52DK_NRF52832>` || \ :kconfig:`BOARD_NRF52DK_NRF52810 <CONFIG_BOARD_NRF52DK_NRF52810>` || \ :kconfig:`BOARD_NRF52840DK_NRF52840 <CONFIG_BOARD_NRF52840DK_NRF52840>` || \ :kconfig:`BOARD_NRF52833DK_NRF52833 <CONFIG_BOARD_NRF52833DK_NRF52833>` || \ :kconfig:`BOARD_NRF5340DK_NRF5340_CPUNET <CONFIG_BOARD_NRF5340DK_NRF5340_CPUNET>` || \ :kconfig:`BOARD_RV32M1_VEGA <CONFIG_BOARD_RV32M1_VEGA>`) && \ :kconfig:`BT_LL_SW_SPLIT <CONFIG_BT_LL_SW_SPLIT>` && \ :kconfig:`BT_CTLR <CONFIG_BT_CTLR>` && \ :kconfig:`BT_HCI <CONFIG_BT_HCI>` && \ :kconfig:`BT <CONFIG_BT>`

*(Includes any dependencies from ifs and menus.)*

Defaults
========

No defaults. Implicitly defaults to ``n``.

Kconfig definition
==================



At ``<Zephyr Subsystem>/bluetooth/controller/Kconfig.ll_sw_split:818``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:44`` → ``<Zephyr Subsystem>/Kconfig:9`` → ``<Zephyr Subsystem>/bluetooth/Kconfig:175`` → ``<Zephyr Subsystem>/bluetooth/controller/Kconfig:659``

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

.. code-block:: kconfig

    config BT_CTLR_DEBUG_PINS
    	bool "Bluetooth Controller Debug Pins"
    	depends on (BOARD_NRF51DK_NRF51422 || BOARD_NRF52DK_NRF52832 || BOARD_NRF52DK_NRF52810 || BOARD_NRF52840DK_NRF52840 || BOARD_NRF52833DK_NRF52833 || BOARD_NRF5340DK_NRF5340_CPUNET || BOARD_RV32M1_VEGA) && BT_LL_SW_SPLIT && BT_CTLR && BT_HCI && BT
    	help
    	  Turn on debug GPIO toggling for the BLE Controller. This is useful
    	  when debugging with a logic analyzer or profiling certain sections of
    	  the code.

*(The 'depends on' condition includes propagated dependencies from ifs and menus.)*