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

CONFIG_MBEDTLS_DEBUG¶

mbed TLS debug activation

Type: bool

Help¶

Enable debugging activation for mbed TLS configuration. If you use mbedTLS/Zephyr integration (e.g. net_app), this will activate debug logging (of the level configured by MBEDTLS_DEBUG_LEVEL). If you use mbedTLS directly instead, you will need to perform additional configuration yourself: call mbedtls_ssl_conf_dbg(&mbedtls.conf, my_debug, NULL); mbedtls_debug_set_threshold(level); functions in your application, and create the my_debug() function to actually print something useful.

Direct dependencies¶

MBEDTLS_BUILTIN && MBEDTLS

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

Defaults¶

No defaults. Implicitly defaults to n.

Kconfig definition¶

At ext/lib/crypto/mbedtls/Kconfig:74

Included via Kconfig:10 → Kconfig.zephyr:41 → ext/Kconfig:13 → ext/lib/crypto/Kconfig:10

Menu path: (top menu) → External Sources → Cryptography → mbedTLS Support

config MBEDTLS_DEBUG
    bool
    prompt "mbed TLS debug activation" if MBEDTLS_BUILTIN && MBEDTLS
    depends on MBEDTLS_BUILTIN && MBEDTLS
    help
      Enable debugging activation for mbed TLS configuration. If you use
      mbedTLS/Zephyr integration (e.g. net_app), this will activate debug
      logging (of the level configured by MBEDTLS_DEBUG_LEVEL).
      If you use mbedTLS directly instead, you will need to perform
      additional configuration yourself: call
      mbedtls_ssl_conf_dbg(&mbedtls.conf, my_debug, NULL);
      mbedtls_debug_set_threshold(level);
      functions in your application, and create the my_debug() function to
      actually print something useful.

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