No /dev/ttyUSBx and no display : return to sender?

Autonomous Vehicles DRIVE AGX Xavier DRIVE AGX Xavier General
1

Please provide the following info (check/uncheck the boxes after clicking “+ Create Topic”):
Software Version
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.5.0.7774
other

Host Machine Version
native Ubuntu 18.04
other

Hi,

we have a Drive AGX system (Peagasus) but when USB is plug between host pc and device (in debug port) no /dev/ttyUSB is visible on host PC despite we have well:

Bus 001 Device 057: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 001 Device 056: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 001 Device 055: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 001 Device 054: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC

sdkmanager doesnt detect the board.

Previously the /dev/ttyUSB* allowing communication with the device were visible but since a last reboot that doesnt appear anymore. Our device still pings after booting but we dont have ssh available. We make the hypothese that the device/OS is(are) waiting for user input… but…

but more over: we can’t get video/hdmi signal when a screen/display is connected… the display stays black. it appears that the hdmi connector of our device looks lose…

what are the options ?

eventually : how do you do a full factory reset ?

Thank you.

2

Dear @g.starck,
Just to confirm if you have performed steps in Install DRIVE with SDK Manager :: DRIVE Platform Installation Guide with NVIDIA SDK Manager after flashing?
Could you check connecting from other host to confirm if there is any issue with target?

3

Hi SivaRamaKrishna,

yes these steps were executed when we first setup the device.

The problem right now is the missing of /dev/ttyUSB* preventing to communicate at all (given the 2 OS are not up) with the device(s) ?

Also : What would you advise about the loose hdmi connector ?

4

Hi @g.starck ,

DRIVE forums are for those developers in NVIDIA DRIVE Developer Program for DRIVE AGX. We will need you to use your account with corporate or university email address.

Or you can also change your current account to use corporate or university email address by following below links:

My Profile | NVIDIA Developer → “Edit Profile” → “Change email” → “CHANGE”

Sorry for any inconvenience.

5

Here I am…

sorry I used by mistake my perso account… should I make a new post with my/this pro account ??

6

No, this one should be find. We can keep using it.

7

@gregory.starck ,
Please share your complete “$ lsusb” output.

8 
gregory.starck@axcompute03:~$ lsusb 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 057: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 001 Device 056: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 001 Device 055: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 001 Device 054: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 001 Device 053: ID 0424:2807 Standard Microsystems Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
gregory.starck@axcompute03:~$
9

Could you try if removing this USB device, using another USB 2.0 Type A to Type A cable, or rebooting the host system will help?

10

rebooted. but same than previously ; no /dev/ttyUSB* despite lsusb shows well what it should.

I’m checking for your request about the hub…

11

You can also have a quick try with another host system to clarify.

12

have tried with another computer… that has the same hardware than the previous one.

and that succeeded.

So case closed, thank you for your suggestion.

13

Thanks for letting us know.