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

  • 0

    @Bjorn I tried as you suggested. I compiled the HRM example and created a zip file using the generated hex file. But I am not ble to upload the zip file.

    I am facing the same problem which I mentioned in the previous comment.While uploading , it goes till "Starting DFU" and then gets disconnected or hangs with the status showing "Disconnecting".

  • 0

    Which nrfutil version did you use to generate the .zip? Could you post the nrfutil command that you used to generate the .zip ?

  • 0

    I am using nrfutil v2.3.0.

    the command I used i following

    nrfutil pkg generate --hw-version 52 --sd-req 0x81 --application-version 1 --application HRM.hex --key-file hrmkey.pem hrm_dfu.zip

  • 0

    If you're using SDK v11.0.0 then you need to use nrfutil v0.5.2 or older, which can be downloaded from here. All newer versions are for the new Secure DFU only.

  • 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.

Related