https://devzone.nordicsemi.com/f/nordic-q-a/17991/dfu-remote-dfu-operation-failedDuring 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 compilingen-USTelligent Community 13Thu, 05 Jan 2017 09:23:00 GMThttps://devzone.nordicsemi.com/thread/69361?ContentTypeID=1Thu, 05 Jan 2017 09:23:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:31d03291-473c-4fa0-bc26-404ffb9848f1bjorn-spockeli<p>Glad to hear that you&#39;re able to perform Secure DFUs. Let me know if you run into any other issues.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/69362?ContentTypeID=1Thu, 05 Jan 2017 03:25:33 GMT137ad170-7792-4731-bb38-c0d22fbe4515:12dc15b1-450c-4816-975f-0527a530a318cody<p>Yes it works now, even with my self generated key. I dont know what was wrong though...</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/69363?ContentTypeID=1Wed, 14 Dec 2016 14:28:53 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c131dce8-a92a-4dd5-9229-c05933294df3bjorn-spockeli<p>The last response received from the DFU Control Point was: <code>60-04-05</code> (Response Code - Procedure Opcode - Error code), i.e. and Execute procedure caused an error with error code 05. Error code 5 corresponds to</p> <pre><code>The data object did not match the firmware and hardware requirements, the signature was missing, or parsing the command failed. </code></pre> <p>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?</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/69360?ContentTypeID=1Tue, 13 Dec 2016 21:06:46 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7d71af44-711a-4dbd-890c-9955bd152c79cody<p>With original secure_dfu_secure_dfu_ble_s130_pca10028_debug.hex and dfu_test_app_hrm_s130.zip I get this: <a href="http://pastebin.com/BTPmuPW8">http://pastebin.com/BTPmuPW8</a></p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/69359?ContentTypeID=1Wed, 30 Nov 2016 12:27:43 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a7455b72-c098-446d-82bb-dd0b868f2637bjorn-spockeli<p>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?</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/69357?ContentTypeID=1Mon, 28 Nov 2016 20:39:40 GMT137ad170-7792-4731-bb38-c0d22fbe4515:49c549ba-ca3c-4640-9277-1a41d17a706bcody<p>nrfutil pkg generate --debug-mode --application myapp.hex --key-file mykey.pem</p> <p>Yes, I have replaced dfu_public_key.c with the code generated from mykey.pem.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/69358?ContentTypeID=1Mon, 28 Nov 2016 09:45:36 GMT137ad170-7792-4731-bb38-c0d22fbe4515:0e4f0c99-caae-49ac-b84d-9bbac32956a1bjorn-spockeli<p>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?</p><div style="clear:both;"></div>