Re: pcmcia card in wince 5.0 problem

Make sure do not set BSP_PCCARD_I82365
You should have setting like this
set BSP_PCCARD_I82365=
set BSP_PCCARD_TIPCCARD=1
before making image.

Have you try PCI PC Card (not the one built in) on this machine?

"david" <dajun.chen@xxxxxxxxx> wrote in message
news:1136903212.320805.4340@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Hi Remi and David,
>
> Here is the relevant debug trace cought after a pcmcia card inderted to
> the pccard socket:
>
> PID:83f99a32 TID:83eecbd6 0x83ee9998: ISA PCCARD: ThreadRun
> Intr(nSocket=0) status bCardStatusChange = 0x8, BSocketState = 0xc
> PID:83f99a32 TID:83eecbd6 0x83ee9998: CARDBUS: CPcmciaCardSocket
> (Socket=204 Index=2) Created
> PID:83f99a32 TID:83eecbd6 0x83ee9998: PCCARD: PCMCIA (dwWinIndex=0)
> memory window created
> PID:83f99a32 TID:83eecbd6 0x83ee9998: PCCARD: PCMCIA (dwWinIndex=1)
> memory window created
> PID:83f99a32 TID:83eecbd6 0x83ee9998: PCCARD: PCMCIA (dwWinIndex=2)
> memory window created
> PID:83f99a32 TID:83eecbd6 0x83ee9998: PCCARD: PCMCIA (dwWinIndex=3)
> memory window created
> PID:83f99a32 TID:83eecbd6 0x83ee9998: PCCARD: PCMCIA (dwWinIndex=4)
> memory window created
> PID:83f99a32 TID:83eecbd6 0x83ee9998: PCCARD: PCMCIA (dwWinIndex=0)
> memory window created
> PID:83f99a32 TID:83eecbd6 0x83ee9998: PCCARD: PCMCIA (dwWinIndex=1)
> memory window created
> PID:83f99a32 TID:83eecbd6 0x83ee9998: PDCardResetSocket: CARD IN SOCKET
> NOT RDY AFTER 2000ms
> PID:83f99a32 TID:83eecbd6 0x83ee9998:
> CPCPcmciaCard::GetConfigureRegisterBase: Can't get PCMCIA register
> address. return FAILS
> PID:83f99a32 TID:83eecbd6 0x83ee9998: ISA PCCARD: ThreadRun
> Intr(nSocket=0) status bCardStatusChange = 0x4, BSocketState = 0xc
> PID:83f99a32 TID:83eecbd6 0x83ee9998: ISA PCCARD: ThreadRun
> Intr(nSocket=0) status bCardStatusChange = 0x8, BSocketState = 0x0
>
> The CEPC used was a Toshiba Satlellite Pro laptop PC, about a year old.
> I checked that the pccard bridge worked fine under XP. The laptop uses
> a TI pccard controller, but its device ID is not included in the
> original wince 5.0 "pcc_tipccard.reg".
>
> Better than controllers from other verdors, actions were observed after
> pccard inserted. But problem is still there.
>
> David
>
> It is
>


.

Relevant Pages

  • Re: PCMCIA I82365 issue
    ... PC Card socket driver and PC Card service has to be loaded at phase one. ... After I insert the PCMCIA CF card in the PCMCIA slot the system ... ISA PCCARD: ThreadRun Intrstatus bCardStatusChange = 0x8, ... 0x83f29800: PCCARD: PCMCIA memory window created ...
    (microsoft.public.windowsce.platbuilder)
  • PCMCIA I82365 issue
    ... I have WinCe 5.0 on GeodeLx platform .I set BSP_PCMCIA_I82365 ... After I insert the PCMCIA CF card in the PCMCIA slot the system ... ISA PCCARD: ThreadRun Intrstatus bCardStatusChange = 0x8, ... 0x83f29800: PCCARD: PCMCIA memory window created ...
    (microsoft.public.windowsce.platbuilder)
  • Re: pcmcia card in wince 5.0 problem
    ... memory window created ... The CEPC used was a Toshiba Satlellite Pro laptop PC, ... I checked that the pccard bridge worked fine under XP. ... a TI pccard controller, but its device ID is not included in the ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Wnidows 2000 and PCI-Cardbus bridge resources
    ... in the card space using the bus driver interface PCMCIA_MODIFY_MEMORY_WINDOW. ... The initial host memory window should be allocated in the INF. ... > I am a device driver newbie and I have been reading a lot lately. ...
    (microsoft.public.development.device.drivers)
  • WinCe 5.0 CF Wifi card problem.
    ... I am using WinCe 5.0 and I am trying to use the D-link DCF-660W Wifi CF ... When attaching the CF card, it gives the following log entries, and ... memory window created ...
    (microsoft.public.windowsce.platbuilder)