From: Sascha Hauer <s.hauer@pengutronix.de>
To: Kamel BOUHARA <k.bouhara@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: FEC Not working with imx27 based board
Date: Tue, 12 Jul 2011 15:58:16 +0200 [thread overview]
Message-ID: <20110712135816.GY6069@pengutronix.de> (raw)
In-Reply-To: <20110712135443.GW6069@pengutronix.de>
On Tue, Jul 12, 2011 at 03:54:43PM +0200, Sascha Hauer wrote:
> On Mon, Jul 11, 2011 at 05:14:54PM +0200, Kamel BOUHARA wrote:
> > Hi,
> >
> > Im trying to port barebox to my Armadeus apf27 board (based on the Freescale
> > imx27 with a 512MiB NAND and 1GB of SDRAM).
> > I've first tried the phytec imx27 configuration and I got it worked until
> > the Linux uncompressing task (the machine ID is bad so I didn't expect it
> > will boot fine :)).
> > So I just copied the phycard-imx27 board directory and I followed the
> > boards.dox in order to add support for my board.
> > But when I've tried to boot again it was not working anymore ...
> >
> > There are somethings stranges with the FEC, here is the result of a memory
> > display with both phytec and my own board :
> >
> > > barebox@Phytec phyCard-i.MX27:/ md -s /dev/phy0
> > >
> > > 00000000: ffffffff ffffffff ffffffff ffffffff ................
> > >
> > > 00000010: ffffffff ffffffff ffffffff ffffffff ................
> > >
> > > 00000020: ffffffff ffffffff ffffffff ffffffff ................
> > >
> > > 00000030: ffffffff ffffffff ffffffff ffffffff ................
>
> This means your phy is not configured correctly. Do you usse the correct
> address (can be passed in platform_data).
GPIO pins which hold the phy in reset are another thing which might go
wrong.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-07-12 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 15:14 Kamel BOUHARA
2011-07-12 13:54 ` Sascha Hauer
2011-07-12 13:58 ` Sascha Hauer [this message]
[not found] ` <CAM9uW_4_d1NcZZYvfFpTW2g=pjeM1nQ0Ohf3RXiYX7fhK6tseA@mail.gmail.com>
2011-07-15 10:13 ` Fwd: " Kamel BOUHARA
2011-07-19 16:33 ` Kamel BOUHARA
2011-07-20 7:04 ` Sascha Hauer
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=20110712135816.GY6069@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=k.bouhara@gmail.com \
/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