Debugging DFU ("Remote DFU operation failed")

[Lee Daniel Crocker]

I'm using SDK 8.1.0 (SoftDevice 7). I built a version of dual_bank_ble_s110. Installed both on a freshly erased pca10028. It comes up fine and sets the LED on. It's advertising as "DfuTarg".

I packaged my application into a ZIP file using pc-nrfutils. Specifically, "nrfutil dfu genpkg --application package.zip" Aeverything indicates success, and it produces a ZIP file with my .bin, a .dat, and a manifest.json. I copy that file to my tablet.

When I run nRF Toolbox on my tablet, I choose the file, then connect to DfuTarg, and press the upload button. It appears to begin. It says "Connecting", then "Starting DFU...", then "Remote DFU operation failed").

I've done this with both the pca10028 and my custom board, and with my Nexus 7 tablet and a Samsung Galaxy (I know the Nexus 7 is notorious for slow BLE).

This post:

devzone.nordicsemi.com/.../

implies that perhaps there's a newer init packet format?

If not that, I'm not sure where to begin debugging (I do have a facility for outputting debug messages from the bootloader if needed).

[Vidar Berg]

Hi, I would suggest to try with the dfu_test_app_hrm_s110.zip located here :\nRF51_SDK_8.1.0\examples\dfu\ble_dfu_send_hex\test_images_update\dfu_test_app_hrm_s110.zip" and see if you get the same result. Then try with the unmodified bootloader in the SDK and do DFU with the file above if it doesn't work. With this I guess you can narrow down the issue to the bootloader itself, or something with the central.