aviralgarg05 commented on PR #18373:
URL: https://github.com/apache/nuttx/pull/18373#issuecomment-3938704784

   Thank you for the detailed review and for outlining the expected flow.
   
   I agree with the direction. I have already switched to using `BIOC_PARTINFO` 
to resolve the selected partition offset and moved segment loading to 
`bootloader_mmap()/bootloader_munmap()` + copy from flash.
   
   Your points about robustness are valid, especially:
   - validating header fields and allowed address/size ranges before any 
handoff,
   - avoiding heap-backed handoff stack,
   - using fixed reserved DRAM/IRAM regions for stack + stub handoff so the 
path does not depend on RTC-specific placement.
   
   I will rework the handoff path accordingly so it follows the generic 
sequence you described and does not rely on heap allocation in the critical 
stage.
   
   On validation: I have verified CI/build behavior and static checks, but I 
have not yet completed full on-target slot-switch validation for this PR. I am 
setting up a dedicated validation flow for chain-boot 
(`boardctl(BOARDIOC_BOOT_IMAGE)`) and will report results (boot success/failure 
conditions, and memory-boundary cases) in the PR.
   
   Also, for point 7, I will implement the stub/argument handoff exactly in the 
reserved region model and include the final layout in the PR notes so it is 
easy to review.
   


-- 
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]

Reply via email to