:orphan:

.. title:: MBEDTLS_DEBUG

.. option:: 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
===================

\ :option:`MBEDTLS_BUILTIN <CONFIG_MBEDTLS_BUILTIN>` && \ :option:`MBEDTLS <CONFIG_MBEDTLS>`

*(Includes any dependencies from ifs and menus.)*

Defaults
========

No defaults. Implicitly defaults to ``n``.

Kconfig definition
==================

.. highlight:: kconfig

At ``modules/Kconfig.mbedtls:61``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:23`` → ``modules/Kconfig:21``

Menu path: (Top) → Modules → mbedTLS Support

.. parsed-literal::

    config MBEDTLS_DEBUG
    	bool "mbed TLS debug activation"
    	depends on \ :option:`MBEDTLS_BUILTIN <CONFIG_MBEDTLS_BUILTIN>` && \ :option:`MBEDTLS <CONFIG_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.

*(The 'depends on' condition includes propagated dependencies from ifs and menus.)*