RE: Problem with implementing DFU over iOS

Hung Bui — Wed, 16 Jan 2019 14:15:40 GMT

Hi,

I don't think the advertising data would be the issue here. As you can see in the log, the DFU master on the phone managed to switch from the application to DFU bootloader, and the bootloader get connected and the phone tried to do service discovery. This was where the issue happened. DFU service was not found.

We suspected it was due to cached attribute table, but as you mentioned you already included service changed, nobond, turn off and on Bluetooth, it should work.

A sniffer trace would be really helpful to check if the service discovery actually happens or not.

I would suggest you after you have the disconnection, try using nRFConnect to scan and find the DFU bootloader and connect to it and check what's inside the attribute table at that point.

In addition you can also test to trigger the switching from application to bootloader by 1. Enable indication. 2. Write 0x01 to the DFU control point characteristic. The device should switch to bootloader and it should start advertising as DFU target. You then can switch to scan mode in nRFConnect and connect to the DFU target. If there is a DFU service inside the bootloader, you should be able to perform DFU.

I would suggest to test with the stock ble_app_buttonless example instead of your application, just to align with what we have here.

RE: Problem with implementing DFU over iOS

eyalasko — Tue, 15 Jan 2019 13:00:00 GMT

one interesting observation -

The advertised field payload is marked as incomplete 16-bit service, while its actually 128 bit.

Can it be related to the problem?