L4T R35.2.1 Ethernet (eth0) not working - Xavier NX

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
, , ,
1

Hi,

we have problems with the eth0 interface in L4T R35.2.1 on Jetson Xavier NX.

I flashed the Jetson Xavier NX with the JetPack 5.1 applying the following steps:

  1. Install SDK Manager
  2. Download Target Components (Jetson Linux only)
  3. Synchronize Sources (source_sync.sh)
  4. Compile kernel and device tree
  5. Flash Jetson Xavier NX (flash.sh)

We use a custom carrier board. But the issue is most likely not related to the custom carrier as the Ethernet works fine when flashing the same Jetson Xavier NX module and custom carrier board with L4T R32.7.2 instead of L4T R35.2.1.
So with L4T R32.7.2 everything works fine. But using the L4T R35.2.1 the eth0 interface is not operational.

The eth0 is not able to obtain an IPv4 address. It has an IPv6 address tough.

eth0
eth01481×328 176 KB

When setting an static IP we are able to communicate on the local network but do not have internet access.

I appreciate any help to understand what the difference between L4T R32.7.2 and L4T R35.2.1 is, regarding the Ethernet interface?

Best regards
Bruno

3

Is this issue reproduced if using jp5.0.2?

4

Hi WayneWWW,

I just flashed JetPack 5.0.2. Same issue here.

I noticed following errors in SDK Manager Terminal (JetPack 5.0.2 & JetPack 5.1):

09:42:35 ERROR: Flash Jetson Xavier NX - flash: 36144 blocks
09:42:35 ERROR: Flash Jetson Xavier NX - flash: gzip: /home/bruno/nvidia/nvidia_sdk/JetPack_5.0.2_Linux_JETSON_XAVIER_NX_TARGETS/Linux_for_Tegra/kernel/Image: not in gzip format
09:42:43 ERROR: Flash Jetson Xavier NX - flash: 53066 blocks
09:42:43 ERROR: Flash Jetson Xavier NX - flash: 20+0 records in
09:42:43 ERROR: Flash Jetson Xavier NX - flash: 20+0 records out
09:42:43 ERROR: Flash Jetson Xavier NX - flash: 20 bytes copied, 0,000199964 s, 100 kB/s
09:44:28 ERROR: Flash Jetson Xavier NX - flash: 131072+0 records in
09:44:28 ERROR: Flash Jetson Xavier NX - flash: 131072+0 records out
09:44:28 ERROR: Flash Jetson Xavier NX - flash: 67108864 bytes (67 MB, 64 MiB) copied, 0,413798 s, 162 MB/s

But it finishes indicating successful operation. So we observe the same behavior for JetPack 5.0.2 (L4T R35.1) and JetPack 5.1 (L4T R35.2.1).

5

Hi,

  1. Don’t need to care about those flash errors.

  2. We don’t have any other user reporting same issue as your case. My device didn’t have such issue either.

Thus, please check

  1. If this is only happened to specific module?

  2. Is this issue on devkit or your custom board?

  3. Is this issue related to your network environment or not?

  4. I notice you mentioned you compiled the kernel. Please do not try that for now. Just use pure jetpack BSP.

6

Hi,

okay. This is helpful. So we can rule out errors in the flash process.

Just to clarify the issue we are facing:

  • We use a custom carrier board.
  • Using JetPack 4.6.2 ethernet works fine.
  • Using JetPack 5.x ethernet is not working.
  • Same module, same custom carrier board. Only difference is the JetPack version. That’s why I am pretty sure it can’t be related to network environment or hardware related issues.
  • I tried flashing the module directly from within SDK Manager. Same issue.

Thanks so far!

7

Do you have NV devkit to test?

8

Unfortunately not. The problem is most likely not hardware related. But we are considering to purchase one if we are unable to fix the issue soon - just to be certain about hardware related issues.

10

Quick update:

When I manually reset the DHCP for eth0 the IPv4 address is assigned. I used the following commands for this:

sudo dhclient -r eth0
sudo dhclient eth0
11

What is “hardware” here? Carrier board?

12

Hi,

yes I meant carrier boards but I confused this problem with another problem… Basically I just wanted to post our solution for the eth0 issue. I will modify the post to avoid further confusion.

The issue with eth0 was experienced on all carrier boards but only when using JetPack 5.1, not when using JetPack 4.6.2.

13

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