Help¶

Include client code for this EXT_API. This also puts a request for this EXT_API into the firmware info, marked as optional. The user must check that it is present before using it.

Direct dependencies¶

!BL_SECP256R1_EXT_API_ATLEAST_REQUIRED && <choice: Request to use the BL_SECP256R1 EXT_API.>

(Includes any dependencies from ifs and menus.)

Kconfig definition¶

At <nRF>/subsys/fw_info/Kconfig.template.fw_info_ext_api:15

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:9 → <BuildDir>/Kconfig/Kconfig.modules:1 → <nRF>/Kconfig.nrf:25 → <nRF>/subsys/Kconfig:8 → <nRF>/subsys/bootloader/Kconfig:225 → <nRF>/subsys/bootloader/bl_crypto/Kconfig:141

Menu path: (Top) → Modules → Nordic nRF Connect → Bootloader → Secure Boot Crypto → Request to use the BL_SECP256R1 EXT_API.

config BL_SECP256R1_EXT_API_OPTIONAL
    bool "Request to use the BL_SECP256R1 EXT_API (optional)."
    depends on !BL_SECP256R1_EXT_API_ATLEAST_REQUIRED && <choice: Request to use the BL_SECP256R1 EXT_API.>
    help
      Include client code for this EXT_API. This also puts a request for
      this EXT_API into the firmware info, marked as optional. The user must
      check that it is present before using it.

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