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 on WL1837 and WL1807

Part Number: WL1837MOD
Other Parts Discussed in Thread: AM3354, WL1837, , WL1807MOD

Hi Everyone,


We are using AM3354 & WL1807 with Bluetopia and BlueZ to implement BLE and according to literature, the WL1837 could be used for that. However, we did some tests with the modules WL1807 & WL1837 with the next result:

  • WL1837MOD does NOT seem to support Bluetooth.
  • WL1807MOD appears to support both WiFi and Bluetooth. this is confusing since this is the opposite to what the literature suggests:

NOTES:

  • We have opened the modules and found them to be identical internally, so it's possible this is a TI firmware loading issue.
  • We did the tests with several units and the results are always the same

QUESTION:

  • any idea what may be happening?

Thanks!

  • The literature is definitely correct as to what is supported for each device, though they are from the same silicon.  I'll get one of our experts to chime in.  What is the method of determining it works/doesn't work?  Is the FW confirmed loaded?  What does the host logs say?

    Thanks,

    Travis

  • Hi Travis,

    We have been using BlueZ, when I use the WL1807MOD and activate the Bluetooth and then do the scan (using the commands hciattach -t 5000 /dev/ttyO1 texas 3000000 flow and hcitool lescan --passive & hcidump --raw) the results are as follows:

    • WL1807MOD

              

           The Bluetooth runs successfully with the WL1807MOD and responds to HCI commands.

    Following the same procedure by using the WL1837MOD, no response is received:

    • WL1837MOD

            

           Communication with WL1837MOD is not running.

    Question: What is the procedure to confirm that FW is ok?

    Regards!

  • Did, you assert the BT_EN GPIO, before exercising hciattach? I would typically recommend doing the assert/deassert couple of times, before invoking hciattach.

    ex:

    echo 1 > /sys/class/gpio/gpioxx/value

    echo 0 > /sys/class/gpio/gpioxx/value

    sleep 1;

    echo 1 > /sys/class/gpio/gpioxx/value

    echo 0 > /sys/class/gpio/gpioxx/value

    hciattach /dev/ttyO1 texas ..