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

    Did you create your own image or did you use one of the test images in the SDK, if so which image did you use? How did you perferom the DFU, with nrfutil or with one of our mobile apps? Are you able to start a debug session in the bootloader and see if you reach the

    nrf_bootloader_app_start(MAIN_APPLICATION_START_ADDR);

    statment in nrf_dfu_init () in nrf_dfu.c?

Reply
  • 0

    Did you create your own image or did you use one of the test images in the SDK, if so which image did you use? How did you perferom the DFU, with nrfutil or with one of our mobile apps? Are you able to start a debug session in the bootloader and see if you reach the

    nrf_bootloader_app_start(MAIN_APPLICATION_START_ADDR);

    statment in nrf_dfu_init () in nrf_dfu.c?

Children
No Data
Related
Terms of service