Anyone have luck with WLE900VX?

Ben Greear greearb at candelatech.com
Mon Feb 24 11:35:45 EST 2014


On 02/24/2014 08:17 AM, Kalle Valo wrote:
> Ben Greear <greearb at candelatech.com> writes:
> 
>> I managed to get a few WLE900VX, and I've seen some funny things so far.
> 
> Do you have any more info what type of board it is? Is it CUS223, XBNNN
> (N being a decimal) or something else?

http://www.compex.com.sg/Datasheets/WLE900VX_Dsv1.0.0.pdf

I was told the ref design, but cannot remember it..will ask
again.  It is not a high power design like the CUS223, evidently.

> What's the chip id?

05:00.0 Network controller: Atheros Communications Inc. Device 003c
	Flags: bus master, fast devsel, latency 0, IRQ 18
	Memory at f4400000 (64-bit, non-prefetchable) [size=2M]
	Expansion ROM at f4600000 [disabled] [size=64K]
	Capabilities: [40] Power Management version 2
	Capabilities: [50] MSI: Enable- Count=1/8 Maskable+ 64bit-
	Capabilities: [70] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Virtual Channel
	Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
	Kernel driver in use: ath10k_pci


>> First, with the official firmware 10.1.467.1-1 it immediately crashes on startup.
>> I don't have that firmware source, so I don't know why it crashes.
>> I wasn't even trying to create more than the default wlanX station.
> 
> Is that with stock ath10k driver or does ath10k contain any custom
> changes?

It had custom changes, and at least one patch that might cause
trouble:  The one that doubled the number of key cache entries that
I posted a few days ago.

I can try with all that backed out.

>> With my firmware (based on 10.1.389), it boots up OK and I can create
>> and associate 32 station vifs.
>>
>> Both NICs that I have tried so far report the same mostly bogus
>> MAC:  00:03:07:12:34:56
>>
>> The NIC's spec sheet claims it is 3x3, but 'iw phy phyX info' shows only
>> 2 streams supported for both the 2.4Ghz n band and the 5Ghz /ac band.
> 
> Hmm, I wonder if otp.bin fails. Can you check what result code you get
> from otp.bin? Add something like this to ath10k_download_and_run_otp():
> 
> 	ret = ath10k_bmi_execute(ar, address, &exec_param);
>         ath10k_dbg(ATH10K_DBG_BOOT, "boot otp execute result %d\n", exec_param);


Will do, thanks!

Ben


-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com




More information about the ath10k mailing list