LL_VERSION_IND and LL_FEATURE_REQ Continuous messages

RE: LL_VERSION_IND and LL_FEATURE_REQ Continuous messages

Jimmy Wong — Thu, 11 Jul 2019 11:31:35 GMT

HI,

This is violated the bluetooth specification.

RE: LL_VERSION_IND and LL_FEATURE_REQ Continuous messages

sridharnaidu — Thu, 11 Jul 2019 06:38:54 GMT

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?

RE: LL_VERSION_IND and LL_FEATURE_REQ Continuous messages

Jimmy Wong — Mon, 08 Jul 2019 14:46:47 GMT

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.

RE: LL_VERSION_IND and LL_FEATURE_REQ Continuous messages

sridharnaidu — Mon, 08 Jul 2019 12:27:54 GMT

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?

RE: LL_VERSION_IND and LL_FEATURE_REQ Continuous messages

Jimmy Wong — Sat, 06 Jul 2019 01:37:49 GMT

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.