:orphan:

.. title:: CONFIG_BT_DEBUG_MONITOR_UART

.. kconfig:: CONFIG_BT_DEBUG_MONITOR_UART

CONFIG_BT_DEBUG_MONITOR_UART
############################

*Monitor protocol over UART*

Type: ``bool``

Help
====

.. code-block:: none

    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 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:`LOG <CONFIG_LOG>`
- \ :kconfig:`CONSOLE_HAS_DRIVER <CONFIG_CONSOLE_HAS_DRIVER>`
- \ :kconfig:`BT_MONITOR <CONFIG_BT_MONITOR>`

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



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

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_UART
    	bool "Monitor protocol over UART"
    	select BT_DEBUG
    	select LOG
    	select CONSOLE_HAS_DRIVER
    	select BT_MONITOR
    	depends on <choice BT_DEBUG_TYPE>
    	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.)*