Nvidia DRIVE AGX Orin setup error state help

Autonomous Vehicles DRIVE AGX Orin DRIVE AGX Orin General
1

Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.8.1
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other

Target Operating System
Linux
QNX
other

Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other

SDK Manager Version
1.9.3.10904
other

Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other

Nvidia DRIVE AGX Orin setup help

Note: SDK Manager 2.1.0.11682

Hi, I’m tring to setup a Nvidia Drive AGX Orin following this steps found in : https://developer.nvidia.com/drive/secure/drive-orin/drive-agx-orin-devkit-qsg-du-11049-001.pdf

image
image873×531 97.1 KB

But when I get to step 8, instead of geeting any EULA agreement, I get the following error in the minicom terminal (dev/ttyACM1):

*************** NvShell Initialization Start******************
DRIVE-V6.0.4-P3710-AFW-Aurix-StepB-5.05.03
Compilation date: Jul 16 2022, 01:07:14
Enter 'help' to see the available commands.

*************** NvShell Initialized  *************************
 Press 'Enter' for NvShell prompt 
*************************************************************


MCU_FOH: E2E Initialized
MCU_FOH: Initialization done
INFO: MCU_PLTFPWRMGR: Power-on Triggered...
MCU_FOH: SOC error pin is asserted
ERROR: MCU_PLTFPWRMGR: Enable Pre-regulator Request failed ....Move to error state !
INFO: MCU_SWC_FanControl: max_rpm fan1 : 0
INFO: MCU_SWC_FanControl: maxrpm of fan1 has more than 50 percent deviation against rated maxrpm
INFO: MCU_SWC_FanControl: max_rpm fan2 : 0
INFO: MCU_SWC_FanControl: maxrpm of fan2 has more than 50 percent deviation against rated maxrpm

I don’t see any fan movement or LED or something on.

I have the following connections:

image
image766×606 61.3 KB

I tried also flashing the device with SDK Manager, but it also fails:

image
image778×370 76.8 KB

Can someone help me find the way to solve this, please. Any documentation that can help me understand the problem. What does “Pre-regulator Request failed” refers to? Thanks in advance.

2

Dear @chd,
In the log I see disk avail on parition as zero. Does host has enough space? Please check Requirements for Your Development Environment | NVIDIA Docs for system requirement.
Also, is there any reason to use DRIVE OS 6.0.6 ? Can you upgrade to latest update i.e. DRIVE OS 6.0.8.1 ?

4
  1. DRIVE OS 6.0.6 is the latest version that SDK Manager 2.1.0.11682 show me as an option, but there is not a special reason for choosing that version.
    image
    image1028×660 114 KB

  1. I think the Ubuntu 20.04 host computer have has enough space: 202.9 GBs in the system partition. Not sure what partition is referring (?):

    image
    image1577×553 152 KB

    Data from failed flashing via SDK Manager:

  1. For trying to install DRIVE OS 6.0.8.1 the following link was used as reference (docker-ngc method):
    Install DRIVE OS Linux Docker Containers from NGC | NVIDIA Docs.

    But it also failed:

    image
    image1848×601 142 KB

    Files attached with data about failed flashing via docker method:

P.S. “Pre-regulator Request failed” is still reported in terminal when device is turned on

Hope you can help me. Thank you.

5

@chd Does the files get downloaded and driveos installed in the 202 GB same partition. You can change the path in sdkmanager UI. Anyways, we recommend to use docker to avoid host system state related issues.

Do you see any issue on target and hence you want to flash the target to see if it fix the issue? If so, could you share issue details?

Note that /dev/ttyACM1 gives access to aurix console and /dev/ttyACM0 give access to Tegra console. Please access the tegra console and share the already installed version using cat /etc/nvidia/version-ubuntu-rootfs.txt

Also, From the log it appears the board could not set in recovery mode.

Do you an additional Nvidia device in lsusb on host after you set the target in recovery mode.

tegrarecovery x1 off # on aurix
tegrareset x1 # On aurix
`lsusb` # On host
tegrarecovery x1 on # on aurix
tegrareset x1 # On aurix
`lsusb` # On host.  This should show additional Nvidia device entry
6

Do you see any issue on target and hence you want to flash the target to see if it fix the issue? If so, could you share

Yes, that was my the intention of trying to flash the device, to see if it fix the issue.

When the Main Power Switch is pressed to the ON position, the unit doesn’t seen to power up (No FAN movement, any LED, display, or anything), and in the Aurix console send me:

ERROR: MCU_PLTFPWRMGR: Enable Pre-regulator Request failed …Move to error state !

image
image743×327 124 KB

And I never get to the step 8 of the Hardware Quick Start Guide:

  1. Accept the End User License Agreement (EULA) and set up account username(s) and
    password(s) in the Terminal Emulator window that was opened in Step 6.
7

@chd EULA notice will come on tegra console(not aurix console) on the first boot after flash.

8

This is what I get, i only see the Nvidia Corp. Tegra On-Plataform Operator:

image
image1802×898 293 KB

9

The Aurix console (dev/ttyACM1) is the only one that responds (send messages) after I Press the Main Power Switch to the ON position. I tried to connect to Tegra console (dev/ttyACM0 ), but I don’t see anything. I used the configuration found in Configuring Minicom | NVIDIA Docs.
image

I Press the Main Power Switch to the ON position, and nothing is shown in dev/ttyACM0 minicom terminal, also pressed “Enter” and nothing happens.

I’m not able to get that.

Im using this configuration:
image

image

Is there something that I’m missing?
Thanks in advance

10

Dear @chd,
The Tegra seems to be not turning on. Could you give a try running version and poweron commands on aurix console and update the results.
Is the board used in office premises or car? When was this issue noticed?

11

image
image759×597 149 KB

In office. I notices the issue since I received it.

12

Dear @chd,
Could you check the private message and provide the asked details?

13

Dear @SivaRamaKrishnaNV
I responded with the information currently available. thank you.

Do you think is there other thing I can try, does it makes sense to try flashing an older DRIVE OS version (other than 6.0.6 or 6.0.8.1)… or any another suggestion?

14

Dear @chd,
did you try poweroff and poweron on aurix console. could you share the log. I suspect Tegra is not turning on.

board condition is like that only since you receive from vendor? Can you check changing PSU if you have other?

15

Dear @SivaRamaKrishnaNV

image
image793×743 197 KB

I don’t have other PSU. I have a multimeter, maybe I can check some test-point or something if you recommend to measure something. Input voltage is ~127 VAC, which I think is in line with the documentation:

image
image825×78 7.83 KB

Yes… I’m asking for more details about the acquisition process (as commented in private message).

17

Dear @chd,
This looks like a HW issue. I am checking internally on further guidance. Please check my private message

19

Dear @chd,
Could you share the location and board S/N picture in private message.