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.

WL1831MOD: fw file with lower baud rate

Part Number: WL1831MOD
Other Parts Discussed in Thread: WL1831, AM3352

Hi TI,

We have an AM3352 custom borad with WL1831. We have porting the driver and dts (uart with cts and rts) and put firmware files in system.

The bluetooth function works. It's OK to transmit data through bluetooth but lost data of package while receiving data through bluetooth.
[Thu Feb 02 16:49:52.183 2023] aaeon@SRG-3352C:~$ sudo nmcli radio wifi offl2test -R -r
[Thu Feb 02 16:49:53.460 2023] l2test[1516]: Waiting for connection on psm 4113 ...
[Thu Feb 02 16:49:55.791 2023] l2test[1518]: Connect from 00:1A:7D:DA:71:15 (bredr, psm 4113, dcid 64)
[Thu Feb 02 16:49:55.804 2023] [ 1569.201763] Bluetooth: hci0: Frame reassembly failed (-90)
[Thu Feb 02 16:49:55.809 2023] [ 1569.202101] Bluetooth: hci0: Frame reassembly failed (-84)
[Thu Feb 02 16:49:55.809 2023] [ 1569.202395] Bluetooth: hci0: Frame reassembly failed (-84)
[Thu Feb 02 16:49:55.809 2023] [ 1569.202422] Bluetooth: hci0: Frame reassembly failed (-84)
[Thu Feb 02 16:49:55.809 2023] [ 1569.202743] Bluetooth: hci0: Frame reassembly failed (-84)
[Thu Feb 02 16:49:55.809 2023] [ 1569.203963] Bluetooth: hci0: Frame reassembly failed (-84)
[Thu Feb 02 16:49:55.810 2023] l2test[1518]: Local device 0C:1C:57:83:75:36 (bredr, psm 4113, scid 64)
[Thu Feb 02 16:49:55.810 2023] l2test[1518]: Options [imtu 672, omtu 672, flush_to 65535, mode 0, handle 1, class 0x1c0104, priority 0, rcvbuf 180224]
[Thu Feb 02 16:49:55.810 2023] l2test[1518]: Receiving ...
[Thu Feb 02 16:49:55.810 2023] l2test[1518]: seq mismatch: 0 -> 1
[Thu Feb 02 16:49:55.810 2023] l2test[1518]: data mismatch: byte 645 0x00
[Thu Feb 02 16:49:55.815 2023] l2test[1518]: 672 bytes in 0.00 sec, 378.02 kB/s
[Thu Feb 02 16:49:55.816 2023] [ 1569.211274] Bluetooth: hci0: Frame reassembly failed (-84)
[Thu Feb 02 16:49:55.816 2023] [ 1569.211395] Bluetooth: hci0: Frame reassembly failed (-84)
[Thu Feb 02 16:49:55.816 2023] [ 1569.211652] Bluetooth: hci0: Frame reassembly failed (-84)
[Thu Feb 02 16:49:55.816 2023] [ 1569.211883] Bluetooth: hci0: Frame reassembly failed (-84)
[Thu Feb 02 16:49:55.816 2023] [ 1569.211894] Bluetooth: hci0: Frame reassembly failed (-84)
[Thu Feb 02 16:49:55.816 2023] [ 1569.212119] Bluetooth: hci0: Frame reassembly failed (-84)
[Thu Feb 02 16:49:55.817 2023] [ 1569.212353] Bluetooth: hci0: Frame reassembly failed (-84)
[Thu Feb 02 16:49:55.817 2023] [ 1569.212586] Bluetooth: hci0: Frame reassembly failed (-84)
[Thu Feb 02 16:49:55.817 2023] [ 1569.212840] Bluetooth: hci0: Frame reassembly failed (-84)
[Thu Feb 02 16:49:55.817 2023] [ 1569.213081] Bluetooth: hci0: Frame reassembly failed (-84)
[Thu Feb 02 16:49:55.817 2023] [ 1569.213316] Bluetooth: hci0: Frame reassembly failed (-84)
[Thu Feb 02 16:49:55.817 2023] [ 1569.216417] Bluetooth: hci0: Frame reassembly failed (-84)
[Thu Feb 02 16:49:55.834 2023] [ 1569.216564] Bluetooth: hci0: Frame reassembly failed (-84)
[Thu Feb 02 16:49:55.834 2023] [ 1569.216815] Bluetooth: hci0: Frame reassembly failed (-84)
[Thu Feb 02 16:49:55.834 2023] [ 1569.217052] Bluetooth: hci0: Frame reassembly failed (-84)
[Thu Feb 02 16:49:55.834 2023] [ 1569.217291] Bluetooth: hci0: Frame reassembly failed (-84)
[Thu Feb 02 16:49:55.834 2023] [ 1569.217545] Bluetooth: hci0: Frame reassembly failed (-84)

I found the baud rate config in firmware is 3M. I try to modify the TIInit_11.8.32.bts but cannot open it.


BTW, bluetooth works with fw wl18xx_bt_sp_v4.7 but fails with wl18xx_bt_sp_v4.8.
Could you give me a firmware with lower baud rate of wl18xx_bt_sp_v4.7?
Thank you.

Best Regards,
Sophie

  • Hi Sophie,

    Let me look into getting a v4.7 lower baud rate version, I will update this thread once it's completed.

    Best Regards,

    Daniel

  • Hi Sophie, 

    Please try the attached .bts file. I've lowered the baud rate to 921600. If this works you can update the baud rate in the initialization script using Script Pad.https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/968/0878.TIInit_5F00_11.8.32.bts

  • Hi Daniel,

    Thank you. This firmware is very helpful. It reduces the package data lost rate.
    However, if it receives for a little bit longer, "Frame reassembly failed (-84)" still occurs and it still losts data of package.
    I want to test reducing baud to 115200.
    I open the dts file in ScriptPad and modify baud to 115200 but cannot save file.
    Besides, I cannot see any other command from your screenshot in my ScriptPad, is it correct?

    Best Regards,
    Sophie

  • Hi Sophie, 

    That is indeed one of the correct commands. In order to see the others in the file, go to View in the Menu > Options > HCI Library Path and click the 3 dots on the side to browse for the HCI library file. Please select the TIInit_11.8.32.xml file that came with the service pack. 

    After doing so, you should be able to see other commands in the init file, in this case the other you need to change is

    Send_HCI_VS_Update_Uart_HCI_Baudrate 0xFF36, 0x000e1000

    The second parameter is the 8 digit hex number, in the case of 115200 it would be 0x0001C200.

  • Hi Daniel,

    I modify the bts file like this, but the bluetooth cannot be established. Is that correct? Would you give me a bts file with baud 115200?

    Best Regards,
    Sophie

  • Hi Sophie, I believe those commands should be fine. To sanity check, the bluetooth was able to be established with the previous step down in baud rate (921600)? Regardless, I've attached another copy of the BTS file, now set for 115200.

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/968/5545.TIInit_5F00_11.8.32.bts

  • Hi Daniel,

    Thanks for quicklly reply. The BT cann't establish with 5545.TIInit_11.8.32.bts(115200) either, but it can establish with previos bts file 0878.TIInit_11.8.32.bts(921600). Maybe wl1831 can't establish in any baud rate? Since data lost rate decreases in 921600 but still exists, is there any baud rate as lower as possible that wl1831 can use and give me a bts file? I want to verify if lost data issue can be solved by lower baud rate first.
    Thank you.

    Best Regards,
    Sophie

  • Hi Sophie, 

    It's odd that BT cannot establish at 115200 as that should be the default: 

    Could you try removing the Send_HCI_VS_Update_Uart_HCI_Baudrate and Wait_HCI_Command_Complete_VS_Update_Uart_HCI_Baudrate_Event commands from the BTS script? If that does not work try removing the COM_SetParams command as well?

    Hopefully we will boot into 115200 and it'll stay as is. Please attempt those changes and let me know the results.

  • Hi Daniel,

    It is the same. The bluetooth connection still cannot be established in 115200.

    BTW, I also test baud rate 460800, 230400, 9600, and 4800. All of them fail.
    I attach by this command:
    /usr/bin/hciattach /dev/ttyS5 texas 115200 flow

    Best Regards,
    Sophie

  • Hi Sophie,

    I will try to run the initialization scripts on my end in case there to double-check the script itself is fine. In the meantime if you could collect logs that might help point us in the right direction as to why the issue occurs. Here is a link to the Wilink Software guide: https://www.ti.com/lit/ug/swru415a/swru415a.pdf 

  • Hi Sophie, update on my end, I was able to run the TI Demos on our evaluation platform using the BTS script so at least on its own the BTS script I sent is fine. One other thing to check would be whether the correct power up sequence is being fed to the device as detailed in the datasheet: WL18x1MOD, WL18x5MOD WiLinkTm 8 Single-Band Combo Module – Wi-Fi®, Bluetooth®, and Bluetooth Low Energy (LE) datasheet (Rev. N) (ti.com)