Nvidia Drive Orin AGX Developer not working, unable to accept terms and conditions for intial setup

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.10.0
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
2.1.0
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

Issue Description
Unable to setup Nvidia Drive AGX Orin Developer kit, unable to accept EULA terms and conditions to setup username and password for the dev kit. I have attached all the serial logs below.

Error String

Logs

teraterm-com24-log.txt (38.3 KB)

teraterm-Com23-log.txt (6.6 KB)

Please paste the complete application log here. If there are multiple logs, please use multiple text box

*************** 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
INFO: NvMCU_OrinTMON: Toggle check of Alert and Therm pins for local sensor successfull
ERROR: NVMCU_ORINPWRCTRL: FUNC_NIRQ Toggle check has failed
INFO: NvMCU_OrinTMON: Toggle check of Alert and Therm pins for remote sensor successfull
INFO: NVMCU_ORINPWRCTRL: FUNC_NIRQ continuous monitoring Enabled…!
INFO: NvMCU_OrinTMON: Orin Temperature sensor initialized
ERROR: MCU_PLTFPWRMGR: Request VMON Power-up sequence verification failed …Continue sequence !

INFO: BtChn_Cfg: No valid next bootchain loaded
INFO: NVMCU_ORINPWRCTRL: Tegra x1 Boot Chain: A
INFO: SftyMon_tmon: Board Temperature sensor initialized
INFO: MCU_PLTFPWRMGR: Board TMON enabled …
INFO: MCU_PLTFPWRMGR: Orin TMON enabled …
INFO: Marvell Switch: p3710_oak_init
INFO: Marvell Switch: Device ID in the Spruce slave address 0x8 is not as expected
INFO: Marvell Switch: Expected 0xf130/0xf131/0xf132/0xf133, but reading back 0xa722
INFO: Marvell Switch: IfxEth_Marvell_Switch_write_reg: write the extend 16 bit data 0x3
INFO: Marvell Switch: IfxEth_Marvell_Switch_write_reg: write the extend 16 bit data 0x3
INFO: Marvell Switch: IfxEth_Marvell_Switch_write_reg: write the extend 16 bit data 0x1
INFO: Marvell Switch: IfxEth_Marvell_Switch_write_reg: write the extend 16 bit data 0x1
INFO: Marvell Switch: IfxEth_Marvell_Switch_write_reg: write the extend 16 bit data 0x1
INFO: Marvell Switch: IfxEth_Marvell_Switch_write_reg: write the extend 16 bit data 0x1
INFO: Marvell Switch: IfxEth_Marvell_Switch_write_reg: write the extend 16 bit data 0x1
INFO: Marvell Switch: IfxEth_Marvell_Switch_write_reg: write the extend 16 bit data 0x1
INFO: Marvell Switch: IfxEth_Marvell_Switch_write_reg: write the extend 16 bit data 0x1
INFO: Marvell Switch: IfxEth_Marvell_Switch_write_reg: write the extend 16 bit data 0x1
INFO: Marvell Switch: IfxEth_Marvell_Switch_write_reg: write the extend 16 bit data 0x1
INFO: Marvell Switch: IfxEth_Marvell_Switch_write_reg: write the extend 16 bit data 0x0
INFO: Marvell Switch: Port restrictions for Aurix port(P8) enabled
INFO: Marvell Switch: p3710_spruce_init
INFO: Marvell Switch: Spruce device with chip revision B4 detected on SMI address 0x1.
INFO: Marvell Switch: IfxEth_Marvell_Switch_write_reg: write the extend 16 bit data 0x0
INFO: Marvell Switch: IfxEth_Marvell_Switch_write_reg: write the extend 16 bit data 0x0
INFO: Marvell Switch: IfxEth_Marvell_Switch_write_reg: write the extend 16 bit data 0x3
INFO: Marvell Switch: IfxEth_Marvell_Switch_write_reg: write the extend 16 bit data 0x3
INFO: MCU_PltfPwrMgr: Switch Init
INFO: MCU_PltfPwrMgr: Linkup status is not active
INFO: MCU_PltfPwrMgr: 88Q5072 OAK Link Active
INFO: Marvell Phy: Initial 88Q2112 config
INFO: Marvell Phy:
Start init 88Q222x slave address 1 at group 1
INFO: Marvell Phy: Apply Legacy mode
INFO: Marvell Phy: Initialed 88Q2112 A2 silicon 1G, slave address 1 at group 1, API 1.10
INFO: Marvell Phy:
Start init 88Q222x slave address 2 at group 1
INFO: Marvell Phy: Apply Legacy mode
INFO: Marvell Phy: Initialed 88Q2112 A2 silicon 1G, slave address 2 at group 1, API 1.10
INFO: Marvell Phy:
Start init 88Q222x slave address 3 at group 1
INFO: Marvell Phy: Apply Legacy mode
INFO: Marvell Phy: Initialed 88Q2112 A2 silicon 1G, slave address 3 at group 1, API 1.10
INFO: Marvell Phy:
Start init 88Q222x slave address 4 at group 1
INFO: Marvell Phy: Apply Legacy mode
INFO: Marvell Phy: Initialed 88Q2112 A2 silicon 1G, slave address 4 at group 1, API 1.10
INFO: Marvell Phy:
Start init 88Q222x slave address 5 at group 1
INFO: Marvell Phy: Apply Legacy mode
INFO: Marvell Phy: Initialed 88Q2112 A2 silicon 1G, slave address 5 at group 1, API 1.10
INFO: Marvell Phy:
Start init 88Q222x slave address 6 at group 1
INFO: Marvell Phy: Apply Legacy mode
INFO: Marvell Phy: Initialed 88Q2112 A2 silicon 1G, slave address 6 at group 1, API 1.10
INFO: Marvell Phy:
Start init 88Q222x slave address 7 at group 1
INFO: Marvell Phy: Apply Legacy mode
MCU_FOH: SOC error pin is de-asserted
INFO: Marvell Phy: Initialed 88Q2112 A2 silicon 1G, slave address 7 at group 1, API 1.10
INFO: Marvell Phy:
Start init 88Q222x slave address 1 at group 0
INFO: Marvell Phy: Apply Legacy mode
INFO: Marvell Phy: Initialed 88Q2112 A2 silicon 1G, slave address 1 at group 0, API 1.10
INFO: Marvell Phy:
Start init 88Q222x slave address 2 at group 0
INFO: Marvell Phy: Initialed 88Q2112 A2 silicon 100M, slave address 2 at group 0, API 1.10
INFO: MCU_PltfPwrMgr: PHYs Init
INFO: MCU_PltfPwrMgr: StbM Init
INFO: MCU_PLTFPWRMGR: Power-up sequence is complete !
INFO: MCU_PLTFPWRMGR: DL Ready drive to HIGH !
ERROR: SftyMon_IoHwAbs: VRS11 PGOOD Failure notification…!
INFO: MCU_PLTFPWRMGR: VRS11 PG Monitoring enabled …
Power on the system
ERROR: MCU_ERRHANDLER: PGOOD failure notification…error detected by VRS11
MCU_FOH: MCU FOH : Power state notification for Orin Power On
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
MCU_FOH: SOC error pin is asserted
MCU_FOH: Spi Transmit Started
MCU_FOH: ErrReport: ErrorCode-0x240008cb ReporterId-0x8001 Error_Attribute-0x0 Timestamp-0x5c648ea
MCU_FOH: ErrReport: ErrorCode-0x89abcdef ReporterId-0x8013 Error_Attribute-0x0 Timestamp-0x5c69152
MCU_FOH: ErrReport: ErrorCode-0x1012 ReporterId-0xe00e Error_Attribute-0x0 Timestamp-0x645298a
MCU_FOH: ErrReport: ErrorCode-0x20000007 ReporterId-0x8030 Error_Attribute-0x0 Timestamp-0x9b95ffa
MCU_FOH: ErrReport: ErrorCode-0x20000 ReporterId-0x8030 Error_Attribute-0x0 Timestamp-0x9b9f362
MCU_FOH: Periodic Report: KeyOfSeed-0xffff
MCU_FOH: Periodic Report[0]:SystemFailureId-0xabcd, MaturationState-0xef, Failure_Attribute-0x22
MCU_FOH: Periodic Report[9]:SystemFailureId-0x1234, MaturationState-0x56, Failure_Attribute-0xee
MCU_FOH: ErrReport: ErrorCode-0x100c ReporterId-0xe00e Error_Attribute-0x0 Timestamp-0x2278090a
MCU_FOH: ErrReport: ErrorCode-0x100c ReporterId-0x800e Error_Attribute-0x1002 Timestamp-0x22780dd2

5

Dear @sgollapa ,
May I know if it is same target in Drive AGX Not powering on freshly out of the package ?

Did you check flashing DRIVE OS 6.0.10(https://developer.nvidia.com/docs/drive/drive-os/6.0.10/public/drive-os-linux-installation/common/topics/installation/docker-ngc/install-drive-os-linux-docker-from-ngc-devzone.html) ?

6

Hi SivaRamaKrishnaNV,

Yes. Both these threads are for the same issue. You can close the one created by Shanthosh(sgollapa).

Regards,

Bharath

7

No, this issue is on a Different Nvidia Drive. In the Drive I have, i can hear the fan sound and led lights turn on. the logs I have attached is from serial terminal.

8

Kindly support to resolve this issue asap. Thanks

9

Hello,

The issue I posted is for as different Nvidia Drive. The drive I have has a different behavior, I can hear the fan sound and see led lights when I turn on the Nvidia Drive,and it is fresh out of the box. I have already attached the logs from serial post on my post in Nvidia Developer forum. Kindly support to resolve this issue asap.

Thanks

10

Did you check this @sgollapa . If so, Could you share the flashing logs.

11

log_sgn3u0824y7tvjiamcb9drzl5xh6owf1.txt (1.9 KB)

driveinstaller.log (690.2 KB)

12

here are the logs, when I try to flash 6.0.10

13

[2025-10-16 13:24:30,270 root DEBUG console_logger.py 17 32] b’[bootburnTegra-A]: [executeShellCommand(165)] : Output: Sending blob\r\nERROR: might be timeout in USB write.\r\n\r\n’

Noticed board goes into recovery mode and additional NVIDIA device is detected. USB connection seems failing, can you try hard rebooting both host and device. Also make sure there are two USB wire connection(not single connection) between host and target. Please see Quick start guide for details of the connection. Also, try changing USB connection wires and ports on host. Update us if it helps to fix the issue.

14

did a hard reboot for both Drive and Host PC. yes there are two USB wire connections, one is USB type A to Micro usb, and the other is USB Type a to type c (connected to the left C type port according to documentation). switched to different USB ports, when I run lsusb, i see only one Nvidia device showing up.

After trying all these I still have the same issue. please suggest any additional steps.
Thanks.

15

there is different error this time,

i have attached the logs

log_lzj3ikbgrdw0mfosp5uvy2t1chq796n8.txt (1.9 KB)

driveinstaller.log (677.8 KB)

16

any update on this topic? @SivaRamaKrishnaNV

17

I still see the same error “[2025-10-16 13:24:30,268 root DEBUG console_logger.py 17 32] b’[bootburnTegra-A]: [executeShellCommand(163)] : shell command – /drive/drive-foundation/tools/flashtools/flash/tegrarcm_v2 --instance /dev/bus/usb/001/012 --download blob ./rcm_blob.bin failed\r\n’
[2025-10-16 13:24:30,270 root DEBUG console_logger.py 17 32] b’[bootburnTegra-A]: [executeShellCommand(165)] : Output: Sending blob\r\nERROR: might be timeout in USB write.\r\n\r\n’” in shared logs. Double check if the new logs are shared.

Could you check boot into other bootchain to confirm if the issue persists in current bootchain?

  1. Connect to aurix console using sudo minicom -D /dev/ttyACM1 and run below command
getdfltbtchain x1  # confirm the boot chain. Default is A.
setdfltbtchain x1 B # Set the boot chain B. 
aurixreset #wait 30 secs and issue next command
poweroff #wait 30 secs and issue next command
poweron 
getdfltbtchain x1 #to confirm if the bootchain is changed to B
  1. Connect to tegra console sudo minicom -D /dev/ttyACM0 and press ENTER to see if it can be accessed.

If the above does not work, Can you try flashing using bootburn directly. Please check below commands and update the status

  1. Connect to aurix console(sudo minicom -D /dev/ttyACM1) and run poweroff and wait for 30 secs and run poweron
  2. Make all the connections between host and target as indicated in quick start guide and run lsusb on host and expect to see only one NVIDIA device in the output. This indicates the target is in normal mode
  3. On aurix console, run tegrarecovery x1 on and tegrareset x1 to set the board in recovery mode. Now, if you run lsusb on host, we expect to see an additional NVIDIA device.
  4. Close all serial connections to target and check sudo fuser /dev/ttyACM0 & sudo fuser /dev/ttyACM1 outputs nothing.
  5. On host docker run below commands
cd /drive/
./drive-foundation/make/bind_partitions -b p3710-10-s05 linux
./drive-foundation/tools/flashtools/bootburn/bootburn.py -b p3710-10-s05 -B qspi
  1. Connect to aurix console(sudo minicom -D /dev/ttyACM1) and run tegrarecovery x1 off and tegrareset x1 to set the board in normal mode and check accessing target using sudo minicom -D /dev/ttyACM0

Please share your observations .

19

Dear @sgollapa ,
As shared via PM, we need logs of tegra when flashing.
Can you keep the board in recovery mode and check flashing using bootburn command. Please keep the minicom session to tegra open and continue flashing. Share the tegra logs after you hit error

20

Dear @sgollapa ,
Could you provide any update?

21

log_z750jhwqxvenm486f329uritlsbpokdc.txt (2.1 KB)

driveinstaller.log (679.0 KB)

driveinstaller.log.1.txt (1.9 MB)

I have attached all the logs, please let me know if you want to setup another call to troubleshoot further, appreciate your support but is there any way to resolve this faster.

22

I don’t see tegra console logs.

  1. From host(not from docker container), open minicom session to tegra console(sudo minicom -D /dev/ttyACM0 and keep it open.

  2. To keep board is recovery mode

sudo minicom -D /dev/ttyACM1 #connect to aurix console to keep the board in recovery mode
#run below command on aurix console
tegrarecovery x1 on
tegrareset x1
  1. You can close aurix minicom session. Now check lsusb on host to confirm if two NVIDIA devices are visible. This confirms the board is in recovery mode.
  2. Now run bootburn command from docker to flash target
/drive/drive-foundation//tools/flashtools/bootburn/bootburn.py -b p3710-10-s05 -B qspi

Share the tegra console output after you hit issue.

23

i set the board to recovery mode,

ttyACM0-log.txt (87.5 KB)

ttyACM1-log.txt (8.2 KB)

bootburnscript-log.txt (5.6 KB)

lsusb-output.txt (922 Bytes)

24

Dear @sgollapa ,
Could you check private message and share requested details about board