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: Phone binding pairing failed.

Part Number: CC2642R

Hi team,

Here's the request from customer:

After CC2642 is successfully paired with the mobile phone, CC2642 erases the local binding information and then connects to CC2642 with the mobile phone. The mobile phone will pop up a binding pairing pop-up window, and clicking confirm will result in unsuccessful pairing. He needs to reconnect and rebind the pairing again to succeed.

Capture the package and see the prompt  DH Key Check Failed

Can you please check this case?

Thanks and Regards,

Nick

  • Hi Nick,

    Ive assigned to a teammember, can you confirm sdk version and example they are basing their project from.

    Kind Regards,

    Rogelio

  • Hi Rogelio,

    Thanks for your quick response. Here's the further reply from customer:

    SDK version is simplelink_cc13x2_26x2_sdk_4_40_04_04 and example is simple_peripheral_oad_onchip.

  • Hello Nick,

    Let's take a step back to the issue. Costumer has first paired 1 phone to CC2642R with simple_peripheral_oad_onchip example. After bonding, he has disconnected the phone and tried to reconnect it but unsuccessfully  am I right? 

    For what I understood steps by steps his process is: 

    1 - Connect CC2642R to the phone

    2 - Bond CC2642R to the phone

    3 - Disconnect the phone (why costumer needs to erase local binding once the bonding has been made??)

    4 - Try to reconnect with the phone, bonding pop up window appears, connection ends

    5 - Reconnect the phone and bonds it again, connections works properly

    Can you confirm or I miss something?

    Also does costumer has followed the section GAP Bond Manager and LE Secure connection in the user's guide?

    Did he used OAD before with another target? (If OAD_BLE_SECURITY is defined in the user / persistent (for onchip OAD) application project, The OAD distributor will be forced to be paired with the OAD target in order for the OAD to happen.)

    regards,