Issue of AR6K Driver on WinCE 5.0

Jul 2, 2008 at 12:31 PM
Edited Jul 2, 2008 at 12:57 PM

Hi,

Could anyone share your experience about AR6K driver on WinCE 5.0 ?
I am build a PXA270 WinCE 5.0 system with AR6K driver support.
Then I can build AR6K_NDIS_SDIO.dll and I had combined it into NK.bin.
But after I insert AR6K SDIO card into our system, there are one error (ERROR_OUTOFMEMORY) while loading AR6K_NDIS_SDIO.dll.
I'll deeply appreciate if any one can help me to found out any problem on this driver ~

Lawrance

Coordinator
Jul 2, 2008 at 5:16 PM
Can you be a little more specific on where the out of memory error is coming from? The Ar6K driver has been used on CE 5.0 kernels many times.

Paul
Jul 4, 2008 at 7:11 AM
We added AR6K SDIO driver by manual build and got AR6K_NDIS_SDIO.dll.
Then we also added registry and added AR6K_NDIS_SDIO.dll to our image.

I built one debug image to check some debug message and got following error message:

0x87d406a0: virtualcopying 801bd000 <- 801bd000 (2f6ef)!
0x87d406a0: LoadO32 internal Failed, retval = 0000000e
0x87d406a0: Loading of Module 'ar6k_ndis_sdio.dll' (878554c8) failed, prevRefCnt = 0, refcnt = 0, inuse = 00000000, dwErr = 0000000e
0x87d406a0: NK Kernel: DEBUGCHK failed in file c:\wince500\private\winceos\coreos\nk\kernel\loader.c at line 1981
0x87d406a0: DEBUG_BREAK @80163220 MD=1f Ignored.
0x87d406a0: SDBusDriver: Failed to load driver DLL : ar6k_ndis_sdio.dll 

Do any one ever see the same error before ?
Coordinator
Jul 7, 2008 at 9:18 PM
It looks like you don't have enough RAM to load the DLL on top of the SDIO stack. Did you build with platform with max RAM specified?

Paul
Jul 24, 2008 at 4:37 AM

I am able to load AR6K SDIO driver by modifying bib file.
I can see wireless utility running on Marvell PXA270 WinCE 5.0 now.
But there are no any Access Point can be seem within the list.

From driver debug message :
BMI Get Target ID: Exit (ID: 0x13010020)
FIRMWARE MAJOR VERSION ==> 1
FIRMWARE MINOR VERSION ==> 3

Is there any place need to fix for getting connection with any Access Point ?

Coordinator
Jul 28, 2008 at 7:47 PM
Looks like you have target firmware version 1.3.1. You will need to match the host driver to this version. The version on this site is 1.1 version.

Paul

Aug 1, 2008 at 5:54 PM
Seeing that Atheros has released 2.somthing now, and 1.1 is obviously very old, is there any plan to update the open sources or to list the WMI changes so that code can be compatible with new devices produced.....and not just some rare dinesour products we will need to hunt on ebay for?

WS
Coordinator
Aug 5, 2008 at 1:56 AM
Dear Wifi Sucks,
The latest release of host drivers for Windows CE and WinMobile is version 1.3. There is not 2.x for Windows for the AR6001. The hardware version of the AR6001 is exactly the same for the 1.3 and 1.1 firmware.

Regards

Paul
Aug 5, 2008 at 6:47 PM
Well you answered a little of the inquiry: What are we to do when we purchase product with the latest Atheros firmware loaded?  Is it compatible with the current WinCE source here?

WS
Coordinator
Aug 6, 2008 at 12:15 AM
The AR6001 drivers that Atheros posts and gives to OEMs are reference sample drivers. Each OEM ships specific drivers for their design that is based on the AR6001 chip.  You should get the appropriate driver from your hardware vendor. You could also possibly request that they reprogram matching firmware onto your device for another driver version..

Regards

Paul

Aug 6, 2008 at 11:23 PM
Can you give a summary of the differences in the AR6001 firmwares?

WS
Coordinator
Aug 7, 2008 at 11:03 PM
If you have specific questions about different versions of the target firmware, you can ask me non-anonymously via PM.

Regards

Paul