- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have faced MIC(Message Integrity Check) error for LE connection. I can see same issue on following link, could you help how to resolve?
For more information, please refer to the following.
https://community.infineon.com/t5/Studio-Bluetooth/Bug-report-Connection-Terminated-Due-to-MIC-Failu...
https://community.infineon.com/t5/Studio-Bluetooth/Bug-report-BLE-cant-reconnect-to-a-bonded-device/...
1. Test environment
1) H/W
- Local H/W : CYW920706WCDEVAL
- Peer device :
> LG Stylus2
>> Android version 7.0
>> BR/EDR public BD address : DO:13:FD:50:F8:C8
> HUAWEL P9 lite. (Model number : HUAWEL VNS-L22)
>> Android version 7.0
2) S/W
- SDK : ModusToolBox 2.3 and LE_Hello_sensor application
- SDK LIB : Wiced_btsdk baselib release v3.0.0
- Peer Apps : LightBlue, local developed BLE application.
2. Test procedure
- Step 1. Hello_sensor build & download
- Step 2. Pairing with android phone.
- Step 3. Connection success.
- Step 4. Remote disconnect after pairing success.
- Step 5. Start connection from andoid phone.
- Step 6. Link connection fail due to MIC error. (error code 0x3d)
3. Test Results
- I tested other BLE peripheral with two android phones and it works well. (No MIC error)
- CYW920706WCDEVAL works fine with iphone, and other many android phone.
- HCI fail : HCI_Encryption_Change event status code 0x3d. (mic error)
5. attached log file.
- mic_error_app_log.txt : application log with MIC error.
- mic_error_btspy.txt : MIC error with CYW920706WCDEVAL and LG android phone.
- no_mic_with_iphone.txt : No MIC error with CYW920706WCDEVAL and iphone.
Thanks.
- Labels:
-
WICED Studio Bluetooth
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Could you please try the test with the latest SDK release (BTSDK3.2)? I do not see any error in the connect-disconnect procedure.
Also, I have doubts in the test procedure. Is it just connect-disconnect? or repairing is needed from a different device? Could you please explain the test procedure once again?
Thanks,
-Dheeraj.P.K
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
What I'd like to say is that testing with the iPhone and a few other Android phones that I have didn't cause any problems.
However, there is a problem with two phones in particular as I mensioned previous posting.
With Initial pairing is successful without any issues.
However, after pairing, these two phones always do not make connection because of MIC error.
My testing procedure was as follows:
1. update BTSDK from 3.0 to 3.2
2. Build LE_Hello_senosr.
3. Download FW to CYW920706WCDEVAL
4. start BTSpy logging.
5. Reset CYW920706WCDEVAL.
6. Start Piaring from LG Styus2 and LE_Hello_Sensor
7. Pairing success.
>> Line 219 : RECV Command. Name: SMP Pairing Request (0x01) len: 7
>> Line 231 : SEND Command. Name: SMP Pairing Response (0x02) len: 7
>> Line 448 : Event from HCI. Name: HCI_Encryption_Change (Hex Code: 0x08 Param Len: 4)
>> Line 449 : Status : Success (0x00)
>> Line 450 : Connection Handle : 64 (0x0040)
>> Line 451 : Encryption Enable : 1 (0x01)
8. Disconnect.
>> Line 900 : Event from HCI. Name: HCI_Disconnection_Complete (Hex Code: 0x05 Param Len: 4)
>> Line 901 : Status : Success (0x00)
>> Line 902 : Connection Handle : 64 (0x0040)
>> Line 903 : Reason : 19 (0x13)
9. Re Connect to LE_Hello_Sensor
>> Line 985 : Event from HCI. Name: HCI_BLE_Event (Hex Code: 0x3e Param Len: 13)
>> Line 993 : Command to HCI. Name: HCI_LE_Long_Term_Key_Request_Reply (Hex Code: 0x201a Param Len: 18)
>> Line 1014 : Event from HCI. Name: HCI_Encryption_Change (Hex Code: 0x08 Param Len: 4)
>> Line 1025 : Status : Connection Terminated Due to MIC Failure (0x3d)
Captured log file by BTSpy has been attached.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Dheeraj.P.K,
For this issue, I have also opened mycase#00701273 and attached air log when the issue is reproduced as well normal case using competitor vendor.
Thanks,
Liam
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Our team is looking into the issue. Let's discuss the issue in the SFDC case.