Lines Matching refs:an
164 …The selected GPIO will be configured as an input with internal pull-up enabled (note that on some …
165 …not all pins have an internal pull-up, consult the hardware datasheet for details.) To trigger a f…
216 The selected GPIO will be configured as an input with internal pull-up enabled.
220 Note that GPIO34-39 do not have an internal pullup and an external one must be provided.
249 This will ensure that an exception will be triggered whenever the CPU performs a memory
258 It is also useful to prevent a lock up in start code caused by an unstable power source.
318 Bootloader: When bootloader selects an app to boot, an app is selected that has
350 …There should be an entry in partition table with following details: `emul_efuse, data, efuse, , 0x…
364 This option disables the normal validation of an image coming out of
387 Note that in this case it's not possible for the bootloader to detect if an app image is
422 This option reserves an area in the RTC FAST memory (access only PRO_CPU).
463 … This area (rtc_retain_mem_t) is reserved and has access from the bootloader and an application.
469 This option reserves an area in RTC FAST memory for the following features:
568 … Embeds the ECDSA public key in the bootloader and signs the application with an ECDSA key.
616 …If this option is set, the bootloader will be compiled with code to verify that an app is signed b…
647 …table or boot an app if the data has a verified digital signature. There are implications for refl…
733 Key file is an ECDSA private key (NIST256p curve) in PEM format for Secure Boot V1.
734 Key file is an RSA private key in PEM format for Secure Boot V2.
770 NOTE: Once a digest slot is revoked, it can never be used again to verify an image
816 … Note: After first boot, the system will be permanently encrypted. Re-flashing an encrypted
857 …to flash.) This mode is not secure, it's possible for an attacker to write their own chosen plaint…
928 … space. This prevents an attacker from appending unverified data after the app image in the flash,
943 … Boot is enabled. This may allow an attacker to read-protect the BLK2 efuse (for ESP32) and
944 …CK4-BLOCK10 (i.e. BLOCK_KEY0-BLOCK_KEY5)(for other chips) holding the public key digest, causing an
945 … immediate denial of service and possibly allowing an additional fault injection attack to
962 … Revoking unused digest slots makes ensures that no trusted keys can be added later by an attacker.
1069 If set (default), in an app during startup code,
1090 … If set, during startup the app will burn an eFuse bit to permanently disable the UART ROM
1094 then an error is printed instead.
1107 … If set, during startup the app will burn an eFuse bit to permanently switch the UART ROM
1122 surface" for an attacker to try and bypass them with a successful physical attack.