:orphan:

.. title:: BT_DEBUG_MONITOR

.. option:: CONFIG_BT_DEBUG_MONITOR

*Monitor protocol over UART*

Type: ``bool``

Help
====

Use a custom logging protocol over the console UART
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.

If the target board has two or more external UARTs it is
possible to keep using UART_CONSOLE together with this option,
however if there is only a single external UART then
UART_CONSOLE needs to be disabled (in which case printk/printf
will get encoded into the monitor protocol).

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

\ :ref:`<choice: Bluetooth debug type> <choice_352>`

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

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

- \ :option:`BT_DEBUG <CONFIG_BT_DEBUG>`
- \ :option:`LOG <CONFIG_LOG>`
- \ :option:`CONSOLE_HAS_DRIVER <CONFIG_CONSOLE_HAS_DRIVER>`

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

.. highlight:: kconfig

At ``subsys/bluetooth/common/Kconfig:104``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:34`` → ``subsys/Kconfig:9`` → ``subsys/bluetooth/Kconfig:238``

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

.. parsed-literal::

    config BT_DEBUG_MONITOR
    	bool "Monitor protocol over UART"
    	select \ :option:`BT_DEBUG <CONFIG_BT_DEBUG>`
    	select \ :option:`LOG <CONFIG_LOG>`
    	select \ :option:`CONSOLE_HAS_DRIVER <CONFIG_CONSOLE_HAS_DRIVER>`
    	depends on \ :ref:`<choice: Bluetooth debug type> <choice_352>`
    	help
    	  Use a custom logging protocol over the console UART
    	  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.
	  
    	  If the target board has two or more external UARTs it is
    	  possible to keep using UART_CONSOLE together with this option,
    	  however if there is only a single external UART then
    	  UART_CONSOLE needs to be disabled (in which case printk/printf
    	  will get encoded into the monitor protocol).

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