mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Teresa Remmet <t.remmet@phytec.de>
To: Michael Grzeschik <mgr@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: boards: phytec-som-am335x: ethernet broken after reset
Date: Wed, 30 Sep 2015 16:26:16 +0200	[thread overview]
Message-ID: <1443623176.4612.13.camel@lws-tremmet.phytec.de> (raw)
In-Reply-To: <20150929141202.GB1886@pengutronix.de>

Hello Michael,

Am Dienstag, den 29.09.2015, 16:12 +0200 schrieb Michael Grzeschik:
> On Thu, Sep 24, 2015 at 08:37:31AM +0200, Teresa Remmet wrote:
> > can you give me a little bit more information about the hardware you
> > are using? As the phytec-som-am335x, includes 3 different modules.
> > Names of the images in use and hardware revision of the som whould be
> > great.
> 
> It is an 1358.3 som which uses the MT41K128M16JT memory instead of the
> MT41J128M16125IT. I created an extra image, as it is used with an custom
> baseboard.

The MT41K128M16JT is a newer RAM. We tested that this also runs with the
timings of MT41J128M16125IT. Maybe I should add a comment into the code
as this leads to confusion.

> 
> > I have made a quick test it with a phycore som on master. It worked for
> > me.
> 
> Ok, Than there must be some differences. Possibly another used phy on
> the 1358.3 module.

I have checked this now also on a 1358.3 with MT41K128M16JT and a SMSC
LAN 8710A phy. It works with barebox master.

Regards,
Teresa

> 
> Thanks,
> Michael
> 



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

      reply	other threads:[~2015-09-30 14:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-23 15:28 Michael Grzeschik
2015-09-24  6:37 ` Teresa Remmet
2015-09-29 14:12   ` Michael Grzeschik
2015-09-30 14:26     ` Teresa Remmet [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=1443623176.4612.13.camel@lws-tremmet.phytec.de \
    --to=t.remmet@phytec.de \
    --cc=barebox@lists.infradead.org \
    --cc=mgr@pengutronix.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