DFU failed after GATT connected.

RE: DFU failed after GATT connected.

Hung Bui — Fri, 30 Jun 2017 08:21:58 GMT

Hi Kenta, Sorry for late response. Could you try this: devzone.nordicsemi.com/.../ ?

RE: DFU failed after GATT connected.

Kenta Harada — Wed, 28 Jun 2017 10:04:22 GMT

Thank you for your comment. We don't currently use bond sharing feature. if that is the cause of this issue, we want to use it !

But Bjørn Spockeli said that SDK v11 doesn't support bond sharing which uses peer manager in following question.(We use peer manager, don't use bond manager.)

devzone.nordicsemi.com/.../

Are there any workaround ?

RE: DFU failed after GATT connected.

Hung Bui — Tue, 27 Jun 2017 11:14:25 GMT

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

RE: DFU failed after GATT connected.

Kenta Harada — Tue, 27 Jun 2017 06:55:28 GMT

Thank you for your comment. I removed the pairing/bonding process from Android application an nRF52 FW. DFU finished successfully. But we need encryption, How should we do ? Use AES encryption without pairing, is that good idea ?

RE: DFU failed after GATT connected.

Hung Bui — Thu, 22 Jun 2017 12:15:27 GMT

What do you mean by "nRF sniffer doesn't work well after device turned to bootloader mode" ? If you have trouble because the device change the address, you simply test with just the bootloader and no application, then the device will always be in bootloader.

You do have issue doing DFU with nRFToolbox , but don't with NRFConnect correct ?

RE: DFU failed after GATT connected.

Kenta Harada — Thu, 22 Jun 2017 10:48:33 GMT

I tried to find the difference between nRF toolbox source code and ours. but I could not find the difference. nRF sniffer doesn't work well after device turned to bootloader mode. Do you have any other advice?

RE: DFU failed after GATT connected.

Hung Bui — Wed, 21 Jun 2017 15:41:58 GMT

They are very similar as they both use the DFU library to do the task.

Have you tried to repeat the test several times just to make sure nRFConnect always work ?

A sniffer trace would be useful to see why a disconnection happened.

RE: DFU failed after GATT connected.

Kenta Harada — Wed, 21 Jun 2017 03:20:21 GMT

I tried with following conditions.

Android App nRF Connect for Mobile 4.11.1 nRF Toolbox for BLE 2.4.0

Android Device F-02H(Fujitsu) Android Version : 5.1.1

BLE Device nRF52832, SDK 11.0.0, SoftDevice S132 v2.0.1

Result nRF Connect : DFU Finished successfully

nRF Toolbox : DFU Failed(Showed "DFU Process failed" in Notification message)

DFU finished successfully on nRF Connect! What's the differences between Connect and Toolbox??

I would like to check souce codes of nRF Connect. is that possible ?

RE: DFU failed after GATT connected.

Hung Bui — Tue, 20 Jun 2017 13:00:11 GMT

Please let me know do you have the issue with nRFConnect, just do a connection and don't do DFU. We need to check if it's the issue with DFU library or it's the issue with Android OS. How often do you see disconnection ?

RE: DFU failed after GATT connected.

Kenta Harada — Tue, 20 Jun 2017 01:15:01 GMT

Thank you for your comment.

I don't use nRF Connect, use our original Android application with Android DFU Library. DFU Library waits some seconds before GATT connection but it's not enough on some Android devices. So I added a 1.5 sec delay before calling DfuServiceInitiator.start() (This is because we don't want to customize DFU Library). But disconnection happens on some Android devices such as KYOCERA, SHARP and FUJITSU.

RE: DFU failed after GATT connected.

Hung Bui — Mon, 19 Jun 2017 17:30:15 GMT

Hi Kenta,

How often do you have the issue ? Do you have disconnection when you test with just nRFConnect (no DFU ) ?

Have you tried to do what Philips suggest by adding a delay ?