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

CONFIG_LOG_MODE_MINIMAL¶

Minimal-footprint

Type: bool

Help¶

Enable minimal logging implementation. This has very little footprint overhead on top of the printk() implementation for standard logging macros. Hexdump macros are also supported, with a small amount of code pulled in if used. Build time filtering is supported, but not runtime filtering. There are no timestamps, prefixes, colors, or asynchronous logging, and all messages are simply sent to printk().

Direct dependencies¶

<choice: Mode>

(Includes any dependencies from ifs and menus.)

Symbols implied by this symbol¶

PRINTK

Kconfig definition¶

At subsys/logging/Kconfig.mode:26

Included via Kconfig:8 → Kconfig.zephyr:34 → subsys/Kconfig:31 → subsys/logging/Kconfig:13

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

config LOG_MODE_MINIMAL
    bool "Minimal-footprint"
    imply PRINTK
    depends on <choice: Mode>
    help
      Enable minimal logging implementation. This has very little footprint
      overhead on top of the printk() implementation for standard
      logging macros. Hexdump macros are also supported, with a small
      amount of code pulled in if used. Build time filtering is supported,
      but not runtime filtering. There are no timestamps, prefixes,
      colors, or asynchronous logging, and all messages are simply
      sent to printk().

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