WL1837MOD: BT repeated pairing failure

log.rar

We, will take a look at the logs and get back in a day or two..

Thanks

Hi ,Hari 

  Thanks for your support.  Yesterday, we let  the supplier of BT protocol stack  grab another log   which used  mobile phone oppo r9s,   The failure rate of oppo r9s pairing will be lower than that of pixel4  for comparison. oppo R9s paring fail，then pixel 4 paring fail also.rar.

Hi,Hari

 How about the progresss and results, our customers are doing certification,

so time is urgent.Thank you

The FW logs, do not show any thing abnormal. Are, you referring to the 'LMP_detach' from Pixel phone after paging? This sequence is acceptable as per BT specs. If not, please point us to the logs where, you are seeing the issue..

322790 01:08:52.204   +94:45:55.205 0x00451F28 0x00456323 <---- LMP_detach Reason = Other End Terminated Connection: User Ended Connection 322829 01:08:52.288   +94:45:55.289 0x00451F65 0x0045635F <---- HCI_Disconnection_Complete_Event 323147 01:09:11.743   +94:46:14.744 0x00455C30 0x0045A02B <---- LMP_features_req 3-slot packets = 1, 5-slot packets = 1, Encryption = 1, Slot offset = 1, Timing accuracy = 1, Switch = 1, Hold mode = 1, Sniff mode = 1, Park Mode = 0, RSSI = 1, Channel quality driven data rate = 1, SCO link = 1, HV2 packets = 1, HV3 packets = 1, u-law log = 1, A-law log = 1, CVSD = 1, Paging scheme = 1, Power control = 1, Transparent synchronous data = 1, Flow control lag(least significant bit) = 0, Flow control lag(middle bit) = 0, Flow control lag(most significant bit) = 0, Broadcast encryption = 1, Reserved = 0, Medium Rate ACL 2 Mbps mode = 1, Medium Rate ACL 3 Mbps mode = 1, Enhanced inquiry scan = 1, Interlaced inquiry scan = 1, Interlaced page scan = 1, RSSI with inquiry results = 1, Extended SCO link (EV3 packets) = 1, EV4 packets = 0, EV5 packets = 0, Reserved = 0, AFH capable slave = 1, AFH classification slave = 1, Reserved = 0, Reserved = 1, 3 slot Medium Rate ACL packets = 1, 5 slot Medium Rate ACL packets = 1, Sniff Sub-Rate = 1, Encryption Pause Resume = 1, AFH capable master = 1, AFH classification master = 1, Medium Rate eSCO 2 Mbps mode = 1, Medium Rate eSCO 3 Mbps mode = 1, 3 slot medium rate eSCO packets = 1, Extended Inquiry Response = 0, <future> = 1, <future> = 1, Simple Pairing = 0, Encapsulated PDU = 1, Erroneous Data Reporting = 0, Non-flushable Packet Boundary Flag = 1, (Persistent Sniff) = 1, LSTO = 1, Inquiry TX Power Level = 0, Enhanced Power Control = 0, <future> = 0, <future> = 0, <future> = 1, <future> = ???, Extended features = ??? 323148 01:09:11.743   +94:46:14.744 0x00455C32 0x0045A02D LMP_features_res ----> 3-slot packets = 1, 5-slot packets = 1, Encryption = 1, Slot offset = 1, Timing accuracy = 1, Switch = 1, Hold mode = 1, Sniff mode = 1, Park Mode = 0, RSSI = 1, Channel quality driven data rate = 1, SCO link = 1, HV2 packets = 1, HV3 packets = 1, u-law log = 1, A-law log = 1, CVSD = 1, Paging scheme = 0, Power control = 1, Transparent synchronous data = 1, Flow control lag(least significant bit) = 0, Flow control lag(middle bit) = 1, Flow control lag(most significant bit) = 0, Broadcast encryption = 0, Reserved = 0, Medium Rate ACL 2 Mbps mode = 1, Medium Rate ACL 3 Mbps mode = 1, Enhanced inquiry scan = 1, Interlaced inquiry scan = 1, Interlaced page scan = 1, RSSI with inquiry results = 1, Extended SCO link (EV3 packets) = 1, EV4 packets = 1, EV5 packets = 1, Reserved = 0, AFH capable slave = 1, AFH classification slave = 1, Reserved = 0, Reserved = 1, 3 slot Medium Rate ACL packets = 1, 5 slot Medium Rate ACL packets = 1, Sniff Sub-Rate = 1, Encryption Pause Resume = 1, AFH capable master = 1, AFH classification master = 1, Medium Rate eSCO 2 Mbps mode = 7, Medium Rate eSCO 3 Mbps mode = 1, 3 slot medium rate eSCO packets = 1, Extended Inquiry Response = 0, <future> = 1, <future> = 1, Simple Pairing = 1, Encapsulated PDU = 1, Erroneous Data Reporting = 0, Non-flushable Packet Boundary Flag = 1, (Persistent Sniff) = 1, LSTO = 1, Inquiry TX Power Level = 0, Enhanced Power Control = 0, <future> = 0, <future> = 0, <future> = 1, <future> = ???, Extended features = ??? 323149 01:09:11.743   +94:46:14.744 0x00455C33 0x0045A02E <---- LMP_features_req_ext features page = 1, max supported page = 2, extended features = 0f 00 00 00 00 00 00 00 323150 01:09:11.743   +94:46:14.744 0x00455C35 0x0045A030 LMP_features_res_ext ----> features page = 1, max supported page = 1, extended features = 03 00 00 00 00 00 00 00 323163 01:09:11.747   +94:46:14.748 0x00455C36 0x0045A031 <---- LMP_name_req Name Offset = 0 323164 01:09:11.747   +94:46:14.748 0x00455C38 0x0045A033 LMP_name_res ----> Offset = 0, Length = 8, Fragment = GWM poer 323165 01:09:11.747   +94:46:14.748 0x00455C39 0x0045A034 <---- LMP_detach Reason = Other End Terminated Connection: User Ended Connection 323271 01:09:16.860   +94:46:19.861 0x00456C32 0x0045B02D <---- LMP_version_req VersNr = 9, CompId = Qualcomm, SubVersNr = 702 323291 01:09:16.865   +94:46:19.866 0x00456C34 0x0045B02F LMP_version_res ----> VersNr = 7, CompId = Texas Instruments Inc., SubVersNr = 44040 323292 01:09:16.866   +94:46:19.867 0x00456C35 0x0045B030 <---- LMP_features_req 3-slot packets = 1, 5-slot packets = 1, Encryption = 1, Slot offset = 1, Timing accuracy = 1, Switch = 1, Hold mode = 1, Sniff mode = 1, Park Mode = 0, RSSI = 1, Channel quality driven data rate = 1, SCO link = 1, HV2 packets = 1, HV3 packets = 1, u-law log = 1, A-law log = 1, CVSD = 1, Paging scheme = 1, Power control = 1, Transparent synchronous data = 1, Flow control lag(least significant bit) = 0, Flow control lag(middle bit) = 0, Flow control lag(most significant bit) = 0, Broadcast encryption = 1, Reserved = 0, Medium Rate ACL 2 Mbps mode = 1, Medium Rate ACL 3 Mbps mode = 1, Enhanced inquiry scan = 1, Interlaced inquiry scan = 1, Interlaced page scan = 1, RSSI with inquiry results = 1, Extended SCO link (EV3 packets) = 1, EV4 packets = 0, EV5 packets = 0, Reserved = 0, AFH capable slave = 1, AFH classification slave = 1, Reserved = 0, Reserved = 1, 3 slot Medium Rate ACL packets = 1, 5 slot Medium Rate ACL packets = 1, Sniff Sub-Rate = 1, Encryption Pause Resume = 1, AFH capable master = 1, AFH classification master = 1, Medium Rate eSCO 2 Mbps mode = 1, Medium Rate eSCO 3 Mbps mode = 1, 3 slot medium rate eSCO packets = 1, Extended Inquiry Response = 0, <future> = 1, <future> = 1, Simple Pairing = 0, Encapsulated PDU = 1, Erroneous Data Reporting = 0, Non-flushable Packet Boundary Flag = 1, (Persistent Sniff) = 1, LSTO = 1, Inquiry TX Power Level = 0, Enhanced Power Control = 0, <future> = 0, <future> = 0, <future> = 1, <future> = ???, Extended features = ??? 323293 01:09:16.866   +94:46:19.867 0x00456C37 0x0045B032 LMP_features_res ----> 3-slot packets = 1, 5-slot packets = 1, Encryption = 1, Slot offset = 1, Timing accuracy = 1, Switch = 1, Hold mode = 1, Sniff mode = 1, Park Mode = 0, RSSI = 1, Channel quality driven data rate = 1, SCO link = 1, HV2 packets = 1, HV3 packets = 1, u-law log = 1, A-law log = 1, CVSD = 1, Paging scheme = 0, Power control = 1, Transparent synchronous data = 1, Flow control lag(least significant bit) = 0, Flow control lag(middle bit) = 1, Flow control lag(most significant bit) = 0, Broadcast encryption = 0, Reserved = 0, Medium Rate ACL 2 Mbps mode = 1, Medium Rate ACL 3 Mbps mode = 1, Enhanced inquiry scan = 1, Interlaced inquiry scan = 1, Interlaced page scan = 1, RSSI with inquiry results = 1, Extended SCO link (EV3 packets) = 1, EV4 packets = 1, EV5 packets = 1, Reserved = 0, AFH capable slave = 1, AFH classification slave = 1, Reserved = 0, Reserved = 1, 3 slot Medium Rate ACL packets = 1, 5 slot Medium Rate ACL packets = 1, Sniff Sub-Rate = 1, Encryption Pause Resume = 1, AFH capable master = 1, AFH classification master = 1, Medium Rate eSCO 2 Mbps mode = 7, Medium Rate eSCO 3 Mbps mode = 1, 3 slot medium rate eSCO packets = 1, Extended Inquiry Response = 0, <future> = 1, <future> = 1, Simple Pairing = 1, Encapsulated PDU = 1, Erroneous Data Reporting = 0, Non-flushable Packet Boundary Flag = 1, (Persistent Sniff) = 1, LSTO = 1, Inquiry TX Power Level = 0, Enhanced Power Control = 0, <future> = 0, <future> = 0, <future> = 1, <future> = ???, Extended features = ??? 323301 01:09:16.870   +94:46:19.871 0x00456C38 0x0045B033 <---- LMP_features_req_ext features page = 1, max supported page = 2, extended features = 0f 00 00 00 00 00 00 00 323302 01:09:16.870   +94:46:19.871 0x00456C3A 0x0045B035 LMP_features_res_ext ----> features page = 1, max supported page = 1, extended features = 03 00 00 00 00 00 00 00 323303 01:09:16.870   +94:46:19.871 0x00456C3B 0x0045B036 <---- LMP_host_connection_req 323304 01:09:16.871   +94:46:19.872 0x00456C3B 0x0045B036 <---- HCI_Connection_Request_Event 323316 01:09:16.891   +94:46:19.892 0x00456C43 0x0045B03D HCI_Accept_Connection_Request ----> 323317 01:09:16.892   +94:46:19.893 0x00456C43 0x0045B03D <---- HCI_Command_Status_Event 323318 01:09:16.892   +94:46:19.893 0x00456C45 0x0045B040 LMP_accepted ----> Opcode = LMP_host_connection_req 323319 01:09:16.892   +94:46:19.893 0x00456C49 0x0045B044 LMP_setup_complete ----> 323320 01:09:16.892   +94:46:19.893 0x00456C49 0x0045B044 <---- LMP_set_AFH AFH instant = 9134768, AFH mode = 1, AFH channel map = fe ff ff fe ff ff ff ff ff 3f 323321 01:09:16.892   +94:46:19.893 0x00456C4A 0x0045B045 <---- LMP_channel_classification_req AFH reporting mode = 01 , AFH min interval = 1600, AFH max interval = 8000 323351 01:09:16.896   +94:46:19.897 0x00456C4B 0x0045B046 <---- LMP_setup_complete

Hi,Hari

  The issue was happened in the last part of the two logs. After the mobile phone (pixel4) send LMP_detach command  and then the chip side also responds to the disconnection. The chip side again scans to the MAC of the mobile phone, but there is no pairing action

And there are some problems in the attachment ，and there is a Stack log (includingir log,but not chipset's log)  for refer  which  matched with "20210105Pixel4手机配对车机失败.doc"  but not the same time with chipset's log .The size"Stack log" is 56M,which is larger than ti's upload file size (20m). Please tell me how to upload if necessary5282.Issue Point.docx

Hi,Hari

  The problem is in the last part of the two logs. After the mobile phone (pixel4) send LMP_detach command  and then the chip side also responds to the disconnection. The chip side again scans to the MAC of the mobile phone, but there is no pairing action

And there are some problems in the attachment ，and there is a Stack log (includingir log,but not chipset's log)  for refer , which  matched with "20210105Pixel4手机配对车机失败.doc"  but not the same time with chipset's log. The size of "Stack log "is 56M which is  larger thanTI's upload file size (20m). Please tell me how to upload if necessary

Issue Point.rar

Hi,

1) It seems, the slave did not receive the POLL packet after FHS paging packet from master. So, the connection was not established. I wonder, if this was due to interference. Did, you try with WiFi disabled? If, problem persists and consistent then taking air sniffer logs would help.

2) The controller's Timeout was to an earlier initiated local transaction. It is not with LMP_Detach from peer device. 

3) Since, the controller is in slave role, setting Link supervision timeout is 'disallowed'.

Thanks

Hi,Hari

    Thanks for your support！

 1、The customer only use BT funnction (not used WIFI).  we Grep the air log as your suggestion  and the Chipset log same time ,Please see the new attachment

 2、If  is  the reason  of pairing failue when Local transtratiion timeout?   The  controller means SOC ?   whether Local transtratiion timeout  maybe caused by WL1837 chip?

3、the issue caused by  SOC（car machine），not WL1837 CHip

4、Is it matter  for WL1837   using  The BTS TIIinit_12.8.32_SP3.61.bts  ,There is a suggestion on TI's official website that wl1837 uses 11.8.32.bts

pixel 4发起配对，手机提示无法通信.7z

Hi,Hari

   I'm sorry for trouble .  The pairing failue did not happen when the BT Stack change the  PAGE SCAN TYPE from Standard Scan(default) to Interlaced Scan.

However, the provider of Bluetooth protocol stack does not know why this problem occurs, so please help explain.

The difference between standard and interlaced page scan is described in the BT sig specs. Please refer to 'Page Scan Substate' section. With Interlaced there are back to back scans and the chances of connection are better.

Thanks