After flashing the system using flash.sh, an error occurred after the burning process

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
1

The device was unable to find the network card information. The source code was obtained through source_sync.sh and compiled using nvbuild.sh. The dmesg output is as follows.

ayxx@tegra-ubuntu:~$ sudo dmesg | grep eth
[sudo] password for ayxx:
[    0.000000] psci: probing for conduit method from DT.
[    4.475577] usbcore: registered new interface driver cdc_ether
[    6.295923] optee: probing for conduit method.
[   10.092037] nvethernet 6810000.ethernet: Adding to iommu group 51
[   10.098620] nvethernet 6810000.ethernet: failed to read skip mac reset flag, default 0
[   10.106775] nvethernet 6810000.ethernet: failed to read MDIO address
[   10.113322] nvethernet 6810000.ethernet: setting to default DMA bit mask
[   10.120263] nvethernet 6810000.ethernet: failed to read UPHY GBE mode- default to 10G
[   10.512685] nvethernet 6810000.ethernet: Ethernet MAC address: 3c:6d:66:b1:2d:d8
[   10.520711] nvethernet 6810000.ethernet: macsec param in DT is missing or disabled
[   10.528498] nvethernet 6810000.ethernet: Macsec not supported/Not enabled in DT
[   10.537934] nvethernet 6810000.ethernet: eth0 (HW ver: 31) created with 10 DMA channels
[   14.357594] using random self ethernet address
[   14.362586] using random host ethernet address
[   15.084344] using random self ethernet address
[   15.088940] using random host ethernet address
[   15.093738] mdio_bus 6810000.ethernet: MDIO device at address 0 is missing.
[   15.100956] nvethernet 6810000.ethernet: failed to connect PHY
[   15.107030] net eth0: ether_open: Cannot attach to PHY (error: -19)
[   97.393112] mdio_bus 6810000.ethernet: MDIO device at address 0 is missing.
[   97.400402] nvethernet 6810000.ethernet: failed to connect PHY
[   97.406483] net eth0: ether_open: Cannot attach to PHY (error: -19)
2

The base plate is the official one and the network card has not been modified.

3

jetpack 5.1.2

4

https://forums.developer.nvidia.com/t/unable-to-bring-up-jetson-agx-orin-devkit-onboard-ethernet/290140

Consistent with this issue 2

6

Is the issue there if you just flash the board with sdkmanager?

7

Yes, the same issue occurs when using SDKmanager to flash the device. I have verified the motherboard and the network cable using other Orin modules and found no problems.

8

Then please do the RMA.

9

I would like to clarify a question. During the process of flashing the device using the SDKManager, will the dtb, image, and Pinmux all be reset? Because I previously used the command “sudo ./flash.sh jetson-agx-orin-devkit internal” for flashing, and I’m worried that the SDKManager won’t modify my Pinmux.

10

What does that mean “SDKManager won’t modify my Pinmux”?

Are you talking about the pinmux file on host PC is wrong or you are talking about sdkmanager won’t update the pinmux on your Jetson?

If your BSP on host PC is still intact and not changed by you, then sdkmanager should be correct.

However, if you ever changed something in the BSP and sdkmanager still used that BSP, then please uninstall that and let sdkmanager download a new BSP again to flash.