Skip to contentSkip to conversation

potential Uboot Ping problem

U-Boot Steven Zedeck 3 participants 6 messages Jun 1, 2009 – Jun 2, 2009

lore
Share & tools
lore
#0 lore raw

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.

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

Signature · 2 lines
View this message in context: http://www.nabble.com/potential-Uboot-Ping-problem-tp23815872p23815872.html
Sent from the Uboot - Users mailing list archive at Nabble.com.
#1 lore raw
Quoted 19 lines

-----Original Message-----
From: u-boot-bounces at lists.denx.de [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Steven Zedeck
Sent: Monday, June 01, 2009 8:05 PM
To: u-boot at 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?

Quoted 5 lines

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

Quoted 23 lines

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

Signature · 9 lines
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 at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
#2 lore raw

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

Quoted 63 lines · Sanjeev
Quoted 20 lines

-----Original Message-----
From: u-boot-bounces at lists.denx.de [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Steven Zedeck
Sent: Monday, June 01, 2009 8:05 PM
To: u-boot at 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?

Quoted 5 lines

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

Quoted 4 lines

Does anyone else have a board with another MAC/PHY that you can try this on?

Quoted 19 lines

As for UBOOT code, our environment is based on 2008.10 code. Our MAC/PHY is
the Microchip ENC28J60.

Thanks,
Steve

Signature · 9 lines
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 at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Signature · 2 lines
View this message in context: http://www.nabble.com/potential-Uboot-Ping-problem-tp23815872p23816429.html
Sent from the Uboot - Users mailing list archive at Nabble.com.
#3 lore raw

Hi Steven,

Quoted 6 lines · Steven Zedeck

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

Please don't top post, it makes the conversation hard to follow.
http://www.caliburn.nl/topposting.html

Quoted 31 lines
Quoted 30 lines · Sanjeev
Quoted 20 lines

-----Original Message-----
From: u-boot-bounces at lists.denx.de [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Steven Zedeck
Sent: Monday, June 01, 2009 8:05 PM
To: u-boot at 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?

Quoted 5 lines

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).

Quoted 7 lines
Quoted 7 lines

Now, I too get a feeling that it could be a generic problem.

Best regards,
Sanjeev

Quoted 3 lines

Does anyone else have a board with another MAC/PHY that you can try this on?

Ideally, if there is no link, the ping command should just exit gracefully without attempting network operations. Eg on my 8561-based board with no cables plugged in:
=> ping 192.168.1.1
Auto-neg error, defaulting to 10BT/HD
eTSEC1: No link.
Auto-neg error, defaulting to 10BT/HD
eTSEC2: No link.
ping failed; host 192.168.1.1 is not alive

<there is no delay in the printing of the above info>.

The tsec driver's init function returns -1 when link isn't detected. Perhaps your ethernet driver should do the same?

What happens if you ping a non-existent IP address? Does that also hang the board? Do other network operations hang the board if no ethernet cable is plugged in?

Best,
Peter

#4 lore raw
Quoted 73 lines · Peter Tyser

Hi Steven,

Quoted 7 lines · Steven Zedeck

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

Please don't top post, it makes the conversation hard to follow.
http://www.caliburn.nl/topposting.html

Quoted 31 lines
Quoted 30 lines · Sanjeev
Quoted 20 lines

-----Original Message-----
From: u-boot-bounces at lists.denx.de [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Steven Zedeck
Sent: Monday, June 01, 2009 8:05 PM
To: u-boot at 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?

Quoted 5 lines

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).

Quoted 7 lines
Quoted 7 lines

Now, I too get a feeling that it could be a generic problem.

Best regards,
Sanjeev

Quoted 3 lines

Does anyone else have a board with another MAC/PHY that you can try this on?

Ideally, if there is no link, the ping command should just exit gracefully without attempting network operations. Eg on my 8561-based board with no cables plugged in:
=> ping 192.168.1.1
Auto-neg error, defaulting to 10BT/HD
eTSEC1: No link.
Auto-neg error, defaulting to 10BT/HD
eTSEC2: No link.
ping failed; host 192.168.1.1 is not alive

<there is no delay in the printing of the above info>.

The tsec driver's init function returns -1 when link isn't detected. Perhaps your ethernet driver should do the same?

What happens if you ping a non-existent IP address? Does that also hang the board? Do other network operations hang the board if no ethernet cable is plugged in?

Quoted 9 lines

Best,
Peter

_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

The ethernet driver is also from the uboot distribution. Its enc28j60.c. I'll need to go through it to see where its hanging assuming its in that driver or the ping code that calls it.

thanks,
Steve

Signature · 2 lines
View this message in context: http://www.nabble.com/potential-Uboot-Ping-problem-tp23815872p23824737.html
Sent from the Uboot - Users mailing list archive at Nabble.com.
#5 lore raw
In reply to Peter Tyser
Quoted 74 lines

-----Original Message-----
From: u-boot-bounces at lists.denx.de [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Peter Tyser
Sent: Tuesday, June 02, 2009 3:53 AM
To: Steven Zedeck
Cc: u-boot at lists.denx.de
Subject: Re: [U-Boot] potential Uboot Ping problem

Hi Steven,

Quoted 1 line · Steven Zedeck

I guess thats good news. I looked inside the cmd_ping code

a bit. I bet

Quoted 1 line

there's a "while" loop somewhere that is waiting for

something and may not

Quoted 4 lines

have a timeout loop. Any ideas?

Thanks,
Steve

Please don't top post, it makes the conversation hard to follow.
http://www.caliburn.nl/topposting.html

Quoted 31 lines
Quoted 30 lines · Sanjeev
Quoted 20 lines

-----Original Message-----
From: u-boot-bounces at lists.denx.de [mailto:u-boot-bounces at lists.denx.de] On Behalf Of Steven Zedeck
Sent: Monday, June 01, 2009 8:05 PM
To: u-boot at 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?

Quoted 5 lines

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).

Quoted 7 lines
Quoted 7 lines

Now, I too get a feeling that it could be a generic problem.

Best regards,
Sanjeev

Quoted 3 lines

Does anyone else have a board with another MAC/PHY that you can try this on?

Ideally, if there is no link, the ping command should just exit gracefully without attempting network operations. Eg on my 8561-based board with no cables plugged in:
=> ping 192.168.1.1
Auto-neg error, defaulting to 10BT/HD
eTSEC1: No link.
Auto-neg error, defaulting to 10BT/HD
eTSEC2: No link.
ping failed; host 192.168.1.1 is not alive

<there is no delay in the printing of the above info>.

Quoted 7 lines

The tsec driver's init function returns -1 when link isn't detected. Perhaps your ethernet driver should do the same?

What happens if you ping a non-existent IP address? Does that also hang
the board? Do other network operations hang the board if no ethernet cable is plugged in?

Here is a session from OMAP3EVM:

OMAP3_EVM # setenv autoload no
OMAP3_EVM # dhcp
smc911x: initializing
smc911x: detected LAN9115 controller
smc911x: phy initialized
smc911x: MAC 00:50:c2:7e:88:72
BOOTP broadcast 1
BOOTP broadcast 2
DHCP client bound to address 192.168.1.10
OMAP3_EVM # ping 192.168.1.1
smc911x: initializing
smc911x: detected LAN9115 controller
smc911x: phy initialized
smc911x: MAC 00:50:c2:7e:88:72
ping failed; host 192.168.1.1 is not alive
OMAP3_EVM #

Quoted 9 lines

Best,
Peter

_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot