Unable to bring up Jetson AGX Orin Devkit onboard ethernet

I’m unable to bring up Jetson AGX Orin Devkit onboard ethernet. Similar cases and documentation I’ve been able to find on this forum relate to custom carrier boards and their device trees which I not using. I have the default P3737 carrier board with P3701 module as per Jetson AGX Orin [32GB developer kit version]. The ports rx/tx lights appear permanently illuminated and reflashing (both JetPack 6.0 DP and JetPack 5.1.3) has made no difference.

I’ve listed some relevant commands and outputs below:
dmesg:

[   12.569313] mdio_bus 6810000.ethernet: MDIO device at address 0 is missing.
[   12.569328] nvethernet 6810000.ethernet: failed to connect PHY
[   12.569332] net eth0: ether_open: Cannot attach to PHY (error: -19)

nmcli:

eth0: unavailable
        "eth0"
        ethernet (nvethernet), 48:B0:2D:A4:D3:92, hw, mtu 1466

ip a:

5: eth0: <BROADCAST,MULTICAST> mtu 1466 qdisc noop state DOWN group default qlen 1000
    link/ether 48:b0:2d:a4:d3:92 brd ff:ff:ff:ff:ff:ff

Attempting to bring interface up with ip link set eth0 up results in same dmesg output as listed above :

RTNETLINK answers: No such device

I’d appreciate any insight on what may be causing this - happy to provide additional detail if required.

Hi,
Have you checked the corresponding device tree? I suspect that the problem is caused by the PHY chip. Is the PHY chip welded properly? Has the pin of the chip been measured?

Hi Andy,

Not entirely sure what I should be looking for within the device tree - I can see there are entries for PHY so I have attached it below.

devicetree.txt (564.6 KB)

As for the soldering of the PHY chip - since this isn’t a custom carrier board I wouldn’t expect any issues here. Would this require me to measure voltages coming to U2701? Which test pads could I use to verify correct soldering/voltages?

Thanks

Still hoping to get some input on this - haven’t been able to make any significant progress on this issue.

Hi,

What is the exact hardware change here? Such issue shouldn’t happen on Orin AGX devkit…

Hi Wayne,

No hardware changes have been made, Orin AGX devkit is being used as received.

So it was working fine before and suddenly cannot work?

I believe it failed during a reflash quite some time ago now. A USB RJ45 adapter has been used as a workaround since.

If you are sure it is NV devkit, then it is highly possible a broken hardware.

Cannot attach to PHY (error: -19)

This means the issue is on the ethernet PHY does not respond to driver.

Yes it is definitely NV devkit P3737 carrier board with P3701 module. Is there a way to check the correct driver is installed and being loaded?

If you directly flash with default sdkmanager with any kind of jetpack5 or 6 image, then this thing would be definitely setting correctly…

Okay that’s something I’ve already tried - In that case I’ll look to RMA the unit. Thanks

1 Like