Nvidia AGX Xavier DevKit doesn't turn ON

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.4.0.7363
other

Host Machine Version
native Ubuntu 18.04
other

Hello, When powering the system with the harness and the power supply nothing happens, only some of the LEDs are on. The lit up LEDs are :

  • DS5
  • DS10
  • DS6
  • DS9
  • DS7
  • DS4
  • DS3
  • DS2
  • DS15

I have plugged my laptop to debug usb and it seems that I cannot access the Aurix shell with minicom. (Pressing enter doesn’t give any output.)

We tried what is described in both of those 2 links and none of them worked :

-How to connect to aurix shell?
-How to connect to aurix console？

What could be the problem ?

Thanks !

2

Dear @maxandre.ogeret ,
Could you share lssub output after connecting debug USB cable?
Also, please share minicom connection settings for aurix port(Press CTRL A Z for help)

3

Hello @SivaRamaKrishnaNV
Here is the lsusb output :

Bus 002 Device 002: ID 8087:8001 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8009 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 04f2:b43b Chicony Electronics Co., Ltd 
Bus 003 Device 002: ID 8087:0a2a Intel Corp. 
Bus 003 Device 008: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 003 Device 007: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 003 Device 006: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 003 Device 005: ID 0403:6011 Future Technology Devices International, Ltd FT4232H Quad HS USB-UART/FIFO IC
Bus 003 Device 004: ID 0424:2807 Standard Microsystems Corp. 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

And here’s the minicom config I am using :

port     /dev/ttyUSB3
baudrate 115200
bits     8
parity   N
stopbits 1
rtscts   No
xonxoff  No

(I have tried with ttyUSB1 and ttyUSB3)

Thanks a lot for your help

5

Dear @maxandre.ogeret ,
It seems the board is connected as per lsusb. Could you check the below

  • Connect using sudo minicom -D /dev/ttyUSB3

  • Press CTRL A Z O

  • share screenshot of serial port connection details for confirmation

May I know, the condition of the board before you hit this issue? Is it on office desk or inside car? how it was used?
Did you check flashing latest release using sdkmanager?

6

Thanks for your answer, here is the screenshot :

nvidia-troubleshooting
nvidia-troubleshooting730×331 26.3 KB

the condition of the board before you hit this issue?

The board spent most of this time on a desk for setting up the cameras and updating the firmware. We recently installed it in the car. And when testing the board with the official power supply once the board was installed in the car we had this problem. Nothing else than the power has been plugged, for testing purposes.

It seems that it stopped working without any obvious reasons, the board has been handled according to the documentation without exception.

Thanks again

7

Dear @maxandre.ogeret ,
Can you set “Hardware FLow Control” to “No” and check connecting.

8

We managed to find the problem.
The MCU programming switch has been switched to PRG inadvertently. It’s very sad that there is no notification from the debug TTYs.
Everything is working fine now.

1 Like
9

Thanks for sharing back your finding and solution.