public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Question on MII devices
Date: Thu, 13 Jul 2006 11:22:52 +0200	[thread overview]
Message-ID: <200607131122.52985.sr@denx.de> (raw)
In-Reply-To: <513a5e60607121636t30553633n40eebb9693f6df57@mail.gmail.com>

Hi,

On Thursday 13 July 2006 01:36, Madhu Saravana Sibi Govindan wrote:
> I'm currently debugging u-boot on a custom board. It has a STE100p PHY
> device. However, when I do "mii info" at the U-boot command prompt, I
> see this:
>
> ---------------------------------------------
> PHY_PHYIDR2 @ 0x0 = 0x0011
> device name  = ppc_4xx_eth0
> PHY_PHYIDR[1,2] @ 0x0 = 0x1c040011
> PHY 0x00: OUI = 0x70100, Model = 0x01, Rev = 0x01, 100baseT, FDX

PHY address 0 is on some PHY's a broadcast address. So possibly your PHY will 
respond to it's configured address and to address 0.

What is your PHY address? Meaning for what address is your PHY configured in 
your design?

<snip>

> I'm confident that there is only one PHY device. If so, why should the
> same device be seen twice? Has anyone seen this behavior before and
> know what might be wrong?

See above.

> I can't get the "ping" command to work (though the ethernet interface
> is recognized and initialized by u-boot). The U-boot debug statements
> say that the board is sending out ARP requests, but no body seems to
> receive the request (using ethereal).  Can someone give me directions
> as to how to debug this problem?

It seems to be a custom 4xx board. Did you enable the debug output of the 
ethernet driver (INFO_4XX_ENET)?

Best regards,
Stefan

      parent reply	other threads:[~2006-07-13  9:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-12 23:36 [U-Boot-Users] Question on MII devices Madhu Saravana Sibi Govindan
2006-07-13  0:54 ` [U-Boot-Users] DataFlash on my SBC is failed, can i boot u-boot ? nm
2006-07-13  9:22 ` Stefan Roese [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=200607131122.52985.sr@denx.de \
    --to=sr@denx.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