All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Puschmann <andre.puschmann@stud.tu-ilmenau.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: tftp timeout
Date: Wed, 12 Apr 2006 16:44:13 +0200	[thread overview]
Message-ID: <e1j3a4$42n$1@sea.gmane.org> (raw)
In-Reply-To: <443CEA56.8010701@smiths-aerospace.com>

Jerry Van Baren wrote:
> Andre Puschmann wrote:
> 
>> hallo,
>> i know this newsgroup already talked about this subject and of course i
>> read this stuff but there are still some questions ..
>>
>> i am currently trying to download a kernel image via tftp from a
>> tftp-server on my hostpc which is connected through a ethernet-switch.
>> but i always get timeouts .. look at this:
>>
>> <log>
>> Load address: 0x20800000
>> Loading: *\0x08#######T ##################################T
>> ###################T ####T ##T #
>> \0x09 ###T #T #########T ########T #############T ##T #############T
>> ########T #############T
>> \0x09 #####T ###T ######T #######T #######T #############T ##T
>> ##############T ###########
>> \0x09 ###########
>> done
>> </log>
>>
>> i mean .. the transfer is ok .. but it takes ages :-)
>>
>>
>> it looks like this if i connect my board directly to my hostpc.
>>
>> <log>
>> Load address: 0x20800000
>> Loading: *\0x08T
>> #################################################################
>> \0x09 #################################################################
>> \0x09 #################################################################
>> \0x09 ###########
>> done
>> </log>
>>
>>
>> does anybody got the same issues?
>> i mean there is no huge traffic on the net and my local tftp client 
>> loads the 1MB kernel-image in seconds.
>> i am using u-boot-1.1.1 and i also tried u-boot-1.1.4!
>>
>> regards
>> andre
> 
> 
> My guess is that you have a full duplex/half duplex problem.  Verify 
> that your board/u-boot is setting your ethernet to the proper duplex 
> (full/half).  I'm guessing your board is half duplex but your switch is 
> full (typical of a switch ;-).
> 
> The switch sends traffic to your board while your board is 
> transmitting... that is a collision (late collision at that) to your 
> board but is OK to the switch.  This doesn't happen nearly as much with 
> your PC since you have a dedicated link without much asynchronous traffic.
> 
> This is a FAQ type problem where the software (u-boot/linux) needs to 
> poll the PHY chip for duplex and then (re)configure the MAC chip 
> (separate or built into the CPU) to match.  If the poll isn't happening 
> or has a bug, you have a problem.
> 
> gvb
> 

thanks for your tip ..
sorry i am not that introduced in how autonegotiation works but i guess 
the function dm9161_AutoNegotiate() in dm9161.c does the related stuff.
i mean the switch i am using is a no-name one and with an other 
netg**r-switch it works nice, just tested it ... so it seems to be a bug 
in that fuctions, right??

regards
andre

  parent reply	other threads:[~2006-04-12 14:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-12  7:54 [U-Boot-Users] tftp timeout Andre Puschmann
2006-04-12 11:53 ` Jerry Van Baren
2006-04-12 13:40   ` Wolfgang Denk
2006-04-12 14:44   ` Andre Puschmann [this message]
2006-04-12 14:54     ` [U-Boot-Users] " 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='e1j3a4$42n$1@sea.gmane.org' \
    --to=andre.puschmann@stud.tu-ilmenau.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.