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.

Linux/WL1831MOD: Unable to configure Bluetooth with hcitool consistently

Part Number: WL1831MOD

Tool/software: Linux

Hello,

We are using WL18MODGB in our device and as part of FCC testing we need to configure BT in different modes.

For this we are following http://processors.wiki.ti.com/index.php/WL18xx_Bluetopia_PM_Bluetooth_RF_Testing webpage and using hcitool to run commands on our Yocto platform

When we run commands as per the suggestion in the wiki page, we do not get the respective Channel set/enabled in spectrum analyzer consistently.

Sometimes the same set of commands enables/activate the channel and sometimes same set of commands does not enable/activate the channel.

Below are the commands used for different configurations. Please let us know if there is anything missed here and let us know what might be the issue.

-------------------------------------------------------------------

bt_config_ch00_1mbps.sh

------------

hcitool cmd 0x3f 0x10c 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0x64

hcitool cmd 0x01 0x001 0x33 0x8b 0x9e 0x04 0x00

hcitool cmd 0x03 0x001a 0x00
hcitool cmd 0x3f 0x01fb 0x01 0xff 0x00 0x00 0x00 0x00 0x01
hcitool cmd 0x3f 0x01ca 0x62 0x09 0x01 0x00 0x07 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00

-------------------------------------------------------------------

-------------------------------------------------------------------

bt_config_ch78_1mbps.sh

---------------------

hcitool cmd 0x3f 0x10c 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0x64

hcitool cmd 0x01 0x001 0x33 0x8b 0x9e 0x04 0x00

hcitool cmd 0x03 0x001a 0x00
hcitool cmd 0x3f 0x01fb 0x01 0xff 0x00 0x00 0x00 0x00 0x01
hcitool cmd 0x3f 0x01ca 0xB0 0x09 0x01 0x00 0x07 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00

-------------------------------------------------------------------

-------------------------------------------------------------------

bt_stopcnt.sh - Stop Tx on BT

--------------------------

hcitool cmd 0x3f 0x0301 0x44 0x40 0x01 0x20 0x10 0x00
hcitool cmd 0x3f 0x0301 0x48 0x40 0x01 0x20 0x14 0x00
hcitool cmd 0x3f 0x0301 0x0c 0x90 0x01 0x20 0x00 0x00

-------------------------------------------------------------------

Please let us know how we can enable different channels with different datarate consistently

Thanks,

Vijay

  • Vijaya,

    Can you please share a FW logger output and a sniffer log?

    The best way to test BT on Wlink is via RS232 and HCITester, but this is on Windows. Are you able to switch?

    BR,

    Seong

  • Hi Seong,

    We are using the WL18MODGB module built in the VAR-SOM-MX6 SOM module readily available. Unfortunatley the SOM manufacturer hasnt provided Hardware access to RS232 ports on the SOM module. So we are left with command line interface for accessing Wilink.

    Can you please let me know how to get FW logger/Sniffer log? As mentioned above we do not have access to BT_UART_DBG pin on the hardware. Is there a way to get the logs in Linux (Yocto) using hcitool or other commands?

    Below is the response I get when I try to select a 00 channel as per commands in TI wiki page

    -------------------------------------------------------------------

    Commands

    -------------------------------------------------------------------

    hcitool cmd 0x3f 0x10c 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0x64

    hcitool cmd 0x01 0x001 0x33 0x8b 0x9e 0x04 0x00

    hcitool cmd 0x03 0x001a 0x00
    hcitool cmd 0x3f 0x01fb 0x01 0xff 0x00 0x00 0x00 0x00 0x01
    hcitool cmd 0x3f 0x01ca 0x62 0x09 0x01 0x00 0x07 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00

    -------------------------------------------------------------------

    Response -- seems to be proper as I get 0x0e in HCI event

    -------------------------------------------------------------------

    < HCI Command: ogf 0x3f, ocf 0x010c, plen 8
    00 00 FF FF FF FF FF 64
    > HCI Event: 0x0e plen 4
    01 0C FD 00
    < HCI Command: ogf 0x01, ocf 0x0001, plen 5
    33 8B 9E 04 00
    > HCI Event: 0x0f plen 4
    00 01 01 04
    < HCI Command: ogf 0x03, ocf 0x001a, plen 1
    00
    > HCI Event: 0x0e plen 4
    01 1A 0C 00
    < HCI Command: ogf 0x3f, ocf 0x01fb, plen 7
    01 FF 00 00 00 00 01
    > HCI Event: 0x0e plen 4
    01 FB FD 00
    < HCI Command: ogf 0x3f, ocf 0x01ca, plen 13
    62 09 01 00 07 00 00 00 00 00 00 00 00
    > HCI Event: 0x0e plen 4
    01 CA FD 00

    -------------------------------------------------------------------------------

    Thanks,

    Vijay 

  • Vijay,

    Please disregard my request to share a sniffer log as this is actually not applicable with this issue.

    Are you using the latest service pack, version 4.3? -> http://www.ti.com/tool/WL18XX-BT-SP

    If not, please try this one first.

    If the latest service pack is being used, it would be good to have the FW log. Follow this user's guide: http://www.ti.com/lit/ug/swau058d/swau058d.pdf

    Could you also share the btsnoop as well?

    BR,

    Seong

  • Hi Seong,

    Yes, we are using latest service pack version 4.3 and I see that TIInit_11.8.32.bts is loaded with hciattach.

    As mentioned in my previous response, we do not have hardware level access to BT_UART_DBG/TX_DBG pins. So its not possible for us to get FW logs from BTLogger windows application. Is it possible to get FW logs in linux?

    I have attached the BTSnoop log I got from btmon captured during configuration of BT module for continous TX.

    Please let me know if this is enough.

    Thanks,

    Vijay

    btsnoop��h��P4N��}k,hci0--�h��qW�>+���3�,�	 �d�[z�d���"�l��w'T���--�h��u>+ut �4�	 p`ND�x*n>?���*�~��q�--�h���0�>+a�.{)� {po��+�E��\����i��J��--�h��a,>+�{=d�,�	 E8#$��>�\���R��G�
    L[���h��~Q������d�h��~0p��h��~f3���h��~i��h��~�f�h��~�
    
    �h��~�^����h��~����h�����
    b	�h��!��		�h����U�D@ �h����/�		�h���-j�H@ �h���0��		�h���c��� �h���e���h��[u*������d�h��[wK��h��[�:3���h��[�/�h��[��h��[�
    
    �h��\#�����h��\/����h��\c���
    �	�h��\g����h�ש��

  • Hi Vijaya,

    Apologies for getting back to you late. Thank you for sharing the log, I will look into this and reply back shortly.

    BR,

    Seong

  • Vijaya,

    From your BTSnoop log, I see that your system seems to be doing LE scans in the background while the rest of your script is being run. This may be what is causing your device to be intermittent. Try stopping all background activities.

    Try running the following command to turn off all background activities:

    hcitool cmd 0x03 0x0003

    This is the "Send_HCI_Reset" command. Then implement a 10 second delay before running the rest of the scripts.

    BR,

    Seong

  • Thanks, this resolved the issue.