• State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 62 subscribers
  • Views 7167 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 103750
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

nRF51-SDK 6.1.0 and DFU via Master Control Panel for Windows

Adam

Hi,

I have updated my nRF51-SDK to the latest version 6.1.0. I'm using PCA10000 dongle, nRF6310, PCA10004 and Master Control Panel for Windows. I've programmed my nRF51 device (PCA10004) using SoftDevice file "s110_nrf51822_7.0.0_softdevice.hex" and then uploaded new bootloader.hex from ...\nrf6310\device_firmware_updates\bootloader\arm_build directory and finally I have uploaded ble_app_hrs.hex sample code via DFU. Is it possible now to enter bootloader mode again and upload new sample .hex file? How to enter bootloader mode via over-the-air command (buttonless bootloader mode)?

I've also tried to upload ble_app_hrs_dfu.hex file but I was able to do this only once. During the second firmware upload (once again the same ble_app_hrs_dfu.hex file) via DFU I've got an error "Data could not be sent - failed!!!".

image description

Thx, Adam

  • 0

    Hi,

    The failure happens because Master Control Panel is not yet able to handle the swap from application to bootloader/DFU mode.

    The HRS application does not contain the full DFU implementation but only the service. Writing 'Start DFU' to the Control Point makes the application jump into Bootloader/DFU mode and from there the MCP can be used to perform the update.

    Jumping from app to bootloader/DFU is a manual step that can be done in MCP.

    Just follow the procedure in the attached screen shots. And once this is done, then do a new Service discovery and perform your update using DFU from Master Control Panel.

    note Make sure that the Heart Rate application your are using is the ble_app_hrs_dfu from the project with same name. The normal Heart Rate project does not contain the needed DFU service.

    image description

    image description

  • 0 in reply to Torsten Rasmussen

    Thanks, this solution works for me.

  • 0 in reply to Torsten Rasmussen

    great. Could you also flag the answer as correct :)

Related