Orin devkit 10G internet can't ping other device after reboot

Hi nvida team:

I am using an Orin devit . after I flash the orin through the linux for tegar.
the cmd is : ./flash.sh -r jetson-agx-orin-devkit mmcblk0p1
and config the eth0 ip 192.168.1.101 . at this time if I ping the orin device through my PC(192.168.1.10) . can connected.
but if I reboot the orin devkit . my PC can’t connect the orin devkit ,
and below is log:
orin+devkit-no-eth-log.txt (88.3 KB)

Is the IP still there after you reboot the device?

yes ,the IP is still there ,but can’t connected.


exec ifconfig cmd can’t see the IP

What if you ifconfig up and down the interface again?

below is the step after flash the orin devkit:
1.set IP


2.exec ifconfig

3. ping orin devkit from my PC:
图片
it’s ok first. but after me reboot the devkit .the IP is still there through the UI config ,but can’t connected

  1. exec the follow cmd.
    ifconfig eth0 down
    ifconfig eth0 up
    can not connected.

  2. exec the follow cmd.set the IP again.
    ifconfig eth0 192.168.1.101
    ifconfig eth0 down
    ifconfig eth0 up
    can not connected too.

Hi WayneWWW:
I think the eth0 cann’t connect it’s because of I comment eeprom in bootloader/tegra234-mb2-bct-common.dtsi file
图片
our customized carrier board do not have a eeprom.
and I noticed a new patch Jetson Linux 34.1 | NVIDIA Developer


and I am using this patch for test on Orin devkit now.
The fact is if I comment the eeprom .then the eth0 cann’t connected after reboot,but if I do not comment the eeprom ,it’s ok.

You only need to comment out cvb eeprom in the overlay. CVM is still needed.

thanks WayneWW :
Sorry for the late reply, it’s ok now.

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