OTA DFU on OSX/iOS Caching Issue

RE: OTA DFU on OSX/iOS Caching Issue

Jean-Louis Bonnaffé — Wed, 17 Jun 2015 10:47:21 GMT

The same exact problem happens with my iOS application. But never with the DFU from Nordic Toolbox.

Hey, Nordic, how did you do ?

RE: OTA DFU on OSX/iOS Caching Issue

RK — Wed, 16 Jul 2014 23:14:12 GMT

That was my question originally - I just used the word 'paired' instead of 'bonded' because clearly I'm confused about some of the BTLE terms.

I thought that iOS/OSX was only supposed to cache services for peripherals which were bonded, but I've seen odd things too, which is why I've started randomizing my own addresses as a regular practie. You might want to ask about that on the Apple Bluetooth list and say what you're seeing, there's some helpful guys there who've struggled with every problem under the sun.

RE: OTA DFU on OSX/iOS Caching Issue

Konstantin K — Wed, 16 Jul 2014 14:44:09 GMT

Actually, now that I looked into service changed notification, it seems that it's only for bonded devices. Since I'm not doing bonding, I can't use it. It seems to be an issue with OSX that it caches services for non-bonded devices.

RE: OTA DFU on OSX/iOS Caching Issue

OPQ — Wed, 16 Jul 2014 08:24:14 GMT

Good idea to change the address.

RE: OTA DFU on OSX/iOS Caching Issue

Konstantin K — Tue, 15 Jul 2014 23:19:49 GMT

If by pairing you mean connecting, then yes. I need to connect to the device to write characteristics.

Thank you very much for pointing me to Service Changed indication. I believe this will work for me.

RE: OTA DFU on OSX/iOS Caching Issue

RK — Tue, 15 Jul 2014 23:14:16 GMT

Firstly it should only cache paired devices, are you seeing caching for non-paired ones also, that's not supposed to happen.

BTLE allows paired devices to be cached, and defines the SERVICE CHANGED indication which lets you tell the device you're paired to that you've changed.

Or you can switch your address out for a new random one and pair all over again.