Modifying the "ble_app_hrs_dfu" for Eval. Kit

[azdem]

Hi BLE fellows,

Following the steps explained here, I have tried to integrate the OTA DFU feature & bootloader from the latest SDK to my application and tested it on my own nRF51822-based hardware, it did not work. To eliminate the uncertainty about the hardware, I did the same with the Eval. Kit and I still encounter the same problem. Until point 8 (Verify that the device is now advertising as 'DfuTarg'), everything works as expected, as the answer of this thread also explains. The problem: I can never see the nRF advertising as "DfuTarg".

What I have changed to adapt the example "ble_app_hrs_dfu" to Eval. Kit, is basically just the LED and Button mapping.

Warm Regards.

[Stefan Birnir Sverrisson]

Hi

If you flash S110 v7.0.0 and the bootloader from SDK 6.1.0 (from \Nordic\nrf51822_v6_1_0\Board\nrf6310\device_firmware_updates\bootloader), then it should advertise as DfuTarg and you should see it with that name in e.g. Master Control Panel. When the device is in DFU mode (advertising with DfuTarg, then you can upload the ble_app_hrs_dfu.hex application to the device via the Master Control Panel by:

• Select the device (DfuTarg)
• Perform Service Discovery
• Press DFU button and browse for the ble_app_hrs_dfu.hex file
• Press Program

[azdem]

Hi Stefan, thanks for your reply. I want to use the latest feature, that eliminates push-button requirement. The SDK documentation linked above is either not clear enough or somehow broken. I can not get it working. Additionally, MCP running on Win 8 64 bit looks also not stable enough: DFU progress bar does not pop up every time, although the console says that DFU has started.