public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Fw: TFTP fails when using network switch
Date: Wed, 07 Jan 2009 13:23:06 -0500	[thread overview]
Message-ID: <4964F30A.1000000@ge.com> (raw)
In-Reply-To: <20090107070337.7298ba33@uncle-pecos.Colorado.EDU>

Loren A. Linden Levy wrote:
> On Wed, 07 Jan 2009 07:52:58 -0500
> Jerry Van Baren <gerald.vanbaren@ge.com> wrote:
> 
>> Wolfgang Denk wrote:
>>> Dear Ulf Samuelsson,
>>>
>>> In message <1231282371.32308.276.camel@elrond.atmel.com> you wrote:
>>>> It was tracked down to the autoconfiguration of the 
>>>> Ethernet PHY, so one of the PHYs ended up in 
>>>> 100 Mbps Half Duplex (think that was the switch) 
>>>> while the other PHY ended up in 100 MBps Full Duplex.
>>> That would most probably be a bug in the U-Boot ethernet driver, then.
>>>
>>> Best regards,
>>>
>>> Wolfgang Denk
>> If auto-negotiation fails, the default is half duplex (10 or 100 - the 
>> speed can be discovered independent of the autonegotiation by the encoding).
>>
>> Ulf's recollection that the switch was half duplex would indicate that 
>> the cheap switch did not autonegotiate properly, but u-boot did.  This 
>> could be a u-boot bug (not setting up the negotiation properly), but 
>> more likely would be a switch problem (not handling the u-boot auto-neg 
>> options properly).
>>
>> gvb
 > Hi All,
 >
 > Is there something like ethtool in U-boot that I can use to see what
 > the network negotiated too. This is a fairly cheap netgear switch so I
 > do not have any diagnostics on it.
 >
 > I will also have a look with wireshark when i get back to the lab to
 > see if I can identify what is happening.
 >
 > Alex

Please don't top post.

Wireshark is a Very Good Program[tm], but I would not expect too much if 
this is an autonegotiation issue because autonegotiation uses a sideband 
control channel (link pulses) separate from the data transmission. 
Wireshark only sees the data transmissions.

Having said that, look for runt packets w/ Wireshark - that is a strong 
indicator of full/half duplex problems.

As mentioned by Ed, the u-boot "mii" commands will be more helpful if it 
is an autonegotiation issue.  (Ethernet autonegotiation is a weird 
bugger: both sides send their capabilities, independently match them, 
and (hopefully) come to the same conclusion about what is the right 
configuration.  It looks to me like something designed by three 
committees[1] simultaneously and then turned into a super-subset.)

gvb

[1] A horse is a camel designed by a committee: it looks really good and 
can run fast on an ideal surface, but quickly dies in conditions that 
just cause a camel to grin.
   <http://en.wikipedia.org/wiki/Camel#Eco-behavioural_adaptations>

  parent reply	other threads:[~2009-01-07 18:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-06  0:02 [U-Boot] Fw: TFTP fails when using network switch Loren A. Linden Levy
2009-01-06  7:41 ` Remy Bohmer
2009-01-06 22:52   ` Ulf Samuelsson
2009-01-06 23:00     ` Wolfgang Denk
2009-01-07 12:52       ` Jerry Van Baren
2009-01-07 14:03         ` Loren A. Linden Levy
2009-01-07 15:57           ` Swarthout Edward L
2009-01-07 18:02           ` Ben Warren
2009-01-07 18:23           ` Jerry Van Baren [this message]
2009-01-07 19:36         ` Ulf Samuelsson
2009-01-07 19:58           ` Jerry Van Baren
2009-01-16  0:36             ` L. A. Linden Levy
2009-01-16 15:34               ` Jerry Van Baren
2009-01-20  0:00                 ` Loren A. Linden Levy
2009-01-20  1:14                   ` Jerry Van Baren
2009-01-20  2:39                     ` Loren A. Linden Levy
2009-01-20 16:55                     ` Loren A. Linden Levy
2009-01-20 17:13                       ` Jerry Van Baren
2009-01-21  0:14                         ` Loren A. Linden Levy
2009-01-21 12:23                           ` Jerry Van Baren
2009-01-06 12:45 ` Jerry Van Baren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4964F30A.1000000@ge.com \
    --to=gerald.vanbaren@ge.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox