Updating Drive OS via docker

Please provide the following info (tick the boxes after creating this topic):
Software Version
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-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.2.10884
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

I am trying to install driver OS from the docker.
As a part of that process, I ran flash.py command with the parameters and I hit into the error where it fails to bind the partitions.
Any pointers on this , to help to reason out the failure reasons.

build-linux-sdk:/drive# ./flash.py /dev/ttyACM1 p3710
2023-05-12 20:37:50 INFO : Flashing already set for dual bootchain
2023-05-12 20:37:50 INFO : Flash clean already disabled for persistent partitions
2023-05-12 20:37:50 INFO : Initiating pre-flash check
2023-05-12 20:37:50 INFO : Checking Serial Port Connection
2023-05-12 20:37:50 INFO : Serial Port found /dev/ttyACM1
2023-05-12 20:37:50 INFO : Running basic open/close tests on Serial Port Connection
2023-05-12 20:37:50 INFO : Serial Port is open
2023-05-12 20:37:50 INFO : Flushing input and output buffer, discard all content
2023-05-12 20:37:50 INFO : Serial Port is closed
2023-05-12 20:37:50 INFO : Checking available targets
2023-05-12 20:37:50 INFO : Checking Orin board connection
2023-05-12 20:37:50 INFO : Orin board with Device ID – 0955:7045 found.
2023-05-12 20:37:50 INFO : Orin board device path is /dev/bus/usb/001/008
2023-05-12 20:37:50 INFO : Pre-flash check complete
2023-05-12 20:37:50 INFO : Flashing DRIVE OS Docker
2023-05-12 20:37:50 INFO : driveinstaller v2.0
2023-05-12 20:37:50 INFO :
2023-05-12 20:37:50 INFO : SDK/PDK Installer and Flasher
2023-05-12 20:37:50 INFO : Run ./driveinstaller --help for usage information.
2023-05-12 20:37:50 INFO :
2023-05-12 20:37:50 INFO : Initializing board and OS configuration to Autonomous vehicle p3710 Linux Tegra A
2023-05-12 20:37:50 INFO : Manifest version 2.0
2023-05-12 20:37:50 INFO :
2023-05-12 20:38:03 INFO : BOARD SKU : 940-63710-0010-200
2023-05-12 20:38:03 INFO : Found matching board id p3710-10-s05 in 940-63710-0010-200 sku
2023-05-12 20:38:03 INFO : Applying additional Bind opts
2023-05-12 20:38:06 INFO : Binding of partitions failed ! Check log for more details.
2023-05-12 20:38:06 INFO : Failed to bind partitions!
2023-05-12 20:38:06 INFO : driveinstaller cannot continue! Check the log file for details: /drive/driveinstaller/driveinstaller.log
2023-05-12 20:38:06 INFO :
2023-05-12 20:38:06 INFO :
2023-05-12 20:38:06 ERROR : Flashing failed, please contact provider with logs /drive_flashing/log_rznv9hfog0i4smwp7tqj5ydecl3b682k.txt and /drive/driveinstaller/driveinstaller.log
2023-05-12 20:38:06 ERROR : Traceback (most recent call last):
File “./flash.py”, line 153, in
flash_config(args.board, args.aurixport, args.tegra, args.pct_variant, args.recovery_timeout)
File “./flash.py”, line 143, in flash_config
raise Exception(f’Error {proc.returncode} occurred’)
Exception: Error 140 occurred

Please share the logs mentioned. Also, have you been able to flash any DRIVE OS to this devkit with docker before? In the meantime, please try flashing with sdkmanager. Thanks.

driveinstaller.log (91.5 KB)
log_0p7bic8l4szv9mo25n1judqk6eh3fwyr.txt (2.1 KB)
Here attached both the logs

Yes we are already running 6.0.5

I found the message in the log. Have you observed any abnormalities on the devkit before attempting to flash DRIVE OS 6.0.6?

[2023-05-12 14:39:08,154 root DEBUG utilities.py 294 22] ^[[01;31mCould not put Tegra-A in recovery^[[0m

Please try to power reset the system with the power switch on your orin system, connect USB cable, and then send below commands via aurix console and linux shell respectively in sequence and provide the outpus for our information.

NvShell> tegrareset x1 h
$ lsusb -d 0955:
NvShell> tegrarecovery x1 on
NvShell> tegrareset x1
$ lsusb -d 0955:

Vick, how ever i was able to run ./bind_partitions -b p3710-10-s05 linux with out any issue in the docker.
Docker is latest downloaded today.

NvShell> tegrareset x1 h
after this on the host when i do lsusb i see
~$ lsusb -d 0955:
Bus 001 Device 008: ID 0955:7045 NVIDIA Corp.

NvShell> tegrarecovery x1 on
NvShell> tegrareset x1
after this on the host when i do lsusb i see
~$ lsusb -d 0955:
Bus 001 Device 008: ID 0955:7045 NVIDIA Corp.

Vick, yes when i tried to put the tegra in recovery using

NvShell> tegrarecovery x1 on
NvShell> tegrareset x1

I always saw that tegra is rebooting to normal linux shell.

Do you mean the devkit with DRIVE OS 6.0.5 works now?
Have you observed any abnormalities on the devkit before attempting to flash DRIVE OS 6.0.6?

Hi Vick
The devkit works with 6.0.5. every time i try to flash 6.0.6 , i am seeing the same problem, with respect to the bind partitions.

Could you please provide us with the current Aurix firmware version by running the ‘version’ command on the Aurix console, and also share the power-on log from the Aurix console? We would like to investigate if there is any suspicious information that may help us identify the issue.

hey Vick,

Here is the version information:

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

and here are the attached logs
Aurix-605-logs.txt (7.3 KB)

I didn’t find any suspicious messages in your log, but it might be worth attempting the solution provided in Driver orin flash failed - #16 by user88818 as it helped another developer who had trouble entering recovery mode.

Hey Vick,

Finally, i am able to do upgrade, after the reboot of the devkit, restart the docker and am able to flash the device. I can see the firmware updated on Aurix as well.

Regards,
Sistla.

May I know what fixed your issue? anything to do with the ‘aurixreset’ command?

I dont think my issue is any thing to do with Aurix reset. I did a restart on Orin, restarted my host and with that the docker is restarted. This solved the problem, no other thing as such i see.

No Vick.i did not do any thing on the aurix reset.