From: Sascha Hauer <s.hauer@pengutronix.de>
To: Maxim Gorbachyov <maxim.gorbachyov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: check if RGMII works
Date: Wed, 30 May 2012 07:49:40 +0200 [thread overview]
Message-ID: <20120530054940.GG30400@pengutronix.de> (raw)
In-Reply-To: <CAJLCkXMV6mtW7q7MtQuhJstKwb3mGXwJbunLNVKQRZ+ey_gZ2A@mail.gmail.com>
On Tue, May 29, 2012 at 07:37:47PM +0300, Maxim Gorbachyov wrote:
> Hello.
>
> I'm trying to use barebox (current git version) with a Freescale
> i.MX6q based board. The board is similar to Armadillo 2, but it comes
> with another Ethernet PHY. Barebox starts on the board, and there is a
> fec_imx0:
>
> barebox@Freescale i.MX6q myboard:/ devinfo fec_imx0
> resources:
> num : 0
> start : 0x02188000
> size : 0x00001000
> driver: fec_imx
> no info available for fec_imx0
> no parameters available
>
> I've removed AR8031 (Armadillo 2 PHY) code from the mx6_rgmii_rework()
> and added these lines:
>
> for (i = 0; i < 16; ++i) {
> val = mii_read(mdev, mdev->address, i);
> printf("%s() PHY register %d: 0x%04x\n", __FUNCTION__, i, val);
> }
>
> Relevant boot log:
>
> mx6_rgmii_rework() PHY register 0: 0x7fff
> mx6_rgmii_rework() PHY register 1: 0xffff
> mx6_rgmii_rework() PHY register 2: 0x7fff
> mx6_rgmii_rework() PHY register 3: 0xffff
> mx6_rgmii_rework() PHY register 4: 0x7fff
> mx6_rgmii_rework() PHY register 5: 0xffff
> mx6_rgmii_rework() PHY register 6: 0x7fff
> mx6_rgmii_rework() PHY register 7: 0xffff
> mx6_rgmii_rework() PHY register 8: 0x7fff
> mx6_rgmii_rework() PHY register 9: 0xffff
> mx6_rgmii_rework() PHY register 10: 0x7fff
> mx6_rgmii_rework() PHY register 11: 0xffff
> mx6_rgmii_rework() PHY register 12: 0x7fff
> mx6_rgmii_rework() PHY register 13: 0xffff
> mx6_rgmii_rework() PHY register 14: 0x7fff
> mx6_rgmii_rework() PHY register 15: 0xffff
>
> These values are not PHY defaults and actually look strange. I'm not
> sure if mii_read() really works here.
It seems not.
> Could you please suggest how to check if RGMII communication works?
You already found out ;)
Have you checked the iomux settings are correct?
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
prev parent reply other threads:[~2012-05-30 5:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 16:37 Maxim Gorbachyov
2012-05-30 5:49 ` Sascha Hauer [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=20120530054940.GG30400@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=maxim.gorbachyov@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