[U-Boot] MPC8548 not able to detect Marvell 88E1145 PHY

[Ajeesh Kumar]

Hi Andy,

Thanks for your info. 

>>This points to a hardware problem.  Do you have an oscilloscope?  Take a
look at the MDIO pin, and see what's being sent, and what the reply is.  The
>>protocol for MDIO is pretty simple.  Make sure that the address on the
read request is good, and make sure that the reply is good.
Yeah We do have a scope, when I probed MDIO I could find some transactions
happening. Actually I was using the u-boot1.2 which was working fine with
the EP8548A board. And I'm using the same code piece. So the protocol to
read/write MII management interface will be fine. 

Actually, We are configuring the PHY chip have an address 0,1,2 and 3 but I
dunno why I could read only the address 0x12??

Could you help me in giving the MUST required hardware configuration that
should be done so as to make the PHY chip come up.

Thanks,
Ajeesh Kumar

-----Original Message-----
From: Andy Fleming [mailto:afleming at gmail.com] 
Sent: Wednesday, January 07, 2009 12:02 AM
To: ajeesh at tataelxsi.co.in
Cc: u-boot at lists.denx.de; charlesniranjan at tataelxsi.co.in;
raghut at tataelxsi.co.in; sibaprasad at tataelxsi.co.in
Subject: Re: [U-Boot] MPC8548 not able to detect Marvell 88E1145 PHY

On Mon, Jan 5, 2009 at 2:57 AM, Ajeesh Kumar <ajeesh at tataelxsi.co.in> wrote:
> Hi Sir/Madam,
>

> Net:   eTSEC0: PHY id ffffffff is not supported!
> eTSEC0: No PHY found
> eTSEC1: PHY id ffffffff is not supported!
> eTSEC1: No PHY found
> eTSEC2: PHY id ffffffff is not supported!
> eTSEC2: No PHY found
> eTSEC3: PHY id ffffffff is not supported!
> eTSEC3: No PHY found
> eTSEC0, eTSEC1, eTSEC2, eTSEC3
> Hit any key to stop autoboot:  0


This points to a hardware problem.  Do you have an oscilloscope?  Take a
look at the MDIO pin, and see what's being sent, and what the reply is.  The
protocol for MDIO is pretty simple.  Make sure that the address on the read
request is good, and make sure that the reply is good.

> 2. We connected LAN cable to the PORT 0x12, still its not getting pinged.
>
> We have connected in RGMII mode (TSEC0) During POR the POR register 
> are getting configured for default (GMII) mode, how can we change the 
> PORT to RGMII, after Boot.

I don't believe you can change the data mode at runtime.  You need to
correctly configure the POR bits for RGMII if that's what you want to use.
If you want to test your ethernet using port 0x12, you'll need to change
your u-boot config, too, so that the driver knows which PHY to configure.

Andy


The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments contained in it.