CC2640R2F: [BLE5][SDK_3.10] Failure To Use GAP Connection Update Request

Hi Kenny,

Per default, the simple peripheral waits for a param update request:

// After the connection is formed, the peripheral waits until the central
// device asks for its preferred connection parameters
#define DEFAULT_ENABLE_UPDATE_REQUEST         GAPROLE_LINK_PARAM_UPDATE_WAIT_REMOTE_PARAMS

When it is received, it replies with the parameters given in simple_peripheral.c. The API used is GAP_UpdateLinkParamReqReply(). See peripheral.c:

          else // GAPROLE_LINK_PARAM_UPDATE_WAIT_REMOTE_PARAMS
          {
            // Only use remote requested values.
            rsp.intervalMin = pReq->req.intervalMin;
            rsp.intervalMax = pReq->req.intervalMax;
            rsp.connLatency = pReq->req.connLatency;
            rsp.connTimeout = pReq->req.connTimeout;
          }
        }

        // Send application's requested parameters back.
        VOID GAP_UpdateLinkParamReqReply(&rsp);

Can you try using GAP_UpdateLinkParamReq() driectly in your application or GAPRole?

Hi Marie,

Thanks for your reply.

Actually, we do test the example from the version of BLE5, could you check it again?

Many Thanks.

"S/W : SDK 1.40 Original Code "simple_periphaeral"(BLE5) / SDK 3.10 Original Code "simple_periphaeral"(BLE5)"

Hi Kenny,

I just tested with the default ble5_simple_peripheral project from 3.10 SDK. It's sending a connection parameter update request 6 seconds after the connection has been established.

Did you make any code changes before testing?

Do you have a preference between LL and L2CAP connection parameter update?

Hi Marie,

Do you try to use iPhone 7? this test is based on Bluetooth 4.2 device of iOS.

The sniffing log MSC showed, we have definitely waited for over 6 Secs. You could check the timeline of MSC.

Check the Testing environment what I mentioned before, we modified the connection update parameters of SDK 1.40 according to SDK 1.30.

Please check it, Many Thanks.

Hi Kenny,

I tested with iPhone 7 now. Turns out it doesn't support LL Connection Parameter Request Procedure. (You can see this in the LL_FEATURE_RSP packet the master sends just after the connection is formed.) The BLE-Stack on the CC264R2 will send a HCI command complete event to the application with the HCI_LE_CONNECTION_UPDATE opCode and the return status ( LL_STATUS_ERROR_UNSUPPORTED_REMOTE_FEATURE).

Can you try using L2CAP_ConnParamUpdateReq() directly from your application? (API documentation: dev.ti.com/.../group___l2_c_a_p.html )

Hi Marie,

Actually, "L2CAP_ConnParamUpdateReq()" it is ok what I mentioned before.

Our customer just wants to clarify a paradox between SDK 1.40 and SDK 3.10.

Why SDK 1.40 could work with iPhone 7 but SDK 3.10?

Please help to explain that, Many Thanks.

Hello Marie,

The question is how do you know your peripheral (CC2640R2F) is connected with an iPhone 7 (UNSUPPORT) or a non-iPhone 7? SDK 3.10 makes it a no turning back situation. Once you use LL Connection Parameter Rquest on an iPhone 7, it hangs there. Otherwise, the program can just try L2CAP procedure if the LL procedure fails. The problem is you cannot, because the failed LL or L2CAP procedure blocks the other connection update request forever until the connection is terminated.

Samson

Hello Marrie,

How did you get LL_STATUS_ERROR_UNSUPPORTED_REMOTE_FEATURE? I tried to intercept all HCI Command Complete Events, I didn't see any events after GAP_UpdateLinkParamReq() was called.

Besides, after GAP_UpdateLinkParamReq() was called with the iPhone 7 connection, the call of L2CAP_ConnParamUpdateReq() would be rejected with the returned status code, bleAlreadyInRequestedMode, which is 0x11.

So far, I don't see any events that can help me to determine that the GAP_UpdateLinkParamReq() has failed, and L2CAP_ConnParamUpdateReq() shall to be proceeded. Plus the L2CAP_ConnParamUpdateReq() simply does not work after GAP_UpdateLinkParamReq() has been used.

Samson

Hi Marie,
Thanks for your reply.
Based on your explained, so we could be understanding the behavior of the connection parameter update is definitely different between SDK 1.40 and SDK 3.10? right? If so, but why? I thought they all are BLE5 Stacks, it should be the same result and behavior, not supposed to show like that.
Many Thanks.

Hello Marie,

Thanks a lot for the clarification. Let us wait for the next release. Looking forward to it.

Samson