Help¶

Enabling this option prints out hex dumps of transferred data. There are four types of hex dumps: data that flows from RTT, data that flows to RTT, frames that are passed to network stack, frames that are get from network stack. This option will produce a lot of debug logs, so if you reading it make sure that logger did not discard something because of buffer overrun.

Direct dependencies¶

ETH_RTT_LOG_LEVEL >= 4 && ETH_RTT && HAS_SEGGER_RTT

(Includes any dependencies from ifs and menus.)

Defaults¶

No defaults. Implicitly defaults to n.

Kconfig definition¶

At <nRF>/drivers/net/Kconfig:103

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:9 → <BuildDir>/Kconfig/Kconfig.modules:1 → <nRF>/Kconfig.nrf:27 → <nRF>/drivers/Kconfig:11

Menu path: (Top) → Modules → Nordic nRF Connect → Device Drivers → Ethernet over RTT driver

config ETH_RTT_DEBUG_HEX_DUMP
    bool "Print hex dumps"
    depends on ETH_RTT_LOG_LEVEL >= 4 && ETH_RTT && HAS_SEGGER_RTT
    help
      Enabling this option prints out hex dumps of transferred data. There
      are four types of hex dumps: data that flows from RTT, data that
      flows to RTT, frames that are passed to network stack, frames that
      are get from network stack. This option will produce a lot of debug
      logs, so if you reading it make sure that logger did not discard
      something because of buffer overrun.

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