Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Paul Gettings <p.gettings@ut...> - 2012-03-15 15:54:49
I have an Overo Sand in a Chestnut43 expansion board. I fixed my serial
corruption issues (the COM wasn't fully seated) and fixed the recently
reported problems with some R3078 Chestnut43 boards - my board was
missing the 0 Ohm resistor at R1; it has been replaced with a solder
bridge. My 4.3" LCD works great, as does everything else I have been
trying to use (GPIO pins, ttyO0 and ttyO2).
But, the SMSC 9221 ethernet is not receiving data - at all. I can see
the kernel or MLO driver send data to the network (and the desktop on
the other side of the 100 Mbps switch sees the packets fine), and see the
desktop send packets back to the Chestnut43. The drivers on the Overo
never appear to have received the incoming packets.
Linux kernel counters for the ethernet interface show bytes and packets
going out, and 0 packets for 0 bytes received.
Google searching has not yielded any ideas on what could be wrong.
Boot messages indicate the ethernet chip is detected as an SMSC
LAN9221, with a reasonable hardware address, etc.
Anyone on the list have a notion of why the SMSC ethernet interface can
send, but not receive? Any ideas on where to go looking, in either
hardware or software?
Thanks for any help.
The goal of a scientist is to find an interesting problem, and live
off it for a while. The goal of an engineer is to evade interesting