From: Pierre AUBERT <p.aubert@staubli.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PATCH: fix FEC problems on MPC5200
Date: Thu, 25 Mar 2004 10:57:29 +0100 [thread overview]
Message-ID: <4062AD09.5020509@staubli.com> (raw)
In-Reply-To: <20040325094008.6ECC9C0655@atlas.denx.de>
Wolfgang Denk wrote:
>In message <4062A3C1.40107@staubli.com> you wrote:
>
>
>>On my side, I had the timeouts problems on tftp transferts from the begining.
>>IDE support didn't change anything, the problem exists before.
>>
>>
>
>It would be interesting to know if there were some components in your
>setup that you were not able to replace:
>
> LITE5200 board
> network cable(s)
> switch(es) / hub(s)
> TFTP server
>
>
I've made some tests with several tftp servers (Unix servers and PC
servers). Of course,
I've tried several cables and severals ports on several switches. I've
also made some tests
with a direct connection between a PC and my Lite5200 with same results
(in this case, timeouts
are rare, but it happens sometimes).
Unfortunately, I've got only one Lite5200 board but other people have
same problems
(see thread
http://sourceforge.net/mailarchive/forum.php?thread_id=4080201&forum_id=12898)
I think that my board is OK because I don't have any problem with the
FEC under my
operating system.
>Only if you were able to replace each of them, and the problem
>persisted, I am convinced of a problem with the code.
>
>We had several boards, both with MGT5100 and MPC5200, with SDRAM and
>DDR, in several layour versions of the IceCube / LITE board, and
>additionally some custom boards. Never had that sort of problem until
>around the time the IDE stuff was checked in.
>
>Best regards,
>
>Wolfgang Denk
>
>
>
Best regards
prev parent reply other threads:[~2004-03-25 9:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 8:27 [U-Boot-Users] PATCH: fix FEC problems on MPC5200 Pierre AUBERT
2004-03-25 9:02 ` Wolfgang Denk
2004-03-25 9:17 ` Pierre AUBERT
2004-03-25 9:40 ` Wolfgang Denk
2004-03-25 9:57 ` Pierre AUBERT [this message]
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=4062AD09.5020509@staubli.com \
--to=p.aubert@staubli.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