DRIVE Installer failed with status 140

Autonomous Vehicles DRIVE AGX Orin DRIVE AGX Orin General
1

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

Target Operating System
[1] Linux
QNX
other

Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
[1] DRIVE AGX Orin Developer Kit (not sure its number)
other

SDK Manager Version
1.9.10816
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
[1] native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other

Hello, I am trying to set Up DRIVE OS Linux with NVIDIA GPU Cloud (NGC)(Setting Up DRIVE OS Linux with NVIDIA GPU Cloud (NGC)). And when I run this command ./flash.sh /dev/ttyACM1 p3710, I got this error:

Executing bind + flash
[===    ]

DRIVE Installer failed with status 140
DriveinstallerFlash failed, error 140!
======================================================
          
Error 140 occurred, please resolve the issue or try again.
Please contact provider with log "/drive_flashing/log_36b121b4e16987ea21f9009dec5f43e7.txt".
          
======================================================
NGNG

Here is the content of the log：

Executing bind + flash
/drive/driveinstaller /drive
driveinstaller v2.0

SDK/PDK Installer and Flasher
Run `./driveinstaller --help` for usage information.

Initializing board and OS configuration to Autonomous vehicle p3710 Linux Tegra A
Manifest version 2.0

Could not fetch board revision. Re-try either by re-connecting board or make sure all serial port processes such as minicom are closed.
Failed to bind partitions!
driveinstaller cannot continue! Check the log file for details: /drive/driveinstaller/driveinstaller.log


DRIVE Installer failed with status 140
DriveinstallerFlash failed, error 140!
======================================================
          
Error 140 occurred, please resolve the issue or try again.
Please contact provider with log "/drive_flashing/log_36b121b4e16987ea21f9009dec5f43e7.txt".
          
======================================================
NGNG

How can I solve this problem？
Thanks!

3

Dear @hongjiang.rao,
Did you set the target into recovery mode before flashing by running below commands on aurix console? Please share output of lsusb on host before and after running this commands

tegrarecovery x1 on
tegrareset x1`

4

Yes, I did. I noticed that I connected type-c usb and Mirco usb between my host and dev-kit but lsusb can find only one device with 0955:xxxx NVidia Corp. I don’t know if this is normal or not.

5 
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 413c:2113 Dell Computer Corp. 
Bus 001 Device 030: ID 0955:7045 NVidia Corp. 
Bus 001 Device 002: ID 17ef:608d Lenovo 
Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

after tegrarecovery & tegrareset

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 413c:2113 Dell Computer Corp. 
Bus 001 Device 030: ID 0955:7045 NVidia Corp. 
Bus 001 Device 002: ID 17ef:608d Lenovo 
Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
6

Dear @SivaRamaKrishnaNV
I checked the information in driveinstaller.log. I think some of this information might be useful.

[2022-12-01 06:21:40,566 root DEBUG utilities.py 294 13845] ****** Starting bootburn/bootburn.py ********
[2022-12-01 06:21:40,566 root DEBUG utilities.py 294 13845] Script directory: /drive/drive-foundation/tools/flashtools/bootburn
[2022-12-01 06:21:40,567 root DEBUG utilities.py 294 13845] Parent directory added to path: /drive/drive-foundation/tools/flashtools/bootburn/..
[2022-12-01 06:21:40,567 root DEBUG utilities.py 294 13845] ********* Starting t23x bootburn py ********
[2022-12-01 06:21:40,567 root DEBUG utilities.py 294 13845] Bootburn Starting with arguments ['/drive/drive-foundation/tools/flashtools/bootburn/bootburn.py', '--find_board_name', '-x', '/dev/ttyACM1']
[2022-12-01 06:21:40,567 root DEBUG utilities.py 294 13845] cwd in setBoardConfigPath :: /drive/drive-foundation/tools/flashtools/bootburn_t23x_py
[2022-12-01 06:21:40,567 root DEBUG utilities.py 294 13845]  trying hardware folder:
[2022-12-01 06:21:40,567 root DEBUG utilities.py 294 13845] /drive/drive-foundation/platform-config/hardware/nvidia/platform/t23x/automotive/flashing/board_configs
[2022-12-01 06:21:40,567 root DEBUG utilities.py 294 13845] 
[2022-12-01 06:21:40,567 root DEBUG utilities.py 294 13845] Default Schema:/drive/drive-foundation/tools/flashtools/bootburn_t23x_py/nv-customer-data-schema.json
[2022-12-01 06:21:40,567 root DEBUG utilities.py 294 13845] 
[2022-12-01 06:21:40,567 root DEBUG utilities.py 294 13845] [bootburn]: [GetInfoRom(616)] : Read skuinfo from InfoRom...
[2022-12-01 06:21:40,567 root DEBUG utilities.py 294 13845] [bootburn]: Execute command on Aurix serial port
[2022-12-01 06:21:40,568 root DEBUG utilities.py 294 13845] [bootburn]: [CheckFirmwareisAFW(596)] : AFW firmware found
[2022-12-01 06:21:40,568 root DEBUG utilities.py 294 13845] [bootburn]: [setTargetConfigt23xInfoRomInfo(716)] : 940-63710-0010-200
[2022-12-01 06:21:40,568 root DEBUG utilities.py 294 13845] [bootburn]: [setTargetConfigt23xInfoRomInfo(717)] : None
[2022-12-01 06:21:40,568 root DEBUG utilities.py 294 13845] [bootburn]: [setTargetConfigt23xInfoRomInfo(724)] : ******  s_InforomSkuVersion   200
[2022-12-01 06:21:40,568 root DEBUG utilities.py 294 13845] [bootburn]: [setTargetConfigt23xInfoRomInfo(725)] : ******  s_InforomProdInfo   940-63710-0010
[2022-12-01 06:21:40,568 root DEBUG utilities.py 294 13845] [bootburn]: [findTargetBaseBoardName(763)] : baseBoardName found :: p3710-10-s05
[2022-12-01 06:21:40,568 root DEBUG utilities.py 294 13845] [bootburn]: [findBaseBoardName(3577)] : Detected baseboard with default ChipSku  :: p3710-10-s05
[2022-12-01 06:21:40,568 root DEBUG utilities.py 294 13845] [bootburn]: [updateFindBoardData(352)] : Connected Board Name details ::  baseBoard name - p3710-10-s05
[2022-12-01 06:21:40,568 root DEBUG utilities.py 294 13845] [bootburn]: [GetTegrasAssocWithAurix(507)] : Setting Tegra-A on hold...
[2022-12-01 06:21:40,569 root DEBUG utilities.py 294 13845] [bootburn]: [GetTegrasAssocWithAurix(509)] : Done
[2022-12-01 06:21:40,569 root DEBUG utilities.py 294 13845] [bootburn]: [getListTargetsInRecovery(3645)] : Bus 001 Device 030: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2022-12-01 06:21:40,569 root DEBUG utilities.py 294 13845] [bootburn]: [GetTegrasAssocWithAurix(534)] : Setting Tegra-A in recovery...
[2022-12-01 06:21:40,569 root DEBUG utilities.py 294 13845] [bootburn]: [GetTegrasAssocWithAurix(538)] : Done
[2022-12-01 06:21:40,569 root DEBUG utilities.py 294 13845] [bootburn]: [getListTargetsInRecovery(3645)] : Bus 001 Device 030: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2022-12-01 06:21:40,569 root DEBUG utilities.py 294 13845] [bootburn]: [GetTegrasAssocWithAurix(548)] : No valid Tegra-A ... must have a primary SOC
[2022-12-01 06:21:40,569 root DEBUG utilities.py 294 13845] command line used was:
[2022-12-01 06:21:40,569 root DEBUG utilities.py 294 13845] ['/drive/drive-foundation/tools/flashtools/bootburn/bootburn.py', '--find_board_name', '-x', '/dev/ttyACM1']
[2022-12-01 06:21:40,569 root DEBUG utilities.py 294 13845] 
[2022-12-01 06:21:40,570 root DEBUG utilities.py 294 13845] 
[2022-12-01 06:21:40,570 root DEBUG utilities.py 294 13845] Could not put Tegra-A in recovery
[2022-12-01 06:21:40,570 root DEBUG utilities.py 294 13845] 
[2022-12-01 06:21:40,570 root DEBUG utilities.py 294 13845] [bootburn]: [__exit__(82)] : Exception in critical section :<class 'OSError'>
[2022-12-01 06:21:40,570 root DEBUG utilities.py 294 13845] 
[2022-12-01 06:21:40,570 root DEBUG utilities.py 294 13845] Exception caught in bootburn 
[2022-12-01 06:21:40,570 root DEBUG utilities.py 294 13845] returning to directory /drive/driveinstaller
[2022-12-01 06:21:40,571 root DEBUG utilities.py 294 13845] Cleaning up ...
[2022-12-01 06:21:40,571 root DEBUG utilities.py 294 13845] Cleaning temp dir
[2022-12-01 06:21:40,571 root DEBUG utilities.py 294 13845] Traceback (most recent call last):
[2022-12-01 06:21:40,571 root DEBUG utilities.py 294 13845] File "/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn.py", line 288, in bootburn
[2022-12-01 06:21:40,571 root DEBUG utilities.py 294 13845] bootburnLib.CheckRecoveryTargets()
[2022-12-01 06:21:40,571 root DEBUG utilities.py 294 13845] File "/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn_lib.py", line 3590, in CheckRecoveryTargets
[2022-12-01 06:21:40,571 root DEBUG utilities.py 294 13845] self.aurix.GetTegrasAssocWithAurix(self.targetConfig.s_AurixPort)
[2022-12-01 06:21:40,571 root DEBUG utilities.py 294 13845] File "/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn_aurix.py", line 549, in GetTegrasAssocWithAurix
[2022-12-01 06:21:40,571 root DEBUG utilities.py 294 13845] AbnormalTermination("Could not put {} in recovery".format(name), nverror.NvError_ResourceError)
[2022-12-01 06:21:40,571 root DEBUG utilities.py 294 13845] File "/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/flashtools_nverror.py", line 249, in AbnormalTermination
[2022-12-01 06:21:40,572 root DEBUG utilities.py 294 13845] raise OSError(errorCode)
[2022-12-01 06:21:40,572 root DEBUG utilities.py 294 13845] OSError: 15
[2022-12-01 06:21:40,572 root INFO runner.py 37 13845] Failed to bind partitions!
[2022-12-01 06:21:40,572 root DEBUG runner.py 39 13845] Error on line 910
[2022-12-01 06:21:40,573 root DEBUG runner.py 40 13845] Exception info: Exception Type <class 'module.errors.FailedToBindPartitionsError'>, Traceback <traceback object at 0x7f6a30fddd88>
[2022-12-01 06:21:40,573 root INFO runner.py 45 13845] driveinstaller cannot continue! Check the log file for details: /drive/driveinstaller/driveinstaller.log
[2022-12-01 06:21:40,573 root DEBUG runner.py 62 13845] Cleaning up...
[2022-12-01 06:21:40,573 root DEBUG utilities.py 137 13845] Deleting temporary directories...
[2022-12-01 06:21:40,573 root DEBUG utilities.py 139 13845] Deleting /tmp/pdkinstall-tmp-2e6u4v0q-bind
[2022-12-01 06:21:40,574 root DEBUG runner.py 64 13845] Closing the log file.
7

Dear @hongjiang.rao,
When we set board on recovery mode, we expect to see another device with nvidia in 'lsusb.
Firstly, what is the status of the board? Is it booting? Were you able to access Tegra A via minicom or terminal?

8

Dear @SivaRamaKrishnaNV
I’m not too sure about the current state of the board. I just connected the power and USB cables and turned on the power switch. Then I use minicom to run tegrarecovery & tegrareset commands, and use Docker to run ./flash.sh /dev/ttyACM1 p3710. And this is the first flashing after unboxing.

9

Dear @SivaRamaKrishnaNV
I don’t what Tegra A is. I get this information after running tegrarecovery & tegrareset .

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 
MCU_FOH: MCU FOH : Power state notification for Orin reset
INFO: BtChn_Cfg: No valid next bootchain loaded
INFO: NVMCU_ORINPWRCTRL: Tegra x1 Boot Chain: A 
INFO: MCU_PLTFPWRMGR: Tegra reset trigger is complete !
Command Executed
MCU_FOH: MCU FOH : Power state notification for Orin Power On
MCU_FOH: Spi Transmit Started
10

Dear @SivaRamaKrishnaNV
Now, I am not sure if lsusb can see that the Type-C usb for flashing is connected when flashing for the first time.

11

@hongjiang.rao please see if the developer’s experience at DriveOS 6.0.4 Flashing Failures - #25 by Keelung helps with your issue.

12

Hi @VickNV
Keelung said that it’s his mistake of missing USB-C link. But my USB-C plugged in, only 0955:7045 shown in the output of lsusb. There was no information of another 0955:xxxx, like Keelung’s 0955:7023.

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 413c:2113 Dell Computer Corp. 
Bus 001 Device 034: ID 0955:7045 NVidia Corp. 
Bus 001 Device 002: ID 17ef:608d Lenovo 
Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
13

And could you tell me whether lsusb can see that Type-C usb for flashing is connected when flashing for the first time under normal circumstances? Or，is there any special pre-operation before connecting to USB-C? Thanks.

14

Dear @hongjiang.rao,
Can you check accessing /dev/ttyACM0 and /dev/ttyACM1 and confirm tegra A and aurix console is accessible. If Tegra A is accesible, check login with nvidia/nvidia. This should confirm the Tegra A accessibility

1 Like
15

Dear @SivaRamaKrishnaNV
I tried to use Minicom to accesse /dev/ttyACM0and /dev/ttyACM1.
I run sudo minicom -w -D /dev/ttyACM0 and nvidia/nvidia, and then can’t get anything.

Welcome to minicom 2.7.1

OPTIONS: I18n 
Compiled on Aug 13 2017, 15:25:34.
Port /dev/ttyACM0, 13:57:38

Press CTRL-A Z for help on special keys

nvidia/nvidia

I run sudo minicom -w -D /dev/ttyACM1 and nvidia/nvidia, and then get these.

Welcome to minicom 2.7.1

OPTIONS: I18n 
Compiled on Aug 13 2017, 15:25:34.
Port /dev/ttyACM1, 13:49:40

Press CTRL-A Z for help on special keys

nvidia//nvidia

Info: Executing cmd: nvidia/nvidia, argc: 0, args: 
Error: Unknown command
Invalid Command
NvShell>

Does this mean that aurix console can be accessed, but Tegra A cannot？

16

Dear @hongjiang.rao,
It looks like Tegra A is not accessible.

this is the first flashing after unboxing

Does that mean, you or your collegues never used the board and just started flashing after you receive?

17

Dear @hongjiang.rao,
Also, could you share the complete driveinstaller.log file and output on terminal. We will check internally and update you.

18

Yes, we never used the board and just started flashing after we receive.
This is the driveinstaller.log.
driveinstaller.log (477.0 KB)

19

And this is ouput on terminal after I run ./flash.sh /dev/ttyACM1 p3710 in docker.

root@6.0.5.0-0003-build-linux-sdk:/drive# ./flash.sh /dev/ttyACM1 p3710
Executing bind + flash
[===    ]

DRIVE Installer failed with status 140
DriveinstallerFlash failed, error 140!
======================================================
          
Error 140 occurred, please resolve the issue or try again.
Please contact provider with log "/drive_flashing/log_ca3e20ef18de976a03ffa042ae238873.txt".
          
======================================================
NGNG

This is the log_ca3e20ef18de976a03ffa042ae238873.txt.
log_ca3e20ef18de976a03ffa042ae238873.txt (949 Bytes)

20

Dear @hongjiang.rao,
please share ls -la /dev/ttyACM* to see list of available ports after connecting target and host.
/dev/ttyACM1 is used to connect to aurix. Meanwhile, Could you share Aurix version(run version on aurix terminal).

Also, check running poweroff and poweron commands on aurix terminal with some gap (like ~20sec ) and check accessing Tegra A via dev/ttyACM0. We notice a couple of power off-on commands on aurix can fix such issues.

22

Dear @SivaRamaKrishnaNV
Before connecting target and host, ls -la /dev/ttyACM*: there is no such file or directory.
After connecting target and host：

$ ls -la /dev/ttyACM*
crw-rw---- 1 root dialout 166, 0 12月  2 16:23 /dev/ttyACM0
crw-rw---- 1 root dialout 166, 1 12月  2 16:23 /dev/ttyACM1
crw-rw---- 1 root dialout 166, 2 12月  2 16:23 /dev/ttyACM2
crw-rw---- 1 root dialout 166, 3 12月  2 16:23 /dev/ttyACM3

run version on aurix terminal

NvShell>version

Info: Executing cmd: version, argc: 0, args: 
DRIVE-V6.0.4-P3710-AFW-Aurix-StepB-5.05.03
Command Executed
NvShell>

And I will try to check running poweroff and poweron commands on aurix terminal with some gap.
I will reply here if it is useful.