nRF51 OTA DFU issue with nRF Connect iOS V1.7.5

[heisenberg]

nRF_log_1.8.1.txtHello Nordic Support Team,

We are trying to run the OTA DFU on the nRF51 device via the nRF Connect iOS application V1.7.5. The DFU Device is available, but once selecting the new FW image file, and starting the DFU process, we've got the following error message: "Abort ! DFU service not found". This issue is always detected on different iOs versions (V9.3.5, V10.3.2 and V10.3.3).

TODAY, we've updated the nRF Connect iOS application from V1.7.5 to V1.8.0 (released yesterday 11th October); and as a magic spell the OTA DFU is now working correctly using this updated version. But sometimes the DFU process fails even with the V1.8.0 nRF Connect version with different iOS versions. Issue is not systematic :(

We did not find within the "What's new" section of version V1.8.0 that may explain this behaviour... Any help Please ?

PS: Issue described above is not reproduced, and the DFU process is running successfully, once using: nRF Connect on Android Application V4.13.1 and nRF Toolbox iOS application V4.4.1

nRF_log.txt

BeST Regards, -Heisenberg-

[Mehdi]

Hi Aleksander, 

I tried to perform a DFU  on nRF51 via nRFConnect_v1.8.2 under iOS_v10.3.2.

The DFU still doesn't work with the same issue mentioned by  -Heisenberg-

PS: I added two screen shots showing nRFConnect_v1.8.2 LOG.

Howerver DFU works using nRF toolbox APP under the same envirenement .

What's new about the update from nRFConnect_v1.8.1 to nRFConnect_v1.8.2  about the DFU feature. 

I need a responce ASAP. Many thanks.

Best Regards *Mehdi*

[Hung Bui]

It says, DFU service not found. You may need to check the attribute table to see if you actually added the DFU service. There is a chance that the phone cached the attribute table, you can try to turn off an on Bluetooth or turn off or on the phone, just to check. For attribute table that can change you would need to have service changed service added to the table.