Lines Matching refs:enabled

77                 for external SPIRAM if it is enabled.
131             If this option is enabled, and VDDSDIO LDO is set to 1.8V (using eFuse
164 …The selected GPIO will be configured as an input with internal pull-up enabled (note that on some …
216             The selected GPIO will be configured as an input with internal pull-up enabled.
374             options" is enabled, however it's strongly recommended to NOT enable it as
395 …from a flash corruption event, keep the option BOOTLOADER_WDT_ENABLE enabled and consider also ena…
413             is the only important factor then it can be enabled.
446             RTC FAST memory CRC calculation takes place. When this option is enabled, the
619 …          If hardware secure boot is enabled, this option is always enabled and cannot be disabled.
620 …If hardware secure boot is not enabled, this option doesn't add significant security by itself so …
630 …When enabled, the signature is automatically checked whenever the esp_ota_ops.h APIs are used for …
633 …          If hardware secure boot is enabled, this option is always enabled and cannot be disabled.
634 …If hardware secure boot is not enabled, this option still adds significant security against networ…
646 …Once enabled, Secure Boot will not boot a modified bootloader. The bootloader will only load a par…
648             updated apps once secure boot is enabled.
717 …       Once secure boot or signed app requirement is enabled, app images are required to be signed.
719 …If enabled (default), these binary files are signed as part of the build process. The file named in
765 …         Revocation of keys does not happen when enabling secure boot. Once secure boot is enabled,
855 …  By default Development mode is enabled which allows ROM download mode to perform flash encryption
860 …Release mode should always be selected for production or manufacturing. Once enabled it's no longer
863             When EFUSE_VIRTUAL is enabled, SECURE_FLASH_ENCRYPTION_MODE_RELEASE is not available.
901                 When either flash encryption or secure boot are enabled, the default is to
914                 when either secure boot or flash encryption is enabled.
940 …        efuse when Secure Boot is enabled. This prevents any more efuses from being read protected.
943 …         Boot is enabled. This may allow an attacker to read-protect the BLK2 efuse (for ESP32) and
966             bool "Leave UART bootloader encryption enabled"
977             bool "Leave UART bootloader decryption enabled"
988             bool "Leave UART bootloader flash cache enabled"
999             bool "Require flash encryption to be already enabled"
1003 …  If not set (default), and flash encryption is not yet enabled in eFuses, the 2nd stage bootloader
1005 …  If this option is set, and flash encryption is not yet enabled, the bootloader will error out and
1007 …     If flash encryption is enabled in eFuses, this option does not change the bootloader behavior.
1010 …     the wrong device. The device needs to have flash encryption already enabled using espefuse.py.
1018 …_CACHE(for ESP32) or DIS_ICACHE/DIS_DCACHE(for other chips) eFuse when Flash Encryption is enabled.
1058             when secure boot is enabled.
1065         bool "Check Flash Encryption enabled on app startup"
1097 …              Encryption and/or Secure Boot is enabled and access to Download Mode is not required.
1113                 enabled security features (`get_security_info`).
1119                 Secure Download mode should be enabled in any application where Flash Encryption
1120                 and/or Secure Boot is enabled. Disabling this option does not immediately cancel
1133                 Enabling this option will allow the full UART download mode to stay enabled.