Part Number: CC2640R2F
Hello,
Sometimes, pairing failed because of timeout.
Below is my peripheral's log. GAPROLE_WAITING_AFTER_TIMEOUT showed up just in 325ms after GAPBOND_PAIRING_STATE_STARTED.
Is this related with supervision timeout? The supervision timeout set as 5 secs after connected. So I think it's not supervision timeout.
[ 10.423 ] GAPROLE_CONNECTED
[ 10.426 ] Connected Peer BD_ADDR[0x507705941D09],type[2],handle[0]
[ 11.016 ] ParamUpdate: interval[6] latency[0] timeout[500]
[ 11.501 ] ParamUpdate: interval[39] latency[0] timeout[500]
[ 12.075 ] GAPBOND_PAIRING_STATE_STARTED
[ 12.380 ] ParamUpdate: intervRsp result : 0x00
[ 12.400 ] GAPROLE_WAITING_AFTER_TIMEOUT
[ 12.405 ] terminate reason [8]
Could you check the attached logs?
btsnoop_hci_201909090955.cfa : This is the bt snoop log of the phone side. (from line 23162)
pairing-timeout_in-325ms.cfa : Air log (from frame# 4727 of SMP)
I think it's not about heap memory also. below is the mem status when the timeout occurred.
The timeout occurred with even more heap memory like 6700bytes.
I'm using SDK 2.40 (simplelink_cc2640r2_sdk_2_40_00_32)
Thanks,
Calvin