From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] TFTP pause and timeout on MX28 platforms
Date: Wed, 13 Mar 2013 17:52:20 +0100 [thread overview]
Message-ID: <201303131752.20230.marex@denx.de> (raw)
In-Reply-To: <5140A9ED.7060901@digi.com>
Dear Hector Palacios,
> Dear Marek Vasut,
>
> On 03/13/2013 05:19 PM, Marek Vasut wrote:
> > Dear Hector Palacios,
> >
> >> Dear Marek Vasut,
> >>
> >> On 03/13/2013 11:58 AM, Marek Vasut wrote:
> >>> Dear Hector Palacios,
> >>>
> >>>> Hello,
> >>>>
> >>>> When doing large TFTP downloads (files bigger than 10MiB) on my MX28
> >>>> platform I'm sometimes experiencing pauses and timeouts. U-Boot will
> >>>> eventually restart the transmission and sometimes may successfully
> >>>> complete the download, but other times it won't.
> >>>> On my platform it was somewhat mitigated (but not resolved) by
> >>>> reverting this patch from Marek:
> >>>>
> >>>> commit 67449098a86be18cbdb27345bebe8da57e5d8899
> >>>> Author: Marek Vasut <marex@denx.de>
> >>>> Date: Wed Aug 29 03:49:50 2012 +0000
> >>>>
> >>>> FEC: Rework the TX wait mechanism
> >>>>
> >>>> The problem is reproducible in Freescale's MX28EVK.
> >>>> The larger the file, the more chances to see the problem. Please try
> >>>> with 50MiB files or larger. Has anybody else seen it?
> >>>>
> >>>> On an old U-Boot v2009 TFTP transmission was twice slower than with
> >>>> v2013, but didn't suffer from this.
> >>>
> >>> What version of u-boot do you use ? It was resolved in recent versions.
> >>
> >> I'm using v2013.01.
> >> Could you please point me to the commit(s) that solve it?
> >> The commits I see on drivers/net/fec_mxc.c after v2013.01 are from Troy
> >> Kisky and don't seem to address this.
> >
> > commit c0b5a3bbb0cd40a6b23b7b07e2182a5bcdc8c31c
> > Author: Marek Vasut <marex@denx.de>
> > Date: Wed Aug 29 03:49:51 2012 +0000
> >
> > FEC: Replace magic contants
> >
> > and the three before this one. Is your PHY operating correctly? This
> > fixed the hangs on multiple MX28 platforms for me.
>
> v2013.01 contains all these patches but I was able to reproduce this both
> on my platform and on the mx28evk.
> My problem is not a hang, but TFTP pauses (1 to 3 seconds) and timeouts:
> #################################################################
> #####################################################T T T T T T
>
> At first I thought it was my platform's PHY (Micrel KSZ8031) but I also see
> it on mx28evk.
Do you use PHYLIB (see configs/sc_sps_1.h for example)? Also check if your
transceiver mode is not misconfigured. Moreover, see
board/denx/m28evk/spl_boot.c fecmxc_mii_postcall(), maybe you also need to
program some registers of the PHY (V11 and V10 prototypes used KSZ8051)?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-03-13 16:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 9:46 [U-Boot] TFTP pause and timeout on MX28 platforms Hector Palacios
2013-03-13 10:58 ` Marek Vasut
2013-03-13 15:47 ` Hector Palacios
2013-03-13 16:19 ` Marek Vasut
2013-03-13 16:31 ` Hector Palacios
2013-03-13 16:52 ` Marek Vasut [this message]
2013-03-13 17:14 ` Hector Palacios
2013-03-13 18:10 ` Marek Vasut
2013-03-14 12:05 ` Hector Palacios
2013-03-14 12:31 ` Marek Vasut
2013-03-14 13:28 ` Fabio Estevam
2013-03-13 18:52 ` Fabio Estevam
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=201303131752.20230.marex@denx.de \
--to=marex@denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox