What is the expected success rate of a DFU update?

RE: What is the expected success rate of a DFU update?

Sigurd — Wed, 24 Aug 2022 12:56:24 GMT

Could you get a ellisys sniffer or nRF sniffer trace of the behavior?

https://www.nordicsemi.com/Products/Development-tools/nrf-sniffer-for-bluetooth-le

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_sniffer_ble%2FUG%2Fsniffer_ble%2Fintro.html

RE: What is the expected success rate of a DFU update?

zippert — Tue, 23 Aug 2022 11:28:14 GMT

After updating these values, connection seem more stable, but DFU update fails almost immediately after start. :(

RE: What is the expected success rate of a DFU update?

Sigurd — Tue, 23 Aug 2022 08:47:41 GMT

[quote user="FredrikL"]

If I changes setting for:
NRF_SDH_CLOCK_LF_SRC to NRF_CLOCK_LF_SRC_SYNTH

I end up in a hanged application at:

err_code = nrf_sdh_enable_request();

[/quote]

Set NRF_SDH_CLOCK_LF_RC_CTIV to 0 when doing this test with NRF_CLOCK_LF_SRC_SYNTH

RE: What is the expected success rate of a DFU update?

FredrikL — Mon, 22 Aug 2022 14:39:57 GMT

Hi Sigurd,

Thank you for your response.

We are indeed using an external crystal.

Setting in bootloader are:
#define NRF_SDH_CLOCK_LF_SRC 0
#define NRF_SDH_CLOCK_LF_RC_CTIV 4
#define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV 0
#define NRF_SDH_CLOCK_LF_ACCURACY 1

Settings in application are:

#define NRF_SDH_CLOCK_LF_SRC 0

#define NRF_SDH_CLOCK_LF_RC_CTIV 4

#define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV 0

#define NRF_SDH_CLOCK_LF_ACCURACY 1

If I changes setting for:
NRF_SDH_CLOCK_LF_SRC to NRF_CLOCK_LF_SRC_SYNTH

I end up in a hanged application at:

err_code = nrf_sdh_enable_request();

RE: What is the expected success rate of a DFU update?

Sigurd — Fri, 19 Aug 2022 15:14:01 GMT

Hi,

[quote user="FredrikL"]We are using a Laird module BL652-SA with nRF52832.[/quote]

Do you have a external LF crystal on your board?
In sdk_config.h, what are these currently configured to?

NRF_SDH_CLOCK_LF_SRC
NRF_SDH_CLOCK_LF_RC_CTIV
NRF_SDH_CLOCK_LF_RC_TEMP_CTIV
NRF_SDH_CLOCK_LF_ACCURACY

Check both application project sdk_config.h and the bootloader sdk_config.h

As an test, could you try to set NRF_SDH_CLOCK_LF_ACCURACY to 1 (i.e. 500 ppm) ?

If it's already set to 1 (500ppm), try set NRF_SDH_CLOCK_LF_SRC to 2(NRF_CLOCK_LF_SRC_SYNTH) as well.

RE: What is the expected success rate of a DFU update?

FredrikL — Fri, 19 Aug 2022 06:29:00 GMT

Worth mentioning to the "GATT ERROR" is that when this error occurs we cannot connect ever again.

But if the Bluetooth is turned off on the phone and then turned on again the device can connect again.

RE: What is the expected success rate of a DFU update?

zippert — Thu, 18 Aug 2022 11:42:38 GMT

Thanks, this solved the issue with the device being unpaired. A bit non-intuitive naming imho, I interpreted "restore bond" as in "after update is complete, restore its previous bond", but I understand now.

Strange thing is that setting this to true has been in the code for 1,5 years, and it wasn't until this latest update that this (unwanted) behaviour appeared...?

I will send it to test and see what happens.

The main issue with "GATT ERROR" and connection failure still remains, though.

RE: What is the expected success rate of a DFU update?

Aleksander Nowakowski — Thu, 18 Aug 2022 11:30:31 GMT

Also, if you're using Legacy DFU you may remove "setPrepareObjectDelay" and "setUnsafe...Enabled", as unused.

RE: What is the expected success rate of a DFU update?

Aleksander Nowakowski — Thu, 18 Aug 2022 11:29:20 GMT

set setRestoreBond to false - otherwise it will bond again, instead of reusing the same bond information: github.com/.../DfuServiceInitiator.java

RE: What is the expected success rate of a DFU update?

zippert — Thu, 18 Aug 2022 11:07:59 GMT

Yes, those attributes have always been present:

RE: What is the expected success rate of a DFU update?

Aleksander Nowakowski — Thu, 18 Aug 2022 11:03:06 GMT

[quote userid="92620" url="~/f/nordic-q-a/90943/what-is-the-expected-success-rate-of-a-dfu-update/382156"] the paring information on the phone is always removed after completed DFU upgrade. The nRF chip is upgraded with new firmware and has still the bonding information.[/quote]

Have you tried this: https://github.com/NordicSemiconductor/Android-DFU-Library/blob/913dbc128095b211e85e476fb10d497379e9be33/lib_dfu/src/main/java/no/nordicsemi/android/dfu/DfuServiceInitiator.java#L175 and setting to true?

By default it will remove bond info, as this feature was added later in the SDK.

RE: What is the expected success rate of a DFU update?

FredrikL — Thu, 18 Aug 2022 07:47:00 GMT

Hi,

Hijacking this thread to add information about the issue, I'm working close with the thread creator on the embedded side.

We are using a Laird module BL652-SA with nRF52832.

Most phones can handle the DFU upgrade flow from Android. We can re-create the issue right now on a Google pixel 4. But the issue is reproducible on several other brands eg. Samsung Galaxy S10.
The issue does not always appear. The upgrade flow can sometimes fail sometimes succeed. if the DFU upgrade is successful the paring information on the phone is always removed after completed DFU upgrade. The nRF chip is upgraded with new firmware and has still the bonding information.
So the issue seems to be from the Phone application side.
If we are using nRF Connect debug application and trying DFU upgrade from the debug application the Upgrade always works as expected.

The issue never appears on iPhone. Our iPhone application is not using the NRF DFU SDK but our Android application is using the nRF DFU SDK. We are using the DFU buttonless feature to set the device to DFU mode.

If I scan for Bluetooth devices while upgrading i can see the unit changing from our normal advertising name ABCD_[s/n] to HDFU_[s/n] which is set by our bootloader when we set it to DFU upgrade state. So the device is restarted and set as expected.

To mention is:
I can find two devices with the same MAC when I scan. One with the name (unknown) and one with our desired name.
The same happens when the device is in DFU mode.

We set the device name with: sd_ble_gap_device_name_set

I can't figure out where the (unknown) UUID is coming from. I have an idea that the DFU gets confused and mixup the two when trying to upgrade, but its a long shot.

Relating the thread issue to my text.

The gatt error seems to come after upgrading from our application on Android because the paring information has been lost.

Do you have any ideas how to proceed with the debugging or any known bugs from the nRF DFU SDK or if our (unknown) UUID can affect in any way.

Thanks for your help

RE: What is the expected success rate of a DFU update?

zippert — Thu, 18 Aug 2022 07:39:43 GMT

Sigurd The phone was a Pixel 4a, and this is the device that has been "most reliable" among our testing devices to reproduce the issues. Other devices seem to work every time, some fail intermittently.

RE: What is the expected success rate of a DFU update?

Sigurd — Wed, 17 Aug 2022 11:14:17 GMT

Hi,

What phone did you use? Do you see the same if you test with other phones?

RE: What is the expected success rate of a DFU update?

zippert — Mon, 15 Aug 2022 14:24:56 GMT

As far as I can tell, the logic is implemented more or less verbatim of how it is described here:
github.com/.../documentation

RE: What is the expected success rate of a DFU update?

zippert — Mon, 15 Aug 2022 14:23:45 GMT

I managed to recreate the issue myself (not sure if this issue is identical to those "in the wild"):

08-15 16:20:01.171 23947 24112 D BluetoothGatt: connect() - device: F6:42:C9:C2:D1:1D, auto: false
08-15 16:20:01.171 23947 24112 D BluetoothGatt: registerApp()
08-15 16:20:01.171 23947 24112 D BluetoothGatt: registerApp() - UUID=a605406e-4cd7-4fc7-93a1-6a259ba00ed6
08-15 16:20:01.176  2621  3184 I bluetooth: packages/modules/Bluetooth/system/stack/gatt/gatt_api.cc:1020 GATT_Register: Allocated name:GattClient uuid:e7f2cb30-e8a6-db97-55d1-5642cf64085a gatt_if:6 eatt_support:0
08-15 16:20:01.176 23947 23961 D BluetoothGatt: onClientRegistered() - status=0 clientIf=6
08-15 16:20:01.181  2621  2755 I bt_btif_gattc: packages/modules/Bluetooth/system/btif/src/btif_gatt_client.cc:365 btif_gattc_open_impl: Transport=2, device type=2, address type =1, phy=3
08-15 16:20:01.182  2621  3184 I bt_stack: [INFO:gatt_attr.cc(882)] gatt_sr_init_cl_status: bda=f6:42:c9:c2:d1:1d, cl_supp_feat=0000, aware=1
08-15 16:20:01.182  2621  3184 I bluetooth: packages/modules/Bluetooth/system/stack/gatt/gatt_main.cc:346 gatt_update_app_use_link_flag: check_acl_link is false, no need to check
08-15 16:20:01.190  2621  2995 I bluetooth: packages/modules/Bluetooth/system/gd/hci/le_address_manager.cc:514 OnCommandComplete: Received command complete with op_code LE_ADD_DEVICE_TO_FILTER_ACCEPT_LIST
08-15 16:20:01.949  2621  3184 I bluetooth: packages/modules/Bluetooth/system/stack/gatt/connection_manager.cc:215 on_connection_complete: Le connection completed to device:f6:42:c9:c2:d1:1d
08-15 16:20:01.949  2621  3184 I bluetooth: packages/modules/Bluetooth/system/stack/gatt/connection_manager.cc:215 on_connection_complete: Le connection completed to device:f6:42:c9:c2:d1:1d
08-15 16:20:01.949  2621  3184 I bt_btm_ble: packages/modules/Bluetooth/system/stack/btm/btm_ble.cc:1720 btm_ble_connected: Updating device record timestamp for existing ble connection
08-15 16:20:01.968  2621  3184 E bt_btm  : packages/modules/Bluetooth/system/main/bte_logmsg.cc:191 LogMsg: no pending resolving list operation
08-15 16:20:01.970  2621  2995 I bluetooth: packages/modules/Bluetooth/system/gd/hci/le_address_manager.cc:514 OnCommandComplete: Received command complete with op_code LE_REMOVE_DEVICE_FROM_FILTER_ACCEPT_LIST
08-15 16:20:02.195  2621  3184 E bt_btm_ble: packages/modules/Bluetooth/system/stack/btm/btm_ble_gap.cc:3150 btm_ble_read_remote_features_complete: Failed to read remote features status:Connection Failed Establishment
08-15 16:20:02.195  2621  3184 E bluetooth: packages/modules/Bluetooth/system/stack/btm/btm_sco.cc:950 btm_sco_on_disconnected: Unable to find sco connection
08-15 16:20:02.195  2621  3184 I btm_acl : packages/modules/Bluetooth/system/stack/acl/btm_acl.cc:2569 btm_acl_iso_disconnected: ISO disconnection from GD, handle: 0x10, reason: 0x3e
08-15 16:20:02.196  2621  3184 I bluetooth: packages/modules/Bluetooth/system/stack/gap/gap_ble.cc:303 client_connect_cback: No active GAP service found for peer:xx:xx:xx:xx:d1:1d callback:Disconnected
08-15 16:20:02.196  2621  3184 I bt_bta_gattc: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_act.cc:1212 bta_gattc_conn_cback: Disconnected att_id:3 addr:xx:xx:xx:xx:d1:1d, transport:BT_TRANSPORT_LE reason:GATT_CONN_FAILED_ESTABLISHMENT
08-15 16:20:02.196  2621  3184 I bt_bta_gattc: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_act.cc:1212 bta_gattc_conn_cback: Disconnected att_id:4 addr:xx:xx:xx:xx:d1:1d, transport:BT_TRANSPORT_LE reason:GATT_CONN_FAILED_ESTABLISHMENT
08-15 16:20:02.196  2621  3184 I bt_bta_gattc: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_act.cc:1212 bta_gattc_conn_cback: Disconnected att_id:5 addr:xx:xx:xx:xx:d1:1d, transport:BT_TRANSPORT_LE reason:GATT_CONN_FAILED_ESTABLISHMENT
08-15 16:20:02.196  2621  3184 I bt_bta_gattc: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_act.cc:1212 bta_gattc_conn_cback: Disconnected att_id:6 addr:xx:xx:xx:xx:d1:1d, transport:BT_TRANSPORT_LE reason:GATT_CONN_FAILED_ESTABLISHMENT
08-15 16:20:02.196  2621  3184 W bt_btm_sec: packages/modules/Bluetooth/system/stack/btm/btm_sec.cc:3747 btm_sec_disconnected: Got uncommon disconnection reason:Connection Failed Establishment handle:0x0010 comment:stack::acl::btm_acl::btm_acl_disconnected
08-15 16:20:02.196  2621  3184 E bta_gattc_main: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_main.cc:395 bta_gattc_hdl_event: Ignore unknown conn ID: 3
08-15 16:20:02.196  2621  3184 E bta_gattc_main: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_main.cc:395 bta_gattc_hdl_event: Ignore unknown conn ID: 4
08-15 16:20:02.196  2621  3184 E bta_gattc_main: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_main.cc:395 bta_gattc_hdl_event: Ignore unknown conn ID: 5
08-15 16:20:02.196  2621  3184 W bt_stack: [WARNING:bta_gattc_act.cc(365)] bta_gattc_open_fail: Cannot establish Connection. conn_id=000000. Return GATT_ERROR(133)
08-15 16:20:02.197 23947 23961 D BluetoothGatt: onClientConnectionState() - status=133 clientIf=6 device=F6:42:C9:C2:D1:1D
08-15 16:20:02.197 23947 23961 E DfuBaseService: Connection state change error: 133 newState: 0
08-15 16:20:02.197 23947 24112 I DfuBaseService: Connection error after: 1031 ms
08-15 16:20:02.197 23947 24112 E DfuBaseService: An error occurred while connecting to the device:133
08-15 16:20:02.198 23947 24112 I DfuBaseService: Attempt: 3
08-15 16:20:02.204 23947 24112 I DfuBaseService: Cleaning up...
08-15 16:20:02.204 23947 24112 D BluetoothGatt: cancelOpen() - device: F6:42:C9:C2:D1:1D
08-15 16:20:02.209  2621  2755 I bt_btif_gattc: packages/modules/Bluetooth/system/btif/src/btif_gatt_client.cc:382 btif_gattc_close_impl: client_if=6, conn_id=0, address=xx:xx:xx:xx:d1:1d
08-15 16:20:02.209  2621  3184 E bt_stack: [ERROR:bta_gattc_act.cc(317)] No such connection need to be cancelled
08-15 16:20:02.210  2621  3184 E bt_stack: [ERROR:bta_gattc_utils.cc(444)] bta_gattc_mark_bg_conn unable to find the bg connection mask for bd_addr=f6:42:c9:c2:d1:1d
08-15 16:20:02.210 23947 24112 D BluetoothGatt: close()
08-15 16:20:02.210 23947 24112 D BluetoothGatt: unregisterApp() - mClientIf=6
08-15 16:20:02.213  2621  3184 I bt_stack: [INFO:gatt_api.cc(1042)] GATT_Deregister gatt_if=6
08-15 16:20:02.830  3698  4051 W AiAiEcho: SmartspaceNotificationPredictor no parser can handle this notification or notification is invalid
08-15 16:20:02.831 23947 23947 D BleFirmwareUpgradeHandler: onError() : F6:42:C9:C2:D1:1D 133 1 GATT ERROR
08-15 16:20:02.850 23947 23947 E BLE FW UPGRADE: ERROR
08-15 16:20:02.857 23947 23947 I DfuBaseService: DFU service destroyed

RE: What is the expected success rate of a DFU update?

zippert — Mon, 15 Aug 2022 10:57:50 GMT

2.4.1 is the ble-sdk-version, and 2.0.3 is the dfu-lib-version. I saw that updated versions exist that allows for additional timeout-attributes, but these versions were used the last time we released a bluetooth-update-feature.

So, yeah, as far as I can tell, the only (relevant) code that has changed is the binary itself (and, of course the set of devices used). It is a mystery to me...

RE: What is the expected success rate of a DFU update?

Aleksander Nowakowski — Mon, 15 Aug 2022 10:52:24 GMT

Hello,

Which SDK on the nRF side are you using?

Did you update the DFU library to 2.1 (from which version?), or the "dip" was observed without any changes on your side?

Do you have any phones where it fails more often than on others, or fails all the time?

This GATT ERROR (133) is a generic error thrown when :"something" failed.. really hard to tell the reason.

RE: What is the expected success rate of a DFU update?

zippert — Mon, 15 Aug 2022 06:20:31 GMT

This is the statistics in general for all our supported Android versions (minSdkVersion 26).

RE: What is the expected success rate of a DFU update?

Sigurd — Fri, 12 Aug 2022 15:55:08 GMT

Hi,

[quote user=""](according to our firebase metrics) on Android[/quote]

Do you know anything about what Android version and phone model/brand this is occurring on?