COM6L-T5 (WL1273L module) not working on AM335x EVM

Hi Piero,

Have you tried using the same old kernel configuration from WL1271 on WL1273? I believe modification on kernel isn't necessary for these two devices, since they are both in the WL6 family.

Edit: Also, can you please try with command line connection first and provide the console output? What messages do you see?

Hello Victor,

yes, I tried the stock SDK kernel with the WL1273 module, but it doesn't work either.

Here are some console messages, I tried launching the bluetooth demo script (messages are exactly the same with both kernel configurations):

....

INIT: version 2.88 booting
Starting udev
[    3.726196] Disabling lock debugging due to kernel taint
[    5.871673] cfg80211: Calling CRDA to update world regulatory domain
[    6.016662] wl12xx: driver version: ol_R5.SP4.01-dirty
[    6.022033] wl12xx: compilation time: Thu Apr  4 23:57:00 2013
[    6.164428] cfg80211: World regulatory domain updated:
[    6.169860] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[    6.178619] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[    6.186889] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[    6.195129] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[    6.203399] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[    6.211669] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[    6.463989] wl12xx: loaded

.....

Performing wifi calibration...
[   28.248229] wl12xx: loaded
[   28.252075] wl12xx: power up
[   28.707763] wl12xx: firmware booted in PLT mode (PLT 6.3.10.0.135)
Using nvs version 2.1
Calibrate /lib/firmware/ti-connectivity/wl1271-nvs.bin
Fail to calibrat[   28.757415] wl12xx: power down
e ith radio status (-36)
Writing mac address 00:00:00:00:00:00 to file /lib/firmware/ti-connectivity/wl1271-nvs.bin
Calibration done. FEM1 has 1 bands. AutoFEM is off. Resulting nvs is /lib/firmware/ti-connectivity/wl1271-nvs.bin
[   29.398132] wl12xx: loaded

.....

am335x-evm login:

root@am335x-evm:~# uname -a
Linux am335x-evm 3.2.0 #1 Thu Apr 4 23:52:23 CDT 2013 armv7l GNU/Linux

root@am335x-evm:~# cd /usr/share/wl1271-demos/bluetooth/scripts/
root@am335x-evm:/usr/share/wl1271-demos/bluetooth/scripts# ./BT_Demo.sh
Starting BT Demo .......
[  134.377014] Bluetooth: Core ver 2.16
[  134.380920] NET: Registered protocol family 31
[  134.385559] Bluetooth: HCI device and connection manager initialized
[  134.392211] Bluetooth: HCI socket layer initialized
[  134.397338] Bluetooth: L2CAP socket layer initialized
[  134.402618] Bluetooth: SCO socket layer initialized

/*
 * #################################################
 *                  Cleaning BT
 * #################################################
 */
 


!!!!!!!!!!! Start from the MAIN MENU !!!!!!!!!!!!!!!!!

/*
 * #############################################[  134.481414] Gpio value is :117
####
 *                  Initialize BT
 * #################################################
 */
 
[  134.497283] WL1271: BT Enable
Found a Texas Instruments' chip!
Firmware file : /lib/firmware/TIInit_7.6.15.bts
Loaded BTS script version 1
texas: changing baud rate to 3000000, flow control to 1
[  143.661743] Bluetooth: RFCOMM TTY layer initialized
[  143.666900] Bluetooth: RFCOMM socket layer initialized
[  143.672332] Bluetooth: RFCOMM ver 1.11

+++++++++++++++++++++++++++++++++++++++++++++++++++++
               MAIN NENU
+++++++++++++++++++++++++++++++++++++++++++++++++++++
    1 - BT Scan Remote Devices
    2 - BT Get capabilities of Remote Device
    3 - OPP  Test
    4 - FTP  Test
    5 - HID  Test
    6 - HSP  Test
    7 - A2DP Test
    8 - AVRCP Test
    9 - Pair Remote Device
    10 - Unpair Remote Device
    11 - Exit Without BT Shut Down
    12 - Exit With BT Shut Down
====> Initialization timed out.

Launching dmesg I get:

[  134.377014] Bluetooth: Core ver 2.16
[  134.380920] NET: Registered protocol family 31
[  134.385559] Bluetooth: HCI device and connection manager initialized
[  134.392211] Bluetooth: HCI socket layer initialized
[  134.397338] Bluetooth: L2CAP socket layer initialized
[  134.402618] Bluetooth: SCO socket layer initialized
[  134.481414] Gpio value is :117
[  134.497283] WL1271: BT Enable
[  143.661743] Bluetooth: RFCOMM TTY layer initialized
[  143.666900] Bluetooth: RFCOMM socket layer initialized
[  143.672332] Bluetooth: RFCOMM ver 1.11
[  863.868927] WL1271: BT Disable

When I switch to the WL1271 module (without any other modification), the BT_Demo.sh scripts returns the following messages:

Starting BT Demo .......
[   97.796997] Bluetooth: Core ver 2.16
[   97.800903] NET: Registered protocol family 31
[   97.805541] Bluetooth: HCI device and connection manager initialized
[   97.812194] Bluetooth: HCI socket layer initialized
[   97.817291] Bluetooth: L2CAP socket layer initialized
[   97.822601] Bluetooth: SCO socket layer initialized

/*
 * #################################################
 *                  Cleaning BT
 * #################################################
 */
 


!!!!!!!!!!! Start from the MAIN MENU !!!!!!!!!!!!!!!!!

/*
 * #############################################[   97.901702] Gpio value is :117
####
 *                  Initialize BT
 * #################################################
 */
 
[   97.917266] WL1271: BT Enable
Found a Texas Instruments' chip!
Firmware file : /lib/firmware/TIInit_7.6.15.bts
Loaded BTS script version 1
texas: changing baud rate to 3000000, flow control to 1
[  100.009582] Bluetooth: HCI UART driver ver 2.2
[  100.014251] Bluetooth: HCI H4 protocol initialized
[  100.019317] Bluetooth: HCI BCSP protocol initialized
[  100.024505] Bluetooth: HCILL protocol initialized
[  100.104583] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[  100.110229] Bluetooth: BNEP filters: protocol multicast
[  100.139739] Bluetooth: RFCOMM TTY layer initialized
[  100.144897] Bluetooth: RFCOMM socket layer initialized
[  100.150299] Bluetooth: RFCOMM ver 1.11
Device setup complete

So, it seems that, with the WL1273 module, the HCI UART driver is not loaded, and this leads to the "Initialization timed out." message.

Any help will be greatly appreciated.

Thanks and best regards.

Piero

Hi Piero,

My mistake, according to this wiki page, you need to modify the clock speed for WL1273 device.

First of all, you are using wl1273 indicates that you want to use the 5GHz band, right? It looks like the device is not correctly configured. Can you please try the wiki instruction in this page, and make sure that you are doing the calibration manually? The default TQS_S_2.6.ini is for WL1271, but you need to use the TQS_D_1.7.ini file.

I'm suspecting that if WiFi isn't correctly configured, BT won't work either.

Victor, John,

first of all thanks for your suggestions.

I changed the calibration .ini file for WiFi and the bts file for bluetooth as per your posts. I'm using the kernel I patched with the fast clock modification described in the wiki. I see some improvements, but still it's not working as expected.

Regarding wifi, I get:

root@am335x-evm:/usr/share/wpa_gui# iwconfig wlan0
wlan0     IEEE 802.11abgn  ESSID:off/any  
          Mode:Ad-Hoc  Cell: Not-Associated   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on

root@am335x-evm:/usr/share/wpa_gui# iw phy2 info
Wiphy phy2
        Band 1:
                Capabilities: 0x130
                        HT20
                        Static SM Power Save
                        RX Greenfield
                        RX HT20 SGI
                        RX STBC 1-stream
                        Max AMSDU length: 3839 bytes
                        No DSSS/CCK HT40
                Maximum RX AMPDU length 8191 bytes (exponent: 0x000)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT TX/RX MCS rate indexes supported: 0-7
                Frequencies:
                        * 2412 MHz [1] (20.0 dBm)
                        * 2417 MHz [2] (20.0 dBm)
                        * 2422 MHz [3] (20.0 dBm)
                        * 2427 MHz [4] (20.0 dBm)
                        * 2432 MHz [5] (20.0 dBm)
                        * 2437 MHz [6] (20.0 dBm)
                        * 2442 MHz [7] (20.0 dBm)
                        * 2447 MHz [8] (20.0 dBm)
                        * 2452 MHz [9] (20.0 dBm)
                        * 2457 MHz [10] (20.0 dBm)
                        * 2462 MHz [11] (20.0 dBm)
                        * 2467 MHz [12] (20.0 dBm) (passive scanning, no IBSS)
                        * 2472 MHz [13] (20.0 dBm) (passive scanning, no IBSS)
                        * 2484 MHz [14] (20.0 dBm) (passive scanning, no IBSS)
                Bitrates (non-HT):
                        * 1.0 Mbps
                        * 2.0 Mbps (short preamble supported)
                        * 5.5 Mbps (short preamble supported)
                        * 11.0 Mbps (short preamble supported)
                        * 6.0 Mbps
                        * 9.0 Mbps
                        * 12.0 Mbps
                        * 18.0 Mbps
                        * 24.0 Mbps
                        * 36.0 Mbps
                        * 48.0 Mbps
                        * 54.0 Mbps
        Band 2:
                Capabilities: 0x130
                        HT20
                        Static SM Power Save
                        RX Greenfield
                        RX HT20 SGI
                        RX STBC 1-stream
                        Max AMSDU length: 3839 bytes
                        No DSSS/CCK HT40
                Maximum RX AMPDU length 8191 bytes (exponent: 0x000)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT TX/RX MCS rate indexes supported: 0-7
                Frequencies:
                        * 5035 MHz [7] (disabled)
                        * 5040 MHz [8] (disabled)
                        * 5045 MHz [9] (disabled)
                        * 5055 MHz [11] (disabled)
                        * 5060 MHz [12] (disabled)
                        * 5080 MHz [16] (disabled)
                        * 5170 MHz [34] (disabled)
                        * 5180 MHz [36] (20.0 dBm) (passive scanning, no IBSS)
                        * 5190 MHz [38] (20.0 dBm) (passive scanning, no IBSS)
                        * 5200 MHz [40] (20.0 dBm) (passive scanning, no IBSS)
                        * 5210 MHz [42] (20.0 dBm) (passive scanning, no IBSS)
                        * 5220 MHz [44] (20.0 dBm) (passive scanning, no IBSS)
                        * 5230 MHz [46] (20.0 dBm) (passive scanning, no IBSS)
                        * 5240 MHz [48] (20.0 dBm) (passive scanning, no IBSS)
                        * 5260 MHz [52] (disabled)
                        * 5280 MHz [56] (disabled)
                        * 5300 MHz [60] (disabled)
                        * 5320 MHz [64] (disabled)
                        * 5500 MHz [100] (disabled)
                        * 5520 MHz [104] (disabled)
                        * 5540 MHz [108] (disabled)
                        * 5560 MHz [112] (disabled)
                        * 5580 MHz [116] (disabled)
                        * 5600 MHz [120] (disabled)
                        * 5620 MHz [124] (disabled)
                        * 5640 MHz [128] (disabled)
                        * 5660 MHz [132] (disabled)
                        * 5680 MHz [136] (disabled)
                        * 5700 MHz [140] (disabled)
                        * 5745 MHz [149] (20.0 dBm) (passive scanning, no IBSS)
                        * 5765 MHz [153] (20.0 dBm) (passive scanning, no IBSS)
                        * 5785 MHz [157] (20.0 dBm) (passive scanning, no IBSS)
                        * 5805 MHz [161] (20.0 dBm) (passive scanning, no IBSS)
                        * 5825 MHz [165] (20.0 dBm) (passive scanning, no IBSS)
.....

So it seems that it is correctly configured, with dual band support. But when I run

iw wlan0 scan

with a couple of active wifi access points I can't get any result.

Regarding bluetooth, now initialization process works fine, no more "Initialization timed out" message and the kernel messages are as expected:

[   55.860595] Bluetooth: HCI device and connection manager initialized
[   55.867218] Bluetooth: HCI socket layer initialized
[   55.872314] Bluetooth: L2CAP socket layer initialized
[   55.877624] Bluetooth: SCO socket layer initialized
[   55.902252] Bluetooth: HCI UART driver ver 2.2
[   55.906921] Bluetooth: HCI H4 protocol initialized
[   55.911987] Bluetooth: HCI BCSP protocol initialized
[   55.917175] Bluetooth: HCILL protocol initialized
[   56.000915] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   56.006500] Bluetooth: BNEP filters: protocol multicast
[   56.047698] Bluetooth: RFCOMM TTY layer initialized
[   56.052825] Bluetooth: RFCOMM socket layer initialized
[   56.058227] Bluetooth: RFCOMM ver 1.11

But when I try to scan for bluetooth devices, I get

/*
 * ########### BT-Scan #############
 * Scan for the remote BT devices
 * #################################
 */

Device is not available: No such device

I think we're on the right path, but there is something still missing.

Any other hints?

Thanks for your support and best regards.

Piero

Hi Peiro,

WiFi:
I'm sorry but your 5GHz band is correctly configured. Noticed that almost all 5GHz frequencies are marked "disabled". Can you please try to do the command "iw reg set <country code>" (country code can be, for example, US) and make sure the CRDA is correctly configured (info link)? Then see if you have any changes in "iw phy2 info".

Bluetooth:
Instead of using the scripts, can you please try those commands manually? We need to make sure you see the following message:

root@am335x-evm:~# insmod /lib/modules/$(uname -r)/kernel/drivers/bt_enable/gpio_en.ko
[   58.055053] Gpio value is :117
[   58.077331] WL1271: BT Enable
root@am335x-evm:~# hciattach /dev/ttyO1 texas 3000000
Found a Texas Instruments' chip!
Firmware file : /lib/firmware/TIInit_7.6.15.bts
Loaded BTS script version 1
texas: changing baud rate to 3000000, flow control to 1
[   70.382354] Bluetooth: Core ver 2.16
[   70.386199] NET: Registered protocol family 31
[   70.390869] Bluetooth: HCI device and connection manager initialized
[   70.397521] Bluetooth: HCI socket layer initialized
[   70.402587] Bluetooth: L2CAP socket layer initialized
[   70.407897] Bluetooth: SCO socket layer initialized
[   70.419677] Bluetooth: HCI UART driver ver 2.2
[   70.424316] Bluetooth: HCI H4 protocol initialized
[   70.429382] Bluetooth: HCI BCSP protocol initialized
[   70.434570] Bluetooth: HCILL protocol initialized
[   70.521026] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   70.526611] Bluetooth: BNEP filters: protocol multicast
[   70.556335] Bluetooth: RFCOMM TTY layer initialized
[   70.561523] Bluetooth: RFCOMM socket layer initialized
[   70.566894] Bluetooth: RFCOMM ver 1.11
Device setup complete

Dear Victor,

ok, I've checked my configuration, it matches with everything you wrote on your posts, except for one thing: the antennna...

I've attached one and now I have both bluetooth and wifi working (at least network scanning, I'll do other tests later).

Thank you very much for your support.

Best Regards,

Piero

Hi ,

When I tried below commands as mentioned in "StoneStreet One Bluetopia Platform Manager Bluetooth Stack for TI WL18xx - Texas Instruments Wiki.pdf"

Getting the below error, I searched for "gpio_en.ko" , not found in the path mentioned.

SPPM>Initialize 1

BTPM_Initialize() Success: 0.
DEVM_RegisterEventCallback() Success: 5.
SPPM>SetDevicepower 1

Error: could not load module /lib/modules/3.2.0/kernel/drivers/bt_enable/gpio_en.ko: No such file or directory
DEVM_PowerOnDevice() Failure: -10032, Response Message Timeout.
Function Error.

Please let me know if i am missing something.

Regards

Muragesh Math