From: "Eric Bénard" <eric@eukrea.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] TFTP timeouts, i.mx fec problem?
Date: Fri, 7 Jun 2013 11:39:35 +0200 [thread overview]
Message-ID: <20130607113935.2532b1a6@e6520eb> (raw)
In-Reply-To: <15AE5A936F5E3A42A9144E66875A0A89309153@server1-derijp.CLB-Benelux.lokaal>
Hi Ruud,
Le Fri, 7 Jun 2013 11:28:54 +0200,
Ruud Commandeur <RCommandeur@clb.nl> a ?crit :
> I have not come any further yet in finding the real cause. For now, I just tested with workarounds like lowering the ARP timeout and skipping the phy reset (or only reset for the 1st transfer). Note that also the phy reset and waiting for "link-up" takes about 2 seconds every time. I did not realise earlier that it would take this long, but this is the part before the "TFTP from server..." line is displayed and he transfer even starts.
>
isn't your problem related to the fact that when you reset the PHY it
samples some pins to get some settings and that after the first reset it
could gets wrong settings because the i.MX pins are in a wrong state
(because handled by the FEC) leading to the errors you meet ?
Eric
next prev parent reply other threads:[~2013-06-07 9:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 6:56 [U-Boot] TFTP timeouts, i.mx fec problem? Ruud Commandeur
2013-05-31 7:56 ` Wolfgang Denk
2013-05-31 8:50 ` Stefano Babic
2013-05-31 10:16 ` Ruud Commandeur
2013-05-31 12:54 ` Ruud Commandeur
2013-05-31 14:19 ` Wolfgang Denk
2013-05-31 14:36 ` Ruud Commandeur
2013-05-31 15:40 ` Stefano Babic
2013-05-31 18:56 ` Wolfgang Denk
2013-05-31 15:46 ` Stefano Babic
2013-05-31 16:00 ` Fabio Estevam
2013-05-31 18:58 ` Wolfgang Denk
2013-05-31 19:09 ` Troy Kisky
2013-06-01 9:18 ` Ruud Commandeur
2013-06-07 0:15 ` Fabio Estevam
2013-06-07 1:25 ` Marek Vasut
2013-06-07 1:34 ` Fabio Estevam
2013-06-07 1:50 ` Marek Vasut
2013-06-07 9:28 ` Ruud Commandeur
2013-06-07 9:39 ` Eric Bénard [this message]
2013-06-14 13:01 ` Ruud Commandeur
2013-06-14 15:30 ` Wolfgang Denk
2013-06-17 6:51 ` Ruud Commandeur
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=20130607113935.2532b1a6@e6520eb \
--to=eric@eukrea.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