We are using L4T 35.3.1 & JetPack 5.1.1, and we recently applied the LPDDR patch due to PCN210100.
However, only the modules equipped with SEC DDR are experiencing the following issue:
An Ethernet link drop issue, which was not seen on modules with Micron LPDDR, is now occurring.
Where should we investigate to address this?
The Jetson Orin NX datasheet does not specify the part number of the Ethernet PHY integrated in the module.
Some say a Realtek PHY is used—where can we find this part number?
In case of Orin NX 8GB, can I use below command to disable EEE(energy efficient etherent) function?
If not, could you let me know how I can disable EEE function ?
=================================================
root@82BF:~# ethtool --show-eee eth0
EEE Settings for eth0:
EEE status: disabled
Tx LPI: disabled
Supported EEE link modes: 100baseT/Full
1000baseT/Full
Advertised EEE link modes: Not reported
Link partner advertised EEE link modes: 100baseT/Full
1000baseT/Full
root@82BF:~#
Hi, Wayne
We disabled EEE (Energy Efficient Ethernet) on the Jetson and conducted tests. According to what we found, all devices on the same network need to have EEE enabled for the link to remain stable. Is this correct? We are not using latest jp.
If we upgrade Jetpack to 6.0GA in the current situation, we will also have to make many modifications to our application code.
In order to solve this Ethernet issue, you need a patch that can be applied to the current LT4 35.4.1, rather than upgrading Jetpack to 6.0GA.
Additionally, it is necessary to check which part of the current problematic patch “overlay_PCN210361_PCN210100_r35.4.1.tbz2” affects the operation of ethernet.
Are you guys working together for the current issue?
As Wayne has requested before, please check if you can reproduce the similar issue on Orin Nano devkit(p3768).
You can also clarify which release may fix your issue so that we can help to find the possible fixes.
Please use the Orin Nano devkit to verify with both Jetpack 5.1.2(r35.4.1) and Jetpack 5.1.5(r35.6.1) and share the full dmesg when you hit the issue for further check.