Found 21 other functions taking a
esp_image_metadata_t
argument:
Verify an app image. If encryption is enabled, data will be transparently decrypted. Image validation checks: - Magic byte. - Partition smaller than 16MB. - All segments & image fit in partition. - 8 bit image checksum is valid. - SHA-256 of image is valid (if image has this appended). - (Signature) if signature verification is enabled.
Load an app image without verification (available only in space of bootloader). If encryption is enabled, data will be transparently decrypted.
Verify the bootloader image.
Get metadata of app If encryption is enabled, data will be transparently decrypted.
Verify and load an app image (available only in space of bootloader). If encryption is enabled, data will be transparently decrypted. Image validation checks: - Magic byte. - Partition smaller than 16MB. - All segments & image fit in partition. - 8 bit image checksum is valid. - SHA-256 of image is valid (if image has this appended). - (Signature) if signature verification is enabled.
Enables secure boot V2 if it is not already enabled. @important If this function succeeds, secure boot V2 is permanently enabled on the chip via efuse. @important This function is intended to be called from bootloader code only. @important In case of Secure Boot V2, this will enable write protection of secure boot key on EFUSE in BLK2. .If secure boot is not yet enabled for bootloader, this will 1) enable W protection of secure boot key on EFUSE 2) enable secure boot by blowing the EFUSE_RD_ABS_DONE_1 efuse. This function does not verify secure boot of the bootloader (the ROM bootloader does this.) Will fail if efuses have been part-burned in a way that indicates secure boot should not or could not be correctly enabled.