:orphan:

.. title:: CONFIG_BT_DEBUG_MONITOR_RTT

.. kconfig:: CONFIG_BT_DEBUG_MONITOR_RTT

CONFIG_BT_DEBUG_MONITOR_RTT
###########################

*Monitor protocol over RTT*

Type: ``bool``

Help
====

.. code-block:: none

    Use a custom logging protocol over the RTT buffer instead of
    plain-text output. Requires a special application
    on the host side that can decode this protocol. Currently
    the 'btmon' tool from BlueZ is capable of doing this.

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

\ :kconfig:`USE_SEGGER_RTT <CONFIG_USE_SEGGER_RTT>` && \ :kconfig:`SEGGER_RTT_MAX_NUM_UP_BUFFERS <CONFIG_SEGGER_RTT_MAX_NUM_UP_BUFFERS>` >= 2 && \ :ref:`<choice BT_DEBUG_TYPE: Bluetooth debug type> <choice_501>`

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

Symbols selected by this symbol
===============================

- \ :kconfig:`BT_DEBUG <CONFIG_BT_DEBUG>`
- \ :kconfig:`BT_MONITOR <CONFIG_BT_MONITOR>`

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



At ``<Zephyr Subsystem>/bluetooth/common/Kconfig:309``

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

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

.. code-block:: kconfig

    config BT_DEBUG_MONITOR_RTT
    	bool "Monitor protocol over RTT"
    	select BT_DEBUG
    	select BT_MONITOR
    	depends on USE_SEGGER_RTT && SEGGER_RTT_MAX_NUM_UP_BUFFERS >= 2 && <choice BT_DEBUG_TYPE>
    	help
    	  Use a custom logging protocol over the RTT buffer instead of
    	  plain-text output. Requires a special application
    	  on the host side that can decode this protocol. Currently
    	  the 'btmon' tool from BlueZ is capable of doing this.

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