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.

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.

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) || (MBEDTLS_BUILTIN && MBEDTLS) || (MBEDTLS_BUILTIN && MBEDTLS && 0)

(Includes any dependencies from ifs and menus.)

Defaults

No defaults. Implicitly defaults to n.

Kconfig definitions

At <Zephyr>/modules/mbedtls/Kconfig:84

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:33 → <Zephyr>/modules/Kconfig:6 → <nRF>/doc/_build/kconfig/Kconfig.modules:14

Menu path: (Top) → Modules → mbedtls (/home/runner/work/sdk-nrf/sdk-nrf/ncs/mbedtls) → mbed TLS Support

config MBEDTLS_DEBUG
    bool "mbed TLS debug activation"
    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.

At <Zephyr>/modules/mbedtls/Kconfig:84

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:33 → <Zephyr>/modules/Kconfig:6 → <nRF>/doc/_build/kconfig/Kconfig.modules:68

Menu path: (Top) → Modules → mbedtls (/home/runner/work/sdk-nrf/sdk-nrf/ncs/modules/crypto/mbedtls) → mbed TLS Support

config MBEDTLS_DEBUG
    bool "mbed TLS debug activation"
    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.

At <Zephyr>/modules/mbedtls/Kconfig:84

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:33 → <Zephyr>/modules/Kconfig:80

Menu path: (Top) → Modules → mbed TLS Support

config MBEDTLS_DEBUG
    bool "mbed TLS debug activation"
    depends on MBEDTLS_BUILTIN && MBEDTLS && 0
    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.

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