This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Establishing ethernet support, ping failure
- From: Kelvin Lawson <klawson at ad-holdings dot co dot uk>
- To: ecos-discuss at sources dot redhat dot com
- Date: Thu, 29 Apr 2004 16:15:05 +0100
- Subject: [ECOS] Re: Establishing ethernet support, ping failure
- References: <s090e4d5.034@EMAIL>
Hi Aniket,
Section2: ECOS SH7729 Hardware to server ARP request (But no response from Server)
192.168.174.106 (Board) to 192.168.174.47 ARP Request
MAC of 192.168.174.107 (C0 A8 AE 6A) is : 00 0B DB C1 C4 FE
0000: FF FF FF FF FF FF 00 0B DB C1 C4 FE 08 06 00 01 ................
0010: 08 00 06 04 00 01 00 0B DB C1 C4 FE C0 A8 AE 6A ...............j
0020: 00 00 00 00 00 00 C0 A8 AE 2F 00 00 00 00 00 00 ........./......
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0040:
No response
According to this you're not getting any response from the server. It's
more likely, however, that you're just not seeing the ARP response
because you're running Spynet on a different machine. Unless you're
using a hub or running Spynet on 192.168.174.47, the Spynet machine
won't capture the ARP responses.
I suspect that the ARP response is actually being sent by the server,
but it is not being passed up to the eCos stack by your Ethernet driver.
Could you put some debug statements in the Ethernet driver to find out
if you're actually receiving any interrupts at all ? You seem to be
using DP83902A - you can set the debug level in the file dp83902a.h.
Using the debug you should be able to find out whether the ARP response
from the server is actually being received at all by the Ethernet
driver. If you're not receiving any packets at all, then adding the ARP
entry for the server won't help you.
Cheers,
Kelvin.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss