Re: Good old SA1110 PCMCIA and CE 4.2 :) by Mark
Mark
Wed Jul 30 08:35:52 CDT 2003
Sounds like we might be seeing something...similar...but it doesn't sound
identical.
First, some questions..
What drivers are you using with the Cisco 350 series card? The PCX500
driver that's included with Platform Builder? We've run into other problems
with that driver, so we've been trying to use stuff directly from Cisco.
(Of course, we can't seem to get a driver that "officially" supports CE 4.2
from anyone.)
The driver you're using... Is it loaded via detect routine, or is there a
plug-n-play ID for it in the registry? This question is really related to a
lot of the stuff we're seeing. I'll get to that in a second.
What's your hardware like? Is it an Assabet board? Your own hardware? Is
your BSP based on the Assabet BSP?
Here's what we see...
For us, we run into problems trying to get NIC drivers loaded when the
PCMCIA card is in the slot at cold boot. The only time we see it work is if
the driver is loaded via detect routine. If it's loaded via plug-n-play ID,
it doesn't work. Now, after the platform has settled, if we remove the
card, and re-insert it, the drivers load fine. We've tried this with CE 3.0
era drivers for Cisco cards, Symbol cards, Proxim cards (yeah, someone uses
them), Orinoco cards, and some generic Intersil PRISM chipset based stuff.
This is pretty important to us because our shipping product is completely
sealed. You CAN'T remove the card and re-insert it.
This was something that I saw in CE 4.0 last year, but I saw the following
QFE:
<QFE>
Component: NDIS
a.. 020617_Q322851 - Wireless card will not complete initialization if
card is present during cold boot, due to NDIS deadlock.
</QFE>
I had assumed that whatever was fixed with this QFE was also fixed under CE
4.2. I tried out one card, saw it work (which was loaded via detect
routine) and assumed everything was happy. Now, I'm not so sure.
Another problem we see when we boot with cards in like this is a different
DEBUGCHK in NDIS. It's not the same as yours, but it might be related. I
made a post about it yesterday titled "NDIS EnterCriticalSection DEBUGCHK in
CE 4.2 - HELP!" Check it out, and let me know if you've seen anything like
that.
Either way, if we find out any information on PCMCIA/NDIS releated problems,
or wireless NIC drivers, we'll be sure to share.
Mark Murawski
Vocollect, Inc.
"Bo Henriksen" <bodothenriksenatnordiciddotcom> wrote in message
news:#da3eQpVDHA.2260@TK2MSFTNGP09.phx.gbl...
> Hi,
>
>
> I'm having trouble with the PCMCIA driver for CE 4.2. When I warm/cold
boot
> my device with a CISCO 350 series pcmcia card inserted
> the driver crashes (device.exe) and will not load any PCMCIA cards
> hereafter. However, if I have some other PCMCIA card inserted upon a
> warm/boot, e.g. a wired ne2000 compatible card, the driver loads without
any
> problems. If I then unplug the wired card and insert a CISCO card the
driver
> also loads fine. It seems there are some delay problems in loading the
cisco
> driver upon startup. In CE 4.1 I had no problems (using SA1110 BSP with
the
> same drivers as in 4.2).
>
> Below is some debug information:
>
> 0x8df93000: PCMCIA: DEBUGCHK failed in file
> d:\mckendric\public\common\oak\drivers\pcmcia\mdd\load.c at line 763
> 0x8df93000: DEBUG_BREAK @0306c144 MD=1f Ignored.
> 0x8df93000: PCMCIA PDCardSetSocket
> 0x8df93000: PCMCIA PDCardSetSocket Powersettings
> 0x8df93000: SetSOCK Powering Socket 1
> ....
> ..
> .
>
> I looked up the line in load.c and found a
> DEBUGCHK(pPsock->hLoad == NULL);
>
> Does anyone know what the problem is here?
>
> Best regards,
>
> Bo Henriksen
> NordicID
>
>