Part Number: AM6442
We are observing an issue during Ethernet validation. The internal loopback test is failing on the interface between the AM6442 processor and the DP83867IRRGZT Ethernet PHY.
Kindly review this issue and advise on the possible root cause or additional debugging steps. If required, I can share the test logs, and configuration for further analysis.
Please let me know how we should proceed.
Thank you,
Chittibabu
Log Details:
root@am64xx-evm:~#
root@am64xx-evm:~#
root@am64xx-evm:~# dmesg | grep -i mdio
[ 0.945086] mdio-mux-multiplexer mdio-mux-1: /mdio-mux-1: failed to get mux-control (0)
[ 0.945120] mdio-mux-multiplexer mdio-mux-1: error -ENOENT: Failed to get mux
[ 0.945129] mdio-mux-multiplexer: probe of mdio-mux-1 failed with error -2
[ 1.492119] davinci_mdio 8000f00.mdio: Configuring MDIO in manual mode
[ 1.526103] davinci_mdio 8000f00.mdio: davinci mdio revision 9.7, bus freq 1000000
[ 1.527855] davinci_mdio 8000f00.mdio: phy[0]: device 8000f00.mdio:00, driver TI DP83867
[ 5.785529] davinci_mdio 300b2400.mdio: Configuring MDIO in manual mode
[ 5.834154] davinci_mdio 300b2400.mdio: davinci mdio revision 1.7, bus freq 1000000
[ 5.871651] davinci_mdio 300b2400.mdio: phy[15]: device 300b2400.mdio:0f, driver unknown
[ 12.455158] am65-cpsw-nuss 8000000.ethernet eth0: PHY [8000f00.mdio:00] driver [TI DP83867] (irq=POLL)
root@am64xx-evm:~#
root@am64xx-evm:~#
root@am64xx-evm:~# ethtool --phy-statistics eth0
no stats available
root@am64xx-evm:~#
root@am64xx-evm:~# mii_mgr -d 0 -w 0 -v 0x4140
-sh: mii_mgr: command not found
root@am64xx-evm:~# ethtool -s eth0 speed 1000 duplex full autoneg off
root@am64xx-evm:~#
root@am64xx-evm:~# ethtool -t eth0 online
Cannot test: Operation not supported
root@am64xx-evm:~#
root@am64xx-evm:~# ethtool --set-phy-loopback eth0 on
ethtool: bad command line argument(s)
For more information run ethtool -h
root@am64xx-evm:~#
root@am64xx-evm:~#
root@am64xx-evm:~# ip link set eth0 up
root@am64xx-evm:~# ping 192.168.1.100
PING 192.168.1.100 (192.168.1.100): 56 data bytes
64 bytes from 192.168.1.100: seq=0 ttl=64 time=0.290 ms
64 bytes from 192.168.1.100: seq=1 ttl=64 time=0.261 ms
64 bytes from 192.168.1.100: seq=2 ttl=64 time=0.226 ms
64 bytes from 192.168.1.100: seq=3 ttl=64 time=0.228 ms
^C
--- 192.168.1.100 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 0.226/0.251/0.290 ms
root@am64xx-evm:~#