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.

  • Are you using nRFGo Studio to flash the PCA10036(which should not be used since its the Enginerring version of the nRF52832)? Also can you post the command you used in nrfutil v0.5.2. to generate the .zip file?

  • Ya, I was using nRFGO Studio. Thanks.

    This is the command I used to generate the zip file-

    nrfutil keys generate hrmkey.pem //for generating the key.

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

  • Could you resolve my one more doubt. Which is the bootloader file that I have to flash in the bootloader region? Is it the hex file given in the bootloader example??

    If so, does the hex file code contains only bootloader part or does it also have the application part in it

  • Are you sure that youre using SDK v11.0.0? SDK v11.0.0 and nrfutil v0.5.2 does not support signing keys so you must a newer version if the packet is accepted? What does nrfutil version return?

  • It seems that still the pre-installed higher versions are working. I will delete all other versions, test it and, let you know.. In the meanwhile could you give me some suggestion about bootloader.

Related