-
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).
Symbols selected by this symbol¶
Kconfig definition¶
At <Zephyr>/subsys/bluetooth/common/Kconfig:104
Included via <Zephyr>/Kconfig:8
→ <Zephyr>/Kconfig.zephyr:34
→ <Zephyr>/subsys/Kconfig:8
→ <Zephyr>/subsys/bluetooth/Kconfig:238
Menu path: (Top) → Sub Systems and OS Services → Bluetooth → Bluetooth debug type
config BT_DEBUG_MONITOR bool "Monitor protocol over UART" selectBT_DEBUG
selectLOG
selectCONSOLE_HAS_DRIVER
depends on <choice: Bluetooth 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.)