Keep getting those errors when connecting bonded Cysmart to CYW20719:
Status : Connection Terminated Due to MIC Failure (0x3d)
Encryption Status Event: bd ( 5a 10 0c ef 51 aa ) res 8109
The CYW20719 hardware is CYBT_413034_EVAL.
Clients are Samsung TAB E 7” and Tab A 8” tablets with Android 4.4.4, 5.0.1 and 6.0.1
This error happens:
So I already rise this problem couple months ago, but haven’t receive any solution (neither on any of the bugs I reported so far ☹ ), but at least:
Do you have some sniffer tool that could capture raw packets (incl. MIC) in the communication client <> server so to compare what is the difference when reconnecting go smooth and when fail?
Either there is something wrong on the Cypresses BT stack side or something in the timing parameters/syncs in the connection ☹ The only clue I could guess – slower processors with Android have more MIC failures than faster ones ☹ , but when I try reconnecting bonded CC2540 from TI, don’t have any problems neither with Cysmart, nor nRf Connect or other BLE Android clients on the same Android devices that fails with CYW20719 ☹
17:29:09.988 1 hello_sensor_management_cback: 17
17:29:09.992 1 Advertisement State Change: 0
17:29:09.992 1 ADV stop
17:29:09.994 RCVD  Event from HCI. Name: HCI_Encryption_Change (Hex Code: 0x08 Param Len: 4)
17:29:09.994 Status : Connection Terminated Due to MIC Failure (0x3d)
17:29:09.994 Connection Handle : 64 (0x0040)
17:29:09.994 Encryption Enable : 0 (0x00)
17:29:09.996 1 hello_sensor_management_cback: c
17:29:10.003 1 Encryption Status Event: bd ( 5a 10 0c ef 51 aa ) res 8109
17:29:10.007 1 encryp change bd ( 5a 10 0c ef 51 aa ) res: 8109
17:29:10.010 RCVD  Event from HCI. Name: HCI_Disconnection_Complete (Hex Code: 0x05 Param Len: 4)
17:29:10.010 Status : Success (0x00)
17:29:10.010 Connection Handle : 64 (0x0040)
17:29:10.010 Reason : 61 (0x3d)
17:29:10.010 Connection Terminated Due to MIC Failure
17:29:10.014 1 connection_down 5a 10 0c ef 51 aa conn_id:1 reason:61
Confirmed it is 6.2.1 (as already stated in the title) - 6.4 doesn't work at all with my hardware
The log that I've already posted is from BTSpy, but doesnt give me any clue except that the client (Android) terminated the connection because of MIC.
Now here is the same passage from the same test when it pass Ok:
17:31:40.884 RCVD  Event from HCI. Name: HCI_Encryption_Change (Hex Code: 0x08 Param Len: 4)
17:31:40.884 Status : Success (0x00)
17:31:40.884 Connection Handle : 64 (0x0040)
17:31:40.884 Encryption Enable : 1 (0x01)
17:31:40.889 1 hello_sensor_management_cback: c
17:31:40.893 1 Encryption Status Event: bd ( 5a 10 0c ef 51 aa ) res 0
17:31:40.897 1 encryp change bd ( 5a 10 0c ef 51 aa ) res: 0
I think you are referring toBug report – BLE – cant reconnect to a bonded device , we are not able to reproduce the issue.
Can you confirm if you have made any changes in the hello sensor demo app? Exact testing steps might help us to dig more.
Yes, I'm referring to the same issue, but when I first reported it I was newbie with CYW, so there were and plenty bulk info that might cloud the core of the problem and it reproducing.
If you follow the situation #1 mentioned at the first post in this thread - I always receive this error with the original hello_sensor example from 6.2.1 (maybe only couple extra WICED_BT_TRACEs added and BT address fixed to never change).
So if you follow exactly scenario #1 from first post with Cysmart1.2 with default setting and hello_sensor example from WICED 6.2.1 - I always get those errors doesn't matter what android device and which version is.
Let me know if there is something I didn't explained clear enough how to reproduce the error and what are the prerequisites to start the experiment.
EDIT: In described situation #1 in first post It is important to reset the board before return to reconnecting to not the last Cysmart client in order to reproduce 8109/61 error and then happens on 100% of all the devices and Android versions I tried so far