Problems after DFU on IOS

RE: Problems after DFU on IOS

tesc — Fri, 06 Sep 2019 11:39:26 GMT

Hi,

Thanks for letting me know about the dead link! I have now updated both links. (Link to pm_local_database_has_changed() was also outdated.)

Regards,
Terje

RE: Problems after DFU on IOS

Michael M — Thu, 05 Sep 2019 20:26:03 GMT

The link for the "GATT Service Server Example" is invalid .. can you update it please.

RE: Problems after DFU on IOS

tesc — Thu, 24 Jan 2019 16:40:16 GMT

Hi,

I do not quite understand what you have done and where, but on the application you need both to enable the characteristic and to actually trigger an update notification (e.g. with pm_local_database_has_changed(), see my other recent reply.)

Regards,
Terje

RE: Problems after DFU on IOS

tesc — Thu, 24 Jan 2019 16:37:57 GMT

Hi,

For the bootloader it should not be an issue, as if you use NRF_DFU_BLE_REQUIRES_BONDS it will send service changed notifications. (If you do unbonded DFU then it will increment the BLE address by one when in DFU mode in order to avoid the issue. It then goes back to the old BLE address again for the (old or new) application.)

For the application, if you use the Peer Manager you should use pm_local_database_has_changed() after a bonded DFU, or after any DFU that has updated the GATT table. You may have a look at the GATT Service Server Example Application for an example of notifying a database change (although in that example it is triggered by button press.)

You also need to set NRF_SDH_BLE_SERVICE_CHANGED to 1 in sdk_config.h, in order for the GATT service to include the Service Changed Characteristic.

Regards,
Terje

RE: Problems after DFU on IOS

siruiwang — Wed, 16 Jan 2019 03:06:19 GMT

Hi Terje,

I'm a iOS developer, I tried using nRF Connect for Android and enabled "Service Changed" characteristic, and it's still enabled in DFU mode and after DFU success, but nothing changed if I enabled this characteristic, nRF Connect still not received any GATT table update for both iOS and Android,Is this firmware issues or iOS issues?

Best Regards

Sirui

RE: Problems after DFU on IOS

Richard Yin — Tue, 15 Jan 2019 08:07:12 GMT

Dear Terje,

How to handle "Service Changed" in bootloader and application? Could you please send any any example code to demonstrate this process?

Thanks and Regards,

Richard

RE: Problems after DFU on IOS

tesc — Fri, 11 Jan 2019 15:33:33 GMT

Hi,

When you have a changing GATT table you should also have a "Service Changed" characteristic, and you should handle it properly both in bootloader and application. Otherwise the peer device may assume that the GATT table did not change, which is exactly what iOS does. (Most smart phones do service discovery every time regardless, which explains why they get the new GATT table without problem.)

iOS does not display the Service Changed characteristic, but if you use nRF Connect for Android or for Desktop you can check to see if your application (before and after) and DFU bootloader does use this characteristic. See for instance the thread Buttonless DFU Error: Enabling indications failed.

Regards,
Terje