Laczen commented on issue #19994:
URL: https://github.com/apache/nuttx/issues/19994#issuecomment-5597200484
Hi @hardik08tripathi-svg thanks for the comment.
> 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?
>
These config values would be used to define the NuttX image that is
generated. In the NuttX code they would be used to change part of the code
(e.g. eliminate `bootloader_init()`,...). The result would be a NuttX image
that can be placed at a specific location and started by copying ram segments
and jumping to the entry address.
> 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?
NuttX self.
>
> 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 in NuttX needs to know it to generate the correct image.
--
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]
