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
I’m not able to flash the AGX DRIVE with the SDK Manager there is always a problem with the partition according to the log. For the installation of the DRIVE OS is necessary to install an additional SSD or is enough the space provided by the AGX Drive Orin itself?
Error String
[2025-03-31 22:03:09,709 root ERROR pdk_bind.py 102 8905] Could not fetch board revision. Re-try either by re-connecting board or make sure all serial port processes such as minicom are closed.
[2025-03-31 22:03:09,709 root INFO runner.py 37 8905] Failed to bind partitions!
[2025-03-31 22:03:09,709 root DEBUG runner.py 39 8905] Error on line 958
[2025-03-31 22:03:09,709 root DEBUG runner.py 40 8905] Exception info: Exception Type <class ‘module.errors.FailedToBindPartitionsError’>, Traceback <traceback object at 0x7f79965202c8>
[2025-03-31 22:03:09,710 root INFO runner.py 45 8905] driveinstaller cannot continue! Check the log file for details: /home/somuntea/.nvsdkm/driveinstaller.log
Logs
driveinstaller 3.log (189.4 KB)
This indicates, the board is not connected to host. Please check the connection settings (double check Step 2 and 3 of page 9) in Quick start guide
Also, we encourage to use docker container instead of sdkmanager to avoid system state issues.
Is there any reason to use DRIVE OS 6.0.6?
If you want to flash latest release i.e DRIVE OS 6.0.10 , please follow Install DRIVE OS 6.0.10.0 for NVIDIA Developer Users | NVIDIA Docs
Hello SivaRamaKrishnaNV,
-
The connection to the board should be fine. I double checked it.
I have one connection to the debug connector (via microUSB to USB-A cable) and one connection to the usb-c connector from the rear panel - port from the left (via usb-c to usb-A cable).
By checking the connectivity on the host (with lsusb command) I see both ports available.
-
There is no specific reason for using DRIVE OS 6.0.6, but this is the only one which is available to be flashed with sdkmanager.
-
I will try to install DRIVE OS 6.0.10 via docker. Is the upgrade from DRIVE OS 6.0.6 to DRIVE OS 6.0.10 supported? According to the compatibility table from the official site
seems not to be possible (Requirements for Your Development Environment | NVIDIA Docs).
Thank you in advance for your support!
Best regards,
S. Munteanu
Dear @s.munteanu ,
The board is in recovery mode as per lsusbas I see two NVIDIA devices.
Please put the board in normal mode from aurix using tegrarecovery x1 off & tegrareset x1.
Is the board in working condition? Do you see any issue and wants to re-flash target?
Please power off/on both host and target and check flashing using DRIVE OS 6.0.10 docker.
Hi SivaRamaKrishnaNV,
thanks for your quick reply.
The reason for flashing the board is because we are not able to login into ubuntu anymore (this is due to the fact that python 3.8 package was removed by mistake - and together with it I suppose there were also some dependencies removed.)
I tried to access the terminal via serial debug port (/dev/ttyACM0) but it says that the login is incorrect even though the username and password are valid.
Hi SivaRamaKrishnaNV,
I tried to flash DriveOS 6.0.10 using the docker container, but I still get the error regarding “Failed to bind partitions”.
These were the steps I followed:
-
download and start the Docker container (sudo docker run -it --privileged --net=host -v /dev/bus/usb:/dev/bus/usb -v /drive_flashing:/drive_flashing nvcr.io/drive/driveos-sdk/drive-agx-orin-linux-aarch64-sdk-build-x86:latest)
-
set the DRIVE AGX Orin Board in normal mode using tegrarecovery x1 off & tegrareset x1
-
power off/on the board
-
read the port availability on the terminal using lsusb command.
-
start the flash from the docker container using ‘./flash.py /dev/ttyACM1 p3710’
Attached are the logs, too.
Logs.zip (10.0 KB)
What could be the issue? Could you please check the logs and send me some feedback?
Thank you.
Best regards,
S. Munteanu
Hi SivaRamaKrishnaNV,
I tried to flash again DriveOS 6.0.10 on the board via docker, this time using another cable (usb-c to usb-c) to connect to the flashing usb-c port.
This time I observed that bind partitions was successfully done, but couple of minutes later the flash process fails again.
Please see attached the new logs.
new_logs.zip (27.1 KB)
Any idea on how to solve this issue?
Best regards,
S. Munteanu
Hi SivaRamaKrishnaNV,
I have an update to this topic.
It seems that the root cause for the problem was the virtual machine where I was running the Ubuntu distribution. During the flash, there are some resets performed, and it seems that the VM is having some troubles to re-establish the USB connection after the reset, and therefore the flashing will fail.
Solution: I have used a machine with native linux distribution on it and the flashing was successfully done!
Topic can be closed.
1 Like
Flashing using VM is not supported.
Thanks for update. Glad to hear the issue is resolved.
