CONFIG_BT_DEBUG_MONITOR_UART¶
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¶
<choice BT_DEBUG_TYPE: Bluetooth debug type>
(Includes any dependencies from ifs and menus.)
Symbols selected by this symbol¶
Kconfig definition¶
At subsys/bluetooth/common/Kconfig:291
Included via Kconfig:8 → Kconfig.zephyr:44 → subsys/Kconfig:9 → subsys/bluetooth/Kconfig:173
Menu path: (Top) → Sub Systems and OS Services → Bluetooth → Bluetooth debug type
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.)