Is there a size limit for the app_update.bin using MCUboot?

Hello,
no I am not using LittleFS.
I have used the proposed MCUboot provided in the link, now I am sometimes successful with the update, and some other times timeout occurs.
Note that both cases occur with the same application firmware files, and same MCUboot version.

Regards

Yes I can confirm,

Actually the timeout occurs while transferring the file most of the time.

Hello
I tried the -r3 option: retry 3 times as follows
newtmgr -r3 -c serial image upload build/zephyr/app_update.bin

and this works with a higher probability than with no -r option, I am thinking that maybe the high speed and cable combination is causing issues.
Can I use lower baud rates? I tried to change to baud=115200, but this did not work: the download was not even starting.

maybe some info about my setup would be helpful.
I am on a mac, with USB C connectors, so I have a USB hub(?) in order to have a USB A connector, than use USB A to USB mini cable.
I tried changing the cable but this did not help.

Hello Jared,

The image size will be about 700Kbytes eventually.
The -r3 option seem to be acceptable so far.

I will later on try a better usb cable to see if this helps or not.

Cheers

Hello,

The code is not yet final and we are testing different parts separately.
I will keep you posted.
What is the max file size MCUboot can handle? is it related to the flash size and the partitions of slot0 and slot1?
or are there other limitations ?

By the way I tried with bootloader V2 (supplied from your website) on another board and newtmgr did not timeout at all even without the -r3 option.
so it looks like something board specific on the connection level of the USB …