nRF8001 doesn't acknowledge LL_VERSION_IND

RE: nRF8001 doesn't acknowledge LL_VERSION_IND

Stephan Walter — Tue, 14 Oct 2014 10:07:44 GMT

Hi, thanks for your response. I did the test with an Android and an iOS device, so for the iOS capture the nRF8001 was bonded with the Android device and vice versa.

If I'm understanding you correctly, if we would test this with two iOS devices, the behaviour should be the same as in the Android trace, that is the connection should be set up but encryption would fail.

It seems that the behaviour of the nRF8001 is as it should be, and we have to try to react to this case in the app.

RE: nRF8001 doesn't acknowledge LL_VERSION_IND

run_ar — Tue, 14 Oct 2014 09:30:11 GMT

If the nRF8001 is bonded to a device that has a static address (Android), it will enable address based whitelisting. If it is bonded to a device with a private address (iOS) it will not enable this whitelist (this is because iOS changes its address every 15th minute). Looking at your iOS capture it looks like the whitelist is enabled.

Edit: You could possibly change this behavior by modifying the setup data. Change the whitelist bit in devsett 0x1 -> v3_data -> features.

RE: nRF8001 doesn't acknowledge LL_VERSION_IND

run_ar — Tue, 14 Oct 2014 07:40:00 GMT

When you captured the iOS trace, what is the device bonded with nRF8001?