IOS nrfConnect issue with DFU

RE: IOS nrfConnect issue with DFU

bjorn-spockeli — Fri, 09 Aug 2019 08:09:53 GMT

BinderT:The suggestion that my colleague Edvin gave you, i.e. incrementing the BLE address of the nRF, should solve the issues related to GATT table caching. Alternatively you can call sd_ble_gatts_service_changed() to the BLE_GAP_EVT_CONNECTED case in ble_evt_handler() in main.c.
Note, this will cause the nRF to trigger service discovery on every connection, so this should only be added for ease of development and removed in production code.

RE: IOS nrfConnect issue with DFU

bjorn-spockeli — Fri, 09 Aug 2019 08:05:25 GMT

No, but it should only be the matter of calling sd_ble_gatts_service_changed() after you have added the Buttonless DFU Service, which I am assuming that you do after one sends 0x000610 to the characteristic of your custom service.

There should not have to do anything on the central side, only on the nRF side.

RE: IOS nrfConnect issue with DFU

BinderT — Thu, 08 Aug 2019 19:29:39 GMT

RE: IOS nrfConnect issue with DFU

vivek.spraxa — Thu, 08 Aug 2019 15:09:19 GMT

Do you have any example for it, i am using plugin on RN app for it - react-native-nordic-dfu or any other example

RE: IOS nrfConnect issue with DFU

bjorn-spockeli — Wed, 07 Aug 2019 13:15:37 GMT

Hi vivek,

iOS devices may cache the GATT table based on the address of the peripheral to avoid performing the Service Discovery procedure on every connection. Instead it just assumes that the peripheral will have the same order of services as the last time. So when you are modifying the GATT table of the peripheral by adding/removing a service, then the iOS device will still think its the same GATT table as before. THis is why the DFU service is not shown.

This can be solved by issuing a Service Changed indication, see GATTS Service Changed.

After adding the Nordic DFU service to the GATT table you need to call sd_ble_gatts_service_changed to inform the central that the GATT table has changed.

Best regards

Bjørn

RE: IOS nrfConnect issue with DFU

vivek.spraxa — Tue, 06 Aug 2019 10:49:11 GMT

You have to follow the steps on the given file to active notification and for authentication it is accept any password. devzone.nordicsemi.com/.../output.pdf

RE: IOS nrfConnect issue with DFU

bjorn-spockeli — Fri, 02 Aug 2019 09:35:55 GMT

HI Vivek,

after flashing the hex files to nRF52 DK and I connected to it with a Samsung Galaxy S9 using nRF Connect. I do not see the Nordic Buttonless DFU service with my Android device, just an unknown service. Are you sure that you have added this service?

Best regards

Bjørn

RE: IOS nrfConnect issue with DFU

vivek.spraxa — Thu, 01 Aug 2019 13:46:28 GMT

devzone.nordicsemi.com/.../1_5F00_1.99.3.hex

devzone.nordicsemi.com/.../1_5F00_1.99.4.hex

Here the attached hex files for it

RE: IOS nrfConnect issue with DFU

bjorn-spockeli — Tue, 30 Jul 2019 14:39:29 GMT

But you must have an application firmware that adds the Buttonless DFU service to the GATT table of the SoftDevice using the SoftDevice API? Is it possible to run the application on a nRF52 DK? If yes, could you attach the compiled hex file to the question so that i can test it here?

RE: IOS nrfConnect issue with DFU

vivek.spraxa — Tue, 30 Jul 2019 09:38:16 GMT

We are not using sdk , we have soft device version s132_nrf52_5.0.0 , firmware version 4.1.10, i am using the latest version available on app store and ios version 12.3.1 iphone 6

RE: IOS nrfConnect issue with DFU

bjorn-spockeli — Tue, 30 Jul 2019 09:03:21 GMT

Which SDK version are you using to built the firmware on the nRF device? Which version of the nRF COnnect app are you using? Have you tried erasing the device and reporgramming it as well as turning the iOS device off and on again?

I had no issues when testing with the SDK v15.3.0 example and a iOS device here.

RE: IOS nrfConnect issue with DFU

vivek.spraxa — Mon, 29 Jul 2019 15:13:30 GMT

And here are the screenshot from android nrf connect

RE: IOS nrfConnect issue with DFU

vivek.spraxa — Mon, 29 Jul 2019 14:35:42 GMT

I have checked again by Bluetooth off and then still the same and have nrf52

RE: IOS nrfConnect issue with DFU

bjorn-spockeli — Mon, 29 Jul 2019 13:19:49 GMT

HI Vivek,

the UUID of the Service shown in the nRF Connect app does not match the UUID of the Buttonless DFU Service, which is 0xFE59.

Which SDK example have you flashed to your nRF device? Which SDK version are you using? Is this the nRF52 or the nRF51 series?

The Buttonless DFU Service should have two characteristics with the following UUIDs.

Characteristic name	Required properties	Optional properties	UUID	16-bit
DFU Control Point	Write, Notify		0x8EC90001-F315-4F60-9FB8-838830DAEA50	0x0001
DFU Packet	WriteWithoutResponse, Notify		0x8EC90002-F315-4F60-9FB8-838830DAEA50	0x0002

It could be that your iOS device has cached the GATT table of the previous application on the nRF device. Can you try to turn off and on again the Bluetooth adaptor on the iOS device?

Best regards

Bjørn

RE: IOS nrfConnect issue with DFU

vivek.spraxa — Mon, 29 Jul 2019 02:27:18 GMT

Any other info needed as i am unable to do dfu devices when using ios device