Lines Matching refs:flash

124     ninja -C build/ flash
149     The output contains device information and its flash size:
152     Detected flash size: 4MB
178     Default slot0 size is `0x100000`, but it can change as per application flash partitions.
233 Espressif chips have off-chip flash memory, so to ensure a security chain along with MCUboot image
364 be able to flash other images through UART.__*
367 the use of Download Mode functions to simple flash read, write and erase operations.*
443 ## [Flash Encryption](#flash-encryption)
448 [IDF](https://docs.espressif.com/projects/esp-idf/en/latest/esp32/security/flash-encryption.html)
449 and is intended for encrypting off-chip flash memory contents, so it is protected against physical
454 for keeping the key private and safe). After the flash encryption gets enabled through eFuse
457 ### [Building bootloader with Flash Encryption](#building-bootloader-with-flash-encryption)
499 Encryption, encrypt the flash content including bootloader and image slots, burn the eFuses that no
512 be able to flash other images through UART.__*
515 use of Download Mode functions to simple flash read, write and erase operations.*
525 …he image when working with Flash Encryption](#signing-the-image-when-working-with-flash-encryption)
527 When enabling flash encryption, it is required to signed the image using 32-byte alignment:
552 2. Encrypt flash in-place including bootloader, image primary/secondary slot and scratch.
595 The **first boot** will encrypt the flash content using the host key burned in the eFuse instead
610 1. Encrypt flash in-place including bootloader, image primary/secondary slot and scratch using the
635 agent writes to the flash.
637 For updating with an image encrypted on the host, flash it through serial using `esptool.py` as
646 in the off-chip flash are protected against undesirable reading.