This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Handover DFU connection

Hi,

Instead of initiating the DFU library in Android with an address is it possible to handover a existing GATT connection to a device already in DFU mode?

We have cases where we in our app is detecting devices in DFU mode. We haven't experienced any problems connecting to those from our app but we have experience many problems disconnecting the device and handing over address to DFU library for connection. We have moved to DFU v1.3 and have seen some commits laborating with sleep time, but still we randomly experience problems. Doing re-retries will eventually fix the problem but gives a bad user experience.

Parents
  • About handover, our app has in some case (e.g. out-of-range) connected to the device in bootloader mode. So it seems unnecessary to reset and enter bootloader, dfu mode again.

    If the device already is in bootloader mode, then the DFU library will not trigger another reset. It reads the DFU version characteristic, which determines if the device is in application mode and a reset to the bootloader is necessary. Judging by the error log it could look like the nRF device encounters an error during the DFU procedure resulting in the REMOTE DFU OPERATION FAILED error.

Reply
  • About handover, our app has in some case (e.g. out-of-range) connected to the device in bootloader mode. So it seems unnecessary to reset and enter bootloader, dfu mode again.

    If the device already is in bootloader mode, then the DFU library will not trigger another reset. It reads the DFU version characteristic, which determines if the device is in application mode and a reset to the bootloader is necessary. Judging by the error log it could look like the nRF device encounters an error during the DFU procedure resulting in the REMOTE DFU OPERATION FAILED error.

Children
No Data
Related