From mboxrd@z Thu Jan 1 00:00:00 1970 From: Clemens Koller Date: Sat, 27 Oct 2007 01:15:12 +0200 Subject: [U-Boot-Users] Debugging 85xx eTSEC's In-Reply-To: References: Message-ID: <47227500.4010702@anagramm.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de robert lazarski schrieb: > Where 'is in sgmii mode' comes from standard 85xx stuff: I can't ping > when setting ethact to be eTSEC2, and I get this when running 'mii > info' : > > => mii info > PHY_PHYIDR2 @ 0x0 = 0xffff > PHY_PHYIDR2 @ 0x1 = 0xffff > PHY_PHYIDR2 @ 0x2 = 0xffff > PHY_PHYIDR2 @ 0x3 = 0xffff > Can't read PHY at address 4 > ... > Any ideas? As Ben mentioned already, check your hardware: Check the hw configured PHY addresses. Then you should see at least proper IDs when you do the mii info. PullUps on the MDC/MDIO lines? You should be able to see some traffic there with an oscilloscope. Then, double-check the PHY configuration and it's host interface setting...(CONFIGx<->LEDy connections) The MV88E1111 should work with the generic PHY initialization since the Marvell PHYs have a quite compatible standard register set. If you want, you can send me this part of the schematic for review. I have the MV88E1111 on the MPC85xx working fine using GMII. Regards, -- Clemens Koller _______________________________ R&D Imaging Devices Anagramm GmbH Rupert-Mayer-Str. 45/1 81379 Muenchen Germany http://www.anagramm-technology.com Phone: +49-89-741518-50 Fax: +49-89-741518-19