• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 51 subscribers
  • Views 341 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

LAUNCHXL-CC26X2R1: OOB Pairing failed after connect L2CAP COC.

Kong Lingwen
Prodigy 160 points
Part Number: LAUNCHXL-CC26X2R1


Dear Ti members:

sequence1:

1. Central: genrate ECC keys, random and confirm

2. Peripheral: set remote oob data using random and confirm from No.1

3. Central: connect to peripheral

4. Central: start pairing (successfully)

sequence2:

1. Central: genrate ECC keys, random and confirm

2. Peripheral: set remote oob data using random and confirm from No.1

3. Central: connect to peripheral

4. Central: open L2CAP COC and connect COC

5. Central: start pairing (failed)

The only difference if No.4

Pairing can not start after L2CAP COC connected?

SDK version: simplelink_cc13xx_cc26xx_sdk_6_20_00_29

Best regards.

Kong

  • 0
    TI__Mastermind 25810 points

    Hey Kong,

    I'm not sure this behavior is supported, as I don't see any L2CAP api's that enable pairing. Let me investigate this further and I will get back to you.

  • 0 in reply to Ammar N
    TI__Mastermind 25810 points

    Hey Kong,

    Apologies for the delay. After some initial investigation, it looks like this should be possible (last time I recall this was verified was in this e2e thread).

    One thing I'd like for you to try is to add a timer and wait to trigger pairing, maybe 1 s or so after the connection is established. When L2CAP connections are enabled, there may already be a control procedure ongoing at the same time pairing is triggered, which can cause the pairing to fail. This quick test can confirm the suspected behavior.

    Can you also share a sniffer log of the behavior over the air if you have it?

  • 0 in reply to Ammar N
    Prodigy 160 points

    Hi Ammar,

    Thank you for you answer.

    This problem can not be reproduced.

    It works fine now.

    I have check several vertions of my code, And I have no idea why it can not be reproduced.

    Thanks anyway.