Search Linux Wireless

RE: wl12xx over spi with no scan results

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Luca,

I'm trying to calibrate my device as suggested, following the guide found at: http://processors.wiki.ti.com/index.php/OMAP_Wireless_Connectivity_Calibration_Proccess_NLCP

In particular I'm trying to replicate the example at the end of the document and at step 3 of the example I'm obtaining:

root@(none):~/ti-utils# ./calibrator plt calibrate
wl1271: power up
chip_id read from memory: 04030111
wl1271_fetch_firmware - fetching firmware wl1271-fw.bin
wl1271_fetch_nvs - fetching firmware wl1271-nvs.bin
enable_interrupts_wl1271
wl1271: firmware booted in PLT mode (Rev 6.1.0.50.350)
Fail to calibratwl1271: power down
e ith radio statdisable_interrupts_wl1271
us (-80)
root@(none):~/ti-utils#


Any idea about why my calibration process is failing ? I was able to complete the first steps creating the nvs from ini files 
But I'm failing in "calibrator plt calibrate". 

Thanks in advance 

Alberto

-----Original Message-----
From: Luciano Coelho [mailto:coelho@xxxxxx] 
Sent: mercoledì 12 dicembre 2012 11:17
To: Alberto Garau
Cc: linux-wireless@xxxxxxxxxxxxxxx; Ido Yariv; Arik Nemtsov; Adriano Melis; Luca Fresi
Subject: Re: wl12xx over spi with no scan results

On Wed, 2012-12-12 at 10:13 +0000, Alberto Garau wrote:
> Thanks Luca,
> 
> we tried with FALLING_EDGE for the interrupt but the driver got stucked so I had to put again RISING_EDGE.
> 
> We successfully cross compiled iw but also with that tool we always 
> see only on ESSID from one specific AP

I didn't expect the scan to improve with iw, but at least now you're using the right tool. :)


> while the others ESSID from the second AP are available only sometime. 
> 
> That's very strange.
> 
> Do you think we are facing calibration problems ?

Yes, I guess calibration is the most likely cause now.


> In our CMD0 we have
> 
> bit 13 = 1 IB interrupt is active high
> 
> bit 14 = 1 IB interrupt is open drain
> 
> Do you think is right according do RISING_EDGE interrupt ?

I think this is okay.  I don't think the problem is the interrupt now.

You should try to calibrate your device and generate a proper NVS file.

--
Luca.


��.n��������+%������w��{.n�����{���zW����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f



[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Wireless Personal Area Network]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Hiking]     [MIPS Linux]     [ARM Linux]     [Linux RAID]

  Powered by Linux