WLAN Applications Forum - Recent Threads

wl1271 stops sending hardware keep alive packets

T. Li — Tue, 21 May 2013 18:01:41 GMT

wl1271 suddenly stops sending keep alive packets after a while. This causes my device being idled out by AP.

My system never goes into power saving or suspend. The wifi is working in power saving mode though. There is no problem with the AP. The connection is on a fixed channel. The problem has been verified by packet captures.

The keep alive packet is configured to 55 seconds.

.keep_alive_interval = 55000,

wl1271: firmware booted (Rev 6.3.6.0.79_2)
wl1271: Driver version: R4_SP2_03_00

Android ICS 4.0.3,

linux 2.6.37

OMAP 3730

Is this a known issue? Any suggestions?

Thanks for help.

Tiegang

wlan not working on Jelly Bean on Blaze Board

Prakash Divate — Tue, 30 Apr 2013 13:43:08 GMT

I am running Android jelly bean 4.2.2 on Blaze Board. As per the release notes i built the compat_wl18xx and copied the modules to the /system/lib/modules, but it failed to load the modules when i booted the board. So i switched on to compat_wl12xx and built the modules and copied them to /system/lib/modules, the modules were successfully loaded this time however wlan still does not work. Could someone please guide me on this? I have attached the log for your reference.

Thank You

prakash

Wl1271 firmware

mukesh thakur1 — Mon, 20 May 2013 06:35:43 GMT

Hi,

<6>[   22.108337] wl1271: loaded
<6>[   22.111999] wl1271: initialized
<6>[   22.535125] (stc): add_channel_to_table: id 2
<6>[   22.541351] (stc): st_register(3)
<6>[   22.545684] (stc): add_channel_to_table: id 3
<6>[   22.551147] (stc): st_register(4)
<6>[   22.560241] (stc): add_channel_to_table: id 4
<3>[   22.729705] wl1271: ERROR could not get firmware: -2
##My question is though wl1271 is loaded and initialized then why it is showing not found.....am i putting at wrong place(I have push it at /system/etc/firmware/ti-connectivity)

Where i have to copy this firmware??

Please help me out

Regards

Mukesh

SCO Initiialization Timeout

radar — Mon, 25 Mar 2013 15:18:32 GMT

Champs,Posting this on behalf of my customer for the moment; as I don't have the HW handy to debug this. But the methodology seems sound- just trying to get he LSR TiWi-BLE module working with am335x EVM. When we use the module that came with the AM335x EVM; all is well; but when we try the TiWi module; the SCO initialization times out. the clocks appear to be running ot the module and the HCI seemsw to have initialized so I am assuming we got the reset and the UART hooked up correctly. Heres' the dumps we get with the EVM module (first- this one works); and then the TiWi module (second). Any ideas?

root@am335x-evm:/usr/share/wl1271-demos/bluetooth/scripts# ./BT_Init.sh

* #################################################

* Initialize BT

* #################################################

[ 342.027038] Gpio value is :117

[ 342.046264] 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

[ 344.325561] Bluetooth: Core ver 2.16

[ 344.329498] NET: Registered protocol family 31

[ 344.334106] Bluetooth: HCI device and connection manager initialized

[ 344.340789] Bluetooth: HCI socket layer initialized

[ 344.345855] Bluetooth: L2CAP socket layer initialized

[ 344.351165] Bluetooth: SCO socket layer initialized

[ 344.417938] Bluetooth: HCI UART driver ver 2.2

[ 344.422576] Bluetooth: HCI H4 protocol initialized

[ 344.427642] Bluetooth: HCI BCSP protocol initialized

[ 344.432800] Bluetooth: HCILL protocol initialized

[ 344.575408] Bluetooth: BNEP (Ethernet Emulation) ver 1.3

[ 344.581054] Bluetooth: BNEP filters: protocol multicast

[ 344.662414] Bluetooth: RFCOMM TTY layer initialized

[ 344.667602] Bluetooth: RFCOMM socket layer initialized

[ 344.672973] Bluetooth: RFCOMM ver 1.11

Device setup complete

When I use the LSR eval board I get:

root@am335x-evm:/usr/share/wl1271-demos/bluetooth/scripts# ./BT_Init.sh

* #################################################

* Initialize BT

* #################################################

[ 98.553161] Gpio value is :117

[ 98.576202] 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

[ 105.795227] Bluetooth: Core ver 2.16

[ 105.799163] NET: Registered protocol family 31

[ 105.803771] Bluetooth: HCI device and connection manager initialized

[ 105.810455] Bluetooth: HCI socket layer initialized

[ 105.815521] Bluetooth: L2CAP socket layer initialized

[ 105.820831] Bluetooth: SCO socket layer initialized

Initialization timed out.

root@am335x-evm:/usr/share/wl1271-demos/bluetooth/scripts#

root@am335x-evm:/usr/share/wl1271-demos/bluetooth/scripts# [ 112.379699] Bluetooth: RFCOMM TTY layer initialized

[ 112.384857] Bluetooth: RFCOMM socket layer initialized

[ 112.390289] Bluetooth: RFCOMM ver 1.11

Clarification On WL1271 & WL1271L BTS

Nambirajan Esakkimuthu93283 — Wed, 15 May 2013 12:38:28 GMT

Hi,

We're using a WL1271 chipset in our board. We want to migrate to the Wl1271L chipset with our latest board. So for both the boards we like to use same kernel image, so how to Check which device has been installed and load proper BTS file to the corresponding Wi-Fi module.

Regards,

Nambirajan E

Auto Channel Selection in Wl1271

Manjunath Mandya — Mon, 20 May 2013 01:50:12 GMT

Hi,

Does wl1271 supports Auto channel selection in AP mode, using hostapd?.

Regards,

Manjunath

wl1283 BT firmware

jags gediya — Fri, 17 May 2013 09:24:28 GMT

I have dowanloaded Bluetooth firmware from

https://github.com/TI-ECS/bt-firmware

but i found there same named .bts files for different processors.

so, are that firmwares processor dependent?

if i am using different processor in my custom board then how can i get BT firmware for my processor? i am using wl1283 for wifi and bt.

thanks and regards.

jags gediya

WL8: wl18xx-fw.bin vs. wl18xx-fw-mc.bin

GINNI — Thu, 16 May 2013 10:40:29 GMT

Hi All,

I have noticed that there are two FW files available for WL8 with different naming. If I go to "TI-OpenLink/wl18xx_fw" I can see that the wl18xx-fw-mc.bin seems to be the latest and most updated one.

My question is: Is there a reason why there are several FW files available (with different naming)? If yes, what is the difference?

Thank You very much and best regards,

GINNI

Integrating TiWi-R2 (WL1271) with AM3354 using 1.8V SDIO/MMC?

Andrew Glen — Fri, 10 May 2013 00:22:45 GMT

Hello,

We have designed and made a prototype board using the TiWi-R2 module (encorporating the WL1271 chip) wired to MMC1 on an AM3354, and the power feeds for the corresponding port wired to 1.8V (VDDSHV1,2,3 supplied with 1.8V).

I am using the Angstrom distribution with kernel 3.2 (which uses the AM335x PSP kernel), and have so far had no luck getting the SDIO to function correctly.

Can get the card detected most of the time and am able to get the the stage of receiving the message 'wl1271: loaded', roughly 35 seconds after boot.

When I try to bring up wlan0 the driver reports continual sdio failures:

wl1271: ERROR sdio read failed (-84)
wl1271: WARNING unsupported chip id: 0x66676777

...and the device then freezes.

Looking at the release notes for an earlier version of the AM335x PSP http://processors.wiki.ti.com/index.php/AM335x-PSP_04.06.00.07_Release_Notes I noticed in the 'Known Issues' section the item 'MMC: hsmmc driver doesnt support 1.8v MMC cards'.

I'm wondering if this issue is the source of my problems, at least as far as getting wifi to work goes.

Does anyone know if this issue been fixed in newer versions of the kernel - or if this limitation is actually an issue with the silicon itself and thus not fixable in software?

Angstrom has moved to version 3.8 of the kernel, so I'm wondering if fixes may have been applied there, but so far I've avoided moving to the newer kernel as I had no compelling reason to do so.

Any information will help!

Regards,

Andrew.

Integrating WL1271 (Tiwi-R2) with AM3354: SDIO Problems

Andrew Glen — Fri, 03 May 2013 02:19:53 GMT

Hello,

I am trying to bring up wifi on ourcustom board based on the beaglebone, using Angstrom with linux kernel 3.2, but having some difficulties with the SDIO.

At present the chip gets detected as follows:

[ 1.853399] mmc1: card claims to support voltages below the defined range. These will be ignored.
[ 1.874310] mmc1: queuing unknown CIS tuple 0x91 (3 bytes)
[ 1.881635] mmc1: new SDIO card at address 0001

And the drivers initialise properly: This appears during boot

[ 4.552597] cfg80211: Calling CRDA to update world regulatory domain
[ 4.559411] cfg80211: World regulatory domain updated:
[ 4.564767] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 4.573501] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 4.581770] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 4.590036] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 4.598290] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 4.606556] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)

And 'lsmod' lists as follows:

root@beaglebone:~# lsmod
Module Size Used by
ip_tables 7854 0
x_tables 14585 1 ip_tables
wl12xx_sdio 3248 0
wl12xx 112983 1 wl12xx_sdio
mac80211 150376 1 wl12xx
cfg80211 140275 2 wl12xx,mac80211
rfkill 14673 2 cfg80211
ipv6 211076 14

And about 30 seconds after boot I get the following:

root@beaglebone:~# [ 35.935706] wl1271: loaded

This makes it look like the kernel and drivers are successfully communicating with the wifi chip. This is exactly what I see when using the original beaglebone with the TiWi5 cape, and with the beaglebone I am then able to connect to an access point using wpa_supplicant (the exact same software configuration is being used on our custom board).

On our custom board, however, when I try to bring up wifi and connect to an access point I get the following stream of SDIO errors:

root@beaglebone:~# wpa_supplicant -B -Dwext -iwlan0 -c/etc/wpa_supplicant.conf
[ 741.228588] CALLBACK SWITCHING WIFI POWER:
[ 741.302744] ON
[ 741.628561] wl1271: ERROR sdio write failed (-110)
[ 741.633648] wl1271: ERROR sdio write failed (-110)
[ 741.638749] wl1271: ERROR sdio write failed (-110)
[ 741.643815] wl1271: ERROR sdio write failed (-110)
[ 747.241308] wl1271: ERROR sdio read failed (-110)
[ 747.246218] wl1271: WARNING unsupported chip id: 0x1
[ 747.251442] CALLBACK SWITCHING WIFI POWER:
[ 747.255618] OFF
[ 747.288428] CALLBACK SWITCHING WIFI POWER:
[ 747.362561] ON
[ 747.688537] wl1271: ERROR sdio write failed (-110)
[ 747.693621] wl1271: ERROR sdio write failed (-110)
[ 747.698723] wl1271: ERROR sdio write failed (-110)
[ 747.703789] wl1271: ERROR sdio write failed (-110)
[ 753.301264] wl1271: ERROR sdio read failed (-110)
[ 753.306170] wl1271: WARNING unsupported chip id: 0x1
[ 753.311392] CALLBACK SWITCHING WIFI POWER:
[ 753.315568] OFF
[ 753.348214] CALLBACK SWITCHING WIFI POWER:
[ 753.422377] ON
[ 753.748479] wl1271: ERROR sdio write failed (-110)
[ 753.753564] wl1271: ERROR sdio write failed (-110)
[ 753.758663] wl1271: ERROR sdio write failed (-110)
[ 753.763729] wl1271: ERROR sdio write failed (-110)
[ 759.361197] wl1271: ERROR sdio read failed (-110)
[ 759.366101] wl1271: WARNING unsupported chip id: 0x1
[ 759.371312] CALLBACK SWITCHING WIFI POWER:
[ 759.375488] OFF
[ 759.378520] wl1271: ERROR firmware boot failed despite 3 retries
Could not set interface wlan0 flags: No such device
Failed to initialize driver interface

I have checked that the WLAN_ENABLE pin is indeed following the ON/OFF calls above and it is - the power remains remains on at all times.

The MMC is configured as follows:

am335x_mmc[1].mmc = 2;
am335x_mmc[1].name = "wl1271";
am335x_mmc[1].caps = MMC_CAP_4_BIT_DATA | MMC_CAP_POWER_OFF_CARD | MMC_PW_KEEP_POWER;
am335x_mmc[1].nonremovable = true;
am335x_mmc[1].gpio_cd = -EINVAL;
am335x_mmc[1].gpio_wd = -EINVAL;
am335x_mmc[1].ocr_mask = MMC_VDD_165_195;

VDDSHV1/2/3 are supplied with 1.8V from VDCDC1 on the TPS65217, so all of the I/O should be on the correct 1.8V voltage domain. My pin mux settings are as follows:

static struct pinmux_config mmc1_wl12xx_pin_mux[] = {
    {"gpmc_ad8.mmc1_dat0", OMAP_MUX_MODE2 | AM33XX_PIN_INPUT_PULLUP},
    {"gpmc_ad9.mmc1_dat1", OMAP_MUX_MODE2 | AM33XX_PIN_INPUT_PULLUP},
    {"gpmc_ad10.mmc1_dat2", OMAP_MUX_MODE2 | AM33XX_PIN_INPUT_PULLUP},
    {"gpmc_ad11.mmc1_dat3", OMAP_MUX_MODE2 | AM33XX_PIN_INPUT_PULLUP},
    {"gpmc_csn2.mmc1_cmd", OMAP_MUX_MODE2 | AM33XX_PIN_INPUT_PULLUP},
    {"gpmc_csn1.mmc1_clk", OMAP_MUX_MODE2 | AM33XX_PIN_INPUT_PULLUP},
    {NULL, 0},
};

static struct pinmux_config wl12xx_pin_mux[] = {
{"gpmc_ad12.gpio1_12", OMAP_MUX_MODE7 | AM33XX_PIN_OUTPUT},   // WLAN_EN
    {"gpmc_ad13.gpio1_13", OMAP_MUX_MODE7 | AM33XX_PIN_INPUT},    // WLAN_IRQ
    {"gpmc_ben1.gpio1_28", OMAP_MUX_MODE7 | AM33XX_PIN_OUTPUT}, // BT_EN
    {NULL, 0},
};

NOTE: I have not wired a UART to the wifi chip - could this be causing a problem?

I am certain all of the signals are wired correctly and I have looked at the many forum posts from people with similar problems, but I have not been able to track down a solution.

One thing I noticed that is different in our hardware design is that the signals SDIO_DAT0/1/2/3 and SDIO_CMD have a 22-Ohm series but also a 10k resistor to a single net that for some reason isn't actually wired to anything on the Tiwi-R2 side of the circuit. Looking at other reference designs this doesn't seem to be done elsewhere, could this be a possible source of my problem? (I'm in the process of figuring out what the reasoning was behind this)

The SDIO_CLK signal is wired with just a 22-Ohm series resistor, as are WLAN_IRQ and WLAN_ENABLE.

Are there other settings I should be looking at regarding line impedance for these signals, and what is the recommended way of wiring these signals?

Are there any other tools available to testing the SDIO connectivity? Trying to scope out the signals causes all sorts of different SDIO issues, which also occur when trying to scope the same signals on the Beaglebone.

At this point I have run out of clues, so would greatly appreciate any suggestions of additional tests I could carry out to figure out what is going wrong here.

Regards,

Andrew Glen.

wl1271: ERROR sdio read failed (-110)

Sean Machin — Tue, 14 May 2013 20:11:00 GMT

I'm bringing up a custom AM3352 board with wl1271 Wifi module.

I can bring up the interface initially and transfer data, but after a few minutes I start seeing " wl1271: ERROR sdio read failed (-110)" messages, then just now got the stack dump below. I am using the 5.06 PSP. How can I fix this?

[ 621.299377] wl1271: ERROR sdio read failed (-110)
[ 621.304443] wl1271: ERROR command complete timeout
[ 621.312438] ------------[ cut here ]------------
[ 621.319549] WARNING: at drivers/net/wireless/wl12xx/cmd.c:107 wl1271_cmd_send+0x36c/0x3c8 [wl12xx]()
[ 621.331359] Modules linked in: wl12xx_sdio wl12xx mac80211 cfg80211
[ 621.339172] Backtrace:
[ 621.342315] [<c001bac4>] (dump_backtrace+0x0/0x10c) from [<c03ba4e4>] (dump_stack+0x18/0x1c)
[ 621.352691] r6:0000006b r5:bf0ffca8 r4:00000000 r3:00000002
[ 621.359130] [<c03ba4cc>] (dump_stack+0x0/0x1c) from [<c0044024>] (warn_slowpath_common+0x54/0x6c)
[ 621.369476] [<c0043fd0>] (warn_slowpath_common+0x0/0x6c) from [<c0044060>] (warn_slowpath_null+0x24/0x2c)
[ 621.380371] r8:00007bd2 r7:cf135e08 r6:00007b0a r5:ffffff92 r4:cf135760
[ 621.387756] r3:00000009
[ 621.390563] [<c004403c>] (warn_slowpath_null+0x0/0x2c) from [<bf0ffca8>] (wl1271_cmd_send+0x36c/0x3c8 [wl12xx])
[ 621.402191] [<bf0ff93c>] (wl1271_cmd_send+0x0/0x3c8 [wl12xx]) from [<bf101dec>] (wl12xx_cmd_stop_fwlog+0x4c/0x78 [wl12xx])
[ 621.414581] [<bf101da0>] (wl12xx_cmd_stop_fwlog+0x0/0x78 [wl12xx]) from [<bf0fef14>] (wl1271_recovery_work+0x1c8/0x2c8 [wl12xx])
[ 621.427429] r5:cf1357ac r4:cf135b50
[ 621.431243] [<bf0fed4c>] (wl1271_recovery_work+0x0/0x2c8 [wl12xx]) from [<c00596b0>] (process_one_work+0x190/0x448)
[ 621.443023] [<c0059520>] (process_one_work+0x0/0x448) from [<c005a2dc>] (worker_thread+0x15c/0x350)
[ 621.453186] [<c005a180>] (worker_thread+0x0/0x350) from [<c005e2a0>] (kthread+0x8c/0x94)
[ 621.462310] [<c005e214>] (kthread+0x0/0x94) from [<c0047368>] (do_exit+0x0/0x6a8)
[ 621.470794] r6:c0047368 r5:c005e214 r4:cf815eb0
[ 621.475830] ---[ end trace ce100cd8b4228f17 ]---
[ 621.480651] wl1271: ERROR failed to send stop firmware logger command
[ 627.081024] wl1271: ERROR sdio read failed (-110)
[ 632.680267] wl1271: ERROR sdio read failed (-110)
[ 638.281677] wl1271: ERROR sdio read failed (-110)
[ 638.288452] wl1271: Hardware recovery in progress. FW ver: Rev 6.3.0.0.77 pc: 0x1
[ 638.298187] wl1271: down
[ 638.301452] setting wifi radio off
[ 638.309906] ieee80211 phy0: Hardware restart was requested
[ 638.344757] setting wifi radio on
[ 639.046203] wl1271: firmware booted (Rev 6.3.0.0.77)
[ 639.155120] wl1271: Association completed.
[ 846.551544] wl1271: ERROR sdio read failed (-110)
[ 852.149261] wl1271: ERROR sdio read failed (-110)
[ 857.746826] wl1271: ERROR sdio write failed (-110)
[ 857.758728] wl1271: ERROR sdio write failed (-22)

wl1273 interuptions

Genci Deljana — Thu, 09 May 2013 13:29:09 GMT

wl1273 is interrupted now and then because of ELP (extreme low power), but fortunately recovers itself.

We are trying it in an Android smartphone with linux kernel 3.0.8. Please if anyone has a clue to a fix implementation. Thank you!!

Here is our progress with the problem also dmesg logs are there. LINK

wl1283 related binaries for Android

jags gediya — Wed, 15 May 2013 15:31:17 GMT

Hi,

from where i can get wpa_supplicant, hostapd and dhcpd for android jelly bean?

how can we include them in Android file system?

What firmware(SOFTWARE PACKAGE) been used for COMBO MODULE?

janaki pillai — Mon, 22 Apr 2013 06:51:31 GMT

Hi all .,
i finalize the COMBO MODULE "LBEH59XUHC(TypeUH) - with TI/WL1271L" Murrata ELECTRONICS .
Now i had Query i need software package for this module to work

Can some one give idea which software package i can be used ?

whether i can get it from TI?

Thanks in advance

Issue of intermittant ip address using dhcp for 2.6.32 kernel

Aparna Anand — Tue, 14 May 2013 10:15:16 GMT

Hi,

For the custom board based on AM37xx processor and Muratas chipset using WL1271, I am trying to connect to a particular access point(Verizon Jetpack device). I am using ported 2.6.32 kernel from linux-03.00.01.06 PSP and Wilink drivers for WL1271. I am facing this strange issue where in dynamic ip address allocation is sometimes happening and sometimes not for the custom board.

Association with AP is happening and static IP is also obtained. While trying to get dynamic ip using "udhcpc -i tiwlan0" , sometimes ip address is got after a long long wait and sometimes not at all. Only for this particular access point this issue is seen. I have tried updating the udhcpc binary to the latest busybox version 1.20.

One interesting thing to be noted is that, on EVM based on am335x, dynamic ip allocation is happening fine for the linux kernel version 3.2 whereas not in 2.6.32.

This could definitely point out to kernel problems, but because it involves lot of work, we don't want to do kernel upgrade right away.

Can someone give suggestions on anything that can be tried out to fix this issue.

Thanks in advance for any help put forward!

Regards,

Aparna

wl1271 driver crashing, but station is still connected

Manjunath Mandya — Mon, 13 May 2013 08:55:03 GMT

Hi,

We have wl1271 interfaced to OMAPL138. WL1271 is configured in AP mode

following are the details

Platform: OMAPL138

Wifi chipset :wl1271

Firmware : Rev 6.3.3.0.79

Firmware Name: wl1271-fw-multirole-roc.bin

compat-wireless : compat-wireless-0.20120206r412_02-r64c

Now iam able to connect stations to my wifi AP, but wifi driver crashes with following messages

wl1271: WARNING corrupted packet in RX with status: 0x1
wl1271: ERROR watchdog interrupt received! starting recovery.
wl1271: Reading FW panic log
wl1271: ERROR command complete timeout
------------[ cut here ]------------
WARNING: at /da850-omapl138-evm-none-linux-gnueabi/compat-wireless-0.20120206r412_02-r64c/compat-wireless/drivers/net/wireless/wl12xx/cmd.c:107 wl1271_cmd_send+0x334/0x368 [wl12xx]()
Modules linked in: wl12xx_sdio wl12xx mac80211 smsc95xx cfg80211 compat
Backtrace:
[<c00336fc>] (dump_backtrace+0x0/0x114) from [<c02f17dc>] (dump_stack+0x18/0x1c)
r7:00000000 r6:bf19830c r5:bf1ab648 r4:0000006b
[<c02f17c4>] (dump_stack+0x0/0x1c) from [<c0045a64>] (warn_slowpath_common+0x54/0x6c)
[<c0045a10>] (warn_slowpath_common+0x0/0x6c) from [<c0045aa0>] (warn_slowpath_null+0x24/0x2c)
r9:bf196d88 r8:00000000 r7:c9789360 r6:cf80f20c r5:cf80ee60
r4:ffffff92
[<c0045a7c>] (warn_slowpath_null+0x0/0x2c) from [<bf19830c>] (wl1271_cmd_send+0x334/0x368 [wl12xx])
[<bf197fd8>] (wl1271_cmd_send+0x0/0x368 [wl12xx]) from [<bf1984cc>] (wl12xx_cmd_stop_fwlog+0x58/0x88 [wl12xx])
[<bf198474>] (wl12xx_cmd_stop_fwlog+0x0/0x88 [wl12xx]) from [<bf196e30>] (wl1271_recovery_work+0xa8/0x2d8 [wl12xx])
r5:cf80f098 r4:c040719c
[<bf196d88>] (wl1271_recovery_work+0x0/0x2d8 [wl12xx]) from [<c0059c90>] (process_one_work+0x21c/0x380)
[<c0059a74>] (process_one_work+0x0/0x380) from [<c005a2e8>] (worker_thread+0x1f8/0x34c)
[<c005a0f0>] (worker_thread+0x0/0x34c) from [<c005f9fc>] (kthread+0x8c/0x94)
[<c005f970>] (kthread+0x0/0x94) from [<c0049404>] (do_exit+0x0/0x6a4)
r7:00000013 r6:c0049404 r5:c005f970 r4:cf85bee8
---[ end trace b7b2f876bbfa41b0 ]---
wl1271: ERROR failed to send stop firmware logger command
First address of fwlogger = 0x25fe
wl1271: Hardware recovery in progress. FW ver: Rev 6.3.3.0.79 pc: 0xbab0
wl1271: down
ieee80211 phy0: Hardware restart was requested
wl1271: firmware booted (Rev 6.3.3.0.79)
wl1271: Driver version: R4_SP2_03_00

But still the station is connected to AP.
Currently this may not be the issue, but going further it may cause serious error.

Thanks,
Manjunath

wl1271 is returning error

Manjunath Mandya — Fri, 10 May 2013 10:08:06 GMT

Hi,

We have wl1271 interfaced to OMAPL138. WL1271 is configured in AP mode

following are the details

Platform: OMAPL138

Wifi chipset :wl1271

Firmware : Rev 6.3.3.0.79

Firmware Name: wl1271-fw-multirole-roc.bin

compat-wireless : compat-wireless-0.20120206r412_02-r64c

Now iam able to connect stations to my wifi AP, but iam getting following warning regularly

" wl1271: WARNING corrupted packet in RX with status: 0x1"

Let me know how to go about this.

Thanks,

Manjunath

driver and firmware version

jags gediya — Fri, 10 May 2013 06:42:21 GMT

i have wl12xx driver in kernel. i have downloaded firmware wl128x-fw* from https://github.com/TI-OpenLink.

How can we know the driver version and firmware version?

Getting WL12xx wireless to work on custom AM3352 board

Sean Machin — Wed, 01 May 2013 23:39:42 GMT

Hi Michael and others,

I have started trying to get wifi working on my custom AM3352 based board, the circuitry is a cut and paste of the SK EVM circuit (WL1271).

After performing a "modprobe wl12xx" only displays the message

[ 108.424346] cfg80211: Calling CRDA to update world regulatory domain

I don' see any further activity. I also have no wlan0 interface. How can I get the above working?

My kernel settings are at http://resplendid.com/seeds_defconfig

WL1271L Bluetooth Patch

Ryan Erickson — Tue, 14 May 2013 16:05:33 GMT

Where can I download the latest .BTS file for the WL1271L?

Implementation, availability, pricing

Yoel Frischoff — Wed, 08 May 2013 06:42:47 GMT

Hello everyone;

I have been looking for Implementation, availability, pricing, of the wilink7 (GPS BLE).

Who can advise?

Apart from information, I would like to get my hands on a working product.

Kind regards,

wl12xx driver not turning ON

Kishan Illur — Thu, 09 May 2013 13:10:06 GMT

HI,

We are using wl12xx in our custom board. We are facing the following problem.

When Wifi is turned on for the first time, it turns on with no problem. But when I turn it off and then try turning it on, it is failing. I am trying it like below.

ifconfig wlan0 up (to turn on)

ifconfig wlan0 down (to turn off)

From the second time, the kernel is crashing and below is the trace.

WARNING: at drivers/mmc/core/core.c:349 mmc_wait_for_cmd+0x94/0x9c()
Modules linked in: wl12xx_sdio
[<80043420>] (unwind_backtrace+0x0/0xfc) from [<8006c39c>] (warn_slowpath_common+0x4c/0x64)
[<8006c39c>] (warn_slowpath_common+0x4c/0x64) from [<8006c3d0>] (warn_slowpath_null+0x1c/0x24)
[<8006c3d0>] (warn_slowpath_null+0x1c/0x24) from [<80362f08>] (mmc_wait_for_cmd+0x94/0x9c)
[<80362f08>] (mmc_wait_for_cmd+0x94/0x9c) from [<80369a64>] (mmc_io_rw_direct_host+0xa8/0x140)
[<80369a64>] (mmc_io_rw_direct_host+0xa8/0x140) from [<8036af54>] (sdio_disable_func+0x3c/0xa8)
[<8036af54>] (sdio_disable_func+0x3c/0xa8) from [<7f00019c>] (wl1271_sdio_set_power+0x6c/0x100 [wl12xx_sdio])
[<7f00019c>] (wl1271_sdio_set_power+0x6c/0x100 [wl12xx_sdio]) from [<8030cd18>] (wl1271_op_add_interface+0x11c/)
[<8030cd18>] (wl1271_op_add_interface+0x11c/0x2a8) from [<80495858>] (ieee80211_do_open+0x590/0x618)
[<80495858>] (ieee80211_do_open+0x590/0x618) from [<803af0d0>] (__dev_open+0x9c/0xe8)
[<803af0d0>] (__dev_open+0x9c/0xe8) from [<803abe44>] (__dev_change_flags+0x74/0x120)
[<803abe44>] (__dev_change_flags+0x74/0x120) from [<803aeffc>] (dev_change_flags+0x10/0x48)
[<803aeffc>] (dev_change_flags+0x10/0x48) from [<804031e0>] (devinet_ioctl+0x7cc/0x8a8)
[<804031e0>] (devinet_ioctl+0x7cc/0x8a8) from [<8039b8d4>] (sock_ioctl+0x68/0x250)
[<8039b8d4>] (sock_ioctl+0x68/0x250) from [<800fbf9c>] (do_vfs_ioctl+0x80/0x5b0)
[<800fbf9c>] (do_vfs_ioctl+0x80/0x5b0) from [<800fc504>] (sys_ioctl+0x38/0x60)
[<800fc504>] (sys_ioctl+0x38/0x60) from [<8003c5c0>] (ret_fast_syscall+0x0/0x30)
---[ end trace da227214a82491bd ]---
wl1271: ERROR firmware boot failed despite 3 retries
ifconfig: SIOCSIFFLAGS: Connection timed out

Does anyone have any idea of why this is happening? Any help is appreciated.

Thanks

Jorjin WG7310 / WL1271 - WinCE 6R3 - BT stops transmitting after 10 minutes in FCC tests

Doug DeVries — Fri, 10 May 2013 03:16:10 GMT

Hi,

We are using a Jorjin WG7310 (WL1271) radio module in a system running WinCE 6R3. We are experinecing a problem wherein the BT radio shuts itself off after10 minutes of operation during FCC testing. We are using HCI commands to configure the radio for test operation such as continuous TX on one channel, continuous TX with frequency hopping etc. For some unknown reason the BT radio will cease transmititng after 10 minutes of operation. We know that WinCE isn't going to sleep, WZ config is disabled etc. etc. There are no log files of which we are aware that are generated at the time the radio turns off.

The HCI commands to control the BT radio in testing are in script files (.bts files) that run when the BT driver loads. We started with a base example script that we were given. We use SriptPad to alter the last few lines in the scripts when we want to change the power level, modulation, hopping vs fixed frequency and so forth. Everything is working fine except that the BT radio will turn itself off 10 minutes after the script file is run. To get the test going again we must reboot the system. It is not necessary to power cycle, but just reboot to get the driver to load and script to run again.

The attached ZIP contains the 3 script files that we use to enable contiunous transmission at maximum power level in frequency hopping mode - one script for each modulation type. ScriptPad is needed to properly view or edit them, of course. We have other scripts that put the radio into single channel (non-hopping) continuoust transmit modes as well. No matter the script, the radio still shuts off after 10 minutes.

Has anyone else encountered this problem? Anyone have a clue if there could be something in the script files that cause the 10-minute shut down behavior?

Thanks,

Doug

(Please visit the site to view this file)

Confusion on appropriate firmware version for Wl127x application

Dennis O'Brien — Fri, 03 May 2013 19:23:13 GMT

Dear sirs,

We are using the WL7310 from Jorgin with the AM37x. Our design is similar to the AM37x EVM and we started with the 05.05.00-SDK (about 6 months ago). We have an operational solution at this time.

We are trying to do regulatory testing and are failing because the firmware we're using doesn't support the test. According to Jorgin, we should be using either 6.1.0.1.149 or 6.1.0.10.335 version of firmware.

The 05.05.00-SDK with ti-compat-wireless package and the SDK docs indicate that the wl12xx firmware should come from a ti-utils repo. At the time we started this the firmware version was 6.3.8.0.111_1.

We have pulled the 05.07-SDK for comparison. It also points at the ti-utils as the place to get firmware. A new pull from this repos shows version 6.3.10.0.136. The firmware located in the rootfs of 05.07-SDK was 6.3.10.0.135.

Could someone tell me the "history" of the 6.1.x.x.x versus the 6.3.x.x.x version numbering? Is there an association between these number systems?

The test we are failing is "EN 300 328 v1.8.1, test item "adaptive test" (released 6/2012). Could someone tell me which firmware is required for this test?

Thanks,

Dennis O'Brien

EQware Engineering, Inc.

WL1273 + AM335x

miya yin — Thu, 09 May 2013 03:47:37 GMT

hi experts,

I‘m porting wl1273 wifi module to AM335X .And maybe there have some problem of my sdio bus.So I want to use the test procedure for test.
I get if form http://wireless.kernel.org/en/users/Drivers/wl12xx#HACKS wl12xx_sdio_test.tar.gz
But when insmod the test module,it don't work as expected,can you tell me the right way to use it.

Thanks!