:orphan:

.. title:: CONFIG_MBEDTLS_DEBUG

.. kconfig:: CONFIG_MBEDTLS_DEBUG

CONFIG_MBEDTLS_DEBUG
####################

*mbed TLS debug activation*

*mbed TLS debug activation*

Type: ``bool``

Help
====

.. code-block:: none

    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
====

.. code-block:: none

    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
===================

(\ :kconfig:`MBEDTLS_BUILTIN <CONFIG_MBEDTLS_BUILTIN>` && \ :kconfig:`MBEDTLS <CONFIG_MBEDTLS>`) || (\ :kconfig:`MBEDTLS_BUILTIN <CONFIG_MBEDTLS_BUILTIN>` && \ :kconfig:`MBEDTLS <CONFIG_MBEDTLS>` && 0)

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

Defaults
========

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

Kconfig definitions
===================



At ``<External Modules>/mbedtls/Kconfig:79``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:33`` → ``<External Modules>/Kconfig:6`` → ``<BuildDir>/kconfig/Kconfig.modules:26``

Menu path: (Top) → Modules → mbedtls (/home/runner/work/bridle/bridle/workspace/modules/crypto/mbedtls) → mbed TLS Support

.. code-block:: kconfig

    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 ``<External Modules>/mbedtls/Kconfig:79``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:33`` → ``<External Modules>/Kconfig:74``

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

.. code-block:: kconfig

    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.)*