• State
  • Locked Locked
  • Replies 9 replies
  • Subscribers 42 subscribers
  • Views 355 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

WL1831MOD: wlan0 interface not found, wl18xx not up in am335x custom hardware

Bluetooth broadcast caused by the calibration event and the mobile phone cannot search for the Bluetooth

Amelie Zheng
Genius 10865 points
Part Number: WL1831MOD

Hi Team,

At present, my customer's combo module (using the WL1831GYFVT chip) has three cases of Bluetooth abnormality at the customer. Please help with the support of the TI product line team, thank you!
The fault description is as follows:
     1. The module is used in the car. After the car has walked more than 6000 Km, Bluetooth appears in Advertising and can be found. Hcic_process_hci_commands: HCI_Write_Scan_Enable (Group 3 Opcode 0x1a);
Use different mobile phones (Apple, Huawei, Black Shark, etc.) to search for the BT address, but the mobile phone cannot search for the BT address;
     2. Test the power-on sequence. The internal DC2DC output voltage of the module's main chip is normal, and the fast clock and slow clock waveforms are normal. The wifi search and connection ap are normal.
     3. Finally, I saw the following log when grabbing the chip BT log:
1915 15: 18: 29.948 +0: 00: 05.149 Calibration started. Vector = 0x0, 0x20
1916 15: 18: 29.948 +0: 00: 05.149 DC_Calibration: Calibration Status (1-Pass; 0-Failed) = 0, Calibrated Regions (Bitwise 3 bits) = 0
1917 15: 18: 29.948 +0: 00: 05.149 Calibration was stoped before it was finished. Not Finished Vector = 0x0, 0x20
1918 15: 18: 29.948 +0: 00: 05.149 Calibration Failure Indication. Failure Code = 0x1, 0x1111
1919 15: 18: 29.948 +0: 00: 05.149 calibration 20 FAILED due to general interference. No more attempts. Going to the next calibration in the vector.
1922 15: 18: 29.948 +0: 00: 05.149 Coarse Open Loop Calibration: DCO DLO PVTH offset: 65500, Mode (0: 2X, 1: OSLO)-0
1923 15: 18: 29.948 +0: 00: 05.149 Coarse Open Loop Calibration: DCO DLO PVTH offset: 65484, Mode (0: 2X, 1: OSLO)-0
1924 15: 18: 29.948 +0: 00: 05.149 Coarse Open Loop Calibration: DCO DLO PVTH offset: 65484, Mode (0: 2X, 1: OSLO)-0
1925 15: 18: 29.948 +0: 00: 05.149 Coarse Open Loop Calibration: DCO DLO PVTH offset: 65484, Mode (0: 2X, 1: OSLO)-0
1926 15: 18: 29.948 +0: 00: 05.149 Coarse Open Loop Calibration: DCO DLO PVTH offset: 65484, Mode (0: 2X, 1: OSLO)-0
1927 15: 18: 29.948 +0: 00: 05.149 Coarse Open Loop Calibration: DCO DLO PVTH offset: 65484, Mode (0: 2X, 1: OSLO)-0

The preliminary judgment is that the Bluetooth broadcast caused by the calibration event and the mobile phone cannot search for the Bluetooth;
Please help analyze what is causing the problem? The end customer cannot reach the module during use,
Attached is the captured log file and the file in txt format; thank you!WL1831 Bluetooth address 2A9B main chip log calibration 1891-1920 line error offset value exceeds normal value 2019-12-05.txt

  • 0
    TI__Mastermind 27080 points

    Can, you send the complete log file (i.e .lgr file). When is this log taken? Does, rebooting the device help? 

    Thanks

  • 0 in reply to Hari Nagalla
    TI__Genius 10865 points

    Yes, Of course. 

    I have sent to you directly.

    Thanks!

  • 0 in reply to Amelie Zheng
    TI__Mastermind 27080 points

    Hi,

    We reviewed the logs and have the following observations/recommendations :

    a) Did, you try powering off the unit for some time and power up to see if it helps?

    b) What are the temperature conditions underwent in the auto units? Are they exceeding the WL18xx temperature ranges?

    c) Did, you capture the fast and slow clock wave forms? If, so can you please send across..

    Thanks

  • 0 in reply to Hari Nagalla
    Prodigy 50 points

    Hi，Hari：

             Thank you for your feedback！

             

    Hari Nagalla said:

    Hi,

    We reviewed the logs and have the following observations/recommendations :

    a) Did, you try powering off the unit for some time and power up to see if it helps?--------The failure persists after the power is turned off for a while and restarted.

    b) What are the temperature conditions underwent in the auto units? Are they exceeding the WL18xx temperature ranges?  ----I will ask the end customer to confirm the ambient temperature of the vehicle unit；We tested the faulty unit at room temperature after they returned.

    c) Did, you capture the fast and slow clock wave forms? If, so can you please send across.. 

    26MHz

    RTC

    Thanks

    Thanks

    best regards！

  • 0 in reply to wenchen
    Prodigy 50 points

    Dear Hari：

    BTW，I would like to know the following questions：

    1、  USD calibration : IPM mode = 0 , Initial PERINV = 683
    USD calibration : Usd_ldo = 0 , PERINV = 683
    DCO Tank Tune calibration : PVT_H Tune = 0 , PVT_H IF = 10
    DCO Tank Tune calibration : PVT_L Tune = 0 , PVT_L IF = 1fe
    DC_Calibration: Calibration Status (1 - Pass; 0 - Failed) = 0, Calibrated Regions (Bitwise 3 bits) = 0
    Calibration was stoped before it was finished. Not Finished Vector=0x0, 0x20
    Calibration Failure Indication。Failure Code=0x1,0x1111，-----Which function of the chip is calibrated here?What are the reasons for this, and what are the circumstances that will cause it to fail？
    2、 Coarse Open Loop Calibration: DCO DLO PVTH offset: 65500, Mode (0:2X, 1:OSLO) - 0
    Coarse Open Loop Calibration: PVTH OFFSET is out of range : 65520, Mode (0:2X, 1:OSLO) - 1
    -----What does PVTH mean here?
    3、The calibration failure is a software or hardware problem？Do calibration failure become permanent and unrecoverable  problems？
    4、If it can be determined that the cause of failure is beyond the temperature range, then can the normal chip work in the higher and lower temperature environment beyond the  temperature range to simulate and recurrence？
    Hope to get an early reply，
    Above, Many thanks！
    best regards！
  • 0 in reply to wenchen
    TI__Mastermind 27080 points

    The calibration issues do point to some inherent hardware/clock issues. Is this hardware layout and schematics reviewed by TI HW apps team? 

    Did, you try using the units only indoors and still fail after some time?

    Thanks

  • 0 in reply to Hari Nagalla
    Prodigy 50 points

    Hi，Hari：

                 This project is a relatively early product, about 2013, the schematics and hardware layout should have been reviewed, but the test at room temperature has not been found, and there is no case to refer to.

            At present, this product is mass production state, the shipment is very big. However, it seems that there was one bluetooth search failure last year, and now there are several similar problems.

           Therefore, we need your help to make an in-depth analysis。

    Thanks.

  • 0 in reply to wenchen
    TI__Mastermind 27080 points

    Does, the WiFi still work normally on these faulty units?

    Thanks

  • 0 in reply to Hari Nagalla
    Prodigy 50 points


    Use different mobile phones (Apple, Huawei, Black Shark, etc.) to search for the BT address, but the mobile phone cannot search for the BT address;
         2. Test the power-on sequence. The internal DC2DC output voltage of the module's main chip is normal, and the fast clock and slow clock waveforms are normal. The wifi search and connection ap are normal.

     

    For the two failed parts received, the WiFi of the two products can search the AP and connect to it normally.

     

     

    Thanks