The problem seems to stem from the DHCP network that the static system is
running alongside. When I sever the uplink from the hub, everything works
fine. But when the uplink is there, no luck. So it doesn't seem like
it's going to be possible to maintain a single TFTP server that can be used by
anyone in the office who needs to flash a gumstix.
have done two tcpdumps. One while the uplink is severed and the
other when it is attached. It doesn't seem like the gumstix can even get
through to the server when attached, perhaps because it's impeded by other
computers on the network. I'd like to include the dumpfiles, but I'm a bit
leery to do so given the public nature of this list, and also because I don't
think much more than what's already known can be pulled from
The only solution I
can think of is to make a new subnet, which of course isn't a really good
solution since we'd have to re-wire the office. For now I will just sever
the machine from the network. :(
On Mar 24, 2006, at 11:13 AM, J.P. Norair wrote:
Alright, I found out that the particular etherstix I was using was
faulty, so I switched to a different one. The LED is blinking, which is
good, and I can ping the server. But tftp still won't work. It's
asking me for a "gatewayip" environment variable. When I set it to
192.168.0.1 (out actual gateway), it doesn't work. This is
annoying, since I'm dealing with a static network and it shouldn't need a
gateway address. What could be screwing this
u-boot's networking code needs that gateway IP to be set; don't know why,
since as you say, 99% of the time in a u-boot situation, you only need LAN
What do you see on the LAN via tcpdump while the gumstix is trying to make
its TFTP requests? Is your TFTP server serving the file "boot/uImage"
which is what I think tftp is configured to ask for by default (can be
over-ridden using the bootfile u-boot var).
On Mar 24, 2006, at 10:41 AM, J.P. Norair wrote:
tftp in u-boot with other embedded platforms fairly easily, but it's not
working with the gumstix.
using a static ip as follows:
It seems like the problem is that
the Etherstix is simply not working. The SMC-91111 seems to be
recognized in u-boot, but it can't establish itself on the network.
pinging yields nothing, from either side. Before anyone is tempted to
assume: yes, I am
plugged into a hub (using a straight
anyone could shed on this problem would be much
What are the LEDs doing on the etherstix? One LED is programmed to
show 10/100 status (will be lit solidly when connected to a 10/100 or 100 hub)
and the other is programmed to blink on Tx/Rx, so it should blink when you try
Also, can you run tcpdump on that network segment, and see if you're
seeing any packets from the gumstix (like the ICMP echo requests)?