DFU fails with 0x05 response to Execute command after writing Init data.

[BobS]

I've successfully written DFU client code on a Debian host using Bluez a few years ago.  We are modifying our system to use a 52840 as a BLE client.  I'm able to write commands to the control point handle until after writing the Init data to the packet handle. 

The 0x05 error code says: "Data object does not match the firmware and hardware requirements, the signature is wrong, or parsing the command failed."

BTW, we cannot modify the target device firmware to use MCUboot.  I've included sniffer captures for the same file for comparison.  Thanks for any ideas.

Works_Bluez_version.pcapngBT840_Exe_fails_with_0x05.pcapng

[Vidar Berg]

Hello,

Could you please attempt to upload the same DFU package using nRF Connect on either Android or iOS? This should help us narrow down the problem. If the same error occurs with the mobile app, it may indicate that the problem lies with the init command rather than your DFU client.

Thanks,

Vidar

[BobS]

I found this bug.  We are using the same Debian host to process the zip file and transfer the Init and binary files over UART to the BT840 module.  I was printing out the last 10 bytes of each to verify the data.  This caused me to miss that the first 8 bytes being sent were wrong.  I was freeing memory before I sent it in my Debian code. 

So now I'm getting past that part but get a seg fault writing the binary firmware.  Maybe another ticket.  Thanks.