
I guess thats good news. I looked inside the cmd_ping code a bit. I bet there's a "while" loop somewhere that is waiting for something and may not have a timeout loop. Any ideas?
Thanks, Steve
Premi, Sanjeev wrote:
-----Original Message----- From: u-boot-bounces@lists.denx.de [mailto:u-boot-bounces@lists.denx.de] On Behalf Of Steven Zedeck Sent: Monday, June 01, 2009 8:05 PM To: u-boot@lists.denx.de Subject: [U-Boot] potential Uboot Ping problem
Hi, It appears the ping in UBOOT is broken. The ping works fine if you have a network connection. But if the network connection is disconnected the ping hangs the system. There is no response to Control-C either. I have to power cycle the proto to get back to a UBOOT prompt. Is this a known issue or did I possibly break something?
I have a board based on the Atmel AT91SAM9RL-EK. My theory is that it "may" be a generic problem with the uboot ping. I can't confirm that since the only hardware I have is our protos.
It was noticed on the OMAP3EVM last FRI and we were suspecting it to be problem with the omap3 board configuration itself. (Though did not spend much time in debug).
Now, I too get a feeling that it could be a generic problem.
Best regards, Sanjeev
Does anyone else have a board with another MAC/PHY that you can try this on?
As for UBOOT code, our environment is based on 2008.10 code. Our MAC/PHY is the Microchip ENC28J60.
Thanks, Steve
-- View this message in context: http://www.nabble.com/potential-Uboot-Ping-problem-tp23815872p 23815872.html Sent from the Uboot - Users mailing list archive at Nabble.com.
U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot