DFU OTA mcumgr slot 1 stuck (bad state 6)

[86s9f5w8]

Hi, I have issue where the slot 1 image seems stuck. It can not be erased, confirmed, or swapped in the state that it is currently on. When I click erase, the error bad state 6 will show. As per the error code, the source has this definition "The device is not currently in a state to handle the request.

This firmware image is thoroughly tested in production and has been working for 2 years. The version is stable and supports the SMP server version and implementation same as in the other version on slot 1 and slot 0.

Can the slot 1 still be recovered in some way?

nrf sdk v2.4.2
nrf device manager

[Amanda Hsieh]

Hi, 

This firmware image is thoroughly tested in production and has been working for 2 years. The version is stable and supports the SMP server version and implementation same as in the other version on slot 1 and slot 0.

Is the firmware enabled for the downgrade protection? Do you update the new firmware with the same partition?

Can the slot 1 still be recovered in some way?

You can upload a new file built with the same partition of the image in slot 0. If it enables the downgrade protection, also ensure to update the version.  

86s9f5w8 said:

does confirm and test set some additional flags to check this version which would prevent it from downgrading?

No, the mcuboot would check it before swapping. 

Could you upload the mcuboot log if it's possible?

Regards,
Amada H.