Unable to Flash after power-failure

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

Target Operating System
Linux

Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-300)

Host Machine Version
native Ubuntu Linux 20.04 Host installed with Docker

Issue Description

Dear @SivaRamaKrishnaNV From the thread : External monitor not working after flashing - #6 by SivaRamaKrishnaNV it is mentioned about Orin2, however I have Orin1, which cannot be flashed by me yet, after said power-failure in the parent thread.

Error String

root@6.0.10.0-0009-build-linux-sdk:/drive# ./flash.py --clean /dev/ttyACM1 p3710
2025-09-16 09:34:14 INFO : Setting flash clean to initialize persistent partitions
2025-09-16 09:34:14 INFO : Initiating pre-flash check
2025-09-16 09:34:14 INFO : Checking Serial Port Connection
2025-09-16 09:34:14 INFO : Serial Port found /dev/ttyACM1
2025-09-16 09:34:14 INFO : Running basic open/close tests on Serial Port Connection
2025-09-16 09:34:14 INFO : Serial Port is open
2025-09-16 09:34:14 INFO : Flushing input and output buffer, discard all content
2025-09-16 09:34:14 INFO : Serial Port is closed
2025-09-16 09:34:14 INFO : Checking available targets
2025-09-16 09:34:14 INFO : Checking Orin board connection
2025-09-16 09:34:14 INFO : Orin board with Device ID -- 0955:7045 found.
2025-09-16 09:34:14 INFO : Orin board device path is /dev/bus/usb/003/010
2025-09-16 09:34:14 INFO : Pre-flash check complete
2025-09-16 09:34:14 INFO : Flashing DRIVE OS Docker
2025-09-16 09:34:34 INFO : driveinstaller v2.0
2025-09-16 09:34:34 INFO : 
2025-09-16 09:34:34 INFO : SDK/PDK Installer and Flasher
2025-09-16 09:34:34 INFO : Run `./driveinstaller --help` for usage information.
2025-09-16 09:34:34 INFO : 
2025-09-16 09:34:34 INFO : Initializing board and OS configuration to Autonomous Vehicle p3710 Linux Tegra A
2025-09-16 09:34:34 INFO : Manifest version 2.0
2025-09-16 09:34:34 INFO : 
2025-09-16 09:34:34 INFO : BOARD SKU : 940-63710-0010-300
2025-09-16 09:34:34 INFO : Found matching board id p3710-10-s05 in 940-63710-0010-300 sku
2025-09-16 09:34:34 INFO : Applying additional Bind opts []
2025-09-16 09:34:34 INFO : Binding of partitions failed ! Check log for more details.
2025-09-16 09:34:34 INFO : Failed to bind partitions!
2025-09-16 09:34:34 INFO : driveinstaller cannot continue! Check the log file for details: /drive/driveinstaller/driveinstaller.log
2025-09-16 09:34:34 ERROR : Flashing failed, please contact provider with logs /drive_flashing/log_m0l28qob6rxze1a5hyg79uinw4vdc3fj.txt and /drive/driveinstaller/driveinstaller.log.
root@6.0.10.0-0009-build-linux-sdk:/drive#

Logs

subprocess.CalledProcessError: Command 'python3 /drive/drive-foundation/tools/flashtools/bootburn/bootburn.py --find_board_name -x /dev/ttyACM1' returned non-zero exit status 15.
[2025-09-16 09:34:34,438 root ERROR pdk_bind.py 217 108] Binding of partitions failed ! Check log for more details.
[2025-09-16 09:34:34,438 root DEBUG utilities.py 294 108] ****** Starting bootburn/bootburn.py ********
[2025-09-16 09:34:34,438 root DEBUG utilities.py 294 108] ********* Starting t23x bootburn py ********
[2025-09-16 09:34:34,438 root DEBUG utilities.py 294 108] Bootburn Starting with arguments ['/drive/drive-foundation/tools/flashtools/bootburn/bootburn.py', '--find_board_name', '-x', '/dev/ttyACM1']
[2025-09-16 09:34:34,438 root DEBUG utilities.py 294 108] logfile :: /drive/drive-foundation/tools/flashtools/bootburn_t23x_py/bootburn.txt
[2025-09-16 09:34:34,438 root DEBUG utilities.py 294 108] cwd in setBoardConfigPath :: /drive/drive-foundation/tools/flashtools/bootburn_t23x_py
[2025-09-16 09:34:34,438 root DEBUG utilities.py 294 108]  trying hardware folder:
[2025-09-16 09:34:34,439 root DEBUG utilities.py 294 108] /drive/drive-foundation/platform-config/hardware/nvidia/platform/t23x/automotive/flashing/board_configs
[2025-09-16 09:34:34,439 root DEBUG utilities.py 294 108] 
[2025-09-16 09:34:34,439 root DEBUG utilities.py 294 108] Default Schema:/drive/drive-foundation/tools/flashtools/bootburn_t23x_py/nv-customer-data-schema.json
[2025-09-16 09:34:34,439 root DEBUG utilities.py 294 108] 
[2025-09-16 09:34:34,439 root DEBUG utilities.py 294 108] [bootburn]: [GetInfoRom(620)] : Read skuinfo from InfoRom...
[2025-09-16 09:34:34,439 root DEBUG utilities.py 294 108] [bootburn]: Execute command on Aurix serial port
[2025-09-16 09:34:34,439 root DEBUG utilities.py 294 108] [bootburn]: [CheckFirmwareisAFW(600)] : AFW firmware found
[2025-09-16 09:34:34,439 root DEBUG utilities.py 294 108] [bootburn]: [setTargetConfigt23xInfoRomInfo(720)] : 940-63710-0010-300
[2025-09-16 09:34:34,439 root DEBUG utilities.py 294 108] [bootburn]: [setTargetConfigt23xInfoRomInfo(721)] : None
[2025-09-16 09:34:34,439 root DEBUG utilities.py 294 108] [bootburn]: [setTargetConfigt23xInfoRomInfo(728)] : ******  s_InforomSkuVersion   300
[2025-09-16 09:34:34,439 root DEBUG utilities.py 294 108] [bootburn]: [setTargetConfigt23xInfoRomInfo(729)] : ******  s_InforomProdInfo   940-63710-0010
[2025-09-16 09:34:34,439 root DEBUG utilities.py 294 108] [bootburn]: [findTargetBaseBoardName(767)] : baseBoardName found :: p3710-10-s05
[2025-09-16 09:34:34,439 root DEBUG utilities.py 294 108] [bootburn]: [findBaseBoardName(3907)] : Detected baseboard with default ChipSku  :: p3710-10-s05
[2025-09-16 09:34:34,439 root DEBUG utilities.py 294 108] [bootburn]: [updateFindBoardData(337)] : Connected Board Name details ::  baseBoard name - p3710-10-s05
[2025-09-16 09:34:34,439 root DEBUG utilities.py 294 108] [bootburn]: [GetTegrasAssocWithAurix(507)] : Setting Tegra-A on hold...
[2025-09-16 09:34:34,439 root DEBUG utilities.py 294 108] [bootburn]: [GetTegrasAssocWithAurix(509)] : Done
[2025-09-16 09:34:34,439 root DEBUG utilities.py 294 108] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2025-09-16 09:34:34,439 root DEBUG utilities.py 294 108] [bootburn]: [GetTegrasAssocWithAurix(534)] : Setting Tegra-A in recovery...
[2025-09-16 09:34:34,439 root DEBUG utilities.py 294 108] [bootburn]: [GetTegrasAssocWithAurix(538)] : Done
[2025-09-16 09:34:34,440 root DEBUG utilities.py 294 108] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2025-09-16 09:34:34,440 root DEBUG utilities.py 294 108] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2025-09-16 09:34:34,440 root DEBUG utilities.py 294 108] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2025-09-16 09:34:34,440 root DEBUG utilities.py 294 108] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2025-09-16 09:34:34,440 root DEBUG utilities.py 294 108] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2025-09-16 09:34:34,440 root DEBUG utilities.py 294 108] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2025-09-16 09:34:34,440 root DEBUG utilities.py 294 108] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2025-09-16 09:34:34,440 root DEBUG utilities.py 294 108] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2025-09-16 09:34:34,440 root DEBUG utilities.py 294 108] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2025-09-16 09:34:34,440 root DEBUG utilities.py 294 108] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2025-09-16 09:34:34,440 root DEBUG utilities.py 294 108] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2025-09-16 09:34:34,440 root DEBUG utilities.py 294 108] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2025-09-16 09:34:34,440 root DEBUG utilities.py 294 108] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2025-09-16 09:34:34,440 root DEBUG utilities.py 294 108] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2025-09-16 09:34:34,440 root DEBUG utilities.py 294 108] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2025-09-16 09:34:34,440 root DEBUG utilities.py 294 108] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2025-09-16 09:34:34,440 root DEBUG utilities.py 294 108] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2025-09-16 09:34:34,440 root DEBUG utilities.py 294 108] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2025-09-16 09:34:34,440 root DEBUG utilities.py 294 108] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2025-09-16 09:34:34,440 root DEBUG utilities.py 294 108] command line used was:
[2025-09-16 09:34:34,440 root DEBUG utilities.py 294 108] ['/drive/drive-foundation/tools/flashtools/bootburn/bootburn.py', '--find_board_name', '-x', '/dev/ttyACM1']
[2025-09-16 09:34:34,441 root DEBUG utilities.py 294 108] 
[2025-09-16 09:34:34,441 root DEBUG utilities.py 294 108] 
[2025-09-16 09:34:34,441 root DEBUG utilities.py 294 108] Could not put Tegra-A in recovery
[2025-09-16 09:34:34,441 root DEBUG utilities.py 294 108] 
[2025-09-16 09:34:34,441 root DEBUG utilities.py 294 108] [bootburn]: [__exit__(82)] : Exception in critical section :<class 'OSError'>
[2025-09-16 09:34:34,441 root DEBUG utilities.py 294 108] 
[2025-09-16 09:34:34,441 root DEBUG utilities.py 294 108] Exception caught in bootburn 
[2025-09-16 09:34:34,441 root DEBUG utilities.py 294 108] Traceback (most recent call last):
[2025-09-16 09:34:34,441 root DEBUG utilities.py 294 108] File "/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn.py", line 271, in bootburn
[2025-09-16 09:34:34,441 root DEBUG utilities.py 294 108] bootburnLib.CheckRecoveryTargets()
[2025-09-16 09:34:34,441 root DEBUG utilities.py 294 108] File "/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn_lib.py", line 3920, in CheckRecoveryTargets
[2025-09-16 09:34:34,441 root DEBUG utilities.py 294 108] self.aurix.GetTegrasAssocWithAurix(self.targetConfig.s_AurixPort)
[2025-09-16 09:34:34,441 root DEBUG utilities.py 294 108] File "/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn_aurix.py", line 551, in GetTegrasAssocWithAurix
[2025-09-16 09:34:34,441 root DEBUG utilities.py 294 108] AbnormalTermination("Could not put {} in recovery".format(name), nverror.NvError_ResourceError)
[2025-09-16 09:34:34,441 root DEBUG utilities.py 294 108] File "/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/flashtools_nverror.py", line 251, in AbnormalTermination
[2025-09-16 09:34:34,441 root DEBUG utilities.py 294 108] raise OSError(errorCode)
[2025-09-16 09:34:34,441 root DEBUG utilities.py 294 108] OSError: 15
[2025-09-16 09:34:34,441 root INFO runner.py 37 108] Failed to bind partitions!
[2025-09-16 09:34:34,441 root DEBUG runner.py 39 108] Error on line 972
[2025-09-16 09:34:34,441 root DEBUG runner.py 40 108] Exception info: Exception Type <class 'module.errors.FailedToBindPartitionsError'>, Traceback <traceback object at 0x7efd00d156c0>
[2025-09-16 09:34:34,442 root INFO runner.py 42 108] driveinstaller cannot continue! Check the log file for details: /drive/driveinstaller/driveinstaller.log
[2025-09-16 09:34:34,442 root DEBUG runner.py 62 108] Cleaning up...
[2025-09-16 09:34:34,442 root DEBUG utilities.py 137 108] Deleting temporary directories...
[2025-09-16 09:34:34,442 root DEBUG utilities.py 139 108] Deleting /tmp/pdkinstall-tmp-4nk3z_dk-bind
[2025-09-16 09:34:34,442 root DEBUG runner.py 64 108] Closing the log file.
root@6.0.10.0-0009-build-linux-sdk:/drive#

Before flashing when applying manual recovery and reset like this :

NvShell>
NvShell>tegrarecovery x1 on 
Info: Executing cmd: tegrarecovery, argc: 2, args: x1 on 
Command Executed
NvShell>tegrareset x1
Info: Executing cmd: tegrareset, argc: 1, args: x1 
NvShell>INFO: MCU_PLTFPWRMGR: Reseting Tegra
INFO: MCU_PLTFPWRMGR: VRS11 PG Monitoring disable.
INFO: NVMCU_ORINPWRCTRL: Wait for Safe Shutdown notification...(20 seconds max)
I:RptrID - 0x810B PsCd - 0x22 - VMON Nirq Disabled
I:RptrID - 0x810B PsCd - 0x21 - VMON Nirq Enabled
INFO: BtChn_Cfg: Tegra x1 Boot Chain is : A 
INFO: BtChn_Cfg: Btchn Pin ORIN_BOOTCHAIN0 set to 0
INFO: BtChn_Cfg: Btchn Pin ORIN_BOOTCHAIN1 set to 0
I:RptrID - 0x810F PsCd - 0x6 - BootchainCfg Dio set success
INFO: MCU_PLTFPWRMGR: Tegra reset trigger is complete !
Command Executed
MCU_FOH: MCU FOH : Initiate SOC Error Pin Monitoring & SPI communication
MCU_FOH: MCU FOH : Start Monitoring Initiated
INFO: MCU_ERRHANDLER: Published Power State: Power-up complete
MCU_FOH: Spi Transmit Started
MCU_FOH: SOC error pin is asserted
ERROR: MCU_ERRHANDLER: SOC error pin is asserted
INFO: SftyMon_IoHwAbs: PG_VRS11 monitoring started...
INFO: MCU_SWC_FanControl: max_rpm fan2 : 0
INFO: MCU_SWC_FanControl: maxrpm of fan2 has more than 50 percent deviation against rated maxrpm

Then closing the port and rechecking lsusb output :

pomo@pomodriver:~$ lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 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 007: ID 145f:02aa Trust Trust Full HD Webcam
Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
Bus 003 Device 009: ID 046d:c34a Logitech, Inc. LogiG TKL MKeyboard
Bus 003 Device 008: ID 0000:3825   USB OPTICAL MOUSE
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pomo@pomodriver:~$

I did put the board back to normal mode as well before executing the flash command. Still the top logs appear while attempting to flash. However I can open ACM0 and ssh and access the fs.

4

Dear @ashwin.nanda ,
I see after running commands in aurix console, we don’t see additional NVIDIA device in lsusb output.
Could you double check if there is any loose connection between host and Target. Note that there are two wire connection between host and Target. Please check the quick start guide for target and host connection. You can share the host and Target connection picture for confirmation.
Also, check changing connection wires and host USB ports

Note that when you use flash commands from docker, all serial connections(minicom) connections should be closed and the target has to be set in normal mode. You can restart host to make sure serial connections are closed.

Please check above suggestion and provide feedback.

6

Dear @SivaRamaKrishnaNV please check the following steps I performed again with the Orin :

  1. Connections :
    I am using the same cables that was shipped with kit, for both type-c and micro-usb, please confirm if these connections appear correct.

image
image1080×1920 183 KB

  1. I put tegra in recovery mode (after basic poweron), through ACM1 port like before.

  2. NvShell>
NvShell>tegrarecovery x1 on 
Info: Executing cmd: tegrarecovery, argc: 2, args: x1 on 
Command Executed
NvShell>tegrareset x1
Info: Executing cmd: tegrareset, argc: 1, args: x1 
NvShell>INFO: MCU_PLTFPWRMGR: Reseting Tegra
INFO: MCU_PLTFPWRMGR: VRS11 PG Monitoring disable.
INFO: NVMCU_ORINPWRCTRL: Wait for Safe Shutdown notification...(20 seconds max)
I:RptrID - 0x810B PsCd - 0x22 - VMON Nirq Disabled
I:RptrID - 0x810B PsCd - 0x21 - VMON Nirq Enabled
INFO: BtChn_Cfg: Tegra x1 Boot Chain is : A 
INFO: BtChn_Cfg: Btchn Pin ORIN_BOOTCHAIN0 set to 0
INFO: BtChn_Cfg: Btchn Pin ORIN_BOOTCHAIN1 set to 0
I:RptrID - 0x810F PsCd - 0x6 - BootchainCfg Dio set success
INFO: MCU_PLTFPWRMGR: Tegra reset trigger is complete !
Command Executed
MCU_FOH: MCU FOH : Initiate SOC Error Pin Monitoring & SPI communication
MCU_FOH: MCU FOH : Start Monitoring Initiated
INFO: MCU_ERRHANDLER: Published Power State: Power-up complete
MCU_FOH: Spi Transmit Started
MCU_FOH: SOC error pin is asserted
ERROR: MCU_ERRHANDLER: SOC error pin is asserted
INFO: SftyMon_IoHwAbs: PG_VRS11 monitoring started...
INFO: MCU_SWC_FanControl: max_rpm fan2 : 0
INFO: MCU_SWC_FanControl: maxrpm of fan2 has more than 50 percent deviation against rated maxrpm

NvShell>

  3. this time, restarted my host to ensure the ports are closed.

  4. lsusb output after this still doesnt show the extra device you are pointing to.

  5. pomo@pomodriver:~$ lsusb
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 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 007: ID 145f:02aa Trust Trust Full HD Webcam
Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
Bus 003 Device 009: ID 046d:c34a Logitech, Inc. LogiG TKL MKeyboard
Bus 003 Device 008: ID 0000:3825   USB OPTICAL MOUSE
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pomo@pomodriver:~$

  6. nevertheless, I put tegra back in normal mode

  7. NvShell>
NvShell>tegrarecovery x1 off
Info: Executing cmd: tegrarecovery, argc: 2, args: x1 off 
Command Executed
NvShell>tegrareset x1
Info: Executing cmd: tegrareset, argc: 1, args: x1 
NvShell>INFO: MCU_PLTFPWRMGR: Reseting Tegra
INFO: MCU_PLTFPWRMGR: VRS11 PG Monitoring disable.
INFO: NVMCU_ORINPWRCTRL: Wait for Safe Shutdown notification...(20 seconds max)
I:RptrID - 0x810B PsCd - 0x22 - VMON Nirq Disabled
I:RptrID - 0x810B PsCd - 0x21 - VMON Nirq Enabled
INFO: BtChn_Cfg: Tegra x1 Boot Chain is : A 
INFO: BtChn_Cfg: Btchn Pin ORIN_BOOTCHAIN0 set to 0
INFO: BtChn_Cfg: Btchn Pin ORIN_BOOTCHAIN1 set to 0
I:RptrID - 0x810F PsCd - 0x6 - BootchainCfg Dio set success
INFO: MCU_PLTFPWRMGR: Tegra reset trigger is complete !
Command Executed
MCU_FOH: MCU FOH : Initiate SOC Error Pin Monitoring & SPI communication
MCU_FOH: MCU FOH : Start Monitoring Initiated
INFO: MCU_ERRHANDLER: Published Power State: Power-up complete
MCU_FOH: Spi Transmit Started
MCU_FOH: SOC error pin is asserted
ERROR: MCU_ERRHANDLER: SOC error pin is asserted
MCU_FOH: ErrReport: ErrorCode-0x28ba ReporterId-0xe031 Error_Attribute-0x0 Timestamp-0x5e6e5c4
MCU_FOH: Periodic Status [0] 0xab [1] 0xcd [250] 0x12 [251] 0x34
INFO: SftyMon_IoHwAbs: PG_VRS11 monitoring started...
INFO: MCU_SWC_FanControl: max_rpm fan2 : 0
INFO: MCU_SWC_FanControl: maxrpm of fan2 has more than 50 percent deviation against rated maxrpm

NvShell>INFO : MCU_ISTMGR: IST Manager initialized to send/receive commands 
I:RptrID - 0x810A PsCd - 0x11 - ISTManager:IST result fetched.
INFO : IST_TESTAPP: IST Result Ready to fetch

  8. closed the port again and did a restart (host)

  9. tried flashing again on the same container mounted for flashing.

  10. pomo@pomodriver:~$ sudo docker start -ia ee910662b09f 
root@6.0.10.0-0009-build-linux-sdk:/drive# ./flash.py --clean /dev/ttyACM1 p3710 
2025-09-16 11:22:34 INFO : Setting flash clean to initialize persistent partitions
2025-09-16 11:22:34 INFO : Initiating pre-flash check
2025-09-16 11:22:34 INFO : Checking Serial Port Connection
2025-09-16 11:22:34 INFO : Serial Port found /dev/ttyACM1
2025-09-16 11:22:34 INFO : Running basic open/close tests on Serial Port Connection
2025-09-16 11:22:34 INFO : Serial Port is open
2025-09-16 11:22:34 INFO : Flushing input and output buffer, discard all content
2025-09-16 11:22:34 INFO : Serial Port is closed
2025-09-16 11:22:34 INFO : Checking available targets
2025-09-16 11:22:34 INFO : Checking Orin board connection
2025-09-16 11:22:34 INFO : Orin board with Device ID -- 0955:7045 found.
2025-09-16 11:22:34 INFO : Orin board device path is /dev/bus/usb/003/010
2025-09-16 11:22:34 INFO : Pre-flash check complete
2025-09-16 11:22:34 INFO : Flashing DRIVE OS Docker
2025-09-16 11:22:54 INFO : driveinstaller v2.0
2025-09-16 11:22:54 INFO : 
2025-09-16 11:22:54 INFO : SDK/PDK Installer and Flasher
2025-09-16 11:22:54 INFO : Run `./driveinstaller --help` for usage information.
2025-09-16 11:22:54 INFO : 
2025-09-16 11:22:54 INFO : Initializing board and OS configuration to Autonomous Vehicle p3710 Linux Tegra A
2025-09-16 11:22:54 INFO : Manifest version 2.0
2025-09-16 11:22:54 INFO : 
2025-09-16 11:22:54 INFO : BOARD SKU : 940-63710-0010-300
2025-09-16 11:22:54 INFO : Found matching board id p3710-10-s05 in 940-63710-0010-300 sku
2025-09-16 11:22:54 INFO : Applying additional Bind opts []
2025-09-16 11:22:54 INFO : Binding of partitions failed ! Check log for more details.
2025-09-16 11:22:54 INFO : Failed to bind partitions!
2025-09-16 11:22:54 INFO : driveinstaller cannot continue! Check the log file for details: /drive/driveinstaller/driveinstaller.log
2025-09-16 11:22:54 ERROR : Flashing failed, please contact provider with logs /drive_flashing/log_zh6j9x0lgyqt54p281kswfevib3nu7ao.txt and /drive/driveinstaller/driveinstaller.log.
root@6.0.10.0-0009-build-linux-sdk:/drive#

  11. Im still encountering the same logs :

  12. subprocess.CalledProcessError: Command 'python3 /drive/drive-foundation/tools/flashtools/bootburn/bootburn.py --find_board_name -x /dev/ttyACM1' returned non-zero exit status 15.
[2025-09-16 11:22:53,995 root ERROR pdk_bind.py 217 21] Binding of partitions failed ! Check log for more details.
[2025-09-16 11:22:53,995 root DEBUG utilities.py 294 21] ****** Starting bootburn/bootburn.py ********
[2025-09-16 11:22:53,995 root DEBUG utilities.py 294 21] ********* Starting t23x bootburn py ********
[2025-09-16 11:22:53,995 root DEBUG utilities.py 294 21] Bootburn Starting with arguments ['/drive/drive-foundation/tools/flashtools/bootburn/bootburn.py', '--find_board_name', '-x', '/dev/ttyACM1']
[2025-09-16 11:22:53,995 root DEBUG utilities.py 294 21] logfile :: /drive/drive-foundation/tools/flashtools/bootburn_t23x_py/bootburn.txt
[2025-09-16 11:22:53,995 root DEBUG utilities.py 294 21] cwd in setBoardConfigPath :: /drive/drive-foundation/tools/flashtools/bootburn_t23x_py
[2025-09-16 11:22:53,995 root DEBUG utilities.py 294 21]  trying hardware folder:
[2025-09-16 11:22:53,996 root DEBUG utilities.py 294 21] /drive/drive-foundation/platform-config/hardware/nvidia/platform/t23x/automotive/flashing/board_configs
[2025-09-16 11:22:53,996 root DEBUG utilities.py 294 21] 
[2025-09-16 11:22:53,996 root DEBUG utilities.py 294 21] Default Schema:/drive/drive-foundation/tools/flashtools/bootburn_t23x_py/nv-customer-data-schema.json
[2025-09-16 11:22:53,996 root DEBUG utilities.py 294 21] 
[2025-09-16 11:22:53,996 root DEBUG utilities.py 294 21] [bootburn]: [GetInfoRom(620)] : Read skuinfo from InfoRom...
[2025-09-16 11:22:53,996 root DEBUG utilities.py 294 21] [bootburn]: Execute command on Aurix serial port
[2025-09-16 11:22:53,996 root DEBUG utilities.py 294 21] [bootburn]: [CheckFirmwareisAFW(600)] : AFW firmware found
[2025-09-16 11:22:53,996 root DEBUG utilities.py 294 21] [bootburn]: [setTargetConfigt23xInfoRomInfo(720)] : 940-63710-0010-300
[2025-09-16 11:22:53,996 root DEBUG utilities.py 294 21] [bootburn]: [setTargetConfigt23xInfoRomInfo(721)] : None
[2025-09-16 11:22:53,996 root DEBUG utilities.py 294 21] [bootburn]: [setTargetConfigt23xInfoRomInfo(728)] : ******  s_InforomSkuVersion   300
[2025-09-16 11:22:53,996 root DEBUG utilities.py 294 21] [bootburn]: [setTargetConfigt23xInfoRomInfo(729)] : ******  s_InforomProdInfo   940-63710-0010
[2025-09-16 11:22:53,996 root DEBUG utilities.py 294 21] [bootburn]: [findTargetBaseBoardName(767)] : baseBoardName found :: p3710-10-s05
[2025-09-16 11:22:53,996 root DEBUG utilities.py 294 21] [bootburn]: [findBaseBoardName(3907)] : Detected baseboard with default ChipSku  :: p3710-10-s05
[2025-09-16 11:22:53,996 root DEBUG utilities.py 294 21] [bootburn]: [updateFindBoardData(337)] : Connected Board Name details ::  baseBoard name - p3710-10-s05
[2025-09-16 11:22:53,996 root DEBUG utilities.py 294 21] [bootburn]: [GetTegrasAssocWithAurix(507)] : Setting Tegra-A on hold...
[2025-09-16 11:22:53,996 root DEBUG utilities.py 294 21] [bootburn]: [GetTegrasAssocWithAurix(509)] : Done
[2025-09-16 11:22:53,996 root DEBUG utilities.py 294 21] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2025-09-16 11:22:53,996 root DEBUG utilities.py 294 21] [bootburn]: [GetTegrasAssocWithAurix(534)] : Setting Tegra-A in recovery...
[2025-09-16 11:22:53,996 root DEBUG utilities.py 294 21] [bootburn]: [GetTegrasAssocWithAurix(538)] : Done
[2025-09-16 11:22:53,996 root DEBUG utilities.py 294 21] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2025-09-16 11:22:53,996 root DEBUG utilities.py 294 21] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2025-09-16 11:22:53,996 root DEBUG utilities.py 294 21] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check...
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] command line used was:
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] ['/drive/drive-foundation/tools/flashtools/bootburn/bootburn.py', '--find_board_name', '-x', '/dev/ttyACM1']
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] 
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] 
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] Could not put Tegra-A in recovery
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] 
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] [bootburn]: [__exit__(82)] : Exception in critical section :<class 'OSError'>
[2025-09-16 11:22:53,997 root DEBUG utilities.py 294 21] 
[2025-09-16 11:22:53,998 root DEBUG utilities.py 294 21] Exception caught in bootburn 
[2025-09-16 11:22:53,998 root DEBUG utilities.py 294 21] Traceback (most recent call last):
[2025-09-16 11:22:53,998 root DEBUG utilities.py 294 21] File "/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn.py", line 271, in bootburn
[2025-09-16 11:22:53,998 root DEBUG utilities.py 294 21] bootburnLib.CheckRecoveryTargets()
[2025-09-16 11:22:53,998 root DEBUG utilities.py 294 21] File "/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn_lib.py", line 3920, in CheckRecoveryTargets
[2025-09-16 11:22:53,998 root DEBUG utilities.py 294 21] self.aurix.GetTegrasAssocWithAurix(self.targetConfig.s_AurixPort)
[2025-09-16 11:22:53,998 root DEBUG utilities.py 294 21] File "/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn_aurix.py", line 551, in GetTegrasAssocWithAurix
[2025-09-16 11:22:53,998 root DEBUG utilities.py 294 21] AbnormalTermination("Could not put {} in recovery".format(name), nverror.NvError_ResourceError)
[2025-09-16 11:22:53,998 root DEBUG utilities.py 294 21] File "/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/flashtools_nverror.py", line 251, in AbnormalTermination
[2025-09-16 11:22:53,998 root DEBUG utilities.py 294 21] raise OSError(errorCode)
[2025-09-16 11:22:53,998 root DEBUG utilities.py 294 21] OSError: 15
[2025-09-16 11:22:53,998 root INFO runner.py 37 21] Failed to bind partitions!
[2025-09-16 11:22:53,998 root DEBUG runner.py 39 21] Error on line 972
[2025-09-16 11:22:53,998 root DEBUG runner.py 40 21] Exception info: Exception Type <class 'module.errors.FailedToBindPartitionsError'>, Traceback <traceback object at 0x7ff65ff7d440>
[2025-09-16 11:22:53,998 root INFO runner.py 42 21] driveinstaller cannot continue! Check the log file for details: /drive/driveinstaller/driveinstaller.log
[2025-09-16 11:22:53,998 root DEBUG runner.py 62 21] Cleaning up...
[2025-09-16 11:22:53,998 root DEBUG utilities.py 137 21] Deleting temporary directories...
[2025-09-16 11:22:53,998 root DEBUG utilities.py 139 21] Deleting /tmp/pdkinstall-tmp-scqp_1mf-bind
[2025-09-16 11:22:53,999 root DEBUG runner.py 64 21] Closing the log file.
root@6.0.10.0-0009-build-linux-sdk:/drive#
7

Also there a frequency of these messages on ACM0 which occur every few seconds, , please note that this is not the case with Orin2 , which is facing only display issues after flashing.

��
benchdev@tegra-ubuntu:~$ ��ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001

Additional steps I did via ssh :

benchdev@tegra-ubuntu:~$ sudo dmesg | grep -i "error\|fail\|corrupt"
[    0.428870] ivc_ext: module verification failed: signature and/or required key missing - tainting kernel
[    1.443511] nvethernet 2310000.ethernet: failed to read MDIO address
[    1.443515] nvethernet 2310000.ethernet: Failed to read nvida,pause_frames, so setting to default support as disable
[    1.443576] nvethernet 2310000.ethernet: failed to get phy reset gpio error: -2
[    1.448919] nvethernet 6810000.ethernet: Failed to read nvida,pause_frames, so setting to default support as disable
[    1.450241] nvethernet 6810000.ethernet: failed to get phy reset gpio error: -2
[    1.457312] nvethernet 6910000.ethernet: failed to read MDIO address
[    1.457348] nvethernet 6910000.ethernet: failed to get phy reset gpio error: -2
[    1.465216] nvethernet 6a10000.ethernet: failed to read MDIO address
[    1.465220] nvethernet 6a10000.ethernet: Failed to read nvida,pause_frames, so setting to default support as disable
[    1.466663] nvethernet 6a10000.ethernet: failed to get phy reset gpio error: -2
[    1.474525] nvethernet 6b10000.ethernet: failed to read MDIO address
[    1.474528] nvethernet 6b10000.ethernet: Failed to read nvida,pause_frames, so setting to default support as disable
[    1.475593] nvethernet 6b10000.ethernet: failed to get phy reset gpio error: -2
[    3.002924] systemd-journald[677]: File /var/log/journal/1a9efbfb0970483b862273b99e470eff/system.journal corrupted or uncleanly shut down, renaming and replacing.
[    3.068577] dce: dce_admin_setup_clients_ipc:560  Get queue info failed for [2]
[    3.170429] cam_fsync c6a0000.tsc_sig_gen: Failed to find frame sync group, creating default group
[   13.208852] systemd-journald[677]: File /var/log/journal/1a9efbfb0970483b862273b99e470eff/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
[   23.082465] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0x65:
[   23.085550] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0x65:
[   23.088598] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0x65:
[   23.091648] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0x65:
[   23.094698] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0x65:
[   23.097747] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0x65:
[   23.100796] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0x65:
[   23.103838] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0x65:
[   23.106885] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0x65:
[   23.109926] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0x65:
[   23.112979] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0x65:
[   23.116043] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0x65:
[   23.119097] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0x65:
[   23.122146] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0x65:
[   23.125197] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0x65:
[   23.128239] NVRM rpcRmApiControl_dce: NVRM_RPC_DCE: Failed RM ctrl call cmd:0x731341 result 0x65:
benchdev@tegra-ubuntu:~$ echo $DISPLAY

benchdev@tegra-ubuntu:~$ systemctl status display-manager
● gdm.service - GNOME Display Manager
     Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled)
     Active: active (running) since Mon 2025-09-15 14:49:02 UTC; 18min ago
    Process: 1724 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS)
    Process: 1735 ExecStartPre=/usr/lib/gdm3/gdm-wait-for-drm (code=exited, status=0/SUCCESS)
   Main PID: 1738 (gdm3)
      Tasks: 3 (limit: 34419)
     Memory: 4.2M
     CGroup: /system.slice/gdm.service
             └─1738 /usr/sbin/gdm3

Sep 15 14:49:02 tegra-ubuntu systemd[1]: Starting GNOME Display Manager...
Sep 15 14:49:02 tegra-ubuntu systemd[1]: Started GNOME Display Manager.
Sep 15 14:49:02 tegra-ubuntu gdm-launch-environment][1743]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
Sep 15 14:49:03 tegra-ubuntu gdm-launch-environment][1743]: pam_unix(gdm-launch-environment:session): session closed for user gdm
Sep 15 14:49:03 tegra-ubuntu gdm3[1738]: GdmDisplay: Session never registered, failing
Sep 15 14:49:03 tegra-ubuntu gdm-launch-environment][1860]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
benchdev@tegra-ubuntu:~$
8

Dear @ashwin.nanda ,
The connections looks good. As you have another working target, can you please replace your target with other target and check setting the target in recovery mode. This confirms if there is any issue with host port or used connection wires.
If the other target works, I suspect it could be a HW issue.

From my understanding, before the power failure, you could flash target without any issue. Please confirm if you could flash DRIVE OS 6.0.10 earlier with same setup.

9

dear @SivaRamaKrishnaNV

I swapped the targets, used my host with same cables and I can put other target into recovery mode and confirm from lsusb output here :

pomo@pomodriver:~$ lsusb 
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 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 145f:02aa Trust Trust Full HD Webcam
Bus 003 Device 007: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
Bus 003 Device 005: ID 046d:c34a Logitech, Inc. LogiG TKL MKeyboard
Bus 003 Device 004: ID 0000:3825   USB OPTICAL MOUSE
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pomo@pomodriver:~$ lsusb 
Bus 002 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 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 145f:02aa Trust Trust Full HD Webcam
Bus 003 Device 007: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
Bus 003 Device 005: ID 046d:c34a Logitech, Inc. LogiG TKL MKeyboard
Bus 003 Device 004: ID 0000:3825   USB OPTICAL MOUSE
Bus 003 Device 008: ID 0955:7023 NVIDIA Corp. APX
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pomo@pomodriver:~$

yes, I had flashed both targets from same host and same cables 2 months ago. After extension cord blew up its fuse which powered both orins, The Orin on my desk cannot be put onto recovery mode.

10

Any Solution to this ? How can I get it sorted? becuause as per my understanding the chip and fs is still accessible to me.

11

dear @SivaRamaKrishnaNV I need an update on this, as I Have two Orins on my desk without any display here, if possible I would request you to reach out the core team to find if any kernel modifications can fix this.

12

Dear @ashwin.nanda ,
Generally we notice similar issue like target aurix/tegra console accessible but not entering recovery mode when issue with host and target connection(Sdkmanager Drive Orin Flash OS 6.0.6 fails - #10 by servanti). Do you have access to NVONLINE? I am checking internally on further guidance.

Also, could you check Running samples on remote server - #13 by SivaRamaKrishnaNV for remotely testing GUI samples using VNC.

13

they seem to have had some connection issues, which is not our case.

No.

image
image1942×1216 608 KB

yes seems like I can connect to it via vnc and access the gui applications here though.

14

dear @SivaRamaKrishnaNV even so I can see the gui apps display on vnc like this, I need the display monitor working to vnc/teamviewer into gnome de. And majorly, we need to understand why it wont go recovery mode.

Summarizing the issue here → power-failure on both orins → one can be flashed / other cannot be put into recovery mode. Both vnc displays are working with blank screen with GUI applications render.

While we are waiting on some fixes from your side, from here I can think of using the sdk manger to let the orin flash DRIVE OS 6.0.6 first as a debug step and then use docker again to flash DRIVE OS 6.0.10, would you recommend performing this step?

regards, Ashwin

15

As target is not going to recovery mode, I doubt if flashing using sdkmanager works.
Could you provide dmesg logs of host
when trying to put target in recovery mode and Target boot logs.

16

Dear @SivaRamaKrishnaNV , thank you replying;

I removed all cables from host, switched the target completely off,

  1. Connected the cables to my host

  2. turned the switch on and captured full boot log here :

    1. tegra_boot_log.log (75.8 KB)

  3. started putting tegra on recovery mode:

    1. ACM1 log: 
      1. Welcome to minicom 2.7.1

OPTIONS: I18n 
Compiled on Dec 23 2019, 02:06:26.
Port /dev/ttyACM1, 11:04:16

Press CTRL-A Z for help on special keys

.
INFO : IST_TESTAPP: IST Result Ready to fetch
INFO: MCU_SWC_FanControl: max_rpm fan2 : 0
INFO: MCU_SWC_FanControl: maxrpm of fan2 has more than 50 percent deviation against rated maxrpm

NvShell>
NvShell>tegrarecovery x1 on 
Info: Executing cmd: tegrarecovery, argc: 2, args: x1 on 
Command Executed
NvShell>tegrareset x1 
Info: Executing cmd: tegrareset, argc: 1, args: x1 
NvShell>INFO: MCU_PLTFPWRMGR: Reseting Tegra
INFO: MCU_PLTFPWRMGR: VRS11 PG Monitoring disable.
INFO: NVMCU_ORINPWRCTRL: Wait for Safe Shutdown notification...(20 seconds max)
I:RptrID - 0x810B PsCd - 0x22 - VMON Nirq Disabled
I:RptrID - 0x810B PsCd - 0x21 - VMON Nirq Enabled
INFO: BtChn_Cfg: Tegra x1 Boot Chain is : A 
INFO: BtChn_Cfg: Btchn Pin ORIN_BOOTCHAIN0 set to 0
INFO: BtChn_Cfg: Btchn Pin ORIN_BOOTCHAIN1 set to 0
I:RptrID - 0x810F PsCd - 0x6 - BootchainCfg Dio set success
INFO: MCU_PLTFPWRMGR: Tegra reset trigger is complete !
Command Executed
MCU_FOH: MCU FOH : Initiate SOC Error Pin Monitoring & SPI communication
MCU_FOH: MCU FOH : Start Monitoring Initiated
INFO: MCU_ERRHANDLER: Published Power State: Power-up complete
MCU_FOH: Spi Transmit Started
MCU_FOH: SPI : E2E_P05Check Status : 7 : 0
ERROR: MCU_ERRHANDLER: McuFoh : ReporterID - 0x810E ErrorCode - 0x3 
 MCU_FOH: SOC error pin is asserted
ERROR: MCU_ERRHANDLER: SOC error pin is asserted
MCU_FOH: SPI : E2E_P05Check Status : 7 : 0
MCU_FOH: SPI : E2E_P05Check Status : 7 : 0
INFO: SftyMon_IoHwAbs: PG_VRS11 monitoring started...
INFO: MCU_SWC_FanControl: max_rpm fan2 : 0
INFO: MCU_SWC_FanControl: maxrpm of fan2 has more than 50 percent deviation against rated maxrpm

NvShell>tegrarecovery x1 off 
Info: Executing cmd: tegrarecovery, argc: 2, args: x1 off 
Command Executed
NvShell>tegrareset x1 on 
Info: Executing cmd: tegrareset, argc: 2, args: x1 on 
Error: Invalid argument
Invalid Command
NvShell>tegrareset x1 
Info: Executing cmd: tegrareset, argc: 1, args: x1 
NvShell>INFO: MCU_PLTFPWRMGR: Reseting Tegra
INFO: MCU_PLTFPWRMGR: VRS11 PG Monitoring disable.
INFO: NVMCU_ORINPWRCTRL: Wait for Safe Shutdown notification...(20 seconds max)
I:RptrID - 0x810B PsCd - 0x22 - VMON Nirq Disabled
I:RptrID - 0x810B PsCd - 0x21 - VMON Nirq Enabled
INFO: BtChn_Cfg: Tegra x1 Boot Chain is : A 
INFO: BtChn_Cfg: Btchn Pin ORIN_BOOTCHAIN0 set to 0
INFO: BtChn_Cfg: Btchn Pin ORIN_BOOTCHAIN1 set to 0
I:RptrID - 0x810F PsCd - 0x6 - BootchainCfg Dio set success
INFO: MCU_PLTFPWRMGR: Tegra reset trigger is complete !
Command Executed
MCU_FOH: MCU FOH : Initiate SOC Error Pin Monitoring & SPI communication
MCU_FOH: MCU FOH : Start Monitoring Initiated
INFO: MCU_ERRHANDLER: Published Power State: Power-up complete
MCU_FOH: SOC error pin is asserted
ERROR: MCU_ERRHANDLER: SOC error pin is asserted
MCU_FOH: Spi Transmit Started
MCU_FOH: ErrReport: ErrorCode-0x28ba ReporterId-0xe031 Error_Attribute-0x0 Timestamp-0x5def812
MCU_FOH: Periodic Status [0] 0xab [1] 0xcd [250] 0x12 [251] 0x34
INFO: SftyMon_IoHwAbs: PG_VRS11 monitoring started...
INFO : MCU_ISTMGR: IST Manager initialized to send/receive commands 
I:RptrID - 0x810A PsCd - 0x11 - ISTManager:IST result fetched.
INFO : IST_TESTAPP: IST Result Ready to fetch
INFO: MCU_SWC_FanControl: max_rpm fan2 : 0
INFO: MCU_SWC_FanControl: maxrpm of fan2 has more than 50 percent deviation against rated maxrpm

NvShell>
CTRL-A Z for help | 115200 8N1 | NOR | Minicom 2.7.1 | VT102 | Offline | ttyACM1

      2. during_recovery_ACM0.log (76.0 KB)

      3. Host Kernel watch log :

        1. pomo@pomodriver:~$ sudo dmesg -C 
pomo@pomodriver:~$ dmesg -w
[75256.999728] usb 3-5: new full-speed USB device number 25 using xhci_hcd
[75257.149985] usb 3-5: New USB device found, idVendor=0955, idProduct=7045, bcdDevice= 0.01
[75257.149998] usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[75257.150003] usb 3-5: Product: Tegra On-Platform Operator
[75257.150007] usb 3-5: Manufacturer: NVIDIA
[75257.150010] usb 3-5: SerialNumber: TOPOEA1D8268
[75257.156036] hid-generic 0003:0955:7045.000C: hiddev1,hidraw4: USB HID v1.10 Device [NVIDIA Tegra On-Platform Operator] on usb-0000:00:14.0-5/input0
[75257.156487] cdc_acm 3-5:1.1: ttyACM0: USB ACM device
[75257.156857] cdc_acm 3-5:1.3: ttyACM1: USB ACM device
[75257.157213] cdc_acm 3-5:1.5: ttyACM2: USB ACM device
[75257.157522] cdc_acm 3-5:1.7: ttyACM3: USB ACM device
^C
pomo@pomodriver:~$ sudo dmesg -C 
pomo@pomodriver:~$ dmesg -w
[75576.695597] usb 3-13: USB disconnect, device number 8
[75577.024410] usb 3-13: new low-speed USB device number 26 using xhci_hcd
[75577.179641] usb 3-13: New USB device found, idVendor=0000, idProduct=3825, bcdDevice= 1.00
[75577.179653] usb 3-13: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[75577.179658] usb 3-13: Product:  USB OPTICAL MOUSE
[75577.182848] input:  USB OPTICAL MOUSE as /devices/pci0000:00/0000:00:14.0/usb3/3-13/3-13:1.0/0003:0000:3825.000D/input/input26
[75577.240535] hid-generic 0003:0000:3825.000D: input,hidraw0: USB HID v1.11 Mouse [ USB OPTICAL MOUSE] on usb-0000:00:14.0-13/input0
[75690.546038] usb 3-1: new full-speed USB device number 27 using xhci_hcd
[75690.674051] usb 3-1: device descriptor read/64, error -71
[75690.910036] usb 3-1: device descriptor read/64, error -71
[75691.146024] usb 3-1: new full-speed USB device number 28 using xhci_hcd
[75691.278042] usb 3-1: device descriptor read/64, error -71
[75691.514077] usb 3-1: device descriptor read/64, error -71
[75691.626109] usb usb3-port1: attempt power cycle
[75692.278067] usb 3-1: new full-speed USB device number 29 using xhci_hcd
[75692.278219] usb 3-1: Device not responding to setup address.
[75692.486197] usb 3-1: Device not responding to setup address.
[75692.694067] usb 3-1: device not accepting address 29, error -71
[75692.822064] usb 3-1: new full-speed USB device number 30 using xhci_hcd
[75692.822214] usb 3-1: Device not responding to setup address.
[75693.030204] usb 3-1: Device not responding to setup address.
[75693.238081] usb 3-1: device not accepting address 30, error -71
[75693.238197] usb usb3-port1: unable to enumerate USB device
17

Dear @ashwin.nanda ,
This looks like a HW issue. I will update you on the next steps.

18

dear @SivaRamaKrishnaNV can you explain how the make the board boot from eMMC partiton, instead of UFS? this response seems to target my issue here : Flashing Drive AGX Orin fails - #30 by VickNV

it is because as provided in the boot logs before Im encountering MCU to UFS handshake error,

ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
19

@SivaRamaKrishnaNV they seem to have received a replacement unit @VickNV can you please look into this?

20

dear @SivaRamaKrishnaNV @VickNV I am urging to raise a RMA for this device if possible, please let me know if I should contact my NVIDIA rep regarding this? It is causing developmental delays and misleading the time investment in fixing and opening them on our side, as requested by @SivaRamaKrishnaNV via DMs we have already opened one device which makes the warranty terminated by default. We do not want to do the same with this one.

22

After reviewing logs concluded as HW issue. Filed RMAV request for this board. Closing the issue.