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.

CC2745R10-Q1: Configuration Impact on Connection: Passkey Entry vs. OOB

Part Number: CC2745R10-Q1

Hi Team,
I have a few technical questions regarding the pairing method configuration on the TI CC2745 platform. Thank you in advance for your support.
  1. Regarding GAPBondMgr_SetParameter(GAPBOND_OOB_ENABLED, ...):
    Does calling this API force the device to use the OOB pairing flow for every​ subsequent connection? How can we configure the stack to trigger the OOB pairing flow only when needed (on-demand)?
  2. Difference between APIs:
    What is the difference and relationship between setting GAPBOND_OOB_ENABLEDvia GAPBondMgr_SetParameter()and using GAPBondMgr_SCSetRemoteOOBParameters()? How do these two APIs work together?
Current Requirement:
We need to support both CCC​ (Car Connectivity Consortium) and ICCE​ (Integrated Car Connectivity Ecosystem) digital key protocols simultaneously:
  • CCC​ requires Out-of-Band (OOB)​ pairing.
  • ICCE​ requires Passkey Entry.
Could you please advise on the recommended configuration strategy to support both pairing methods on the same device?
 
Best regards.
  • One more question: Can I configure the pairing method on a per-connection basis (e.g., setting OOB for one connection and Passkey Entry for another)?

  • Hi Leo,
    1. Have you tried default OOB off, and only enable it when you find CCC in connection,  and after successful pairing turn it off again? 
    2. GAPBondMgr_SetParameter will only set the overall enable/disable of OOB, while GAPBondMgr_SetParameter not only sets the OOB EN/DIS it also both OOB data(rand, confirm) and the name suggests it used in SC pairing.

    Best

  • We find your suggestion feasible and will proceed with testing. Please note that this may introduce certain constraints to the customer pairing flow.