The latest development version of this page may be more current than this released 2.7.5 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_FRONTEND && !LOG_MINIMAL && LOG

(Includes any dependencies from ifs and menus.)

Default¶

y if !SHELL_BACKEND_RTT

Symbols selected by this symbol¶

SEGGER_RTT_CUSTOM_LOCKING

Kconfig definition¶

At subsys/logging/Kconfig.backends:87

Included via Kconfig:8 → Kconfig.zephyr:44 → subsys/Kconfig:31 → subsys/logging/Kconfig:28

Menu path: (Top) → Sub Systems and OS Services → Logging → Backends

config LOG_BACKEND_RTT
    bool "Enable Segger J-Link RTT backend"
    default y if !SHELL_BACKEND_RTT
    select SEGGER_RTT_CUSTOM_LOCKING
    depends on USE_SEGGER_RTT && !LOG_FRONTEND && !LOG_MINIMAL && 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.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)