gustavonihei commented on a change in pull request #4880:
URL: https://github.com/apache/incubator-nuttx/pull/4880#discussion_r756334574
##########
File path: boards/arm/samv7/same70-xplained/Kconfig
##########
@@ -90,4 +90,38 @@ config SAME70XPLAINED_HSMCI0_AUTOMOUNT_UDELAY
endif # SAME70XPLAINED_HSMCI0_AUTOMOUNT
+menuconfig SAME70XPLAINED_APP_FORMAT_MCUBOOT
+ bool "MCUboot-bootable format"
+ default n || MCUBOOT_BOOTLOADER
+ depends on BOOT_MCUBOOT
+ ---help---
+ The SAMV7 port of MCUboot supports the loading of unsegmented
firmware
+ images.
Review comment:
"Multiple image boot" is unrelated to the segmentation we are discussing
here. The **segments** relate to the data and code sections from a given
executable firmware image. Think about the output sections of an ELF file (but
not exactly that).
The ESP32 image format organizes these sections (segments) differently,
optimized for the chip's memory organization:
https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/system/app_image_format.html
So, although it might not be unique to ESP32, that's the segmentation I was
referring to.
The MCUboot's "Multiple image boot" is literally support for multiple
firmware images, but **per image slot**. So this enables the device to support
the execution of a different application firmware image, e.g. a recovery
firmware image as the second image on the slot.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
