Agx orin use rgmii problem

Hi, Our carrier board with L4T 35.2.1 use rtl8211 (rgmii) and disable 10G network.
It seems something wrong. Sometime it can not get ip when booting.
If boot no IP, the network can not work. And then use command “ifconfig” will see RX packets and TX packets is 0. But it always has interrupts on “gpio 39 Level 2310000.ethernet:01”.

nvorin@tegra-ubuntu:~$ ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1466
        ether 48:b0:2d:94:5e:25  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

nvorin@tegra-ubuntu:~$ cat /proc/interrupts |grep eth
 69:          0          0          0          0          0          0          0          0     GICv3 226 Level     eth0.common_irq
 70:          0          0          0          0          0          0          0          0     GICv3 218 Level     eth0.vm0
 71:          0          0          0          0          0          0          0          0     GICv3 219 Level     eth0.vm1
 72:          0          0          0          0          0          0          0          0     GICv3 220 Level     eth0.vm2
 73:          0          0          0          0          0          0          0          0     GICv3 221 Level     eth0.vm3
310:     508041          0          0          0          0          0          0          0      gpio  39 Level     2310000.ethernet:01
nvorin@tegra-ubuntu:~$

You must use command “sudo ifconfig eth0 down” and “sudo ifconfig eth0 up” to enable network.
Then the RX packets and TX packets has value. Network work normally.

Do we get any dmesg error when this situation happened? What if you delay the probe the ethernet driver and see if that could bypass error? Not sure if the reset gpio has abnormal behavior (too early?)

net_log02.txt (69.5 KB)
Attached is dmesg file.

Hi, I found there are 2 cpu usage is high when idle.
what’s wrong with it?

Sorry for the late response, is this still an issue to support? Thanks

It maybe a hardware issue, use the second version of the PCB and it will be fine.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.