[U-Boot-Users] PQ2FADS-VR 2nd Ethernet
Yuli Barcohen
yuli at arabellasw.com
Mon Jul 19 19:55:03 CEST 2004
>>>>> Jihua Cheng writes:
Jihua> Yuli, Thanks very much for your instruction. It seems I move
Jihua> further, however I still do not make Ethernet port2 works
Jihua> fine. Following is the my modification and the symptom.
Jihua> 1) I changed the BCSRs bit FETHIEN2 to 0, reset the Ethernet
Jihua> Port2 (Phy addr 3) to enable auto-negatiation. Now, the
Jihua> MII reg0 = 0x3100, reg1=0x782D. IP Addr 172.18.100.54
Jihua> does exist. when I enable FCC2 and ping 172.18.100.54,
Jihua> ping success. When I "ping 172.18.100.54", the message
Jihua> "fex: tx error" is gone. It seems TX is fine. Is it
Jihua> correct?
Probably it is. Try a sniffer (ethereal, tcpdump) on the host to see if
anything is transmitted by the board.
Jihua> 2) However, "ping 172.18.100.54" fail. the message "ping
Jihua> failed; host 172.18.100.54" is not alive. FCC3 Rx Clock
Jihua> is set to CLK15. PortB4~17, PortC16~17 are enabled.
Why do you think that the problem is still at the hardware level? What
are the board's IP address, MAC address, subnet mask, etc. (just type
printenv). You write that 172.18.100.54 exists but you don't write
anything about the host to which this address belongs. Is it a Linux
machine? Does it respond to pings at all? What's about subnets? There
are too many possible reasons for ping failure.
[...code deleted...]
--
========================================================================
Yuli Barcohen | Phone +972-9-765-1788 | Software Project Leader
yuli at arabellasw.com | Fax +972-9-765-7494 | Arabella Software, Israel
========================================================================
More information about the U-Boot
mailing list