Jump to content

Networking,USB,and Storage Status

From RidgeRun Developer Wiki

Follow us on: YouTube Twitter LinkedIn Email Share this page

Share This Page



Networking, USB, and Storage Status

Networking, USB, and storage are fundamental platform services used by most Xavier based deployments.

This page presents the validation evidence collected for these subsystems on the CIP kernel platform, including interface detection, device enumeration, removable storage support, and root filesystem operation.

The examples and logs shown throughout this section were captured directly from the validation environment used during AGX Xavier and Xavier NX platforms testing.


Info
Networking, USB, and storage are considered foundational services. If any of the checks in this page fail, it is recommended to resolve those issues before continuing with camera, multimedia, GPU, AI, or application validation.


Validation Summary

The following platform services were validated successfully:

  • Networking – Ethernet interface detected and operational.
  • USB – USB devices enumerate correctly.
  • USB Storage – Removable storage detected and mounted successfully.
  • Root Filesystem – System boots from the expected eMMC partition for the AGX Xavier and an SD card for the Xavier NX.

The sections below provide the commands, logs, and validation evidence used to verify each subsystem.

Step 1: Verify System Boot

The first step is confirming that the board reaches userspace successfully and that the kernel boots using the expected root filesystem.

Check the running kernel version:

uname -r

Observed output:

5.10.254-cip72-tegra

Review the kernel command line:

cat /proc/cmdline

Relevant output:

root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4

The boot log should also indicate that the root filesystem was located and mounted successfully:

Root device found: mmcblk0p1
Found dev node: /dev/mmcblk0p1
EXT4-fs (mmcblk0p1): mounted filesystem
Rootfs mounted over mmcblk0p1


Info
A successful boot involves more than reaching a login prompt. The kernel must locate the root device, mount the filesystem, and transition into userspace correctly.


Step 2: Verify Networking

Once the board reaches userspace, verify that the Ethernet controller initialized correctly.

List the available network interfaces:

ip -br link

Observed output:

eth0             UP             48:b0:2d:3a:70:46 <BROADCAST,MULTICAST,UP,LOWER_UP>

The presence of eth0 confirms that the primary Ethernet interface was created successfully.

Next, verify the active driver:

ethtool -i eth0

Observed output:

driver: nvethernet
version: 5.10.254-cip72-tegra
bus-info: 2490000.ethernet

The boot log also shows the controller being initialized:

nvethernet 2490000.ethernet: Ethernet MAC address: 48:b0:2d:3a:70:46
nvethernet 2490000.ethernet: eth0 created


Info
For this validation, the most important result is confirming that eth0 is available and managed by the nvethernet driver. Network throughput and performance measurements belong in separate validation activities.


Step 3: Verify USB Device Enumeration

After networking has been validated, the next step is verifying that the USB subsystem initializes correctly and can detect connected devices.

List the detected USB devices:

lsusb

Observed output:

Bus 001 Device 002: ID 048d:1234 Integrated Technology Express, Inc. Mass storage

This validation was performed using a USB keyboard connected to the both AGX Xavier and Xavier NX platforms.

The USB topology can also be inspected:

lsusb -t

Relevant output for AGX Xavier:

/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/4p, 480M
    |__ Port 4: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 480M

Xavier NX:

/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=tegra-xusb/4p, 480M
    |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 4: Dev 5, If 0, Class=Mass Storage, Driver=usb-storage, 480M


Info
A simple USB keyboard is sufficient to validate USB enumeration because it exercises device discovery, descriptor parsing, and driver binding through the HID subsystem.


Step 4: Verify USB Storage Support

After confirming that USB devices enumerate correctly, a practical next step is validating removable USB storage.

Connect a USB flash drive to one of the available USB ports.

The kernel should automatically detect the new storage device.

Observed kernel log:

sda: detected capacity change from 0 to 62914560000
sda: sda1
sd 1:0:0:0: [sda] Attached SCSI removable disk

Verify that the device appears as a block device:

lsblk

Relevant output:

sda      58.6G
└─sda1   58.6G

Create a mount point:

sudo mkdir -p /mnt/usb

Mount the partition:

sudo mount /dev/sda1 /mnt/usb

The USB storage device should now be accessible through:

/mnt/usb


Info
This validation extends beyond USB enumeration. It confirms that the USB stack, block device layer, partition detection, and filesystem mounting path are all operating correctly.


Step 5: Verify Root Filesystem Storage

The final step is confirming that the system booted from the expected eMMC or SD card devices and that the root filesystem remains mounted correctly.

List the available block devices:

lsblk

Relevant output for AGX Xavier:

mmcblk0      29.1G
└─mmcblk0p1  28G   /

Xavier NX:

mmcblk0      179:0    0  59,5G  0 disk 
├─mmcblk0p1  179:1    0  58,8G  0 part /

Verify the mounted root filesystem:

findmnt /

Observed output:

/      /dev/mmcblk0p1 ext4

The boot log should also indicate that the eMMC or the SD card devices were detected and used as the root filesystem source:

Root device found: mmcblk0p1
Found dev node: /dev/mmcblk0p1
EXT4-fs (mmcblk0p1): mounted filesystem
Rootfs mounted over mmcblk0p1


Info
Only the root filesystem partition is shown here for clarity. The AGX Xavier eMMC or the SD card inserted in Xavier NX contain many additional bootloader and platform partitions that are not relevant to this validation.


Overall Status

The platform successfully reaches userspace and provides the foundational services expected from a functional Linux system.

The Ethernet controller initializes correctly and exposes the primary network interface. USB devices are detected and enumerated successfully. External USB storage can be mounted without additional configuration, and the root filesystem is loaded from the expected eMMC partition.





Cookies help us deliver our services. By using our services, you agree to our use of cookies.