public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Clemens Koller <clemens.koller@anagramm.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Debugging 85xx eTSEC's
Date: Sat, 27 Oct 2007 01:15:12 +0200	[thread overview]
Message-ID: <47227500.4010702@anagramm.de> (raw)
In-Reply-To: <f87675ee0710261427nc86628at4c89e95053eb5cee@mail.gmail.com>

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

  parent reply	other threads:[~2007-10-26 23:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26 21:27 [U-Boot-Users] Debugging 85xx eTSEC's robert lazarski
2007-10-26 21:48 ` Ben Warren
2007-10-26 23:15 ` Clemens Koller [this message]
2007-10-27  7:53 ` C Balakumar
2007-10-31 13:20   ` robert lazarski
2007-10-31 15:58     ` Clemens Koller
2007-11-05 17:21       ` robert lazarski
2007-11-05 19:59         ` Clemens Koller
2007-11-05 22:57           ` robert lazarski
2007-11-07 19:46             ` robert lazarski
2007-11-07 22:27               ` Clemens Koller

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=47227500.4010702@anagramm.de \
    --to=clemens.koller@anagramm.de \
    --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