Searched refs:protected (Results 1 – 11 of 11) sorted by relevance
/hal_espressif-latest/tools/esptool_py/docs/en/espefuse/ |
D | read-write-protections-cmd.rst | 6 There are two commands (to get the correct list of eFuse fields that can be protected, specify the … 19 …d and write protections. See the help for these commands for the eFuse names that can be protected. 21 …protected as a group, so protecting one of eFuse will result in some related eFuses becoming prote… 28 …gh hardware may use the correct value. In espefuse v2.6 and newer, read-protected eFuse values are…
|
D | burn-key-cmd.rst | 40 …eFuse key even if it looks like it is already been written, or is write protected. Note that this … 50 …Keys for ``flash_encryption`` and ``secure_boot_v1`` will be burned as read and write protected. T… 52 …Key for ``secure_boot_v2`` will be burned only as write protected. The key must be readable becaus… 103 …s of this key will be burned to the low part of the eFuse block. These bits will be read protected. 118 Only flash encryption key is read protected if ``--no-read-protect`` is not used. 133 By default, when an encryption key block is burned it is also read and write protected. 160 …llow any eFuse bits to be cleared 1->0, and can not write anything to write protected eFuse blocks. 180 The key block will be read and write protected
|
D | burn-bit-cmd.rst | 15 …. Burn it even if it looks like it is already been written, or is write protected. Note that this …
|
D | burn-block-data-cmd.rst | 19 …eFuse key even if it looks like it is already been written, or is write protected. Note that this …
|
D | burn-key-digest-cmd.rst | 27 …eFuse key even if it looks like it is already been written, or is write protected. Note that this … 38 The secure boot v2 key(s) will be readable and write protected.
|
D | burn-custom-mac-cmd.rst | 14 …eFuse key even if it looks like it is already been written, or is write protected. Note that this …
|
D | dump-cmd.rst | 92 …d to write them back to another chip. Note that some blocks may be read-protected, in which case t…
|
D | summary-cmd.rst | 31 …gh hardware may use the correct value. In espefuse v2.6 and newer, read-protected eFuse values are…
|
/hal_espressif-latest/components/spi_flash/ |
D | esp_flash_api.c | 627 uint64_t protected = 0; in esp_flash_erase_region() local 628 err = chip->chip_drv->get_protected_regions(chip, &protected); in esp_flash_erase_region() 629 if (err == ESP_OK && protected != 0) { in esp_flash_erase_region() 632 if ((protected & BIT64(i)) in esp_flash_erase_region()
|
/hal_espressif-latest/components/bt/porting/ext/tinycrypt/documentation/ |
D | tinycrypt.rst | 276 * Create an authenticated, replay-protected session (HMAC-SHA256 + HMAC-PRNG);
|
/hal_espressif-latest/components/bootloader/ |
D | Kconfig.projbuild | 940 … efuse when Secure Boot is enabled. This prevents any more efuses from being read protected. 948 … NOTE: Once a BLOCK is read-protected, the application will read all zeros from that block
|