Is this the softdevice issue?

RE: Is this the softdevice issue?

Susheel Nuguru — Thu, 16 Jul 2015 12:24:49 GMT

Any updates on this thread?

RE: Is this the softdevice issue?

jimlin — Mon, 20 Apr 2015 02:55:00 GMT

As what you mentioned, how to bond KB with iPad B? Need to press the bond delete button? The periphral should connect to 8 centrals max and how to achieve this?

RE: Is this the softdevice issue?

jimlin — Sun, 19 Apr 2015 10:29:19 GMT

The KB is bond with iPad A and then want to bond with iPad B without pressing the bond delete button with restart. The issue is why the KB could not bond successfully with iPad B. As my understand, if the KB gave the LL_VERSION_IND response, the bond process should be go on to complete, right? Why the KB ignore the 6 connection interval? The ble spec limit? or the softdevice decide it? Even the iPad B is not in the KB's whitelist, if the KB could reponse what the iPad B need, it could add it to the list. I am not clear why the KB did not do so. Additionally, it could bond to iPad B successfully after trying some more times. I think the key difference is the bond delete button pressed or not. Anything else to handle by the SD exclude the flash clear? Thanks.

RE: Is this the softdevice issue?

vich — Sun, 19 Apr 2015 01:22:04 GMT

Hi,

The reason for failure to establish connection with iPad B could be that KB only has iPad A in its whitelist. You have mentioned in step 3 that KB is bonded with iPad A. Please ensure that KB is also bonded with iPad B.

The scenario is "Failed to establish connection" where in iPad B will tx for 6 connection intervals after the CONNECT_REQ, but peripheral does not listen to these events as the CONNECT_REQ did not originate from one of the device (bonded) in its whitelist. In fact the peripheral continues advertising after ignoring the CONNECT_REQ (does not care for 6 connection interval Tx-es from the iPad B).

Hope this helps.

Regards