Using NVIDIA Jetson Modules

‎

Table of Contents [Sticky]

Support for NVIDIA Jetson

NVIDIA Jetson modules and developer kits do not have native support for DPDK due to the NIC manufacturer. In the case of the Jetson Xavier modules, the ethernet interface is based on the Marvell 88E1512PB2, whereas the Jetson Orin modules are based on a Realtek module. In both cases, there is no support for kernel bypassing. More information can be found in the DPDK Compatible Hardware site.

For NVIDIA Jetson modules, it is recommended that an external PCIe or an M2-based network card compatible with DPDK be installed. NVIDIA ConnectX can be used to boost Jetson's networking, providing DPDK and RDMA support.

RidgeRun Use Case

At RidgeRun, we are currently testing the Intel I210-T1 at 1 Gbps for DPDK in both X86 and NVIDIA Jetson Systems

Stay tuned for the updates!

PCIe network card (Intel I210-T1) on Jetson AGX Orin

1. Connect the NIC: Attach the NIC to the Jetson AGX Orin using the external PCIe port and power on the device.

2. Check Ethernet Interfaces: After booting up, run the following command to check the available network interfaces:

nvidia@ubuntu:~$ ip addr

And you should get a result similar to this:

...
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 98:b7:85:1f:ca:d7 brd ff:ff:ff:ff:ff:ff
    altname enP5p1s0
    inet 192.168.100.112/24 brd 192.168.100.255 scope global dynamic noprefixroute eth0
       valid_lft 86265sec preferred_lft 86265sec
    inet6 fe80::a8ac:52de:acc:c9b9/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
...
6: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1466 qdisc mq state DOWN group default qlen 1000
    link/ether 48:b0:2d:78:ba:00 brd ff:ff:ff:ff:ff:ff
    inet 192.168.100.1/24 brd 192.168.100.255 scope global eth1
       valid_lft forever preferred_lft forever
...

Here, eth0 and eth1 interfaces should appear.

Info

Note that eth1 may be assigned the IP address 192.168.100.1, which is often the default gateway address, and may cause connectivity issues.

2.1 Troubleshoot Connectivity Issues: If there’s no connectivity (no ping response or SSH access to the board):

Open Settings > Network.
Check for a duplicate entry of the eth1 interface. This duplicate entry might be manually assigning the IP address 192.168.100.1, leading to a conflict.
Remove the Duplicate Interface:
- In Settings > Network, locate eth1.
- Click the gear icon next to eth1 to access configuration options.
- Select Remove Connection Profile to delete the duplicate entry.

Duplicated eth1 interface in Network options

Duplicated eth1 options menu

3. Verify Connectivity: Once the duplicate profile is removed, the conflict should be resolved, restoring normal connectivity to the board.

❯