MCUMGR is stuck after a flash of a big image

[saoron]

Hi, 

If the image we falshed using mcumgr is 90% of the allowed image size mcumgr flashes the unit without a problem, If the image is 98% the proccess seems stuck.

This is the image list:

root@tina:~# mcumgr --conntype serial --connstring /dev/ttyS4,baud=115200 image 
 list
Images:
 image=0 slot=0
    version: 0.0.0
    bootable: true
    flags: active confirmed
    hash: feb4706e9a332137daf3016bd2c810885ac4139d67e2242b0f2d4cceda1c7b0e
 image=0 slot=1
    version: 0.0.0
    bootable: true
    flags: pending permanent
    hash: 2c8963914df5985f7141b5c1525ac8f1ebefd332d12e4dda9d0ea770634fc473
Split status: N/A (0)

image erase is not working as well and will return Error: 6.

How can we remove the 2nd image and flash the unit again?

Your help would be greatly appreciated, 

[Vidar Berg]

Hello,

Please let me know which version of the SDK you are using so I can attempt to reproduce this.

Thanks,

Vidar

[saoron]

v2.0.2

[saoron]

Any ideas Vidar Berg ?

[Vidar Berg]

The max. image size is limited by the slot size and also the image trailer size as noted in the MCUboot documentation here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.5.0/mcuboot/design.html#image-slots. Ideally, there should have been a static assert to trigger a build error if the image is too big to fit into the allocated slot partition. 

[saoron]

Thanks for your reply, Anything we can do to fix this remotely?