Re: 802.11 WLAN CF card support on WinCE42
- From: alenliau <alenliau@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 17 Apr 2006 08:20:01 -0700
hellow susan~
can you tell me the step to config the wlan cf card，i dont understand that
the sandisk have driver download in web，we just execute .exe，the card will
work correctly right? you have edited the registy , so your way is that
download the dll driver?and embedded it in image?
"Susan" wrote:
Hi Paul,.
Thanks for your help. I found the problem in pCMCIA driver, and the cards
are detected and working properly now.
Cheers
Susan
"Paul G. Tobey [eMVP]" wrote:
OK, and those settings are reasonable for your hardware? I'd check each one
of the entries under Parms, assuming that each in turn is wrong and trying
to prove that it's not. BusNumber looks a little strange. BusType looks
right to me.
The message listing sure makes it look like that PCMCIA error is the
problem. I'd fix that first and then try to get card drivers to work.
Maybe it's reading a value from a register that it thinks is part of the
PCMCIA set and using that value in another call...
Paul T.
"Susan" <Susan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2D6B8EFC-3B6F-41B5-8A9D-6D79CE38945A@xxxxxxxxxxxxxxxx
Thanks for your advice.
Here is the registry entry that I added for WiFi card:
[HKEY_LOCAL_MACHINE\Comm\PRISM]
@=""
"DisplayName"="Sandisk low power 128MB + Wi-Fi CompactFlash Card"
"Group"="NDIS"
"ImagePath"="PRISMNDS.dll"
[HKEY_LOCAL_MACHINE\Comm\PRISM\Linkage]
@=""
"Route"="PRISM1"
[HKEY_LOCAL_MACHINE\Comm\PRISM1]
@=""
"DisplayName"="Sandisk low power 128MB + Wi-Fi CompactFlash Card"
"Group"="NDIS"
"ImagePath"="PRISMNDS.dll"
"PRISMIOC"="ILP1:"
[HKEY_LOCAL_MACHINE\Comm\PRISM1\Parms]
@=""
"LoadFirmware"=dword:00000001
"PlatformID"=dword:0000801d
"InterruptNumber"=dword:0000000a
"IoBaseAddress"=dword:00000280
"Radio"=dword:00000001
"BusType"=dword:00000008
"BusNumber"=dword:00000002
[HKEY_LOCAL_MACHINE\Drivers\PCMCIA\_-IEEE_802.11_Wireless_LAN/CF_Card-E727]
@=""
"DLL"="ndis.dll"
"Prefix"="NDS"
"Miniport"="prism"
[HKEY_LOCAL_MACHINE\Drivers\PCMCIA\SanDisk-ConnectPlus-20D2]
@=""
"Dll"="NDIS.dll"
"Prefix"="NDS"
"Miniport"="prism"
And the following are the messages from kernel when card inserted, (sorry
about the mess message), there are a few lines failed in PCMCIA driver
because HW design are different from Lubbock, but driver code didn't
change
accordingly, those are for PCMCIA slot reset, power off/on, buss off/on:
EVICE!ActivateDeviceEx(Drivers\PCMCIA\SanDisk-ConnectPlus-20D2) entered
25232 PID:83c7d16a TID:439f5002 0x839bf440: >>> Loading module
prismnds.dll at address 0x01D90000-0x01DDF000
Loaded
'C:\WINCE420\PUBLIC\CESTRITON\RELDIR\TRITONARMV4IDEBUG\PRISMNDS.DLL',
no matching symbolic information found.
25337 PID:83c7d16a TID:439f5002 ==>NdisInitializeWrapper
25338 PID:83c7d16a TID:439f5002 <==NdisInitializeWrapper
25338 PID:83c7d16a TID:439f5002 ==>NdisMRegisterMiniport:
NdisWrapperHandle 00048820
25339 PID:83c7d16a TID:439f5002 ==>ndisRegisterMiniportDriver:
NdisWrapperHandle 00048820
25340 PID:83c7d16a TID:439f5002 <==ndisRegisterMiniportDriver: MiniBlock
00048F20
28563 PID:83c7d16a TID:439f5002 NdisMRegisterMiniport: MiniBlock 00048F20
28563 PID:83c7d16a TID:439f5002 <==NdisMRegisterMiniport: MiniBlock
00048F20, Status 0
28565 PID:83c7d16a TID:439f5002
28568 PID:83c7d16a TID:439f5002 ndisMInitializeAdapter: Miniport
00052AC8,
28578 PID:83c7d16a TID:439f5002 ==>ndisQueueMiniportOnDriver: Miniport
00052AC8, MiniBlock 00048F20
32563 PID:83c7d16a TID:439f5002 <==ndisQueueMiniportOnDriver: Miniport
00052AC8, MiniBlock 00048F20, rc 1
32576 PID:83c7d16a TID:439f5002 ==>NdisMSetAttributes: Miniport 00052AC8
32577 PID:83c7d16a TID:439f5002 ==>NdisMSetAttributesEx: Miniport
00052AC8
32577 PID:83c7d16a TID:439f5002 <==NdisMSetAttributes: Miniport 00052AC8
32581 PID:83c7d16a TID:439f5002 0x839bf440: PCMCIA driver BCR set up
failed
37106 PID:83c7d16a TID:439f5002 0x839bf440: PCMCIA driver SS BCR set up
failed
37649 PID:83c7d16a TID:439f5002 0x839bf440: PCMCIA driver SS BCR set up
failed
42106 PID:83c7d16a TID:439f5002 0x839bf440: PCMCIA driver SS BCR set up
failed
42649 PID:83c7d16a TID:439f5002 0x839bf440: PCMCIA driver SS BCR set up
failed
43776 PID:83c7d16a TID:439f5002 0x839bf440: NDIS: ERROR -
INdisReleasePcmciaWindow port ffffffff not found
47565 PID:83c7d16a TID:439f5002 ==>NdisMDeregisterAdapterShutdownHandler:
Miniport 00052AC8
47565 PID:83c7d16a TID:439f5002 <==NdisMDeregisterAdapterShutdownHandler:
Miniport 00052AC8
47566 PID:83c7d16a TID:439f5002 ***NDIS*** (b, 2054)
47566 PID:83c7d16a TID:439f5002 INIT FAILURE: Dequeueing the miniport
from the driver block.
51564 PID:83c7d16a TID:439f5002 ==>ndisDeQueueMiniportOnDriver, Miniport
00052AC8, MiniBlock 00048F20
51565 PID:83c7d16a TID:439f5002 <==ndisDeQueueMiniportOnDriver: Miniport
00052AC8, MiniBlock 00048F20
51567 PID:83c7d16a TID:439f5002 ***NDIS*** (b, 2081)
51568 PID:83c7d16a TID:439f5002 INIT FAILURE: Dereferencing the
miniport block.
51568 PID:83c7d16a TID:439f5002 ndisDereferenceMiniport:Miniport
00052AC8, Ref = 0
51570 PID:83c7d16a TID:439f5002 ==>ndisMUnload: DriverObject 00047D50
51570 PID:83c7d16a TID:439f5002 ndisMUnload: MiniBlock 00048F20
51571 PID:83c7d16a TID:439f5002 <==ndisMUnload: DriverObject 00047D50,
MiniBlock 00048F20
51581 PID:83c7d16a TID:439f5002 0x839bf440: <<< Unloading module
prismnds.dll at address 0x01D90000-0x01DDF000
Unloaded symbols for
'C:\WINCE420\PUBLIC\CESTRITON\RELDIR\TRITONARMV4IDEBUG\PRISMNDS.DLL'
51596 PID:83c7d16a TID:439f5002 0x839bf440: NDIS: ERROR -
NdisPCIBusDeviceInit no BusNumber for
Comm\PCI\SanDisk-ConnectPlus-20D2\Parms
52602 PID:83c7d16a TID:439f5002 0x839bf440: DEVICE!StartOneDriver
RegisterDevice(NDS, 1, NDIS.dll, 0x841f378) failed
52605 PID:83c7d16a TID:439f5002 0x839bf440: PCMCIA:LoadPCCardDriver:
ActivateDeviceEx('Drivers\PCMCIA\SanDisk-ConnectPlus-20D2') failed 110
Thanks
Susan
"Paul G. Tobey [eMVP]" wrote:
Yes, that's what I'd look at. Verify that the slot settings for the
PCMCIA
driver are correct and recheck those for the new card. I'm not entirely
sure that the message is wrong; it might just be that the driver rejected
being loaded because a driver setting appeared wrong to it, and the slot
number was screwed up or something.
What registry entries did you add for the card?
Paul T.
"Susan" <Susan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:79C1F1BD-131C-424D-8D39-BDB9539F0723@xxxxxxxxxxxxxxxx
Hi Paul,
Thanks for your prompt reply.
First of all, PCMCIA slot is functional, I tested with memory card, it
works
OK.
The wireless card I am using is Sandisk 802.11b WiFi with 128 memory.
And
I
got the installation kit from SanDisk website, and extracted registry
settings after install it on the device, and then include both driver
and
registry setting into kernel image. I also tested the same card on
Lubbock
WinCE42 platform, it is functioning on Lubbock. However, on our target
platform, which is also PXA255 WinCE42 based, I got the errors. It is
likely
something worng with PCMCIA driver, but I have no clue what to look
for.
Regards,
Susan
"Paul G. Tobey [eMVP]" wrote:
Is the PCMCIA slot functional, in general? You can plug a flash card,
say,
into it and have it show up as \Storage Card in the filesystem?
Which model number is this card, exactly? Where did you get the
instructions for adding the registry entries to the platform? Can you
use
the installer for the driver to install it on your device via
ActiveSync?
Does that work (at least until you reboot)?
Paul T.
"Susan" <Susan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:74600A26-7E62-4A4C-A0A8-155B07D8BC67@xxxxxxxxxxxxxxxx
Hi Paul,
After insert Wi-Fi CF card into my target platform (PXA255 Win42
based),
system started to load the WiFi card driver and NDIS driver. But I
got
some
error message, as the following,
NDIS: ERROR - INdisReleasePcmciaWindow port ffffffff not found
==>NdisMDeregisterAdapterShutdownHandler: Miniport 00052AC8
<==NdisMDeregisterAdapterShutdownHandler: Miniport 00052AC8
***NDIS*** (b, 2054)
INIT FAILURE: Dequeueing the miniport from the driver block.
I don't have the source code to trace into NDIS driver, could you
give
me
some clue what would cause the problem?
Thanks
Susan
"Paul G. Tobey [eMVP]" wrote:
Out of the box, you can get Intersil support and Cisco 350 support.
The
Intersil support requires that you set a SYSGEN variable manually,
while
the
Cisco support appears in the catalog.
At a guess, your registry settings for the Linksys card probably
have
to
be
adjusted based on the characteristics of your platform. Check the
interrupt
and base address settings...
Paul T.
"Susan" <Susan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3F9F443A-2AE0-44E9-8358-A566C6234121@xxxxxxxxxxxxxxxx
Hi,
What kind of WLAN CF card products are supported by WinCE42? What
components
do I need to include into workspace from WinCE42?
My HW platform is XScale based running WinCE42. I tried two
types
of
WLAN(802.11b) CF card, but both of them can't be recongized by
system.
One
is
LINKSYS wireless-B CF card, I found the driver for WinCE on the
website
(Prismnds.dll), and includeed it into the image along with
registry
settings.
But system still can't recongnize it properly. Another one is a
Sandisk
WLAN
802.11b CF with 128M memory. I couldn't find WinCE42 driver for
it.
Could anyone recommend some WLAN(802.11) CF cards which are
supported
by
WinCE42 platform builder?
Thanks in advance
Susan
- Prev by Date: How to add Prism 2.5 Wireless card drivers?
- Next by Date: Re: How to add Prism 2.5 Wireless card drivers?
- Previous by thread: How to add Prism 2.5 Wireless card drivers?
- Next by thread: WM5 Unintended Wakeups
- Index(es):
Relevant Pages
|
