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: Bluetooth debug type>

(Includes any dependencies from if’s and menus.)

Symbols selected by this symbol¶

Kconfig definition¶

At subsys/bluetooth/common/Kconfig:57

Included via Kconfig:10 → Kconfig.zephyr:35 → subsys/Kconfig:8 → subsys/bluetooth/Kconfig:154

Menu path: (top menu) → Bluetooth → Bluetooth debug type

config BT_DEBUG_MONITOR
    bool
    prompt "Monitor protocol over UART" if <choice: Bluetooth debug type>
    select BT_DEBUG if <choice: Bluetooth debug type>
    select PRINTK if <choice: Bluetooth debug type>
    select CONSOLE_HAS_DRIVER if <choice: Bluetooth debug type>
    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).

(Definitions include propagated dependencies, including from if’s and menus.)