jturnsek commented on code in PR #8684:
URL: https://github.com/apache/nuttx/pull/8684#discussion_r1122206501
##########
arch/arm/src/imxrt/Kconfig:
##########
@@ -151,6 +151,47 @@ config ARCH_FAMILY_IMXRT106x
select ARMV7M_HAVE_DTCM
select IMXRT_HIGHSPEED_GPIO
+config IMXRT_HAVE_OTA_PARTITION
+ bool
+ default n
+
+config IMXRT_PROGMEM
+ bool "Flash progmem support"
+ default n
+ select ARCH_HAVE_PROGMEM
+ ---help---
+ Add progmem support, start block and end block options are
provided to
+ obtain an uniform flash memory mapping.
+
+menu "Application Image Configuration"
+choice
+ prompt "Application Image Format"
+ default IMXRT_APP_FORMAT_LEGACY
+ ---help---
+ Depending on the chosen 2nd stage bootloader, the application
may
+ be required to be perform a specific startup routine.
Furthermore,
+ the image binary must be formatted according to the definition
from
+ the 2nd stage bootloader.
Review Comment:
Actually Application Image Format choice has influence on flash linker
script, where IMXRT_APP_FORMAT_MCUBOOT instructs linker to make changes in the
linking process for the loader and app respectively. In case
IMXRT_APP_FORMAT_MCUBOOT is missing, thus IMXRT_APP_FORMAT_LEGACY is choosen,
linker calls ordinary flash script for linking. I would say
IMXRT_APP_FORMAT_LEGACY should be included, although does not have explicit
usage.
--
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]
