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

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.

0 Vincent over 6 years ago

Hi, Would you mind move your project to SDK12.3. Because I just try the DFU function done nRF51422 in SDK12.3
Cancel
Vote Up 0 Vote Down

Cancel
0 bjorn-spockeli over 6 years ago

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.
Cancel
Vote Up 0 Vote Down

Cancel
0 arjun over 6 years ago

@Bjorn Yes,I am using the image files in the sdk folder you mentioned. I will try and let you know.

However I tried the same with another application, generated zip file using nrfutil. But I am not able to upload the zip file. While uploading , it goes till "Starting DFU" and then gets disconnected.Could you give me some suggestions.
Cancel
Vote Up 0 Vote Down

Cancel
0 arjun over 6 years ago

@Vincent Is it working fine for you in SDK12.3
Cancel
Vote Up 0 Vote Down

Cancel
0 Vincent over 6 years ago

Yes.....very well. and I believe you just miss some step. that's all
Cancel
Vote Up 0 Vote Down

Cancel

Device not connecting after DFU OTA

core_v2_widget.Hide()