NDIS miniport driver and NE2000 Compact Flash Ethernet card

Hi all,
I'm trying to get the "real" miniport driver to work on our platform.
Our XSCALE platform (WinCE 4.2) has only one Ethernet port (PCMCIA-CF card
NE2000). It is based on the Lubbock platform but has as stated only one
Ethernet port.

Downloading and debugging is done over this port and it works fine. Also
VMINI works fine (connects to internet websites, FTP works etc.).
VMINI relies on KITL so it is impossible to use for product Ethernet
networking.
Instead we try to build the device without KITL but with NE200 Compatible
Ethernet Driver.

When we enable the device it detects the NE2000 card, loads the NE2000
driver and can read the MAC adress. But it gets no IP-adress (we use dhcp).
AutomaticIP is enabled in the device so after about 10 seconds we get a
"faked" IP address in the range 169.254.xxx.xxx.
Trying to Ping this IP adress from a PC is of course not successfull. Trying
to ping from our device to a PC on the network is also unsuccessfull. Ping
own IP adress from device seems OK.

As we only have one port it is not possible to do any effective debugging.
But it seems that hardware is OK- VMINI works on it. I have tried to find
some registry setting that solves the problem, but no luck so far.

Any one got a clue, Thanks
Igge

Woojung
Sat Dec 31 12:51:01 CST 2005

Hi,

debug message is the one of best debugging tools. Put debug message where it
might be important to check the status.

Ethereal is also a good tool to debug network stuff, as long as your NIC
driver sends something through wire.

Hope this helps.
Woojung

"Igge H" wrote:

> Hi all,
> I'm trying to get the "real" miniport driver to work on our platform.
> Our XSCALE platform (WinCE 4.2) has only one Ethernet port (PCMCIA-CF card
> NE2000). It is based on the Lubbock platform but has as stated only one
> Ethernet port.
>
> Downloading and debugging is done over this port and it works fine. Also
> VMINI works fine (connects to internet websites, FTP works etc.).
> VMINI relies on KITL so it is impossible to use for product Ethernet
> networking.
> Instead we try to build the device without KITL but with NE200 Compatible
> Ethernet Driver.
>
> When we enable the device it detects the NE2000 card, loads the NE2000
> driver and can read the MAC adress. But it gets no IP-adress (we use dhcp).
> AutomaticIP is enabled in the device so after about 10 seconds we get a
> "faked" IP address in the range 169.254.xxx.xxx.
> Trying to Ping this IP adress from a PC is of course not successfull. Trying
> to ping from our device to a PC on the network is also unsuccessfull. Ping
> own IP adress from device seems OK.
>
> As we only have one port it is not possible to do any effective debugging.
> But it seems that hardware is OK- VMINI works on it. I have tried to find
> some registry setting that solves the problem, but no luck so far.
>
> Any one got a clue, Thanks
> Igge
>
>
>

Remi
Sun Jan 01 06:24:58 CST 2006

I agree with Woojung's method, but I can also imagine you can have trouble
debugging a non-debug image!

Another advice...
This may sound stupid but:

1) Did you try to assign a static IP to your adapter?
2) Did you check your reginit.ini file to make sure the settings you expect
are here, and in the same order you expect? NE2000-related Registry entries
are quite special as they are scattered in both Common.reg and Platform.reg
(at least for CEPC devices)

Happy new year to everyone who reads this.
Remi

IggeH
Thu Jan 05 03:45:02 CST 2006

I finally solved the problem, It was the Interrupt Service Routine that
returned wrong return value for PCMCIA LEVEL IRQ. So if you use
XScale(XSC1BD) code that comes with Platform Builder 4.2 make sure you know
how you defined EBOOT. See code from intxsc1.c below:


else if (SL0T0_IREQREADY_INT_STAT)
{
SL0T0_IREQREADY_INT_STAT_SET (1);
#ifndef EBOOT
return SYSINTR_PCMCIA_LEVEL;
#else
return SYSINTR_ETHER;
#endif
}

Igge
"Remi de Gravelaine" wrote:

> I agree with Woojung's method, but I can also imagine you can have trouble
> debugging a non-debug image!
>
> Another advice...
> This may sound stupid but:
>
> 1) Did you try to assign a static IP to your adapter?
> 2) Did you check your reginit.ini file to make sure the settings you expect
> are here, and in the same order you expect? NE2000-related Registry entries
> are quite special as they are scattered in both Common.reg and Platform.reg
> (at least for CEPC devices)
>
> Happy new year to everyone who reads this.
> Remi
>
>
>

Martinos
Thu Jan 19 05:10:05 CST 2006

Hi Igge,
i've got exactly the same problem but i' not able to solve it. Can you
explain to me in more datails... what do you mean with "make sure you know
how you defined EBOOT"? I'll really appreciate it.
Thanks
OSCAR

"Igge H" wrote:

> I finally solved the problem, It was the Interrupt Service Routine that
> returned wrong return value for PCMCIA LEVEL IRQ. So if you use
> XScale(XSC1BD) code that comes with Platform Builder 4.2 make sure you know
> how you defined EBOOT. See code from intxsc1.c below:
>
>
> else if (SL0T0_IREQREADY_INT_STAT)
> {
> SL0T0_IREQREADY_INT_STAT_SET (1);
> #ifndef EBOOT
> return SYSINTR_PCMCIA_LEVEL;
> #else
> return SYSINTR_ETHER;
> #endif
> }
>
> Igge
> "Remi de Gravelaine" wrote:
>
> > I agree with Woojung's method, but I can also imagine you can have trouble
> > debugging a non-debug image!
> >
> > Another advice...
> > This may sound stupid but:
> >
> > 1) Did you try to assign a static IP to your adapter?
> > 2) Did you check your reginit.ini file to make sure the settings you expect
> > are here, and in the same order you expect? NE2000-related Registry entries
> > are quite special as they are scattered in both Common.reg and Platform.reg
> > (at least for CEPC devices)
> >
> > Happy new year to everyone who reads this.
> > Remi
> >
> >
> >