LL_VERSION_IND and LL_FEATURE_REQ Continuous messages

[sridharnaidu]

Hi Mttrinh,

The following problem is happening in my case with old android devices. I found your answer from other thread. 

"The phone first sends a LL_VERSION_IND and then it sends a LL_FEATURE_REQ before the peripheral has sent its LL_VERSION_IND. In other words, the phone initiates a seconds LL Control Procedure before the first is finished, and this is a clear violation of the Bluetooth specification. The SoftDevice will disconnect at this point". 

Is it really violation of specification?. If so why Nordic fixed it from s132v4.0.2 ?. Is there any part in specification which mention this?. In my case i using s132v3, so how can i fix this in my case?

[Jimmy Wong]

Hi,

yes , it violates on the Bluetooth specifications.

you can use the s132v3.1 to handle this host violation.

it mentions in the release note.

[sridharnaidu]

Hi,

I can see this issue is fixed in s132V3.1.0 ,but what we are using s132V3.0.0. Our customer is facing this issue , is there any patch available from Nordic for s132v3.0.0 so that we can use that. What will be the known challenges to migrate s132v3.1.0 in with sdk 12.1? 

[Jimmy Wong]

Hi,

You can just difference the header file of the softdevice between s132v3.1 and s132v3.0.  Almost all the header API are same.  It only has very little changes on the MTU / DLE on the gap opt setting.

Suppose you can still use the SDK 12.1 and upgrade to S132v3.1.

[sridharnaidu]

Hi,

I understand that part, but is there any patch for s132v3.0 which can nullify this bug?. I still want to understand why nordic has fixed it, if it is violation of specification?

[Jimmy Wong]

HI, 

This is violated the bluetooth specification.