Lines Matching refs:it
70 eventually code revision may differ from what is currently expected, it is recommended using
115 toolchain, however it is recommended to actually create a CMake toolchain file and
116 pass it through `<CMAKE_TOOLCHAIN_FILE>` variable since it may require a distinct set of
141 so that esptool tries to automatically detect it.
178 Default slot0 size is `0x100000`, but it can change as per application flash partitions.
180 For Zephyr images, `--pad-header` is not needed as it already has the padding for MCUboot
211 Version number is added to the image when signing it with `imgtool` (`-v` parameter, e.g.
297 If signing a Zephyr image, the `--pad-header` is not needed, as it already have the padding for
417 1. On startup, since it is the first boot, the ROM bootloader will not verify the bootloader image
418 (the Secure Boot bit in the eFuse is disabled) yet, so it proceeds to execute it (our MCUboot
428 1. On startup, the ROM bootloader checks the Secure Boot enable bit in the eFuse. If it is enabled,
431 Interrupt boot if it fails.
435 2. Generate the application image digest and match it with the image digest in the signature
449 and is intended for encrypting off-chip flash memory contents, so it is protected against physical
527 When enabling flash encryption, it is required to signed the image using 32-byte alignment:
574 command below is used, it will actually burn the physical eFuse.*
634 pre-encrypted data is sent for an OTA update, it would be wrongly double-encrypted when the update
637 For updating with an image encrypted on the host, flash it through serial using `esptool.py` as
672 bootloader is aware of the second image regions and can update it, however it does not load
673 neither boots it.
681 # Enables multi image, if it is not defined, its assumed
701 CPU (current CPU), it is also responsible for update both images as well. Thus multi boot will be
717 # Enables multi image, if it is not defined, its assumed
741 allows a version assigment when signing an image, it is also possible to add the version
759 Supposing that the image 0 is being signed, its version is 1.0.0 and it depends on image 1 with
766 Serial recovery mode allows management through MCUMGR (more information and how to install it:
834 __disabled__, although it is recommended for common Serial Recovery usage*
868 application memory layout, it is mandatory for the OS linker script to avoid overlaping on
870 unavailable, it is reclaimable by the OS after boot as heap.