• State Verified Answer
  • Locked Locked
  • Replies 15 replies
  • Subscribers 63 subscribers
  • Views 5889 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

    The 32 kHz synthesized source is not tester or recommended with the S110 stack. Use NRF_CLOCK_LFCLKSRC_RC_250_PPM_250MS_CALIBRATION instead and that should enable you to use the bootloader and DFU.

  • 0 in reply to Asbjørn

    Also, a quick heads up for you Nordic folks: this thread, and this one both recommend setting the clock source to NRF_CLOCK_LFCLKSRC_SYNTH_250_PPM as a fix for the custom board issue (that's where I got the idea to do so in the first place). If that's changed with v7, you might want to make sure that the forums acknowledge this.

Reply
  • 0 in reply to Asbjørn

    Also, a quick heads up for you Nordic folks: this thread, and this one both recommend setting the clock source to NRF_CLOCK_LFCLKSRC_SYNTH_250_PPM as a fix for the custom board issue (that's where I got the idea to do so in the first place). If that's changed with v7, you might want to make sure that the forums acknowledge this.

Children
No Data
Related