Help¶

This option enables the mbedtls to use the heap. This setting must be global so that various applications and libraries in Zephyr do not try to do this themselves as there can be only one heap defined in mbedtls. If this is enabled, then the Zephyr will, during the device startup, initialize the heap automatically.

Help¶

This option enables the mbedtls to use the heap. This setting must be global so that various applications and libraries in Zephyr do not try to do this themselves as there can be only one heap defined in mbedtls. If this is enabled, then the Zephyr will, during the device startup, initialize the heap automatically.

Direct dependencies¶

NORDIC_SECURITY_BACKEND || MBEDTLS

(Includes any dependencies from ifs and menus.)

Defaults¶

No defaults. Implicitly defaults to n.

Symbols that select this symbol¶

Kconfig definitions¶

At <nrfxlib>/nrf_security/Kconfig:67

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:9 → <BuildDir>/Kconfig/Kconfig.modules:5 → <nrfxlib>/Kconfig.nrfxlib:13

Menu path: (Top) → Modules → Nordic nrfxlib → Nordic Security → Use Nordic provided security backend → mbed TLS memory configuration

config MBEDTLS_ENABLE_HEAP
    bool "Enable global heap for mbed TLS"
    depends on NORDIC_SECURITY_BACKEND
    help
      This option enables the mbedtls to use the heap. This setting must
      be global so that various applications and libraries in Zephyr do not
      try to do this themselves as there can be only one heap defined
      in mbedtls. If this is enabled, then the Zephyr will, during the device
      startup, initialize the heap automatically.

At <Zephyr>/modules/Kconfig.mbedtls:111

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:10 → <Zephyr>/modules/Kconfig:17

Menu path: (Top) → Modules → mbedTLS Support

config MBEDTLS_ENABLE_HEAP
    bool "Enable global heap for mbed TLS"
    depends on MBEDTLS
    help
      This option enables the mbedtls to use the heap. This setting must
      be global so that various applications and libraries in Zephyr do not
      try to do this themselves as there can be only one heap defined
      in mbedtls. If this is enabled, then the Zephyr will, during the device
      startup, initialize the heap automatically.

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