从3.30到3.40更新BLE模块时无法配对手机

你好，
“严格”配对意味着设备应该执行所选择的配对过程（在这种情况下未经认证的配对），并且如果对等设备（移动电话）具有不同的安全级别被选择，将导致配对失败。
如果不检查严格的配对，两个设备将根据协商的安全级别和IO能力选择并进行可能的配对过程。
我可以看到这个问题，这是一个错误与BLE V3.30组件（配对不应发生与您选择的配置与移动电话）。BLE V3.40和以后没有这个问题。
请使用最新的BLE组件版本3.52的新设计，所有以前的错误修复。
-吉安



     以下为原文
  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

谢谢你的回答。
但是我有与BLE模块V3.30相同的策略安全性，并且没有与电话的连接问题。所以我还是看不出问题在哪里。



     以下为原文
  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.

你好，
我可以看到这个问题，这是一个错误与BLE V3.30组件（配对不应发生与您选择的配置与移动电话）。BLE V3.40和以后没有这个问题。
请使用最新的BLE组件版本3.52的新设计，所有以前的错误修复。
-吉安



     以下为原文
  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

谢谢你的回答。
不幸的是，我们必须配对和绑定手机与BLE模块，但我们只有一个按钮上的BLE模块侧。
所以我们所做的是拒绝连接，如果设备以前没有绑定，或者“配对按钮”没有被按下。
我们现在该怎么办？
我不明白用固定的密钥来做同样的事情。



     以下为原文
  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..

您不需要使用固定的密钥来进行身份验证，但欢迎您使用。
只要没有IO键合模式，您就可以将单元设置为绑定到当您的按钮被按下时连接的单元，然后在所有其他时间拒绝连接（或者如果它与先前绑定的单元不匹配）。
有一些线程会遇到类似的情况：
PSOC-4-BLU/100IX项目在Suth.CyPress半导体公司/PSOC-4-BLE·GITHUB中的100100天/Day015x键合
HTTP://www. CyPress .COM/BLUG/100项目-100天/项目016-认证
CY8CKIT-042-BLE：如何设置配对
如何手动输入配对模式？
如何限制服务器只与一个客户端绑定？



     以下为原文
  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:
PSoC-4-BLE/100_Projects_in_100_Days/Day015_Bonding at master · cypresssemiconductorco/PSoC-4-BLE · GitHub
http://www.cypress.com/blog/100-projects-100-days/project-016-authentication
CY8CKIT-042-BLE: How to setup pairing
How to manually enter pairing mode?
How to limit server to bonding with just one client?

你好，
这就是我所做的，但是似乎自从V3.30以来，我们不能选择未经验证的加密配对，而我们想要的是在建立连接后有加密的数据。



     以下为原文
  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.

你好，
不要使用“严格”配对选项（选择为“否”），并且您将能够执行加密的未经验证的配对。
因为我们不知道在您的中央设备中选择的安全级别是什么，并且如果它与外围设备的安全级别不匹配，那么配对将失败。
-吉安



     以下为原文
  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