Other Parts Discussed in Thread: DP83869
Hi
We are using DP83869 with T2080 in 1000Mbps mode,
While trying to ping in uboot we get the following error:
Using FM1@DTSEC3 device
ARP Retry count exceeded; starting again
ping failed; host 169.254.139.108 is not alive
=> ping 169.254.139.108
Using FM1@DTSEC3 device
=> mii info
PHY 0x01: OUI = 0x80028, Model = 0x0F, Rev = 0x03, 1000baseX, HDX
PHY 0x02: OUI = 0x80028, Model = 0x0F, Rev = 0x03, 1000baseX, HDX
=> mii
mii - MII utility commands
Usage:
mii device - list available devices
mii device <devname> - set current device
mii info <addr> - display MII PHY info
mii read <addr> <reg> - read MII PHY <addr> register <reg>
mii write <addr> <reg> <data> - write MII PHY <addr> register <reg>
mii modify <addr> <reg> <data> <mask> - modify MII PHY <addr> register <reg>
updating bits identified in <mask>
mii dump <addr> <reg> - pretty-print <addr> <reg> (0-5 only)
Addr and/or reg may be ranges, e.g. 2-7.
=> mii dump 1 0
0. (1140) -- PHY control register --
(8000:0000) 0.15 = 0 reset
(4000:0000) 0.14 = 0 loopback
(2040:0040) 0. 6,13 = b10 speed selection = 1000 Mbps
(1000:1000) 0.12 = 1 A/N enable
(0800:0000) 0.11 = 0 power-down
(0400:0000) 0.10 = 0 isolate
(0200:0000) 0. 9 = 0 restart A/N
(0100:0100) 0. 8 = 1 duplex = full
(0080:0000) 0. 7 = 0 collision test enable
(003f:0000) 0. 5- 0 = 0 (reserved)
=> mii dump 1 1
1. (7949) -- PHY status register --
(8000:0000) 1.15 = 0 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:0000) 1.10 = 0 100BASE-T2 full duplex able
(0200:0000) 1. 9 = 0 100BASE-T2 half duplex able
(0100:0100) 1. 8 = 1 extended status
(0080:0000) 1. 7 = 0 (reserved)
(0040:0040) 1. 6 = 1 MF preamble suppression
(0020:0000) 1. 5 = 0 A/N complete
(0010:0000) 1. 4 = 0 remote fault
(0008:0008) 1. 3 = 1 A/N able
(0004:0000) 1. 2 = 0 link status
(0002:0000) 1. 1 = 0 jabber detect
(0001:0001) 1. 0 = 1 extended capabilities
=> mii dump 1 1
1. (796d) -- PHY status register --
(8000:0000) 1.15 = 0 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:0000) 1.10 = 0 100BASE-T2 full duplex able
(0200:0000) 1. 9 = 0 100BASE-T2 half duplex able
(0100:0100) 1. 8 = 1 extended status
(0080:0000) 1. 7 = 0 (reserved)
(0040:0040) 1. 6 = 1 MF preamble suppression
(0020:0020) 1. 5 = 1 A/N complete
(0010:0000) 1. 4 = 0 remote fault
(0008:0008) 1. 3 = 1 A/N able
(0004:0004) 1. 2 = 1 link status
(0002:0000) 1. 1 = 0 jabber detect
(0001:0001) 1. 0 = 1 extended capabilities
=> mii dump 1 0
0. (1140) -- PHY control register --
(8000:0000) 0.15 = 0 reset
(4000:0000) 0.14 = 0 loopback
(2040:0040) 0. 6,13 = b10 speed selection = 1000 Mbps
(1000:1000) 0.12 = 1 A/N enable
(0800:0000) 0.11 = 0 power-down
(0400:0000) 0.10 = 0 isolate
(0200:0000) 0. 9 = 0 restart A/N
(0100:0100) 0. 8 = 1 duplex = full
(0080:0000) 0. 7 = 0 collision test enable
(003f:0000) 0. 5- 0 = 0 (reserved)
=> setenv ipaddr 169.254.139.109
=> setenv ethaddr xx:xx:xx:xx:xx:xx ; We have set MAC Address here
=> ping 169.254.139.108
Using FM1@DTSEC3 device
ARP Retry count exceeded; starting again
ping failed; host 169.254.139.108 is not alive
=> ping 169.254.139.108
Using FM1@DTSEC3 device
ARP Retry count exceeded; starting again
ping failed; host 169.254.139.108 is not alive
=> mii read 0 000e
FFFF
=> mii read 0 0-1f
addr=00 reg=00 data=FFFF
addr=00 reg=01 data=FFFF
addr=00 reg=02 data=FFFF
addr=00 reg=03 data=FFFF
addr=00 reg=04 data=FFFF
addr=00 reg=05 data=FFFF
addr=00 reg=06 data=FFFF
addr=00 reg=07 data=FFFF
addr=00 reg=08 data=FFFF
addr=00 reg=09 data=FFFF
addr=00 reg=0a data=FFFF
addr=00 reg=0b data=FFFF
addr=00 reg=0c data=FFFF
addr=00 reg=0d data=FFFF
addr=00 reg=0e data=FFFF
addr=00 reg=0f data=FFFF
addr=00 reg=10 data=FFFF
addr=00 reg=11 data=FFFF
addr=00 reg=12 data=FFFF
addr=00 reg=13 data=FFFF
addr=00 reg=14 data=FFFF
addr=00 reg=15 data=FFFF
addr=00 reg=16 data=FFFF
addr=00 reg=17 data=FFFF
addr=00 reg=18 data=FFFF
addr=00 reg=19 data=FFFF
addr=00 reg=1a data=FFFF
addr=00 reg=1b data=FFFF
addr=00 reg=1c data=FFFF
addr=00 reg=1d data=FFFF
addr=00 reg=1e data=FFFF
addr=00 reg=1f data=FFFF
=> mii read 1 0-1f
addr=01 reg=00 data=1140
addr=01 reg=01 data=796D
addr=01 reg=02 data=2000
addr=01 reg=03 data=A0F3
addr=01 reg=04 data=01E1
addr=01 reg=05 data=CDE1
addr=01 reg=06 data=006F
addr=01 reg=07 data=2001
addr=01 reg=08 data=4D29
addr=01 reg=09 data=0300
addr=01 reg=0a data=3800
addr=01 reg=0b data=0000
addr=01 reg=0c data=0000
addr=01 reg=0d data=0000
addr=01 reg=0e data=0000
addr=01 reg=0f data=F000
addr=01 reg=10 data=5048
addr=01 reg=11 data=BF12
addr=01 reg=12 data=0000
addr=01 reg=13 data=1C46
addr=01 reg=14 data=29C7
addr=01 reg=15 data=0000
addr=01 reg=16 data=0000
addr=01 reg=17 data=0040
addr=01 reg=18 data=6150
addr=01 reg=19 data=4444
addr=01 reg=1a data=0002
addr=01 reg=1b data=0000
addr=01 reg=1c data=0000
addr=01 reg=1d data=0000
addr=01 reg=1e data=0012
addr=01 reg=1f data=0000
=> mii read 0x1 0x1df
0000
=> mii write 0x1 0x1DF 0x40
=> mii read 0x1 0x1df
0040
=> mii write 0x1 0x0 0x1140
=> mii write 0x1 0x4 0x01E1
=> mii write 0x1 0x9 0x0300
=> mii write 0x1 0x10 0x5048
=> mii write 0x1 0x1F 0x4000
=>
=>
=> ping 169.254.139.108
Using FM1@DTSEC3 device
ARP Retry count exceeded; starting again
ping failed; host 169.254.139.108 is not alive
=>
Using FM1@DTSEC3 device
ARP Retry count exceeded; starting again
ping failed; host 169.254.139.108 is not alive
=> ping 169.254.139.108
Using FM1@DTSEC3 device
Let us know anything can be checked.
