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.

Wl1835 chipset/interface misbehavior

hi:

 An error occurred when I received a file larger than 6M.

Reduce the baud rate from 3000000 to 1000000,the error still happen.

log:

root@zynq:~# (stc): chip/interface misbehavior dropping frame starting with 0xea
Bluetooth: bad checksum in packet
(stc): chip/interface misbehavior dropping frame starting with 0x00
(stc): chip/interface misbehavior dropping frame starting with 0x00
(stc): chip/interface misbehavior dropping frame starting with 0xbc
(stc): chip/interface misbehavior dropping frame starting with 0x00
(stc): chip/interface misbehavior dropping frame starting with 0xef
(stc): chip/interface misbehavior dropping frame starting with 0x00
(stc): chip/interface misbehavior dropping frame starting with 0xfb
(stc): chip/interface misbehavior dropping frame starting with 0x00


  • Hello Wayen Zhang,

    can you please add some more details?

    Is everything works as expected when receiving a smaller file?
    Does the system crash? or the chip is still functional?

    Can you please add FW logs, sniffer logs and driver logs.

    BR,
    Chen Loewy
  • hi chen:
    smaller than 6M is ok.
    uim log:

    uim:read 1 from install
    uim:@ st_uart_config
    uim: signal received, opening /dev/ttyS3
    uim:@ set_baud_rate
    uim:set_baud_rate() done
    uim:Setting speed to 3000000
    uim:@ read_command_complete
    uim: Command complete started
    uim:@ read_hci_event
    uim: read_hci_event
    uim:Command complete done
    uim:Speed changing to 3000000, 1
    uim:@ set_custom_baud_rate
    uim:Installed N_TI_WL Line displine
    uim:begin polling...

    uim state looks no error.

    driver log :
    (stc): chip/interface misbehavior dropping frame starting with 0xe5
    Bluetooth: bad checksum in packet
    (stc): chip/interface misbehavior dropping frame starting with 0x48
    (stc): chip/interface misbehavior dropping frame starting with 0x7b
    (stc): chip/interface misbehavior dropping frame starting with 0xb8
    (stc): chip/interface misbehavior dropping frame starting with 0x34
    (stc): chip/interface misbehavior dropping frame starting with 0x4e
    (stc): chip/interface misbehavior dropping frame starting with 0x95
    (stc): chip/interface misbehavior dropping frame starting with 0x54
    (stc): chip/interface misbehavior dropping frame starting with 0x4e
    (stc): chip/interface misbehavior dropping frame starting with 0xfa
    (stc): chip/interface misbehavior dropping frame starting with 0xe7
    (stc): chip/interface misbehavior dropping frame starting with 0xa5
    (stc): chip/interface misbehavior dropping frame starting with 0x88
    (stc): chip/interface misbehavior dropping frame starting with 0xda

    Is the uart problem?

    If the baud rate is set to 115200, receive more than 6M of the file is ok .

  • Hello Wayen Zhang,

    Without FW logs it's hard for me to find the root cause.

    Most likely you are correct and it's a baud rate issue.
    can you please try 921600 and let me know if that works?

    BR,
    Chen Loewy
  • HI chen:

    could U tell me how to print FW log?

    921600 also failed····:(

  • Hello Wayen Zhang,

    You will need to do the following:

    1. Dependent on the board you are using. Look at the schematics, Connect the BT_DEBUG pin GPIO.

    2. Download the logger tool -
    you can download all tools from the following link: www.ti.com/.../WILINK-BT_WIFI-WIRELESS_TOOLS

    3. Configure the logger using the correct .xml and .ili files (should be part of the package of the .bts file you use for BT).

    4. Once everything is setup correctly the logs will start showing up on the logger tool.

    Thanks,
    Chen Loewy
  • Hello Wayen,

    I went over the log file.

    What i can see is the following:

    1. For some reason you download the initscript twice (no idea why do you do that) so please make sure you only download the initscript once.

    2. We start receiving a file - and after the first few packets we stop receiving any data. 

    3. The only suspect i have which i can see in the log file is the AFH - (automatic frequency hopping).

    Please try adding the following commands to the end of your init script.

    # Disable AFH Master

    Send_HCI_VS_Set_Supported_Features 0xFF26, 0x05, 0x03, 0x00

    Wait_HCI_Command_Complete_VS_Set_Supported_Features_Event 5000, 0x00, 0xff26, 0x00

     

    # Disable AFH Classification Master

    Send_HCI_VS_Set_Supported_Features 0xFF26, 0x05, 0x04, 0x00

    Wait_HCI_Command_Complete_VS_Set_Supported_Features_Event 5000, 0x00, 0xff26, 0x00

     

    #Command to disable AFH channel assessment :

    Send_HCI_Write_AFH_Channel_Assessment_Mode 0x00

    Wait_HCI_Command_Complete_Write_AFH_Channel_Assessment_Mode_Event 5000, 0x00, 0x0c49, 0x00

     

    # Disable AFH Slave

    Send_HCI_VS_Set_Supported_Features 0xFF26, 0x04, 0x03, 0x00

    Wait_HCI_Command_Complete_VS_Set_Supported_Features_Event 5000, 0x00, 0xff26, 0x00

     

    # Disable AFH Classification Slave

    Send_HCI_VS_Set_Supported_Features 0xFF26, 0x04, 0x04, 0x00

    Wait_HCI_Command_Complete_VS_Set_Supported_Features_Event 5000, 0x00, 0xff26, 0x00

     

    please try.

    Thanks,

    Chen Loewy

  • hi chen:

    the first  time download bts  is  insmod btwilink.ko , second time  is hciconfig hci0 up;

    i add these codes but still fail.

    bts log:

    Untitled_afh.rar

  • hi chen:

    in the bts log ,i can not find LMP_SCO_link_req . 

    Want to achieve Bluetooth voice