DFU OTA mcumgr slot 1 stuck (bad state 6)

RE: DFU OTA mcumgr slot 1 stuck (bad state 6)

Amanda Hsieh — Wed, 02 Jul 2025 18:06:37 GMT

We suspect the issue is that the bootloader will ignore an image in the secondary slot if it detects that the image doesn't correspond to any of the primary slots, leaving the image in a pending state as a result. The issue is addressed in v2.6.0. See https://docs.nordicsemi.com/bundle/ncs-2.6.0/page/nrf/releases_and_maturity/releases/release-notes-2.6.0.html

RE: DFU OTA mcumgr slot 1 stuck (bad state 6)

86s9f5w8 — Wed, 02 Jul 2025 07:04:56 GMT

[quote userid="77782" url="~/f/nordic-q-a/122469/dfu-ota-mcumgr-slot-1-stuck-bad-state-6/540887"]It sounds like a known issue that is addressed in v2.6.0. [/quote]

Can you link or describe this issue? On our side, we need to document this to know the full extent. We are currently on 2.4.2.

[quote userid="77782" url="~/f/nordic-q-a/122469/dfu-ota-mcumgr-slot-1-stuck-bad-state-6/540887"]Have you already distributed the FW update to your customers, or did you catch this issue during release testing? [/quote]

No, this FW package is not in distribution. This was noticed during DFU testing.

RE: DFU OTA mcumgr slot 1 stuck (bad state 6)

Amanda Hsieh — Mon, 30 Jun 2025 14:00:44 GMT

Hi,

It sounds like a known issue that is addressed in v2.6.0. To recover from this, you must physically attach a debugger to the device and erase the secondary partition.

[quote user="86s9f5w8"]Not at the moment because this is a production device with no access to JTAG interface.[/quote]

It won't be able to recover from this without JTAG.

Have you already distributed the FW update to your customers, or did you catch this issue during release testing?

It needs to figure out what caused the update to become stuck in the pending state in the first place to prevent it from happening again on other devices.

-Amanda H.

RE: DFU OTA mcumgr slot 1 stuck (bad state 6)

86s9f5w8 — Thu, 26 Jun 2025 06:51:14 GMT

[quote userid="77782" url="~/f/nordic-q-a/122469/dfu-ota-mcumgr-slot-1-stuck-bad-state-6/540360"]Is the firmware enabled for the downgrade protection?[/quote]

CONFIG_MCUBOOT_DOWNGRADE_PREVENTION is not set. CONFIG_BOOT_UPGRADE_ONLY is not set. We have functionality to downgrade our devices using older firmwares which is why these options are not set. It has been working for 2 years now aswell with thousands of firmware updates.

[quote userid="77782" url="~/f/nordic-q-a/122469/dfu-ota-mcumgr-slot-1-stuck-bad-state-6/540360"]Do you update the new firmware with the same partition?[/quote]

Yes, the same yml is used with the partitions specified.

[quote userid="77782" url="~/f/nordic-q-a/122469/dfu-ota-mcumgr-slot-1-stuck-bad-state-6/540360"]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. [/quote]

I have tried this solution but to no luck.

[quote userid="77782" url="~/f/nordic-q-a/122469/dfu-ota-mcumgr-slot-1-stuck-bad-state-6/540360"]Could you upload the mcuboot log if it's possible?[/quote]

Not at the moment because this is a production device with no access to JTAG interface.

RE: DFU OTA mcumgr slot 1 stuck (bad state 6)

Amanda Hsieh — Tue, 24 Jun 2025 14:10:52 GMT

Hi,

[quote user=""]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.[/quote]

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

[quote user=""]Can the slot 1 still be recovered in some way?
[/quote]

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.

[quote user="86s9f5w8"]does confirm and test set some additional flags to check this version which would prevent it from downgrading? [/quote]

No, the mcuboot would check it before swapping.

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

Regards,
Amada H.

RE: DFU OTA mcumgr slot 1 stuck (bad state 6)

86s9f5w8 — Tue, 24 Jun 2025 09:26:07 GMT

Here is additional context.

As per another nrf5340 device the same flags are applied for another image. When I send confirm command the permanent changes to true so I believe this or the reset command is the last command sent to the device before it has got stuck.

zephyr 28a3fca7da5

first one point to the img_mgmt_erase which reads the info from the specified slot so i believe this fails causing it to check the the slot in secondary slot has flash confirmed or pending.

reset is not swapping the images either so does this mean the mcuboot is not swapping the images because of version downgrade protection or something. i have downgraded the device many times before so I don't know why it is issue this time.

does confirm and test set some additional flags to check this version which would prevent it from downgrading? I know that nrf5340 does not support the mcumgr test command because of the multi core nature. Does it mean I can softbrick my device using this confirm and test command?