• State Not Answered
  • Locked Locked
  • Replies 34 replies
  • Subscribers 63 subscribers
  • Views 5679 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

    I tried with the nrfutil v 0.5.2. I am still facing the same problem.

    Meanwhile I have one more doubt.When I am flashing the softdevice and bootloader from 10040 board, I am having no problem, whereas when I am doing the same with the 10036 board, after flashing the softdevice, I am unable to flash bootloader code.It gives the following error, the hex file has data in softdevice region.

Reply
  • 0

    I tried with the nrfutil v 0.5.2. I am still facing the same problem.

    Meanwhile I have one more doubt.When I am flashing the softdevice and bootloader from 10040 board, I am having no problem, whereas when I am doing the same with the 10036 board, after flashing the softdevice, I am unable to flash bootloader code.It gives the following error, the hex file has data in softdevice region.

Children
No Data
Related