Anurag Kar 62b0d51c02 Enable secure boot only after encrypting flash ... This prevents a device from being bricked in case when both secure boot & flash encryption are enabled and encryption gets interrupted during first boot. After interruption, all partitions on the device need to be reflashed (including the bootloader). List of changes: * Secure boot key generation and bootloader digest generation logic, implemented inside function esp_secure_boot_permanently_enable(), has been pulled out into new API esp_secure_boot_generate_digest(). The enabling of R/W protection of secure boot key on EFUSE still happens inside esp_secure_boot_permanently_enable() * Now esp_secure_boot_permanently_enable() is called only after flash encryption process completes * esp_secure_boot_generate_digest() is called before flash encryption process starts		2019-04-10 18:17:58 +05:30
..
bootloader_clock.h	esp32: Fix backwards compatibility for pre-v2.1 bootloaders	2017-12-18 13:45:57 +11:00
bootloader_common.h	merge esp_flash_data_types into esp_flash_partitions	2019-03-18 08:51:55 +00:00
bootloader_random.h	bootloader_support: Move bootloader_random.h to public header directory	2018-09-03 04:39:45 +00:00
bootloader_util.h	bootloader: verify that loaded image does not overlap bootloader code	2018-10-26 12:44:10 +08:00
esp_flash_data_types.h	merge esp_flash_data_types into esp_flash_partitions	2019-03-18 08:51:55 +00:00
esp_flash_encrypt.h	Merge branch 'master' into feature/cmake	2018-09-05 10:35:04 +08:00
esp_flash_partitions.h	merge esp_flash_data_types into esp_flash_partitions	2019-03-18 08:51:55 +00:00
esp_image_format.h	esp32: Add firmware version to app	2018-12-03 16:52:04 +08:00
esp_secure_boot.h	Enable secure boot only after encrypting flash	2019-04-10 18:17:58 +05:30