Quantcast
Channel: Forums - Recent Threads
Viewing all articles
Browse latest Browse all 262198

CC2642R: LL_CONNECTION_PARAM_REQ and L2CAP CONNECTION PARAMETER UPDATE REQUEST

$
0
0

Part Number:CC2642R

Hello,

I'm using the SDK v2.40.

In gap.h, the description of the API GAP_UpdateLinkParamReq() is as follows:

"As long as LL connection updates are supported on the own device (which is the case by default), an LL Connection Update procedure will be attempted. If this fails, the stack will automatically attempt an L2CAP parameter update request."

I called the API on my Central device which is based on TI BLE Stack to the update the connection parameters of the connection with an iPhone as Peripheral, I got LL_REJECT_EXT_IND with the error code 0x1A(Unsupported Remote Feature). However, I don't see, on the sniffer capture, any attempt to send L2CAP Connection Parameter Update Request from my Central. Instead, I got the GAP event GAP_LINK_PARAM_UPDATE_EVENT with the error code 0x1A. For sure, the parameter values are all compliant to Apple's accessary guide and the error code 0x1A doesn't mean the parameters are not acceptable. It means either the iPhone is temporarily too busy to handle the request or it actually doesn't support LL_CONNECTION_PARAM_REQ even if it is declared to be supported in the Features Response.

What's a little more strange is, if I call L2CAP_ConnParamUpdateReq() to send L2CAP Connection Parameter Update Request after receiving the GAP_LINK_PARAM_UPDATE_EVENT with the error, I get the status code bleAlreadyInRequestedMode. Does that mean the TI stack is already doing it as described in the above? Anyway, I don't see any over the air L2CAP signal and I don't get L2CAP Connection Parameter Update Response, whether or not I call the function L2CAP_ConnParamUpdateReq().

What is the expected behavior?

- Cetri


Viewing all articles
Browse latest Browse all 262198

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>