Can you please tell which project you have programmed, in the pioneer kit.
Thank you very much for your reply.
The project I loaded in the pioneer kit is the BLE_4.2_DataLength_Security_Privacy project.
I would like to come back with another question.
Sorry for all these posts with questions, but I am trying to have a better understanding of the BLE security features.
In our custom application, the configuration "Unauthenticated pairing with encryption" as well as "Bonding" has been selected since no input/no output is available.
The functionality of our custom application has been verified using the dongle CY5677 BLE4.2 and using the previous version of the dongle, that with BLE 4.1.
I monitor the events passed to the application when the connection/pairing/bonding/disconnection procedure takes place.
When I use the dongle with BLE 4.1, after bonding, the encryption keys are not exchanged in future connections. I believe this is correct.
When I use the dongle with BLE 4.2, even if bonding is accomplished successfully, in future connections the encryption keys are always exchanged. I can trace this because the CYBLE_EVT_GAP_KEYINFO_EXCHNGE_CMPLT event fires at every pairing request sent by CySmart software. Is this behavior correct?
I believe that the bond mechanism is used in order the keys to be exchanged once. After bonding, only if bonding info is removed this exchange will happen again. So why using the BLE4.2 dongle the encryption keys are sent at every connection? Am I missing something?
Thank you in advance.