Re: Ethernet driver problem

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Michele Bove (michele.bove_at_selesta.it)
Date: 03/04/04


Date: 4 Mar 2004 06:19:25 -0800

OK, bug found in NE2000 driver - function CardSetup().
Original driver doesnt provide a multiplier parameter for address
shifting, and uses a loop to download mac address into NIC

    for (i = 0; i < NE2000_LENGTH_OF_ADDRESS; i++)
    {
        NdisRawWritePortUchar(
            Adapter->IoPAddr + (NIC_PHYS_ADDR + i),
            Adapter->StationAddress[i]
        );
    }

My board have IO addresses shifted by 1, So MAC address is written
wrong.
I dont understand why DHCP packets went out correctly, but after this
correction driver starts the work.
I'm going now to apply QFEs ...

michele.bove@selesta.it (Michele Bove) wrote in message news:<6a4bf7d7.0402270920.10c22a9d@posting.google.com>...
> Thank you for your answer, Valter.
> I'm using a JTAG hardware debugger (RAVEN + Intel compiler EXDI
> driver) and I'm not using KITL, for now.
> So, BSP_NOSHAREETH = 1
> I think that some registry settings are OK, because :
> - If I enable DHCP client, DHCP packets are sent to DHCP server and
> packets from DHCP are received and decoded correctly. After this the
> board send some ARP packets for verifying if IP address received is
> valid.
> - If I disable DHCP client, ARP packets are sent immediately.
> I see also WINS packets in output, but without answer, so I'm
> investigating about them.
> But after these operations, the board receive for example ICMP packets
> but doesn't work.
> This is my first job with WIndowsCE and I think I have a lot to learn
> ....
> Any other suggestion is good for me.
>
> Valter Minute <vminute@REMOVEMEinwind.it> wrote in message news:<Xns949BB394D579DVALTERMINUTE@207.46.248.16>...
> > michele.bove@selesta.it (Michele Bove) wrote in
> > news:6a4bf7d7.0402260819.7a9d98ee@posting.google.com:
> >
> > > Hi, I'm developing a board with a PXA255 and Asix 10/100 Ne2000
> > > compatible ethernet controller.
> > > First step of WindowsCE 4.2 porting (ethernet bootloader) works
> > > fine. Second step instead give me some troubles.
> > > Kernel start correctly, ethernet drivers seems to works (I obtain
> > > an IP address from a DHCP server) but after this step TCP/IP
> > > doesnt work. I'm using a serial debug interface, and I can see
> > > that ping ethernet packets from my PC (60 bytes len) are received
> > > but not routed to an higher level.
> > > Someone can suggest me a potential reason for this ?
> > > Thanks.
> >
> > Are you connected to PB using KITL?
> > In this case check that the BSP_NOSHAREETH environment variable is not
> > set and that you followed the directions of the article entitled
> > "Ethernet Debug Sharing Procedures" in PB help.
> >
> > If your system is working in release mode, without KITL, and the frames
> > are received only at the ethernet level and not by the TCP/IP stack,
> > check that the registry settings that link TCP/IP and your network
> > adapter are correct. Try to build a debug image without KITL and enable
> > the debug zones related to TCP/IP and network drivers (you should put
> > the correct entries under HKEY_LOCAL_MACHINE\DebugZones on the target
> > device).



Relevant Pages

  • Re: Ethernet driver problem
    ... driver) and I'm not using KITL, ... If I enable DHCP client, DHCP packets are sent to DHCP server and ... packets from DHCP are received and decoded correctly. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Filter Hook
    ... the callback routine is been invoked at DISPATCH_LEVEL. ... If you really have to keep such a queue for the packets, then the IP filter driver is not suitable for your needs since you have to process all the packets in the callback routine without any wait actionand return it to the tcpip driver immediately when the callback routine returns. ... What IRQL are you running at when you crash, ...
    (microsoft.public.development.device.drivers)
  • Re: MAC bridging and sniffing packets with specific Ethertype
    ... That is, the Ethernet adapters are bound to the Mbridge driver (which, since ... Mbridge handles the bridging of packets between the adapters. ...
    (microsoft.public.windowsce.embedded)
  • Re: Test on 10GBE Intel based network card
    ... Who ya gonna call, why me of course, its my driver:) ... ix0: ... Driver dropped packets = 0 ... ix1: ...
    (freebsd-performance)
  • Re: Degradation of TCP connection
    ... "Each of our boards will have an ethernet driver specific ... once you get a target into a failed state, ... when the VxWorks box stops ACKing packets sent from the Windows box. ...
    (comp.os.vxworks)