This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: No joy on the network so far
- From: Andrew Lunn <andrew at lunn dot ch>
- To: Chuck McManis <ecos at mcmanis dot com>
- Cc: ECOS Discussion Group <ecos-discuss at sources dot redhat dot com>
- Date: Wed, 15 Feb 2006 13:29:23 +0100
- Subject: Re: [ECOS] No joy on the network so far
- References: <6.1.2.0.2.20060215040442.02accec0@66.125.189.29>
On Wed, Feb 15, 2006 at 04:17:13AM -0800, Chuck McManis wrote:
> Well, its curiouser and curiouser ;-)
>
> Ok, so I've got my new driver written. Started with the rhine driver but
> pretty much replaced everything except the buffer handling code.
>
> I added some instrumentation to see packets being transmitted as well as
> packets being received. I've got tcpdump of course.
>
> In order to simplify things I configured redboot to NOT use bootp and
> instead merely assign the address 192.168.110.177 directly.
>
> It does, and it comes up to the redboot prompt, but if I try to ping my
> server (on the same subnet) it can't see it. Now tcpdump(8) can see my
> target board send out an ARP request for the server, and it sees the
> response. The printf's in the ethernet driver are showing that the ethernet
> chip is seeing those packets as well and fetching them in the _recv()
> function. But they never seem to make up into the networking stack where
> they belong.
You will have to add some diag_printf messages to see where the
messages get dropped. Or use gdb and follow the packet.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss