mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Christian Kapeller <christian.kapeller@cmotion.eu>
To: barebox@lists.infradead.org
Subject: tx51 ethernet regression
Date: Mon, 16 Jul 2012 13:28:13 +0200	[thread overview]
Message-ID: <5003FACD.80400@cmotion.eu> (raw)

Hi,

I recently came to update my barebox port based on the karo tx51 imx
module from v2012.03.0 to v2012.07.0.

I discovered, that, when trying to use the ethernet connection, I more
often than not get frame errors reported by the FEC.

--snip--
barebox@Ka-Ro tx51:/ dhcp
phy0: Link is up - 1000/Full
error frame: 0x97b961c0 0x00000890
error frame: 0x97b96188 0x00000882
DHCP client bound to address 10.41.14.147
--snap--

The errors range from 'non octet aligned frame' over 'Fifo overrun' to
timeouts. It renders the ethernet support unusable. Small images may
work but, require the one and other retry.

One thing that catches my eye is that the auto negotioation resulted in
a 1000MBit link. The imx fec does only support 100MBit. I forced the
link to be set to 10MBit by declaring xcv_type=MII10 in the
fec_platform_data structure. Interestingly the link is now reported as
100MBit, and shows the same behaviour.

Another thing I checked was the changed pad definitions in commit
2bdc9f57a86dff41cfc1f87b644a2e53fdcce2b6. Not only the type of the pad
data structure changed, but also some of their configuration as well.
For example, pads that were configured with FEC_PAD_CTL, now have other
settings enabled.

I'reverted the pad changes, but still no luck. Auto negtiation starts,
but I don't seem to get any packets.

So my question is: What change since v2012.03.0 could cause this kind of
behaviour?

Regards
Christian


-- 
Christian Kapeller
cmotion GmbH
Kriehubergasse 16
1050 Wien / Austria
http://www.cmotion.eu

christian.kapeller@cmotion.eu
Phone: +43 1 789 1096 38


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2012-07-16 11:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16 11:28 Christian Kapeller [this message]
2012-07-16 11:44 ` Eric Bénard
2012-07-16 12:52   ` Christian Kapeller
2012-07-16 14:21     ` Sascha Hauer
2012-07-17  9:49       ` [PATCH] imx51: fix pad definition used for fec communication Christian Kapeller

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=5003FACD.80400@cmotion.eu \
    --to=christian.kapeller@cmotion.eu \
    --cc=barebox@lists.infradead.org \
    /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