SDK_V10, S110_V8.0.0,
Just Works, getting error BLE_GAP_SEC_STATUS_CONFIRM_VALUE when bonding, attached file is Sniffer data. What is the problem?
SDK_V10, S110_V8.0.0,
Just Works, getting error BLE_GAP_SEC_STATUS_CONFIRM_VALUE when bonding, attached file is Sniffer data. What is the problem?
Hi Matt,
I am sorry for the delay.
It is most probably a peer issue calculating the confirm value wrong on the peer device that is sending the pairing request.
Could you check that up with your peer device and also provide any new information about your findings?
Hi, Martin:
I think you are right. But the calculating process is done in SoftDevice, is it? How can I check it or modify?
Hi Matt,
The calculation part in SoftDevice should be correct, we believe that the confirm value calculation in the peer is wrong, you can check it manually using the specification.
If you are having any trouble, let me know.
Hi, Martin:
Could you use one of example in SDK to tell me where is the confirm value calculation in the peer?
Hi, Martin:
Could you use one of example in SDK to tell me where is the confirm value calculation in the peer?
(sorry for the delay)
What I meant was for you to do this confirm value calculation manually from the Specification document. (It didn't evolve the SDK or Softdevice)
However, It appears that the peer is calculating the confirm value wrong, it should be calculated using the address on air (that's how the Softdevice does it), but the peer is calculating using another address most probably.
Hi, Martin:
Slave "sent pairing random" is done in SoftDecive? I only find API "sd_ble_gap_sec_params_reply()", can not find how to "sent pairing random".