No internet access on NVIDIA DRIVE AGX Xavier, Marvell switch driver shows some errors

Autonomous Vehicles DRIVE AGX Xavier DRIVE AGX Xavier General
1

Please provide the following info (check/uncheck the boxes after creating this topic):
Software Version
DRIVE OS Linux 5.2.6
DRIVE OS Linux 5.2.6 and DriveWorks 4.0
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
other

Target Operating System
Linux
QNX
other

Hardware Platform
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
other

SDK Manager Version
1.9.1.10844
other

Host Machine Version
native Ubuntu 18.04
other

Hello. Upon several tries and directly contacting the representatives from NVIDIA, i was advised to open a ticket similar to one before. I am a developer at a corporation and we have no knowledge or experience with NVIDIA DRIVE AGX Xaviers. I have at my disposal 2 of them, although not connected between them. I am facing the difficulty of not being able to access the internet on either of the Tegras. Upon executing dmesg it shows some errors for the Marvell switch.

Screenshots and terminal outputs can be found on this topic: Support for installing newer version of Python - DRIVE AGX Xavier / DRIVE AGX Xavier General - NVIDIA Developer Forums

2

You have internet issue on both DRIVE AGX Xavier devkits?

Can you share dmesg log?

Can you try force wipeout and check flashing DRIVE OS 5.2.0 release to see if the network issue is observed. Please use sdkmanger-archievedversions to get old releases.

3

Yes

I am attaching the log
dmesg.log (66.4 KB)

I will now go and try to see if i can flash it for an older release.

4

I am sorry but i think you have typed incorrectly the command. I presume you meant to write sdkmanager --archived-versions. Either way, it actually removes the option to select Xavier, it only shows Orin. when i run it with sdkmanager --show-all-versions, i am able to select Xavier, however, i cannot select older DRIVEOS versions.

5

Please use sdkmanager --archivedversions

6

Hello. It has the same output as --archived-versions

7

I don’t see any references to marvel in dmesg log.
From previous topic, I notice we get IP from DHCP which failed to happen in your case. Was networking on board working well before ? Is it like you have only 2 boards and both have same issue or you have other working boards as well? Also, I see the issue persists even after reflashing (erasing persistent partition).

I assume you tested with sdkmanager --archivedversions and noticed no older releases are present with sdkmanager 2.x releases. Can you please share the screen shots to share with engineering team?

8

yes.
About the dmesg, i might be wrong. However, simply by trying to print the firmware version of the switch, i can see the same messages that i happened to see before.
here are the sceenshots of the sdkmanager

image
image690×493 45.6 KB

image
image690×447 64.5 KB

here is the switch firmware message:

image
image690×433 61.1 KB

10

I notice the old releases were removed from sdkmanager. So this behaviour is expected now.

Is it possible to test target network connection in different network as you are getting IP from DCHP.

Could you also try the steps in https://docs.nvidia.com/drive/drive-os-5.2.6.0L/drive-os/index.html#page/DRIVE_OS_Linux_SDK_NGC_Development_Guide/config_network_setup.html#wwconnect_header to enable network on target.