[U-Boot] Fw: TFTP fails when using network switch

Loren A. Linden Levy
2009-01-20T00:00:26Z

Hi All,

I still have not found a solution and I am a bit desperate. I did not
seem to be able to send any packets (using ping) from the FECO on the
M5282Lite board to the tftp host, however pings from the host were
answered and I saw packets going from the coldfire board to the host
in wireshark. I also get a strange error when I ask for mii info:

uBOOT=>> mii device
MII devices: 'FEC0'
Current device: 'FEC0

uBOOT=>> mii info
MII not complete
MII not complete
...

a dump gives me:

uBOOT=>> mii dump
MII not complete
0. (ffff) -- PHY control register --
(8000:8000) 0.15 = 1 reset
(4000:4000) 0.14 = 1 loopback
(2040:2040) 0. 6,13 = b11 speed selection = ??? Mbps
(1000:1000) 0.12 = 1 A/N enable
(0800:0800) 0.11 = 1 power-down
(0400:0400) 0.10 = 1 isolate
(0200:0200) 0. 9 = 1 restart A/N
(0100:0100) 0. 8 = 1 duplex = full
(0080:0080) 0. 7 = 1 collision test enable
(003f:003f) 0. 5- 0 = 63 (reserved)

I have tried a few other commands, but am not sure how to interpret
the output. See below:

uBOOT=>> mii dump 0 1
MII not complete
1. (ffff) -- PHY status register --
(8000:8000) 1.15 = 1 100BASE-T4 able
(4000:4000) 1.14 = 1 100BASE-X full duplex able
(2000:2000) 1.13 = 1 100BASE-X half duplex able
(1000:1000) 1.12 = 1 10 Mbps full duplex able
(0800:0800) 1.11 = 1 10 Mbps half duplex able
(0400:0400) 1.10 = 1 100BASE-T2 full duplex able
(0200:0200) 1. 9 = 1 100BASE-T2 half duplex able
(0100:0100) 1. 8 = 1 extended status
(0080:0080) 1. 7 = 1 (reserved)
(0040:0040) 1. 6 = 1 MF preamble suppression
(0020:0020) 1. 5 = 1 A/N complete
(0010:0010) 1. 4 = 1 remote fault
(0008:0008) 1. 3 = 1 A/N able
(0004:0004) 1. 2 = 1 link status
(0002:0002) 1. 1 = 1 jabber detect
(0001:0001) 1. 0 = 1 extended capabilities

uBOOT=>> mii dump 0 2
MII not complete
2. (ffff) -- PHY ID 1 register --
(ffff:ffff) 2.15- 0 = 65535 OUI portion

uBOOT=>> mii dump 0 3
MII not complete
3. (ffff) -- PHY ID 2 register --
(fc00:fc00) 3.15-10 = 63 OUI portion
(03f0:03f0) 3. 9- 4 = 63 manufacturer part number
(000f:000f) 3. 3- 0 = 15 manufacturer rev. number

uBOOT=>> mii dump 0 4
MII not complete
4. (ffff) -- Autonegotiation advertisement register --
(8000:8000) 4.15 = 1 next page able
(4000:4000) 4.14 = 1 reserved
(2000:2000) 4.13 = 1 remote fault
(1000:1000) 4.12 = 1 reserved
(0800:0800) 4.11 = 1 asymmetric pause
(0400:0400) 4.10 = 1 pause enable
(0200:0200) 4. 9 = 1 100BASE-T4 able
(0100:0100) 4. 8 = 1 100BASE-TX full duplex able
(0080:0080) 4. 7 = 1 100BASE-TX able
(0040:0040) 4. 6 = 1 10BASE-T full duplex able
(0020:0020) 4. 5 = 1 10BASE-T able
(001f:001f) 4. 4- 0 = 31 selector = ???

I also tried to look at the tftp server side of things:

=>> sudo mii-tool -v eth1
eth1: negotiated 1000baseT-HD flow-control, link ok
product info: vendor 00:60:51, model 0 rev 1
basic mode: autonegotiation enabled
basic status: autonegotiation complete, link ok
capabilities: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
advertising: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
link partner: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD

Any more advice on what could be wrong or how to debug it would be
greatly appreciated.

Alex

On Fri, 16 Jan 2009 10:34:39 -0500
Jerry Van Baren <gerald.vanbaren@ge.com> wrote:

> L. A. Linden Levy wrote:
> > Can someone tell me how to use the mii command? I have the following
> > from a dump:
> >
> > uBOOT=>> mii dump
> > MII not complete
> > 0. (ffff) -- PHY control register --
> > (8000:8000) 0.15 = 1 reset
> > (4000:4000) 0.14 = 1 loopback
> > (2040:2040) 0. 6,13 = b11 speed selection = ??? Mbps
> > (1000:1000) 0.12 = 1 A/N enable
> > (0800:0800) 0.11 = 1 power-down
> > (0400:0400) 0.10 = 1 isolate
> > (0200:0200) 0. 9 = 1 restart A/N
> > (0100:0100) 0. 8 = 1 duplex = full
> > (0080:0080) 0. 7 = 1 collision test enable
> > (003f:003f) 0. 5- 0 = 63 (reserved)
>
> Please don't top post.
>
> U-Boot can tell you how to use the mii command: "help mii"
>
> It has been a long time since I used mii, but it looks like you need to
> use "mii device" to find your PHY and then "mii dump <addr> <reg>" to
> dump the registers of that device.
>
> HTH,
> gvb

--
--
---------------------------------------------
Loren A. Linden Levy
Department of Physics
390 UCB
University of Colorado
Boulder, CO 80309-0390
Tel: 303-735-6146 (CU) / +049 040 8998 4789 (DESY)
Fax: 303-492-3352 (CU) / +049 040 8998 4034 (DESY)
Cell: 303-332-2768 (U.S.) / +049 (0)151 5496 1831 (Germany)
Email: Loren.Lindenlevy at colorado.edu
url: http://up.colorado.edu/~lindenle
_____________________________________________
---------------------------------------------
This email has been cryptographically signed.
Search for "lindenle" at pgp.mit.edu
to obtain my public key which can be used
to verify the authenticity of this message.
_____________________________________________
---------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090119/d951e66b/attachment.pgp