Dfu.status missing body containing length

Hi,
I am working on a host device firmware update. To download the firmware to the host, I have been using the “length” keyword in the body, and it was working well. However, after experimenting with outbound firmware updates or related settings, I no longer receive the body of the message when I use “dfu.status”. On the other hand, “dfu.get” still returns the host firmware as the payload. How can I resolve this issue or reset my device to restore its previous functionality?

Hi @Thareeq and sorry for the delay in getting back to you.

If the length argument is absent, that means the length is likely 0. Are you seeing anything else in the response (like a crc value for instance)?

Hi Rob - Might be related… last week, e.g. 1/7/2026 my dfu started failing ( esp32s3 ). I figured I broke it while doing some code cleanup but after going back to my know good code dfu was still not happening. Then about 1/9 things seemed to start working again. I’m still pouring through my logs and notes but what stood out was that the notehub got to ready state , which implies the code is now on the notecard.

Looking at the host mcu side esp32s3 I saw that the length was 0 and thus no download.

Notecard fw: 9.2.3.17324

Thoughts ?

1 Like

Hi @gomario2,

Are you seeing anything else in the body element of the dfu.status request?

Rob