Re: PCCARD driver question
- From: "liguangyu" <lgy1980@xxxxxxx>
- Date: Fri, 5 May 2006 15:07:43 +0800
I guess "CardGetNextTuple returned fails" is not so bad because it's only
mean that the CIS has got it end.
the next step the BUS driver should do it to scan the reg entry to find
which client driver to load.
do you have any reg entry in [HKEY_LOCAL_MACHINE\Drivers\PCMCIA\ to indicate
the client driver?
Liguangyu
"Bruce Eitman (eMVP)" <beitman.nospam@xxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:OeOU5rOVGHA.4452@xxxxxxxxxxxxxxxxxxxxxxx
1341689 PID:43f8fb16 TID:83dde0aa 0x83e116b8: GetCardCRC: CardGetNextTuple
returned fails
That is bad, and can be a symptom of incorrect power and/or PCMCIA timing.
--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net
Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member
"C. Klaver" <CKlaver@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:28A63267-710E-45D1-9CAE-0E28751F82C3@xxxxxxxxxxxxxxxx
Thanks for your reply!
I checked the dll's you mentioned and they are all present in the (denug)
image. When I look at the debugger output when inserting the card, I see
the
following (excuses for the formatting):
1341192 PID:43f8fb16 TID:83deba82 0x83debcc4: PCCARD: PCMCIA
(dwWinIndex=0)
memory window created
1341193 PID:43f8fb16 TID:83deba82 0x83debcc4: PCCARD: PCMCIA
(dwWinIndex=1)
memory window created
1341193 PID:43f8fb16 TID:83deba82 0x83debcc4: PCCARD: PCMCIA
(dwWinIndex=0)
memory window created
1341194 PID:43f8fb16 TID:83deba82 0x83debcc4: PCCARD: PCMCIA
(dwWinIndex=1)
memory window created
1341689 PID:43f8fb16 TID:83dde0aa 0x83e116b8: GetCardCRC:
CardGetNextTuple
returned fails
1341800 PID:43f8fb16 TID:83dde0aa 0x83e116b8:
DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\PCCARD\PCMCIA\INSTANCE\PCMCIA1\Prefix) returned 2
1341801 PID:43f8fb16 TID:83dde0aa 0x83e116b8:
DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\PCCARD\PCMCIA\INSTANCE\PCMCIA1\BusPrefix)
returned 2
1341814 PID:43f8fb16 TID:83dde0aa 0x83e116b8: >>> Loading module
pcmcia.dll
at address 0x01900000-0x01915000
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\MYSANDGATE\RELDIR\SANDGATEII_ARMV4I_DEBUG\PCMCIA.DLL'
1341874 PID:43f8fb16 TID:83dde0aa 0x83e116b8: CardBus.DLL
DLL_PROCESS_ATTACH
1341882 PID:43f8fb16 TID:83dde0aa 0x83e116b8: GetCardCRC:
CardGetNextTuple
returned fails
1341897 PID:43f8fb16 TID:43bf0e32 0x83da9400: >>> Loading module
serial.dll
at address 0x03320000-0x0333B000 (RW data at 0x01F39000-0x01F395C8)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\MYSANDGATE\RELDIR\SANDGATEII_ARMV4I_DEBUG\SERIAL.DLL'
1341963 PID:43f8fb16 TID:43bf0e32 0x83da9400: <<< Unloading module
serial.dll at address 0x03320000-0x0333B000 (RW data at
0x01F39000-0x01F395C8)
Unloaded symbols for
'C:\WINCE500\PBWORKSPACES\MYSANDGATE\RELDIR\SANDGATEII_ARMV4I_DEBUG\SERIAL.DLL'
1341976 PID:23fc34ee TID:43bf0e32 0x83da9400: RELFSD: Opening file
NE2000.DLL from desktop
1342837 PID:43f8fb16 TID:43bf0e32 0x83da9400: >>> Loading module
ne2000.dll
at address 0x01780000-0x01791000
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\MYSANDGATE\RELDIR\SANDGATEII_ARMV4I_DEBUG\NE2000.DLL'
1342894 PID:43f8fb16 TID:43bf0e32 0x83da9400: NE2000: DLL_PROCESS_ATTACH
1342894 PID:43f8fb16 TID:43bf0e32 0x83da9400: DetectNE2000: DevType = 4,
expected 6
1342896 PID:43f8fb16 TID:43bf0e32 0x83da9400: NE2000: DLL_PROCESS_DETACH
1342897 PID:43f8fb16 TID:43bf0e32 0x83da9400: <<< Unloading module
ne2000.dll at address 0x01780000-0x01791000
Unloaded symbols for
'C:\WINCE500\PBWORKSPACES\MYSANDGATE\RELDIR\SANDGATEII_ARMV4I_DEBUG\NE2000.DLL'
1342904 PID:43f8fb16 TID:43bf0e32 0x83da9400: INFO: Setting PCCARD slot 0
voltage to 0v (off).
1342972 PID:c3d9b242 TID:43bf0e32 0x83da9400: DlgMgr: FindDlgItem id 1
returning NULL.
Where PID:43f8fb16 is device.exe
What I understand from this is that the device.exe first loads a driver
for
a serial card, then unloads it. Secondly it tries to load a doesNE2000
driver, then unloads it. I don't understand however why it doesnt try to
load
a memory card driver, which is present in the image.
The output of mi mod at the shell prompt is:
M56: pcc_mainstoneii.dll 83deb978 00000008 01950000 000000ff
M57: pcc_serv.dll 83f0a0a8 00000008 01920000 00000003
M58: pcmcia.dll 83b16e14 00000008 01900000 00000003
I don't see pccard.dll however...
What could be the next step?
Thanks for your time!
C
"Bruce Eitman (eMVP)" wrote:
There can be different reasons for the result that you see:
1. No driver included in the device for the card that you are using
2. PCMCIA timing is not set up right for your board
3. The driver as it came with PB is polling for interrupts - not so
good
for production
and possibly others.
First check that you actually have a driver for the card that you are
using.
Use a debug build of device.exe, pcc_serv.dll, pcmcia.dll and your
pccard.dll. These will provide you with significantly more information
to
go on to debug this problem. But, if the timing isn't right the message
that you see in the debug output is just a simptom of the timing
problem.
--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net
Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member
"C. Klaver" <C. Klaver@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C015C3B8-4990-4E26-BDFA-F6208E3B7077@xxxxxxxxxxxxxxxx
Hi,
I am working with a SandgateII eval board (PXA270). I got WCE 5.0 up
and
running. Now when I put in a Flash PCCARD into the slot I get a window
with
the title "Unidentified PCCARD Adapter" and the prompt "Enter the name
of
the
driver for this PCCARD:". The entry field is filled with the text
"Unknown
card in socket xx" (where xx is increasing with each try).
As far as I can see, I have included in the OS the PCCARD drivers that
came
with the BSP, so I understood that the OS would see the driver and
load it
when needed.
Is there anything additional that I need to do in order to get PCCARD
working?
I am pretty new to this field, so I might be asking something very
obvious
here. If so, sorry.
.
- Prev by Date: Re: touch.dll
- Next by Date: Re: touch.dll
- Previous by thread: SBOOT Problem in CEPC Platform
- Next by thread: WinCE based devices enabled with printing capability
- Index(es):
Relevant Pages
|
