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.

WL1837MOD: Bluetooth firmware hangs when first writing memory block in section NFC DMEM Init of the TIInit_11.8.32 script

Part Number: WL1837MOD
Other Parts Discussed in Thread: WL1837, OMAP-L138

WL1837MOD bluetooth firmware initialization hangs (no response) consistently at the first memory write of section NFC DMEM Init (regardless UART speed, tried 115200, 460800, 921600, 3000000):

#------------------ End of Platform specific Init -------------------------------
#------------------ NFC DMEM Init -----------------------------------------------

#--------------------------------------------------------------------------------
#--------------------------------------------------------------------------------
Send_HCI_VS_Write_Memory_Block 0xFF05, 0x20040300, 0x20, "03:21:76:20:C0:46:C0:46:04:22:40:1C:C0:46:C0:46:C0:46:C0:46:C0:46:C0:46:C0:46:C0:46:C0:46:C0:46"
Wait_HCI_Command_Complete_VS_Write_Memory_Block_Event 5000, 0x00, 0xff05, 0x00

The firmware is lately downloaded from TI's website, but it's the same with old version:

TIInit_11.8.32.bts

#--------------------------------------------------------------------------------
# Description : 185x/189x PG2 ROM Initialization Script
#
# Compatibility : 185x/189x 8.0.32 ROM
#
# Last Updated : 24-Jul-2018 14:40:04
#
# Version : TI_P2.143
#
#
#
#
# 185x LMP Subversion : ac8f
# 189x LMP Subversion : b08f
#
# Notes : Use this script on Diamond ROM device only (FW v8.0.32)
#--------------------------------------------------------------------------------

Appreciate for a fix on this.

By the way, why is there a NFC DMEM Init section in the script? does WL1837MOD support NFC features?

Shengchu

  • Humm.. That is strange.. What is your exact Wilink part number and are you using with BlutopiaPM or Bluez?

    Thanks
  • Thanks for reply, Hari.

    We're using BlueZ 5.49

    The version numbers are below:

    HCI Version 4.2 (0x8) - Reversion 0 (0x0000)
    LMP Version 4.2 (0x8) - Subversion (0xac0f)

    Hanging may mean slow processing inside bluetooth chip WL1837MOD, it seems WL1837MOD doesn't work on hardware flow control, the RTS line is only toggled through enable pin, if enabled, RTS is low, if disabled, RTS is high, during initialization, RTS stays low regardless what UART speed is, RTS never turns high.

    Shengchu
  • Humm.. The default HCI configuration on WL1837 does use hardware flow control (H4). What is your Host processor? Please ensure, UART hardware flowcontrol is supported/configured and the baudrates 3M is supported..

    Thanks
  • Thanks Hari,

    this is not on host side (host is OMAP-L138), when hanging, both RTS and CTS stay low, after host sent first NFC DMEM INIT command to WL1837MOD, receives nothing. Right now I did a workaround by delay 100 ms on each command in this block, but it adds unexpected initialization time. It seems this issue is specific to NFC DMEM INIT.

    Shengchu
  • Is it on a custom board? Or, are you using WL18xx COM8 module? What is the exact WL18xx part number, you are using? We, have n't seen any issue when testing with WL18xx COM8 with AM35x/AM47x EVM boards..

    Thanks
  • Hi Nari,

    the following version info is read from the chip:
    HCI version: Bluetooth 4.2 (0x08) - Revision 0 (0x0000)
    LMP version: Bluetooth 4.2 (0x08) - Subversion 44047 (0xac0f)
    Manufacturer: Texas Instruments Inc. (13)

    Shengchu
  • I tried on AM335x BeagleBone with Bleuz 5.46 and do not see any issue:

    _____                    _____           _         _  

    |  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_

    |     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|

    |__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|  

                 |___|                    |___|            

    Arago Project am335x-evm ttyS0

    Arago 2018.04 am335x-evm ttyS0

    am335x-evm login: root

    root@am335x-evm:~#

    root@am335x-evm:~#

    root@am335x-evm:~#

    root@am335x-evm:~# hciattach /dev/ttyS1 texas 3000000

    Found a Texas Instruments' chip!

    Firmware file : /lib/firmware/ti-connectivity/TIInit_11.8.32.bts

    Loaded BTS script version 1

    texas: changing baud rate to 3000000, flow control to 1

    [   76.065746] Bluetooth: Core ver 2.22

    [   76.082112] NET: Registered protocol family 31

    [   76.086607] Bluetooth: HCI device and connection manager initialized

    [   76.102923] Bluetooth: HCI socket layer initialized

    [   76.107847] Bluetooth: L2CAP socket layer initialized

    [   76.116930] Bluetooth: SCO socket layer initialized

    [   76.133701] Bluetooth: HCI UART driver ver 2.3

    [   76.144706] Bluetooth: HCI UART protocol H4 registered

    [   76.151681] Bluetooth: HCI UART protocol LL registered

    [   76.169816] Bluetooth: HCI UART protocol Three-wire (H5) registered

    Device setup complete

    root@am335x-evm:~#

    root@am335x-evm:~# bluetoothctl --version

    5.46

    root@am335x-evm:~#

    I am also attaching the BTS file used.. It is from the TI processor SDK..TIInit_11.8.32.bts

  • Hi,

    We, have n't heard from you.. Did, you get the issue fixed? If not, please raise a new ticket..

    Thanks