Jamie
Jamie
There is a way of knowing this before beginning an upload if you use MCUboot's data sharing, one of the values provided there is the maximum application size, so you...
~~Fix (for zephyr itself): https://github.com/zephyrproject-rtos/zephyr/pull/64586~~ can see you are seeing a different issue
> > ~Fix (for zephyr itself): [zephyrproject-rtos/zephyr#64586](https://github.com/zephyrproject-rtos/zephyr/pull/64586)~ can see you are seeing a different issue > > True, but we might still be able to use this to prevent it...
> Let's say the image slot is 896 KiB with flash sectors of 128KiB. I observe that if the signed binary is larger than 768KiB, after upload this last sector...
That Kconfig is the maximum number of sectors that will be searched and are supported (i.e. controls how large the swap field size will be), the size is limited by...
> The image in a given slot will be loaded (if it has a higher version than the other slot) without the need for it to be marked for an...
> I see, but the installation of the image, in my opinion, should be controlled via the pending/confirmed flags, otherwise, a reset alone would cause the new image to be...
> > We should not be adding a third image slot without a very good justification, original comment mentions swap using scratch, so just use swap using move instead? >...