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

    Are you using the dfu_test_app_hrm_s132.zip image in examples\dfu\ble_dfu_send_hex_test_images_update_nrf52? Have you tried compiling the HRM example and creating a zip file with nrfutil using the generated hex file? This way you will also be able to debug the application.

Reply
  • 0

    Are you using the dfu_test_app_hrm_s132.zip image in examples\dfu\ble_dfu_send_hex_test_images_update_nrf52? Have you tried compiling the HRM example and creating a zip file with nrfutil using the generated hex file? This way you will also be able to debug the application.

Children
No Data
Related