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: Pairing Mode and Bonding

Part Number: CC2642R

Tool/software:

hello!

This is the pairing setting,sdk ver 7_41

1、If the Maximum Number of Characteristic is set to 0, the pair can be successfully paired, but the save error is 0x04 !When the connection is made again, it will not be paired again, but the data communication is not encrypted 。

2、If the Maximum Number of Characteristic is set to 4, the pair can be successfully paired, The pair binding is saved successfully !The data transmitted on each subsequent connection is encrypted, but the notify function is enabled before each subsequent connection。

The help I need is that I hope the pairing succeeds and can be successfully saved. In the case of no active cancellation of the pairing, the data of subsequent connections will be encrypted and transmitted, which is the process of the second situation. However, I do not want to start a notify for each subsequent connection, because the notify before the connection callback is meaningless to me, how to remove it? 

I really hope to get your help, thank you!

  • Hi,

    Thank you for reaching out. We will take a look at your questions and get back to you as soon as possible.

    Best Regards,

    Jan

  • Thank you and look forward to your help!

  • Hello,

    Are you using an out of the box example here? I ask in order to try to reproduce this and better understand your case. To be clear, you don't want to re-enable notifications after paring correct on the peripheral side correct?
    Any enabled notifications or configurations made during the temporary connection will be reset when the devices disconnect. However while bonding, a more permanent relationship between two Bluetooth devices is created by exchanging and storing link keys. This allows the devices to automatically re-connect and maintain configurations like enabled notifications when they come back in range. Without bonding, the connection is treated as temporary by the devices.

    BR,

    David.

  • Hello,

         I modified it based on the routine "simple_peripheral_CC26X2R1_LAUNCHXL_tirtos7_ticlang". I found that only pairing is not binding, the air packet is plaintext transmission, and subsequent connections will not start notify before entering the connection callback.  The notify enabled before the connection callback has no meaning for me. The process of connecting a mobile phone to cc2642 is physical connection, updating mtu, enabling notify, and transparent data transmission. Therefore, I set pairing and binding to realize transparent and encrypted transmission.  But I want to remove the issue of enabling notify before the connection callback。 

    What worries me most is whether the stability of the device will be affected after the pairing and binding, and whether the notify function is enabled before the connection callback. Before the pairing and binding function is added, the device has been running for more than one year。

    thank you!

         

  • Hello Wang,

    Apologies for the delay. I think I am not understanding correctly what your expectation is from the behaviour. May I ask what connection callback event you are referring to?

    BR,

    David.