The latest development version of this page may be more current than this released 1.14.1 version.

CONFIG_LOG_BACKEND_RTT¶

Enable Segger J-Link RTT backend

Type: bool

Help¶

When enabled, backend will use RTT for logging. This backend works on a per message basis. Only a whole message (terminated with a carriage return: ‘r’) is transferred to up-buffer at once depending on available space and selected mode. In panic mode backend always blocks and waits until there is space in up-buffer for a message and message is transferred to host.

Direct dependencies¶

USE_SEGGER_RTT && LOG

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

Defaults¶

“y” if !SHELL_BACKEND_RTT && USE_SEGGER_RTT && LOG

Kconfig definition¶

At subsys/logging/Kconfig:242

Included via Kconfig:10 → Kconfig.zephyr:39 → subsys/Kconfig:20

Menu path: (top menu) → Logging

config LOG_BACKEND_RTT
    bool
    prompt "Enable Segger J-Link RTT backend" if USE_SEGGER_RTT && LOG
    default "y" if !SHELL_BACKEND_RTT && USE_SEGGER_RTT && LOG
    depends on USE_SEGGER_RTT && LOG
    help
      When enabled, backend will use RTT for logging. This backend works on a per
      message basis. Only a whole message (terminated with a carriage return: 'r')
      is transferred to up-buffer at once depending on available space and
      selected mode.
      In panic mode backend always blocks and waits until there is space
      in up-buffer for a message and message is transferred to host.

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