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.

WL1835MOD: Bluetooth fixed frequency test tools.

Part Number: WL1835MOD
  • Bluetooth frequency setting tool of WL1835MOD module and its usage instructions.

  • Hi, please help to confirm whether WL18XX_bt_sp_v4.8 and Swru136b can be used to test the Bluetooth fixed frequency function of WL1835MOD.

  • Added schematic diagram of hardware design.

  • Hello,

    Will look into it and get back to you next week. In the meantime note that for hardware design reviews you may refer to our design review page: https://www.ti.com/tool/WILINK-DESIGN-REVIEWS

    BR, 

    Jessica M. Torres

  • 5023.swru136b.pdf,Bluetooth fixed frequency use HCITester tool, operation instructions use "Swru136b" right?

  • Can we schedule a Zoom meeting to clear this issue with  our client ASAP. How is your time availability?

  • before the meeting, Please can you ask someone who is specilise in  Bluetooth fixed frequency to check  If the HCI Tester is correct? 

  • Hi Jessica,

    The video file displays a failure to open the BLE fixed frequency tool .

  • What I can observe from your video is that when you open the "HCI tester" tool it did not find the device at the selected com port. You should click the icon on the top bar to "configure connections" (see image below), and make sure to select the correct com port where the device is connected. (You may use Windows "Device manager" to observe which com port number appears when you connect the usb cable)

       

    For BT testing using the HCI Tester Tool is correct, and the HCI Commands User's Guide is here.   I recommend you review section 1.2 "Configuration Requirements" which explains what files you need that should be found in your "wl18xx_bt_sp_v4.8" zip file.

    BR,

    Jessica M. Torres

  • HCITester Trace Log--Fail.txt
    17:34:24.040 Loading Library "C:\Program Files (x86)\Texas Instruments\Wireless Tools\TIInit_11.8.32.xml"...
    17:34:25.779 Load Succeeded
    17:34:25.785 --
    17:34:25.785 VersionPlatform = "DIAMOND"
    17:34:25.785 VersionMajor = 8
    17:34:25.785 VersionMinor = 32
    17:34:25.785 --
    17:36:21.506 Loading Library "C:\Program Files (x86)\Texas Instruments\Wireless Tools\TIInit_11.8.32.xml"...
    17:36:23.264 Load Succeeded
    17:36:23.265 --
    17:36:23.265 VersionPlatform = "DIAMOND"
    17:36:23.265 VersionMajor = 8
    17:36:23.265 VersionMinor = 32
    17:36:23.265 --
    17:36:53.130 Loading Library "C:\Program Files (x86)\Texas Instruments\Wireless Tools\TIInit_11.8.32.xml"...
    17:36:54.881 Load Succeeded
    17:36:54.882 --
    17:36:54.882 VersionPlatform = "DIAMOND"
    17:36:54.882 VersionMajor = 8
    17:36:54.882 VersionMinor = 32
    17:36:54.882 --
    17:37:29.313 ERROR - Timeout waiting for event HCI_Command_Complete_BLE_Receiver_Test_Event
    17:37:29.313 ERRORed Line (1): Wait_HCI_Command_Complete_BLE_Receiver_Test_Event 5000, any, HCI_BLE_Receiver_Test, 0x00
    17:37:34.752 --
    17:37:34.752 Packet "HCI_BLE_Transmitter_Test", Opcode 0x201e
    17:37:34.752 Parameters:
    17:37:34.752 | TX Frequency        : 0x00
    17:37:34.752 | Data Length         : 0x00
    17:37:34.752 | Packet Payload Type : 0x00 (PRBS 9)
    17:37:34.752 --
    17:37:34.752 Outgoing Dump:
    17:37:34.752     0000: 01 1e 20 03 00 00 00                            .. ....
    17:37:39.765 ERROR - Timeout waiting for event HCI_Command_Complete_BLE_Transmitter_Test_Event
    17:37:39.765 ERRORed Line (5): Wait_HCI_Command_Complete_BLE_Transmitter_Test_Event 5000, any, HCI_BLE_Transmitter_Test, 0x00
    17:37:46.473 --
    17:37:46.473 Packet "HCI_BLE_Test_End", Opcode 0x201f
    17:37:46.473 --
    17:37:46.474 Outgoing Dump:
    17:37:46.474     0000: 01 1f 20 00                                     .. .
    17:37:52.055 --
    17:37:52.056 Packet "HCI_BLE_Receiver_Test", Opcode 0x201d
    17:37:52.056 Parameters:
    17:37:52.056 | RX Frequency : 0x00
    17:37:52.056 --
    17:37:52.056 Outgoing Dump:
    17:37:52.056     0000: 01 1d 20 01 00                                  .. ..
    17:38:01.824 ERROR - Timeout waiting for event HCI_Command_Complete_BLE_Transmitter_Test_Event
    17:38:01.824 ERRORed Line (1): Wait_HCI_Command_Complete_BLE_Transmitter_Test_Event 5000, any, HCI_BLE_Transmitter_Test, 0x00
    

  • Hi Jessica,

    Added Video, log, circuit schematics for BLE test failures. I am currently using Uart A. Help analyze the cause of the failure.

    TKS !

  • First have you been able to verify that the HCITester tool and your WL8 device are communicating after choosing the correct com port?

    If not I recommend you find the HCI_VS_Get_Sytem_Status command under the HCI VS commands. (You can refer to section "4.3.2.1 Searching for a Specific Command in the Command Library" to find it quicker)

    This HCI_VS_Get_System_Status (0xFE1F) command can be used to verify that there is good communication when the device is connected. After the command is sent once, check that the trace window has message similar to the image below: 

    Most importantly make sure that before running your script that you initialize the board with the modified BTS script. As mentioned in section 3.2 you must replace the "5000, 0x00" with "5000, any" then save that script as a new initialization file in .txt format. Example below:

    AFTER you have run the initialization script you can send other commands or run a new script with your desired HCI commands, but the modified initialization script must be successfully run first.

    BR, 

    Jessica M. Torres

  • Hi Jessica,

    WL1835MOD failed to initialize:

    Here is the log of the test failure:

    HCITester Trace Log--Fail-01.txt
    15:45:39.014 --
    15:45:39.014 VersionPlatform = ""
    15:45:39.014 VersionMajor = 0
    15:45:39.015 VersionMinor = 0
    15:45:39.015 --
    15:47:40.045 Loading Library "C:\Program Files (x86)\Texas Instruments\Wireless Tools\TIInit_11.8.32.xml"...
    15:47:41.806 Load Succeeded
    15:47:41.806 --
    15:47:41.806 VersionPlatform = "DIAMOND"
    15:47:41.806 VersionMajor = 8
    15:47:41.806 VersionMinor = 32
    15:47:41.806 --
    15:47:51.548 *** Script Started: "C:\Program Files (x86)\Texas Instruments\Wireless Tools\TIInit_11.8.32.txt" ***
    15:47:51.548 --
    15:47:51.549 Packet "HCI_VS_Start_VS_Lock", Opcode 0xfe37
    15:47:51.549 Parameters:
    15:47:51.549 | Major Version Number : 0x08
    15:47:51.549 | Minor Version Number : 0x20
    15:47:51.549 --
    15:47:51.549 Outgoing Dump:
    15:47:51.549     0000: 01 37 fe 02 08 20                               .7... 
    15:47:56.564 ERROR - File: "C:\Program Files (x86)\Texas Instruments\Wireless Tools\TIInit_11.8.32.txt", Line: 20
    15:47:56.564 ERROR - Timeout waiting for event HCI_Command_Complete_VS_Start_VS_Lock_Event
    15:47:56.564 ERRORed Line (20): Wait_HCI_Command_Complete_VS_Start_VS_Lock_Event 5000, 0x00, 0xfe37, 0x00
    15:47:56.574 --
    15:47:56.574 *** Script End ***
    15:47:56.574 --
    15:49:52.272 ERROR - Timeout waiting for event HCI_Command_Complete_VS_Get_System_Status_Event
    15:49:52.272 ERRORed Line (1): Wait_HCI_Command_Complete_VS_Get_System_Status_Event 5000, any, HCI_VS_Get_System_Status, 0, 0, 0, 0, 0, 0, 0, 1, 1, 0, 0, 0, 0, 0, 0, 1, 0, 0x00, 0, 0x00, 0x00
    15:50:05.165 *** Script Started: "C:\Program Files (x86)\Texas Instruments\Wireless Tools\TIInit_11.8.32.txt" ***
    15:50:05.165 --
    15:50:05.165 Packet "HCI_VS_Start_VS_Lock", Opcode 0xfe37
    15:50:05.165 Parameters:
    15:50:05.165 | Major Version Number : 0x08
    15:50:05.165 | Minor Version Number : 0x20
    15:50:05.165 --
    15:50:05.165 Outgoing Dump:
    15:50:05.165     0000: 01 37 fe 02 08 20                               .7... 
    15:50:10.176 ERROR - File: "C:\Program Files (x86)\Texas Instruments\Wireless Tools\TIInit_11.8.32.txt", Line: 20
    15:50:10.179 ERROR - Timeout waiting for event HCI_Command_Complete_VS_Start_VS_Lock_Event
    15:50:10.179 ERRORed Line (20): Wait_HCI_Command_Complete_VS_Start_VS_Lock_Event 5000, 0x00, 0xfe37, 0x00
    15:50:10.187 --
    15:50:10.187 *** Script End ***
    15:50:10.187 --
    

  • Hi Jessica,

    The following is the "TIInit_11.8.32" file, can you help to confirm whether it is correct?

    TIInit_11.8.32.txt

  • Hi Jessica,

    "TIInit_11.8.32" file mentions, Use this script on Diamond ROM device only (FW v8.0.32), where can I check the FW version of Module?

    TKS !

  • Hi Jessica,

    When Module enters Test Mode, does it need to burn a different FW or use another command?

    TKS !

  • Hi Jessica,

    The BLE of this Module has several working modes. How do they switch between working modes.

    TKS !

  • Hi Colin,

    First could you confirm that you sent the "Get_System_Status" command once? To send the command make sure to double click on the command once, the command should not need to be run in a script.  I recommend you add this command to "my shortcuts" for ease of use (see 4.3.2.2 "Executing a Single Command" in the HCITester Tool User Guide, Lit# SWRU136). See image below:

     

    As mentioned in section 3.2 of the HCI Tester Guide have you replaced ALL the "5000, 0x00" with  "5000, any" then saved that script as a new initialization file in .txt format? Once you have done that running the initialization script once will download the FW and in general initialize the module.

    Let me know if you have more issues or questions on the matter.

    BR, 

    Jessica M. Torres

  • Hi Jessica,what should i do if the device without reply any message after i send the command "get system status"?

  • Hi Collin,

    Could you run the same command but make sure you are connected to the device using the BT_HCI_RX and  BT_HCI_TX pins (53 and 52 respectfully) ?

    BR, 

    Jessica M. Torres

  • Hi Jessica,

    Thanks for your support. Finally the HCI tester was able to talk to the WL module. Attachment is the result. Please advise what Colin needs to do next.

    0221 Script log.txt0221 Trace log.txt0221bt4.2.txtTIInit_11.8.32BT4.2.bts

    Regards,

    Kien Nguyen

  • It seems you have been able to confirm that the device is communicating by running the "HCI_VS_Get_System_Status" command, which is great!  Although it seems they tried to run the the TIInit_11.8.32BT4.2.txt file (saved as "0221 Script log.txt" for the customer it seems) unsuccessfully? 

    Try successfully running the attached INI file :

     3252.TIInit_11.8.32.txt

    Once the Initialization Script has been successfully run they can use separate HCI commands on the device (see Section4.3.2.2 Executing a Single Command of the HCI Tester UserGuide) or run a new script with the desired HCI commands (see WiLinkTm 8.0 Bluetooth® Vendor-Specific HCI Command ). 

    BR,

    Jessica M. Torres

  • Hi Jessica,

    • The test is ready to begin normally.

  • That is great, if you have any more question or problems with the device I recommend you make a new E2E post. 

    BR, 

    Jessica M. Torres

  • Jessica,

    Thanks a lot for your support!

    Regards,

    Kien Nguyen

  • Of course! Do make a new post for any following question you have.

    BR, 

    Jessica M. Torres