• State Verified Answer
  • Locked Locked
  • Replies 15 replies
  • Subscribers 63 subscribers
  • Views 5922 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 103905
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

Issues with DFU for SD v7

Anne

Hey!

I'm testing out the new SoftDevice and am trying to update firmware OTA but thus far have not been able to do so. I've tried from the Master Control Panel android app (v 2.0.2). I can discover and connect to DfuTarg no problem but when I try to actually update the firmware it gets to 0%, hangs there for maybe 5 seconds, and then disconnects. I also tried from the PC version of Master Control Panel (v3.7.0) and the same thing happened. It connected, discovered, started DFU, and hung at zero.

The SoftDevice is version 7.0.0 flashed from nRFgo Studio (v 1.17.0.3211), the bootloader is the version from SDK v6.1.0, and the firmware I'm trying to upload is the heart rate sensor app from the same SDK. This app works fine when flashed via nRFgo Studio.

I'm using a custom board and so have modified SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_XTAL_20_PPM, true) in ble_stack_init() to be SOFTDEVICE_HANDLER_INIT(NRF_CLOCK_LFCLKSRC_SYNTH_250_PPM, false).

Thanks for your help ^^

Parents
  • 0

    Hi

    I've found the same error. My configuration is as follows:

    • SDK 6.1.0.0 using ble_app_hrs_dfu project without any change.
    • s110_nrf51822_7.0.0_softdevice.hex
    • nRFgoStudio 1.17.0
    • MCP 3.6.0

    I have used the following documentation:

    devzone.nordicsemi.com/.../a00076.html

    On the step 6, I click back but I can only see the device advertising again as 'Nordic_HRM'. I couldn't find the string "DfuTarg" searching files on the current project.

    Debugging I could see that the code is calling the bootloader_start function.

    Any other suggestion to test on my side?

    I have also tried the dfu with the nRF Toolbox from a nexus 4 and iphone 5 without any luck.

    Thanks.

    Screen Captures

    Before flashing the bootloader After flashing the bootloader

  • 0 in reply to Ignacio Lopez

    I'm not sure why you don't see it as advertising as a DFUTarg after you followed the steps and push back as stated in step 6. I would do a quick test with the bootloader example in the SDK just to make sure you are doing the app/MCP correct. Compile and flash the example from the SDK here(placed in my tree structure): C:\Nordic Semiconductor\nRF51 SDK\nrf51_sdk_v6_1_0_b2ec2e6\nrf51822\Board\nrf6310\device_firmware_updates\bootloader

    Erase the chip, program softdevice and this example and you should by default see the DFUTarg advertising. Make sure you can upload a new FW from this first of all.

Reply
  • 0 in reply to Ignacio Lopez

    I'm not sure why you don't see it as advertising as a DFUTarg after you followed the steps and push back as stated in step 6. I would do a quick test with the bootloader example in the SDK just to make sure you are doing the app/MCP correct. Compile and flash the example from the SDK here(placed in my tree structure): C:\Nordic Semiconductor\nRF51 SDK\nrf51_sdk_v6_1_0_b2ec2e6\nrf51822\Board\nrf6310\device_firmware_updates\bootloader

    Erase the chip, program softdevice and this example and you should by default see the DFUTarg advertising. Make sure you can upload a new FW from this first of all.

Children
No Data
Related