Flashing Orin AGX SDK failed

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

Flashing P3710 failed with below log and attached log files.

2023-12-14 18:30:13 INFO : Flashing already set for dual bootchain
2023-12-14 18:30:13 INFO : Flash clean already disabled for persistent partitions
2023-12-14 18:30:13 INFO : Flashing DRIVE OS Docker
2023-12-14 18:30:13 DEBUG : [‘./driveinstaller’, ‘–configjson’, ‘./manifests/install_pdk_config/av_orin_p3710_driveos_linux_tegraA_install_pdk_config.json.set’, ‘–installtype’, ‘bindflash’, ‘–pdkinstalledpath’, ‘/drive’, ‘–boardtype’, ‘ES’, ‘–consoleout’, ‘enable’, ‘–port’, ‘/dev/t
tyACM1’]
2023-12-14 18:31:13 INFO : driveinstaller v2.0
2023-12-14 18:31:13 INFO :
2023-12-14 18:31:13 INFO : SDK/PDK Installer and Flasher
2023-12-14 18:31:13 INFO : Run ./driveinstaller --help for usage information.
2023-12-14 18:31:13 INFO :
2023-12-14 18:31:13 INFO : Initializing board and OS configuration to Autonomous vehicle p3710 Linux Tegra A
2023-12-14 18:31:13 INFO : Manifest version 2.0
2023-12-14 18:31:13 INFO :
2023-12-14 18:31:13 INFO : BOARD SKU : 940-63710-0010-200
2023-12-14 18:31:13 INFO : Found matching board id p3710-10-s05 in 940-63710-0010-200 sku
2023-12-14 18:31:13 INFO : Applying additional Bind opts
2023-12-14 18:31:13 INFO : Executing bind clean cmd make/bind_partitions -b p3710-10-s05 linux clean
2023-12-14 18:31:13 INFO : Executing bind cmd make/bind_partitions -b p3710-10-s05 linux
2023-12-14 18:31:13 INFO : Bind partitions done!
2023-12-14 18:31:13 INFO : Initializing SDK/PDK flasher for configuration
2023-12-14 18:31:13 INFO : Board: p3710
2023-12-14 18:31:13 INFO : Board type: ES
2023-12-14 18:31:13 INFO : Hypervisor config: linux
2023-12-14 18:31:13 INFO :
2023-12-14 18:31:13 INFO : bypassing inforrom for flashing cmd
2023-12-14 18:31:13 INFO : Pre flash script found! Calling scripts/linux_pre_flash.sh
2023-12-14 18:31:13 INFO : b’NV_WORKSPACE:'b’NV_TARGETUSER:'b’NV_TARGETPWD:'b’NV_EULA_ACCEPTED:'b’mount: /drive//drive-linux/filesystem/targetfs: failed to setup loop device for /drive/drive-linux/filesystem/targetfs-images/driveos-oobe-desktop-ubuntu-20.04-rfs.img.\r\n’b’umount: /drive/
/drive-linux/filesystem/targetfs.img: not mounted.\r\n’b’Script scripts/linux_pre_flash.sh fails.\r\nDRIVEOS filesystem Username/Password setup has not been completed.\r\n’b’umount: /drive//drive-linux/filesystem/targetfs.img: not mounted.\r\n’Extracting the PDK failed!
2023-12-14 18:31:13 INFO : driveinstaller cannot continue! Check the log file for details: /drive/driveinstaller/driveinstaller.log
2023-12-14 18:31:13 ERROR : Flashing failed, please contact provider with logs /drive_flashing/log_eba65mywcpgrhzqsfi217x0uj93nltvo.txt and /drive/driveinstaller/driveinstaller.log.
driveinstaller.log (689.7 KB)
log_eba65mywcpgrhzqsfi217x0uj93nltvo.txt (2.6 KB)

4

Thank you for providing the logs. It appears that there is an issue during the pre-flash script execution, specifically in setting up the loop device for the filesystem image.

Could you please provide detailed steps you followed, including the command used to run the Docker container and any subsequent commands leading up to the error? Additionally, ensure that you have referred to the Flash DRIVE OS Linux guide to confirm that the installation steps are correct.

5

Here are the commands used to download the image and flashing:

Downloading the image
sudo docker run -it --privileged --net=host -v /dev/bus/usb:/dev/bus/usb -v /home/aseyoum:/home/nvidia nvcr.io/drive/driveos-sdk/drive-agx-orin-linux-aarch64-sdk-build-x86:latest

Before flashing
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

The flashing command
./flash.py /dev/ttyACM1 p3710

I followed the instruction from the link Set Up DRIVE OS Linux with NVIDIA GPU Cloud (NGC) | NVIDIA Docs

6

It appears that you’ve followed the correct steps. However, to investigate further, could you provide the output of the ‘sudo docker images’ command?

Additionally, if you haven’t successfully flashed any other devkits, make sure to closely follow the ‘Getting Started’ section in the ‘DRIVE AGX Orin Hardware Quick Start Guides’ for setting up the necessary connections correctly.

7

Here is the output of the docker command

image
image1299×359 114 KB

I am following the starting guides.

8

It appears that a newer image has been pulled. Have you tried to flash within the updated container to see if it resolves the issue?

9

No, I have not tried. What version should I try?
What command should it be used for the latest version now that you have all the commands I used.
Is the flashing command issued from the host PC or from the docker line root@6.0.8.1-0006-build-linux-sdk:/drive# ?

11

Per your logs, you have just pulled the correct image. Now you should try your previous steps as below:

$ 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
...
# ./flash.py /dev/ttyACM1 p3710
14

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.