Laczen commented on issue #19994: URL: https://github.com/apache/nuttx/issues/19994#issuecomment-5453630046
> > > why not add them to apps/boot (e.g. espboot, simpleboot), which parse the specific image format to load the code to ram or find the entry point, and boardctl into kernel for jumping to it, like uboot/lk. And then you can add any option you want in the apps/boot/xxxx/Kconfig. > > > > > > I am not quite sure how this could be done. The main change is to allow setting the location of the image to a different location from what is expected by the rom bootloader, > > SIMPLE_BOOT_SBLI and SIMPLE_BOOT_SBLI_OFFSET is used only by image creation tool? whether this value is fixed by chip or board? At the moment when SIMPLE_BOOT is selected it is using `CONFIG_BOOTLOADER_OFFSET_IN_FLASH` (defined in one of the device specific espressif include files, varies by device) in code. Next to this it is using this as a switch to create an image that can be processed by the rom bootloader (hiding the rom segments). To be able to override CONFIG_BOOTLOADER_OFFSET_IN_FLASH the bool SIMPLE_BOOT_SBLI is used and CONFIG_BOOTLOADER_OFFSET_IN_FLASH is replaced by SIMPLE_BOOT_SBLI_OFFSET. > > > is the address is this location is set in code as part of the mmu mapping. > > the mapping is set by rom bootloader or nuttx self? By NuttX. > > > The value is not a Kconfig value, but instead set by non NuttX include files (it is not a part of .config). > > so, the code in NuttX doesn't need to know this value. The code does need to know the value, it is just "hidden" from the NuttX configuration. -- 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]
