- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I don't know what is the problem, something linked with the security policy, because when i disable strict pairing it work :
I tried to debug it with CySmart but pairing works with the key..
Do you have any idea ? I didn't see something related with that in the update list ...
Thanks.
Regards,
Solved! Go to Solution.
- Labels:
-
BLE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
'Strict' Pairing means the devices should perform the selected pairing procedure ( Unauthenticated pairing in this case) and if the peer device ( Mobile Phone) has a different Security level selected, will result in pairing failure.
If you do not check the Strict pairing , both devices will choose and go for the possible pairing process based on the negotiated Security levels and IO capabilities between them.
I could see this issue and this is a bug with BLE v3.30 component (pairing Should not happen with your selected configuration with Mobile phone). BLE v3.40 and later does not have this issue.
Please use the latest BLE component version 3.52 for the new designs which has all prior bugs fixed.
-Gyan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
'Strict' Pairing means the devices should perform the selected pairing procedure ( Unauthenticated pairing in this case) and if the peer device ( Mobile Phone) has a different Security level selected, will result in pairing failure.
If you do not check the Strict pairing , both devices will choose and go for the possible pairing process based on the negotiated Security levels and IO capabilities between them.
I could see this issue and this is a bug with BLE v3.30 component (pairing Should not happen with your selected configuration with Mobile phone). BLE v3.40 and later does not have this issue.
Please use the latest BLE component version 3.52 for the new designs which has all prior bugs fixed.
-Gyan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for you answer.
But i had the same policy security with the BLE module v3.30 and there was no connection issue with phones. So i still doesn't see where is the problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I could see this issue and this is a bug with BLE v3.30 component (pairing Should not happen with your selected configuration with Mobile phone). BLE v3.40 and later does not have this issue.
Please use the latest BLE component version 3.52 for the new designs which has all prior bugs fixed.
-Gyan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for your answer.
Unfortunately, we have to pair and bond a mobile phone with the BLE module but we only have one button on the BLE module side.
So what we do is reject connection if the device was not previously bonded or if the "pairing button" is not pressed.
How can we proceed now ?
I don't see the point to use a fixed passkey to do the same thing..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You don't need to use the fixed passkey to authenticate, but you are welcome to.
With just the no IO bonding mode, you can setup the unit to bond to the unit that connects when your button is pressed, and then reject connections at all other times (or if it doesn't match the previously bonded unit).
There are a few threads that go over a similar situation:
http://www.cypress.com/blog/100-projects-100-days/project-016-authentication
CY8CKIT-042-BLE: How to setup pairing
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
This exaclty what i do, but it seems that since v3.30, we can't choose unauthenticated pairing with encryption, and what we want is to have encrypted data after establishing the connection.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Do not use 'Strict ' pairing option ( Select as 'No')and you will able to perform the unauthenticated pairing with encryption.
Because we do not know what is the security level selected in your central device , and if it does not match the peripheral device's security level , the pairing will fail.
-Gyan