DFU: REMOTE DFU OPERATION FAILED

[cody]

During DFU with the nrf Connect app I get the error REMOTE DFU OPERATION FAILED. Here is the log file: http://pastebin.com/y7hFNSBq

• Using NRF5 SDK12 / NRF51 DK
• I have created the zip with nrfutil using the same key as I used when compiling the bootloader_secure example.
• bootloader is compiled in debug mode and I created the zip with debug mode parameter.

What could be wrong here?

[bjorn-spockeli]

Hi Cody, could you post the nrfutil command you used to create the zip file? You have replaced the uint8_t pk[64] in dfu_public_key.c with a new public key generated with nrfutil from a new private key?

[cody]

nrfutil pkg generate --debug-mode --application myapp.hex --key-file mykey.pem

Yes, I have replaced dfu_public_key.c with the code generated from mykey.pem.

[bjorn-spockeli]

Are you seeing this issue if you use the bootloader with the Debug public key and one of the test images in examples\dfu\ble_dfu_send_hex\test_images_update_nrf51?

[cody]

With original secure_dfu_secure_dfu_ble_s130_pca10028_debug.hex and dfu_test_app_hrm_s130.zip I get this: http://pastebin.com/BTPmuPW8

[bjorn-spockeli]

The last response received from the DFU Control Point was: 60-04-05 (Response Code - Procedure Opcode - Error code), i.e. and Execute procedure caused an error with error code 05. Error code 5 corresponds to

The data object did not match the firmware and hardware requirements, the signature was missing, or parsing the command failed.

The pre-compiled bootloader hex file and the test images should work out of the box. Do you get the same error if you compile the bootloader with the default public key, flash it to your nRF51 DK and then try to perform DFU with the dfu_test_app_hrm_s130.zip test image?