michallenc commented on PR #3024: URL: https://github.com/apache/nuttx-apps/pull/3024#issuecomment-2720816171
> Just a question if I may as this seems to be making NXboot much more like MCUboot? What is the reasoning for improving NXboot rather than using MCUboot? I would not say this commit makes NXboot more like MCUboot, it just simplifies the previous, few months old, design and I don't think any of these changes move it closer to MCUboot, but rather opposite (no need for image's tail, one image for both primary and update). Regarding MCUboot, there are several significant problems with the project. Swapping algorithms are not usable if you have secondary partition at external NOR flash as the update process takes several minutes (!!!), swap with scratch also causes a significant flash wear. Move algorithm is not usable for external flash at all because it requires the same size of erase page (or at least required the last time I checked) for internal and external flash. I initially planned to merge the algorithm used in NXboot to MCUboot project but this was rejected by the maintainers (mostly because they didn't want to maintain another algorithm, which is a fair point). Therefore the implementation of NXboot. This commit does not change the used algorithm, but simplifies some user interface and API. Also MCUboot image is padded to partition size, so you have to upload 2 MB image (if you have 2 MB slot) even if the actual code size is much less than this. But you still want to keep the entire primary flash for the image because of future extensions. -- 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: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
