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

DFU failed after GATT connected.

I met this issue on some Android devices. GATT connection is disconnected before before service discovery finished. The issue is reporeted in following link.

github.com/.../35

I'd like to know the workaround of this issue.

Parents
  • @Kenta: By default the ble_app_hrm buttonless example in SDK v11 does support bond forwarding. Do you follow what implemented there to call the SVC call to send bond information to the noinit data area ? If no bonding is forwarded, the phone will terminate the connection because it can't re-encrypt with the device.

    If you want simply to keep bonding on the application, but OK to have non-bonding for DFU, then you can change the address of DFU bootloader to something else (suggest to be +1 of original address) so that no bonding will be used when doing DFU.

Reply
  • @Kenta: By default the ble_app_hrm buttonless example in SDK v11 does support bond forwarding. Do you follow what implemented there to call the SVC call to send bond information to the noinit data area ? If no bonding is forwarded, the phone will terminate the connection because it can't re-encrypt with the device.

    If you want simply to keep bonding on the application, but OK to have non-bonding for DFU, then you can change the address of DFU bootloader to something else (suggest to be +1 of original address) so that no bonding will be used when doing DFU.

Children
No Data
Related