From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Can't connect to PHY, BCM5461
Date: Wed, 29 Oct 2008 12:33:26 -0400 [thread overview]
Message-ID: <49089056.2010406@ge.com> (raw)
In-Reply-To: <28d526a60810290832v2d34b501u94a445a94a939b1c@mail.gmail.com>
Simon Boman wrote:
> I added this code to the uec.c file:
> int i;
> for(i=0;i<20;i++)
> printf("PHY value %d is %x\n", i, phy_read(uec->mii_info, i));
>
> and got this to the prompt..
>
> PHY value 0 is 0
> PHY value 1 is 0
> PHY value 2 is 0
> PHY value 3 is 0
> PHY value 4 is 0
> PHY value 5 is 0
> PHY value 6 is 0
> PHY value 7 is 0
> PHY value 8 is 0
> PHY value 9 is 0
> PHY value 10 is 0
> PHY value 11 is 0
> PHY value 12 is 0
> PHY value 13 is 0
> PHY value 14 is 0
> PHY value 15 is 0
> PHY value 16 is 0
> PHY value 17 is 0
> PHY value 18 is 0
> PHY value 19 is 0
Please don't top post.
I think you first need to *find* your phy. This is likely a
hardware/software issue: I/O lines, I/O configuration, PHY address
strapping.
I wasn't advocating adding code to print PHY registers, I was advocating
using the "mii" command: "help mii". If it isn't in your build, add it.
Then do "mii device", IIRC, it will scan the MII bus to see who is out
there. That will identify mis-strapped (or misunderstood strapping) PHY
address strapping. If nobody answers the call, you likely have a I/O
pin misconfiguration or a more serious hardware problem.
gvb
> 2008/10/29 Jerry Van Baren <gerald.vanbaren@ge.com>:
>> Simon Boman wrote:
>>> Hi!
>>>
>>> I have a modified MPC8360 platform with a PHY named BCM5461 and UEC as
>>> Ethernet Controller. I started with the MPC8360EMDS card from U-boot
>>> and then modified it so that it match the card (what I know). I am
>>> using the git-version of U-boot from October, 20, 2008.
>>> The problem is that I can't even get contact with the PHY. It says
>>> it's a generic phy, but even with that I can't get any contact to it
>>> and the phy_ID u-boot prints is just 0.
>>>
>>> "UEC: PHY is Generic MII (0)"
>>> "warning: FSL UEC0: timeout on PHY link"
>>>
>>> Hereafter the u-boot just hanging..
>>>
>>> TIA
>>> Simon
>> What does the MII command tell you about your MII bus in general and your
>> PHY's registers?
>>
>> gvb
>>
next prev parent reply other threads:[~2008-10-29 16:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 15:09 [U-Boot] Can't connect to PHY, BCM5461 Simon Boman
2008-10-29 15:12 ` Jerry Van Baren
2008-10-29 15:32 ` Simon Boman
2008-10-29 16:33 ` Jerry Van Baren [this message]
2008-10-31 8:40 ` Simon Boman
2008-10-31 9:14 ` Simon Boman
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=49089056.2010406@ge.com \
--to=gerald.vanbaren@ge.com \
--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