Tegra SoC cannot power up after driver flashing successfully

Autonomous Vehicles DRIVE AGX Orin DRIVE AGX Orin General
1

DRIVE OS Version: DRIVE OS version: 6.0.10

Issue Description:

I am currently working with a DRIVE AGX Orin developer kit and am encountering an issue where the Tegra SoC cannot power up. The AURIX console reports that the power-up request fails due to unmet preconditions.

From the AURIX NvShell console I ran the following command:

show_fanrpm

The output is:

Fan1 RPM : ~2527
Fan2 RPM : 0

Additionally, the system previously reported:

“maxrpm of fan2 has more than 50 percent deviation against rated maxrpm”

Because of this, attempts to start Tegra using:

tegrareset x1

result in:

“Power-Up Request failed - Preconditions not met”

Based on this, it appears the AURIX safety logic is blocking Tegra startup due to Fan2 not being detected.

I attempted to inspect the cooling module to check the fan connections. However, after removing the visible screws on the rear panel of the chassis, I am still unable to remove the top cover or access the internal fans. I would appreciate guidance on the correct procedure for opening the enclosure to access the cooling assembly and verify the fan connections.

For reference:

  • DRIVE OS version: 6.0.10

  • AURIX console accessible via /dev/ttyACM1

  • Board appears otherwise functional (AURIX shell operational, flashing completed successfully)

Reference guidance I used for installing latest DRIVE OS: https://developer.nvidia.com/docs/drive/drive-os/6.0.10/public/drive-os-linux-installation/common/topics/installation/docker-ngc/setup-drive-os-linux-devzone.html#flash-instructions-linux

Could you please advise:

  1. The correct procedure to open the DRIVE AGX Orin chassis and access the internal fans

  2. Whether Fan2 RPM = 0 would prevent Tegra power-up in this configuration

  3. Any recommended diagnostics or workaround to confirm the fan hardware status

Thank you for your assistance.

4

Dear @julie.yang,
Could you please below information to triage the issue..

  1. Is the board used in car or office desk?
  2. When did you notice this issue and what did you do before you encounter this issue.
  3. Does that mean, you don’t see any issue with flashing? You see bootburn successful message at the end of flashing ?
  4. Open serial console of tegra and Aurix using minicom and switch off/on power supply button to capture bootlogs of tegra and Aurix console log. Please share them
  5. Share showvoltages output on Aurix console.
5

  1. on office desk

  2. after flashing is done. this is how I flashed the drive OS:

    image
    image959×475 43.4 KB

  3. no issues.

    image
    image738×975 186 KB

6

4.here it is

image
image553×868 13 KB

5.showvoltages command doesn’t work

7

This has no relation to tegra boot.

Dear @julie.yang ,
Opening chasis would void warranty and we do not recommend to do it.

Is the tegra accessible before you flash DOS 6.0.10?
Aurix version seems to 6.0.6. Could you share the flashing logs for confirmation?
Also, Could you share the text logs of poweroff and poweron commands on aurix console.

8

Could you try aurixreset force on aurix console helps you to get access to tegra console?

Could you share the aurix log where you encountered this error. The recently shared log does not seem to have this issue.

9

image
image504×919 19.4 KB

10

image
image616×313 7.12 KB

image
image596×877 9.83 KB

11

Dear @julie.yang ,
Is tegra booting and able to access tegra console now using minicom?

12

No, I’ve been using putty

13

Hi @SivaRamaKrishnaNV , we successfully installed 6.0.10, which is good.
A New question, may I know where we can find sample_lidar_replay for LiDAR plugin testing? like DriveWorks SDK Reference: Lidar Replay Sample

14

Dear @zachary.wu1 ,
Glad to hear you could flash the target and access the console.
May I know what fixed the issue?
For lidar plugin testing, you can use lidar replay sample. Please see DriveWorks SDK Reference: Lidar Plugin Sample .
Please file a new topic incase you have any issues/doubts to avoid cluttering of issues.

15

Dear @julie.yang ,
Could you please clarify what changes allowed to flash DOS 6.0.10 successfully?