From: Ira Snyder <iws@ovro.caltech.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot] TSEC ethernet controller problems (crc errors / corruption)
Date: Tue, 2 Jun 2009 11:17:26 -0700 [thread overview]
Message-ID: <20090602181726.GC6979@ovro.caltech.edu> (raw)
In-Reply-To: <1243964114.10890.62.camel@localhost.localdomain>
On Tue, Jun 02, 2009 at 12:35:14PM -0500, Peter Tyser wrote:
> On Tue, 2009-06-02 at 09:42 -0700, David Hawkins wrote:
> > > I am unable to reproduce the corruption on my MPC8349EMDS eval board,
> > > but I'm running out of ideas to try and find the source of this problem.
> >
> > One more piece of info: the MPC8349E-MDS board contains the
> > MPC8349E processor, whereas our board contains the MPC8349EA
> > (silicon v 3.1) processor. We did have a couple of MPC8349EA-MDS
> > boards, however, the Xilinx CPLD on both boards spontaneously
> > destructed (the CPLD sticky labels melted!).
> >
> > We can try putting the MPC8349EA processor from one of the
> > dead boards into the MPC8349E-MDS board socket - I believe
> > this is ok - feel free to warn us that its not :)
>
> What interface are you using between the MAC and PHY? I saw somewhat
> similar weirdness at gigabit on a board when using RGMII and the clock
> delays in the PHY and PCB didn't match up correctly (Section 5.12.2 from
> the 88e1111 manual). If you aren't using RGMII, this wouldn't be your
> issue though...
>
We're using GMII, exactly the same as the Freescale eval board. I did a
very quick test with the board in RGMII mode as well, and the board
behaved in exactly the same way it does in GMII mode.
Thanks,
Ira
next prev parent reply other threads:[~2009-06-02 18:17 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 16:27 [U-Boot] TSEC ethernet controller problems (crc errors / corruption) Ira Snyder
2009-06-02 16:42 ` David Hawkins
2009-06-02 17:35 ` Peter Tyser
2009-06-02 18:17 ` David Hawkins
2009-06-02 18:17 ` Ira Snyder [this message]
2009-06-02 18:41 ` Kim Phillips
2009-06-02 18:50 ` Wolfgang Denk
2009-06-02 19:01 ` David Hawkins
2009-06-02 19:46 ` Ira Snyder
2009-06-02 20:38 ` [U-Boot] TSEC ethernet controller problems (crc errors/ corruption) Liu Dave-R63238
2009-06-02 20:44 ` Liu Dave-R63238
2009-06-02 21:25 ` Ira Snyder
2009-06-02 22:10 ` [U-Boot] TSEC ethernet controller problems (crc errors/corruption) Liu Dave-R63238
2009-06-02 22:19 ` [U-Boot] TSEC ethernet controller problems (crc errors/ corruption) Ira Snyder
2009-06-02 22:22 ` [U-Boot] TSEC ethernet controller problems (crc errors/corruption) Liu Dave-R63238
2009-06-02 23:08 ` [U-Boot] TSEC ethernet controller problems (crc errors/ corruption) Kim Phillips
2009-06-03 17:50 ` Ira Snyder
2009-06-03 20:19 ` Kim Phillips
2009-06-03 20:46 ` Ira Snyder
2009-06-03 21:41 ` Paul Gortmaker
2009-06-05 18:45 ` Paul Gortmaker
2009-06-06 0:38 ` Kim Phillips
2009-06-06 2:31 ` dwh at ovro.caltech.edu
2009-06-08 15:50 ` Kim Phillips
2009-06-08 16:46 ` David Hawkins
2009-06-08 23:06 ` Liu Dave-R63238
2009-06-08 23:36 ` David Hawkins
2009-06-09 21:46 ` David Hawkins
2009-06-09 23:21 ` Liu Dave-R63238
2009-06-09 23:35 ` David Hawkins
2009-06-03 21:51 ` [U-Boot] TSEC ethernet controller problems (crc errors/corruption) Liu Dave-R63238
2009-06-03 21:58 ` David Hawkins
2009-06-02 22:30 ` Liu Dave-R63238
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=20090602181726.GC6979@ovro.caltech.edu \
--to=iws@ovro.caltech.edu \
--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