Central Address Resolution?

[AndreaO]

I'm migrating form S332 0.9.1alpha (aligned to S132 2.0.0) to the newer S332 2.0.1 (aligned to S132 3.0.0) on a nRF52 board, and I'm seeing a new characteristic under Generic Access 0x1800 primary service: "Central Address Resolution", 0x2AA6.

It suspect that after a firmware update (soft device + bootloader + application) this new characteristic change the BLE device form a OS point of view: I can't write no more to my custom characteristicand and I need to reset manually the Bluetooth cache of OS (Windows, iOS, Android).

Can I disable the Central Address Resolution characteristic?

The same change apply to the standard Nordic bootloader.

[run_ar]

Unfortunately I cannot see any way to disable this, but I will check internally if there is anything we can do about it. For now I'm afraid you will have to manually reset the cache (This can be done programatically on android, but on iOS it requires user action, not sure about windows).

[AndreaO]

Do you think is it possible to implement the Service Changed characteristic, to force a cache reconstruction just after the reconnection?

[run_ar]

Not really, the central address resolution is part of the generic access service which is placed before the Generic attribute service (that contains the service changed indication characteristic) in the attribute table. This means the attribute handle of the service changed characteristic will also change after the DFU.

[AndreaO]

Is there any workaround at app level (iOS, Android) to permit the firmware update from the old soft device to the new one without asking the user to manually reset Bluetooth (to reset the BLE cache) in the middle of update procedure (just after SD+BL update and before application update)?

[run_ar]

I guess you could take a look at this. The change address "fix" also works for iOS as it will show as a new device.