<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="http://www.codeplex.com/rss.xsl"?><rss version="2.0"><channel><title>Windows CE WLAN Driver for Atheros AR-6001</title><link>http://www.codeplex.com/CEWifiDriverAR6000/Project/ProjectRss.aspx</link><description>This is a Windows CE WiFi driver for the Atheros AR-6001 Chipset.</description><item><title>New Post: Issue of AR6K Driver on WinCE 5.0</title><link>http://www.codeplex.com/CEWifiDriverAR6000/Thread/View.aspx?ThreadId=30687</link><description>&lt;div style="line-height: normal;"&gt;If you have specific questions about different versions of the target firmware, you can ask me non-anonymously via PM.&lt;br&gt;
&lt;br&gt;
Regards&lt;br&gt;
&lt;br&gt;
Paul&lt;br&gt;
&lt;/div&gt;</description><author>paullever</author><pubDate>Thu, 07 Aug 2008 22:03:06 GMT</pubDate><guid isPermaLink="false">New Post: Issue of AR6K Driver on WinCE 5.0 20080807100306P</guid></item><item><title>New Post: Issue of AR6K Driver on WinCE 5.0</title><link>http://www.codeplex.com/CEWifiDriverAR6000/Thread/View.aspx?ThreadId=30687</link><description>&lt;div style="line-height: normal;"&gt;Can you give a summary of the differences in the AR6001 firmwares?&lt;br&gt;
&lt;br&gt;
WS&lt;br&gt;
&lt;/div&gt;</description><author>Wifi_Sucks</author><pubDate>Wed, 06 Aug 2008 22:23:56 GMT</pubDate><guid isPermaLink="false">New Post: Issue of AR6K Driver on WinCE 5.0 20080806102356P</guid></item><item><title>New Post: Issue of AR6K Driver on WinCE 5.0</title><link>http://www.codeplex.com/CEWifiDriverAR6000/Thread/View.aspx?ThreadId=30687</link><description>&lt;div style="line-height: normal;"&gt;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.&amp;nbsp; 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..&lt;br&gt;
&lt;br&gt;
Regards&lt;br&gt;
&lt;br&gt;
Paul&lt;br&gt;
&lt;br&gt;
&lt;/div&gt;</description><author>paullever</author><pubDate>Tue, 05 Aug 2008 23:15:26 GMT</pubDate><guid isPermaLink="false">New Post: Issue of AR6K Driver on WinCE 5.0 20080805111526P</guid></item><item><title>New Post: Issue of AR6K Driver on WinCE 5.0</title><link>http://www.codeplex.com/CEWifiDriverAR6000/Thread/View.aspx?ThreadId=30687</link><description>&lt;div style="line-height: normal;"&gt;Well you answered a little of the inquiry: What are we to do when we purchase product with the latest Atheros firmware loaded?&amp;nbsp; Is it compatible with the current WinCE source here?&lt;br&gt;
&lt;br&gt;
WS&lt;br&gt;
&lt;/div&gt;</description><author>Wifi_Sucks</author><pubDate>Tue, 05 Aug 2008 17:47:12 GMT</pubDate><guid isPermaLink="false">New Post: Issue of AR6K Driver on WinCE 5.0 20080805054712P</guid></item><item><title>New Post: Issue of AR6K Driver on WinCE 5.0</title><link>http://www.codeplex.com/CEWifiDriverAR6000/Thread/View.aspx?ThreadId=30687</link><description>&lt;div style="line-height: normal;"&gt;Dear Wifi Sucks,&lt;br&gt;
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.&lt;br&gt;
&lt;br&gt;
Regards&lt;br&gt;
&lt;br&gt;
Paul&lt;br&gt;
&lt;/div&gt;</description><author>paullever</author><pubDate>Tue, 05 Aug 2008 00:56:58 GMT</pubDate><guid isPermaLink="false">New Post: Issue of AR6K Driver on WinCE 5.0 20080805125658A</guid></item><item><title>New Post: Issue of AR6K Driver on WinCE 5.0</title><link>http://www.codeplex.com/CEWifiDriverAR6000/Thread/View.aspx?ThreadId=30687</link><description>&lt;div style="line-height: normal;"&gt;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?&lt;br&gt;
&lt;br&gt;
WS&lt;br&gt;
&lt;/div&gt;</description><author>Wifi_Sucks</author><pubDate>Fri, 01 Aug 2008 16:54:27 GMT</pubDate><guid isPermaLink="false">New Post: Issue of AR6K Driver on WinCE 5.0 20080801045427P</guid></item><item><title>New Post: Issue of AR6K Driver on WinCE 5.0</title><link>http://www.codeplex.com/CEWifiDriverAR6000/Thread/View.aspx?ThreadId=30687</link><description>&lt;div style="line-height: normal;"&gt;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.&lt;br&gt;
&lt;br&gt;
Paul&lt;br&gt;
&lt;br&gt;
&lt;/div&gt;</description><author>paullever</author><pubDate>Mon, 28 Jul 2008 18:47:12 GMT</pubDate><guid isPermaLink="false">New Post: Issue of AR6K Driver on WinCE 5.0 20080728064712P</guid></item><item><title>New Post: Issue of AR6K Driver on WinCE 5.0</title><link>http://www.codeplex.com/CEWifiDriverAR6000/Thread/View.aspx?ThreadId=30687</link><description>&lt;div style="line-height: normal;"&gt;&lt;p&gt;I am able to load AR6K SDIO driver by modifying bib file.&lt;br&gt;
I can see wireless utility running on Marvell PXA270 WinCE 5.0 now.&lt;br&gt;
But there are no any Access Point can be seem within&amp;nbsp;the list.&lt;/p&gt;
&lt;p&gt;From driver debug message : &lt;br&gt;
BMI Get Target ID: Exit (ID: 0x13010020) &lt;br&gt;
FIRMWARE MAJOR VERSION ==&amp;gt; 1 &lt;br&gt;
FIRMWARE MINOR VERSION ==&amp;gt; 3&lt;/p&gt;
&lt;p&gt;Is there any&amp;nbsp;place need to fix for getting connection with any Access Point ?&lt;/p&gt;
&lt;/div&gt;</description><author>LawranceYang</author><pubDate>Thu, 24 Jul 2008 03:37:36 GMT</pubDate><guid isPermaLink="false">New Post: Issue of AR6K Driver on WinCE 5.0 20080724033736A</guid></item><item><title>New Post: Issue of AR6K Driver on WinCE 5.0</title><link>http://www.codeplex.com/CEWifiDriverAR6000/Thread/View.aspx?ThreadId=30687</link><description>&lt;div style="line-height: normal;"&gt;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?&lt;br&gt;
&lt;br&gt;
Paul&lt;br&gt;
&lt;/div&gt;</description><author>paullever</author><pubDate>Mon, 07 Jul 2008 20:18:39 GMT</pubDate><guid isPermaLink="false">New Post: Issue of AR6K Driver on WinCE 5.0 20080707081839P</guid></item><item><title>New Post: Issue of AR6K Driver on WinCE 5.0</title><link>http://www.codeplex.com/CEWifiDriverAR6000/Thread/View.aspx?ThreadId=30687</link><description>&lt;div style="line-height: normal;"&gt;We added AR6K SDIO driver by manual build and got AR6K_NDIS_SDIO.dll.&lt;br&gt;
Then we also added registry and added AR6K_NDIS_SDIO.dll to our image.&lt;br&gt;
&lt;br&gt;
I built one debug image to check some debug message and got following error message:&lt;br&gt;
&lt;br&gt;
0x87d406a0: virtualcopying 801bd000 &amp;lt;- 801bd000 (2f6ef)!&lt;br&gt;
0x87d406a0: LoadO32 internal Failed, retval = 0000000e&lt;br&gt;
0x87d406a0: Loading of Module 'ar6k_ndis_sdio.dll' (878554c8) failed, prevRefCnt = 0, refcnt = 0, inuse = 00000000, dwErr = 0000000e&lt;br&gt;
0x87d406a0: NK Kernel: DEBUGCHK failed in file c:\wince500\private\winceos\coreos\nk\kernel\loader.c at line 1981 &lt;br&gt;
0x87d406a0: DEBUG_BREAK @80163220 MD=1f Ignored.&lt;br&gt;
0x87d406a0: SDBusDriver: Failed to load driver DLL : ar6k_ndis_sdio.dll&amp;nbsp;&lt;br&gt;
&lt;br&gt;
Do any one ever&amp;nbsp;see the same error&amp;nbsp;before ?&lt;br&gt;
&lt;/div&gt;</description><author>LawranceYang</author><pubDate>Fri, 04 Jul 2008 06:11:28 GMT</pubDate><guid isPermaLink="false">New Post: Issue of AR6K Driver on WinCE 5.0 20080704061128A</guid></item><item><title>New Post: Issue of AR6K Driver on WinCE 5.0</title><link>http://www.codeplex.com/CEWifiDriverAR6000/Thread/View.aspx?ThreadId=30687</link><description>&lt;div style="line-height: normal;"&gt;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.&lt;br&gt;
&lt;br&gt;
Paul&lt;br&gt;
&lt;/div&gt;</description><author>paullever</author><pubDate>Wed, 02 Jul 2008 16:16:50 GMT</pubDate><guid isPermaLink="false">New Post: Issue of AR6K Driver on WinCE 5.0 20080702041650P</guid></item><item><title>New Post: Issue of AR6K Driver on WinCE 5.0</title><link>http://www.codeplex.com/CEWifiDriverAR6000/Thread/View.aspx?ThreadId=30687</link><description>&lt;div style="line-height: normal;"&gt;&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Could anyone share your experience about AR6K driver on WinCE 5.0 ?&lt;br&gt;
I am build a WinCE 5.0 system with AR6K driver support.&lt;br&gt;
Then I can build AR6K_NDIS_SDIO.dll and I had combined it into NK.bin.&lt;br&gt;
But after I insert AR6K SDIO card into our system, there are one error (ERROR_OUTOFMEMORY) while loading AR6K_NDIS_SDIO.dll.&lt;br&gt;
I'll deeply appreciate if any&amp;nbsp;one can help me to found out any problem on this driver ~&lt;/p&gt;
&lt;p&gt;Lawrance&lt;/p&gt;
&lt;/div&gt;</description><author>LawranceYang</author><pubDate>Wed, 02 Jul 2008 11:31:31 GMT</pubDate><guid isPermaLink="false">New Post: Issue of AR6K Driver on WinCE 5.0 20080702113131A</guid></item><item><title>New Post: Issue with AR6K SDIO Driver</title><link>http://www.codeplex.com/CEWifiDriverAR6000/Thread/View.aspx?ThreadId=26211</link><description>&lt;div style="line-height: normal;"&gt;Once the WZC window comes up, you should see the APs available. Have you verified that the AP shows up on another system, say a laptop? Start with the AP setup as Open and broadcasting its SSID. Have you re-scanned from WZC? If you have wzctool in your retail dir, you can do these under command line control. Makes it easier to debug. &lt;br&gt;
&lt;br&gt;
Paul&lt;br&gt;
&lt;/div&gt;</description><author>paullever</author><pubDate>Mon, 16 Jun 2008 15:11:57 GMT</pubDate><guid isPermaLink="false">New Post: Issue with AR6K SDIO Driver 20080616031157P</guid></item><item><title>New Post: Issue with AR6K SDIO Driver</title><link>http://www.codeplex.com/CEWifiDriverAR6000/Thread/View.aspx?ThreadId=26211</link><description>&lt;div style="line-height: normal;"&gt;Dear Paul,&lt;br&gt;
I&amp;nbsp;have been able to get past the initialization successfully. Now i am able to get the mailbox interrupts.&lt;br&gt;
&lt;br&gt;
I'm now getting the WZC (ZeroConfig) window on my display but I'm not able to get the list of APs(Access Points).&lt;br&gt;
I&amp;nbsp;have enabled background scanning in the WLAN Client Driver. I have also&amp;nbsp;ensured that an AP is setup properly in proximity of the &lt;br&gt;
WLAN Module.&lt;br&gt;
Can you please guide me where exactly the problem may be arising in detecting the APs.&lt;br&gt;
&lt;br&gt;
Regards,&lt;br&gt;
Mrinal Ray&lt;br&gt;
&lt;/div&gt;</description><author>mrinalray</author><pubDate>Fri, 13 Jun 2008 06:57:41 GMT</pubDate><guid isPermaLink="false">New Post: Issue with AR6K SDIO Driver 20080613065741A</guid></item><item><title>NEW POST: Issue with AR6K SDIO Driver</title><link>http://www.codeplex.com/CEWifiDriverAR6000/Thread/View.aspx?ThreadId=26211</link><description>&lt;div style="line-height: normal;"&gt;Mrinal,&lt;br&gt;
No need to &lt;strong&gt;yell&lt;/strong&gt;.&lt;br&gt;
&lt;br&gt;
The interrupt will come back when the WLAN firmware application has completed initialization. I would suggest that you look closely at the host controller driver for the Davinici. Getting card side interrupt handling, CIRQ, correct on the Davinci SD host controller is not easy. There are a number of hoops you need to jump through and special cases to deal with that are timing dependent. You could put a break at the point in the code that the timeout is detected, but before the halt sequence starts. Then check the SD bus and see if the CIRQ is asserted, indicating that the HCD missed reporting it.&lt;br&gt;
&lt;br&gt;
Regards&lt;br&gt;
&lt;br&gt;
Paul&lt;br&gt;
&lt;/div&gt;</description><author>paullever</author><pubDate>Wed, 04 Jun 2008 15:26:31 GMT</pubDate><guid isPermaLink="false">NEW POST: Issue with AR6K SDIO Driver 20080604032631P</guid></item><item><title>NEW POST: Issue with AR6K SDIO Driver</title><link>http://www.codeplex.com/CEWifiDriverAR6000/Thread/View.aspx?ThreadId=26211</link><description>&lt;div style="line-height: normal;"&gt;Hi Paul!&lt;br&gt;
Thanks for your prompt reply.&lt;br&gt;
I am running on TI's DaVinci Platform with WINCE6.0 OS.&lt;br&gt;
&lt;br&gt;
I am getting the INT_WLAN. &lt;br&gt;
&lt;br&gt;
But i am not able to get the Mailbox interrupt which subsequntly sets the &amp;quot;&lt;span style="font-size:13px"&gt;&lt;em&gt;m_WMIReadyEvent&lt;/em&gt;&amp;quot; event.&lt;br&gt;
Since this event doesn't get set, the waiting thread on this event fails and i get the error message as follows:&lt;br&gt;
&lt;br&gt;
&lt;em&gt;AR6K: ERROR - No WMI_READY event after 20000 ms, failing initialization.&lt;br&gt;
&lt;br&gt;
&lt;/em&gt;It appears to me that it is essential to get a mailbox interrupt after INT_WLAN, otherwise the initialization will fail.&lt;br&gt;
&lt;br&gt;
In case of &lt;strong&gt;Linux&lt;/strong&gt;, i have found that we get the Mailbox interrupt after INT_WLAN and the initialization passes successfully.&lt;br&gt;
&lt;br&gt;
&lt;strong&gt;So, i wanted to know under what exact conditions the Mailbox interrupt comes?&lt;br&gt;
&lt;/strong&gt;&lt;br&gt;
Mrinal Ray&lt;br&gt;
&lt;br&gt;
&lt;/span&gt;
&lt;/div&gt;</description><author>mrinalray</author><pubDate>Wed, 04 Jun 2008 06:37:53 GMT</pubDate><guid isPermaLink="false">NEW POST: Issue with AR6K SDIO Driver 20080604063753A</guid></item><item><title>NEW POST: Issue with AR6K SDIO Driver</title><link>http://www.codeplex.com/CEWifiDriverAR6000/Thread/View.aspx?ThreadId=26211</link><description>&lt;div style="line-height: normal;"&gt;WLAN int occurs after the WLAN firmware completes initialization on the target.&lt;br&gt;
What hardware platform are you running on?&lt;br&gt;
&lt;br&gt;
Paul&lt;br&gt;
&lt;/div&gt;</description><author>paullever</author><pubDate>Tue, 03 Jun 2008 16:36:28 GMT</pubDate><guid isPermaLink="false">NEW POST: Issue with AR6K SDIO Driver 20080603043628P</guid></item><item><title>NEW POST: Issue with AR6K SDIO Driver</title><link>http://www.codeplex.com/CEWifiDriverAR6000/Thread/View.aspx?ThreadId=26211</link><description>&lt;div style="line-height: normal;"&gt;Hi!&lt;br&gt;
I am trying to use this client driver for the WLAN module having Atheros' AR6001GL chip.&lt;br&gt;
&lt;br&gt;
I am getting the following prints&lt;br&gt;
&lt;br&gt;
FIRMWARE MAJOR VERSION ==&amp;gt; 1&lt;br&gt;
FIRMWARE MINOR VERSION ==&amp;gt; 1&lt;br&gt;
&lt;br&gt;
during init.&lt;br&gt;
&lt;br&gt;
But, the Init function is failing because WMI Ready event is not getting set.&lt;br&gt;
It is evident that, for WMI Ready event to get set we must get the Mailbox interrupt from the WLAN module.&lt;br&gt;
&lt;br&gt;
In the process of initialization i get the  &lt;em&gt;Counter Interrupt. &lt;/em&gt;The &lt;em&gt;Mailbox interrupt&lt;/em&gt; is expected after this but i'm not getting that.&lt;br&gt;
This causes the init to fail.&lt;br&gt;
&lt;br&gt;
The error message is as under:&lt;br&gt;
AR6K: ERROR - No WMI_READY event after 20000 ms, failing initialization.&lt;br&gt;
&lt;br&gt;
&lt;strong&gt;I would like to know under what conditions the Mailbox interrupt can come during the init phase and why is it not coming.&lt;br&gt;
&lt;/strong&gt;I have verified that the SDIO interrupt is enabled and acknowledged properly.&lt;br&gt;
I am using Microsoft's earlier version of the Bus Driver. ie, SDBus0.&lt;br&gt;
&lt;br&gt;
&lt;br&gt;
Mrinal Ray&lt;br&gt;
&lt;/div&gt;</description><author>mrinalray</author><pubDate>Tue, 03 Jun 2008 09:50:21 GMT</pubDate><guid isPermaLink="false">NEW POST: Issue with AR6K SDIO Driver 20080603095021A</guid></item><item><title>NEW POST: Atheros Driver Framework Documents.</title><link>http://www.codeplex.com/CEWifiDriverAR6000/Thread/View.aspx?ThreadId=26991</link><description>&lt;div class="wikidoc"&gt;
Dear All,&lt;br /&gt; &lt;br /&gt;Can any body please  provide me with the HIF,WMI,HTC,BMI framework documents?I am trying to understand the code.&lt;br /&gt;If you have any documents written by your selves while understanding the code, please pass it.&lt;br /&gt; &lt;br /&gt;Thank you in Advance,&lt;br /&gt;Santosh&lt;br /&gt;
&lt;/div&gt;</description><author>santoshp</author><pubDate>Fri, 02 May 2008 07:51:39 GMT</pubDate><guid isPermaLink="false">NEW POST: Atheros Driver Framework Documents. 20080502075139A</guid></item><item><title>NEW POST: Issue with AR6K SDIO Driver</title><link>http://www.codeplex.com/CEWifiDriverAR6000/Thread/View.aspx?ThreadId=26211</link><description>&lt;div class="wikidoc"&gt;
The board you have can be reflashed to different target firmware levels. You should check with CardAccess. They should be able to either supply a driver for the current one or flash your board to the older firmware.&lt;br /&gt; &lt;br /&gt;Paul&lt;br /&gt;
&lt;/div&gt;</description><author>paullever</author><pubDate>Tue, 22 Apr 2008 20:11:23 GMT</pubDate><guid isPermaLink="false">NEW POST: Issue with AR6K SDIO Driver 20080422081123P</guid></item></channel></rss>