Nvidia Drive AGX orin flashing though SDK Manager (6.0.6)

Autonomous Vehicles DRIVE AGX Orin DRIVE AGX Orin General
1

Please provide the following info (tick the boxes after creating this topic):
Software Version

[0] DRIVE OS 6.0.6

Target Operating System
Linux

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.2.0

Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager

Issue Description
not able to flash using SDK manager( I need help with SDK manager only not Docker)

Error String
FileNotFoundError: [Errno 2] No such file or directory: ‘/home/user/Downloads/DRIVE_OS_6.0.6_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS//drive-linux/filesystem/targetfs/usr/bin/’

Full Matter:-
Hello NVIDIA Support Team,

I am working with the NVIDIA DRIVE AGX Orin board and attempting to flash it using the SDK Manager (please note that Docker is not an option in my setup).

However, I am encountering the following error during the flashing process:

FileNotFoundError: [Errno 2] No such file or directory: ‘/home/user/Downloads/DRIVE_OS_6.0.6_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS//drive-linux/filesystem/targetfs/usr/bin/’

The directory mentioned in the error does exist on my system, and it has full read-write-execute permissions. Another related issue is that the script fails while copying qemu-aarch64-static from targetfs/usr/bin/. I have verified that this file exists on the host system as well. Even after manually copying it and ensuring full permissions, the SDK Manager continues to throw the same error.

I have also tested the process on three different host machines, all resulting in the same error.

I have attached the relevant log files for your review. Kindly help me resolve this issue using SDK Manager only, without Docker.

Note :- why there has not been a SDK managers for latest versions(6.0.8 or 6.0.10) ?

Regards
Ravi teja

Logs
NV_DRIVE_FLASH_DRIVE_COMP.log (10.3 KB)

3

We have started releasing DRIVE OS releases on docker as notice few host system state issues customers flashing the target. Using docker provide simplified development to flash and develop DRIVE OS applications. The last release for sdkmanager is DRIVE OS 6.0.6. If you want latest release, you need to use docker container.

Please share full sdkm logs at ~/.nvsdkm/logs and ~/.nvsdkm/sdkm*.log
Also, note that, you need two wire connection between host and target. Please review the connections

  1. May I know the reason why you don’t want to use docker container and use sdkmanager only?
  2. Are you able to access Tegra using minicom? what is the DRIVE OS version on target currently?
4

Hello @SivaRamaKrishnaNV

i have checked connections as well micro USB for debugging and LeftType C for flashing

1- when we try to flash through SDK manger we are able to use Bluetooth, network manager and sound card. last time when we tried using docker we were not able to use any of those , that is why we went through SDK manger,.
2- yes I’m able to access Minicom , the current version is 6.0.6 only.
The reason i want to flash the same version is because last time when we flashed though SDK manager, tensorrt was not installing after flashing , nor we could install manually. so now i want to recheck once whether is that the same case with tensorrt or not
But I’m unable to flash.

Note: i can try to flash through docker as well but after that sound , network , Bluetooth doesn’t work it will be a big problem.

here is the full logs as zip file since we can only attach one i zipped it.

Full logs
logs.zip (68.4 KB)

5

Dear @nagireddy.raviteja ,
last time when we tried using docker we were not able to use any of those

The latest tag downloads the DRIVE OS 6.0.10 container. It does not have bluetooth/wifi enabled. You can also use DRIVE OS 6.0.6 docker container for flashing. Please use 6.0.6.0-0004 to pull DRIVE OS 6.0.6.
Docker Image: nvcr.io/drive/driveos-sdk/drive-agx-orin-linux-aarch64-sdk-build-x86:6.0.6.0-0004

6

hello @SivaRamaKrishnaNV
i did not understand what are you trying to say, either i’m not bale to see what you sent fully or may be that’s what you sent totally.
if you are telling like we won’t be able to use Bluetooth n wifi when we try to flash with dockerthat’s exactly i’m trying to tell why i want to flash though sdk manager , caz with sdk manger i can use all those even now i’m using those.

7

You need DRIVE OS 6.0.6 . It can be flashed using docker as well instead of sdkmanager. I believe you might have flashed latest DRIVE OS version last time when you checked(i.e DRIVE OS 6.0.10)

To flash DRIVE OS 6.0.6:

docker run -it --privileged --net=host -v /dev/bus/usb:/dev/bus/usb  -v /drive_flashing:/drive_flashing -v $HOME/:/home/nvidia/  nvcr.io/drive/driveos-sdk/drive-agx-orin-linux-aarch64-sdk-build-x86:6.0.6.0-0004 # download and gets to docker console. 
./flash.py /dev/ttyACM1 p3710 # to flash target
8

hello @SivaRamaKrishnaNV
you misundestood.
i have 6.06 now which i flashed through SDK manager way back till today i’m using same. but now i want to re flash the board using sdk manager for 6.0.6 i’m getting error please don’t suggest me to use docker, if you have any solutions related to sdk manager flashing please share

Important
i don’t want to flash through Docker because if i do i cannot use Bluetooth , WiFi, sound which i need at any cost that is why i want to flash through SDK manager only.

Problems with SDK manager

Tensorrt is not installing after flashing , last time we had this issue that is why i want to recheck whether this problem is solved or not .

9

Hello @SivaRamaKrishnaNV any update on this ?

10

driveinstaller cannot continue! Check the log file for details: /home/user/.nvsdkm/driveinstaller.log

Could you share driveinstaller.log and sdkm*.log files as well. Logs.zip does not have enough info.

11

okay @SivaRamaKrishnaNV i’ll share, before that i have doubt or question
while installing all the necessary libraries using sdkmanager, there will be always be errors while installing the cuda , cuDNN,Tensorrt and vlukan pacakges,
when i try to manully install those it will ask for NV_WORKSPACE path where it has to install the SDK, that is where i’m getting struck like which path i have to give for that.
in general sdk manager install the the things under
" ‘/home/user/Downloads/DRIVE_OS_6.0.6_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS//drive-linux"

so when it ask for path i give usally /home/user/Downloads/DRIVE_OS_6.0.6_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS , then it will exit with errors, if i give some differnt path it will install but id on’t think that is correct path.

now comes to error .

error:-
as you can see here i hava the path here /drive-linux/filesystem/targetsfs/usr/bin is very much available as well as other permissions which are already there

Logs
SDKM_logs_DRIVE_OS_6.0.6_SDK_Linux_for_DRIVE_AGX_Orin_DevKits_2025-06-12_10-24-08.zip (407.8 KB)
.nvsdkm.zip (660.8 KB)

here is the screenshot says i have everything it says still i’m getting error.

image
image3788×604 303 KB

please let me know what i need to do.