• State Not Answered
  • Locked Locked
  • Replies 34 replies
  • Subscribers 73 subscribers
  • Views 7066 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 125259
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

Device not connecting after DFU OTA

arjun

Hi,

I am running the BLE DFU example. I am able to perform the DFU OTA implementation successfully. The problem I am facing is that, once the application has been updated successfully, the device gets disconnected and starts advertising with new name. But when I am trying to connect to it, its disconnecting again and again.

I am using the hrm zip file for updating. The device after updating advertises as Nordic_HRM.But I am not able to connect to it.

Parents
  • 0

    ya, I was able to perform DFU with test images from sdk11.

    The nrfutil command I used is as follows- nrfutil dfu genpkg --application hrm.hex --application-version 1 --dev-revision 0xffff --dev-type 0xffff --dfu-ver 0.5 --sd-req 0x81 --key-file hrmkey.pem hrm_dfu.zip

Reply
  • 0

    ya, I was able to perform DFU with test images from sdk11.

    The nrfutil command I used is as follows- nrfutil dfu genpkg --application hrm.hex --application-version 1 --dev-revision 0xffff --dev-type 0xffff --dfu-ver 0.5 --sd-req 0x81 --key-file hrmkey.pem hrm_dfu.zip

Children
No Data
Related
Terms of service