Laczen commented on issue #18384: URL: https://github.com/apache/nuttx/issues/18384#issuecomment-3890890296
Hi @acassis, thanks for the reply. My goal is twofold: create a decoupling between the different bootloader's in nuttx-apps and nuttx by defining a IS_BOOTLOADER config that could be accompanied by some other config values (e.g. ram_start and ram_size) that would be selected by the nuttx-apps bootloader implementation. This would allow a dedicated bootloader linker script. Second allow creating a almost baremetal bootloader that could still use definitions from nuttx kconfig (e.g. the location and size of images). In many (all?) cases taking the approach of uboot will result in duplicate drivers in the bootloader and the NuttX application. Also bootloader's might not need any nuttx based drivers as they might just verify the image (including a signature in secure boot applications) by doing memrd from the flash region. A bootloader might not include any firmware update scheme at all, like in the case of miniboot, of the update mechanism could be delegated to a different NuttX image. All bootloader's NuttX based of not could benefit from a dedicated startup mechanism. -- 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]
