From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Fw: TFTP fails when using network switch
Date: Tue, 20 Jan 2009 12:13:52 -0500 [thread overview]
Message-ID: <49760650.6040105@ge.com> (raw)
In-Reply-To: <20090120095547.466b2e93@uncle-pecos.Colorado.EDU>
Loren A. Linden Levy wrote:
> Hi Jerry,
>
> It looks to me like for the M%282 board the PHY address is determined
> by querying the MII interface:
>
> include/configs/M5282EVB.h
>
> #define CONFIG_MCFFEC
> #ifdef CONFIG_MCFFEC
> # define CONFIG_NET_MULTI 1
> # define CONFIG_MII 1
> # define CFG_DISCOVER_PHY
> ...
>
> This cause the code in ./drivers/net/mcffec.c specifically
> mii_discover_phy to be run, I tried to enable the debugging in this
> code:
>
> //#undef ET_DEBUG
> //#undef MII_DEBUG
I am not familiar with the code, but I would change them to #defines
rather than commenting out the #undefs, and look to see where they are
used to see what to expect to be printed out.
> but it does not seem to print anything (:(). One interesting feature is
> that once my uClinux image has booted I can talk to it over the
> switched network just fin. So the issue is really something in the
> setup of the MII PHY interface in u-boot. Is there any build target to
> allow me to try and debug this?
I still strongly suspect your hardware initialization isn't right
(again, I'm not familiar with the MPC5282 processor nor your board) or
your PHY is miswired (I'm assuming this is a custom board, not the eval
board).
You need to verify your hardware is toggling the MII pins on the PHY.
If it isn't, you need to verify your hardware is toggling the MII pins
on the processor. If not, it's likely your software
initialization/driver. If so, you have a hardware problem.
If the MII pins are not toggling, you are not going to get anywhere.
Until you verify it (hands on, with some sort of hardware probe), you
are shooting in the dark. While you can hit the target in the dark with
enough rounds, the efficiency sucks.
> Thanks.
>
> Alex
Good luck,
gvb
next prev parent reply other threads:[~2009-01-20 17:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 0:02 [U-Boot] Fw: TFTP fails when using network switch Loren A. Linden Levy
2009-01-06 7:41 ` Remy Bohmer
2009-01-06 22:52 ` Ulf Samuelsson
2009-01-06 23:00 ` Wolfgang Denk
2009-01-07 12:52 ` Jerry Van Baren
2009-01-07 14:03 ` Loren A. Linden Levy
2009-01-07 15:57 ` Swarthout Edward L
2009-01-07 18:02 ` Ben Warren
2009-01-07 18:23 ` Jerry Van Baren
2009-01-07 19:36 ` Ulf Samuelsson
2009-01-07 19:58 ` Jerry Van Baren
2009-01-16 0:36 ` L. A. Linden Levy
2009-01-16 15:34 ` Jerry Van Baren
2009-01-20 0:00 ` Loren A. Linden Levy
2009-01-20 1:14 ` Jerry Van Baren
2009-01-20 2:39 ` Loren A. Linden Levy
2009-01-20 16:55 ` Loren A. Linden Levy
2009-01-20 17:13 ` Jerry Van Baren [this message]
2009-01-21 0:14 ` Loren A. Linden Levy
2009-01-21 12:23 ` Jerry Van Baren
2009-01-06 12:45 ` Jerry Van Baren
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=49760650.6040105@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