This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2642R-Q1: EXT_EP-11975 (BLE_AGAMA-4810): Fix logic, and is there an application-level workaround without upgrading the SDK?

Part Number: CC2642R-Q1
Other Parts Discussed in Thread: CC2642R

Body

Hi,

I am following up on JIRA ticket EXT_EP-11975 / BLE_AGAMA-4810:
"Connection param and channel map update callbacks are coming earlier than the actual instant where the change is reflected in the connection, causing CM instability."

The release notes of SimpleLink CC13xx/CC26xx SDK v8.32 state this issue is fixed, but the description is very brief.

My setup: CC2642R as the main BLE peripheral connected to a phone, with another CC2642R running a Connection Monitor (CM) following the same link.

Could you please clarify:

  1. Fix logic — at the flow level, when is the application callback now raised relative to the actual instant of the parameter / channel map change? A short description of the new sequence would be enough.

  2. Application-level workaround without upgrading — if I stay on the older SDK, is it possible to mitigate this purely from the application layer (e.g., delaying the forwarding of the callback to the CM device until the instant is reached)? If yes, what information is available to the application to determine the correct instant?

Thanks!

  • Hi Chad,

    1. The application callback will be reported on the actual channel map update instant. For example, if current connection event counter is 50, and channel map will update after +9 connection event. Application callback of channel map will be raised on connection event 59.

    2. Please reach out to your FAE to take this fix. I don`t see possible fix on application level

    Regards,
    Kevin