We need to read and write registers to test PHY AQR113C. On your website I find the following reference: Orin can not read the PHY reg data - #15 by WayneWWW method.i try it and can not read the correct ID, I do not know if there is a difference in the device tree, the attachment is the device tree, please help check, thank you.
The phy ID I read with the tool here is incorrect as follows:
Hi,
One question here. Are you able to read the vendor id out from Orin AGX devkit?
The result on Orin AGX devkit:
t@lcfc-desktop:/home/lcfc# ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1466
ether 48:b0:2d:69:57:56 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
l4tbr0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.55.1 netmask 255.255.255.0 broadcast 192.168.55.255
inet6 fe80::1 prefixlen 128 scopeid 0x20
inet6 fe80::acdc:43ff:fec3:1ea1 prefixlen 64 scopeid 0x20
ether ae:dc:43:c3:1e:a1 txqueuelen 1000 (Ethernet)
RX packets 1230 bytes 108531 (108.5 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 376 bytes 46394 (46.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 751 bytes 54037 (54.0 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 751 bytes 54037 (54.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
rndis0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::acdc:43ff:fec3:1ea1 prefixlen 64 scopeid 0x20
ether ae:dc:43:c3:1e:a1 txqueuelen 1000 (Ethernet)
RX packets 1249 bytes 110322 (110.3 KB)
RX errors 0 dropped 4 overruns 0 frame 0
TX packets 408 bytes 67972 (67.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
usb0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether ae:dc:43:c3:1e:a3 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether ec:2e:98:ca:65:af txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@lcfc-desktop:/home/lcfc# ./phytool read eth0/1/2
0xffff
root@lcfc-desktop:/home/lcfc# ./phytool print eth0/1
ieee-phy: id:0xffffffff
ieee-phy: reg:BMCR(0x00) val:0xffff
flags: +reset +loopback +aneg-enable +power-down +isolate +aneg-restart +collision-test
speed: 1000-full
ieee-phy: reg:BMSR(0x01) val:0xffff
capabilities: +100-b4 +100-f +100-h +10-f +10-h +100-t2-f +100-t2-h
flags: +ext-status +aneg-complete +remote-fault +aneg-capable +link +jabber +ext-register
root@lcfc-desktop:/home/lcfc#
Sorry that I don’t know what you want to say here.
Do you mean you cannot read out vendor info even on devkit?
Yes.It’s the same as onboard test and can not read out phy ID info
Where did you get that command? Are you sure that one can read vendor id?
I downloaded the C45 tool from the link you gave above.
README.md (2.6 KB)
在這邊跟你澄清一下以免你搞不清楚我們現在在問的問題…
那個phytool是3rdparty tool. 我們提供它只是因為它有支援C-45. 它上面的example, 我不保證每一個功能都跟你預期的一樣…
請問你確定這個PHY 透過 “phytool read eth0/1/2” 會印出vendor資料嗎? 我的意思是你確定是1跟2這兩個參數嗎…?
That phytool is the 3rdparty tool. We provide it only because it has support for the C-45. I can’t guarantee that every feature will be as you expect…
Are you sure this PHY will print vendor data through “phytool read eth0/1/2”? I mean are you sure it’s 1 and 2…?
I add log to debug the phy ioctl kernel code and modify some parameters.Now it’s OK.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
