Re: Troubles with wl12xx

[Gary Thomas <gary@mlbassoc.com>]

On 2012-03-14 12:44, Gary Thomas wrote:
> On 2012-03-14 07:41, Gary Thomas wrote:
>> On 2012-03-14 06:45, Gary Thomas wrote:
>>> I'm having some issues getting my [newly designed] board to run
>>> with wl12xx (wl1271 on SDIO) My kernel is 2.6.37 and I'm using
>>> a compat-wireless snapshot from 2012-02-28
>>>
>>> Here's what I see when I boot - looks OK:
>>> Compat-wireless backport release: compat-wireless-2012-02-28
>>> Backport based on linux-next.git next-20120228
>>> cfg80211: Calling CRDA to update world regulatory domain
>>> wl12xx: loaded
>>>
>>> If I bring up the wlan0 interface manually, I can talk to the
>>> device, scan for access points, etc. All looks good.
>>>
>>> The problem comes when I try to negotiate for an address with
>>> WPA security.
>>> # ifup wlan0
>>> wl12xx: firmware booted (Rev 6.3.5.0.98)
>>> ADDRCONF(NETDEV_UP): wlan0: link is not ready
>>> udhcpc (v1.19.3) started
>>> Sending discover...
>>> wl12xx: down
>>> Sending discover...
>>> Sending discover...
>>> No lease, failing
>>>
>>> A few seconds later, everything falls apart. Sorry for the verbosity, but
>>> the messages changed at the end and I wanted to make sure you saw it all.
>>
>> A little more information - maybe this helps:
>> # ifup -v wlan0
>> run-parts /etc/network/if-pre-up.d
>> wl12xx: firmware booted (Rev 6.3.5.0.98)
>> wl12xx: ERROR watchdog interrupt received! starting recovery.
>> wl12xx: Reading FW panic log
>> wl12xx: Hardware recovery in progress. FW ver: Rev 6.3.5.0.98 pc: 0x0
>> wl12xx: down
>> ieee80211 phy0: Hardware restart was requested
>> ADDRCONF(NETDEV_UP): wlan0: link is not ready
>> wl12xx: ERROR timeout waiting for the hardware to complete initialization
>> wl12xx: ERROR timeout waiting for the hardware to complete initialization
>> wl12xx: ERROR timeout waiting for the hardware to complete initialization
>> wl12xx: ERROR firmware boot failed despite 3 retries
>> ifconfig wlan0 up
>> udhcpc -R -n -p /var/run/udhcpc.wlan0.pid -i wlan0
>> udhcpc (v1.19.3) started
>> Sending discover...
>> Sending discover...
>> Sending discover...
>> No lease, failing
>
> Even more info - I enabled all the debug flags in the wl12xx driver and
> captured this sequence (it's 100% repeatable with my current configuration)
> The log is at http://www.mlbassoc.com/misc/messages.wl12xx
>
> Any ideas what's going on?

Even more confusion - I've found that I need to be careful with the
sequence and timing of bringing up the wl12xx.

* This sequence will always fail:
   -- [re]boot Linux
   # ifup wlan0

* This sequence also fails:
   -- [re]boot Linux
   # ifconfig wlan0 up
   # ifup wlan0

* This sequence seems to always work:
   -- [re]boot Linux
   # ifconfig wlan0 up
   # iw wlan0 scan
   # ifup wlan0

What could be special about this [slight] change in bring-up behaviour/timing?

Sadly, even when it works, it dies if I try to run
   # ifdown wlan0
   # ifup wlan0

Interestingly, I've seen this work perfectly on my OMAP4430 PandaBoard.  We based
our design on that board, so it's a bit puzzling why we are having so much trouble.

Any ideas?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------