Docker installation of OS 6.0.8.1 failure

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

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’m trying to use the docker method to install 6.0.8.1 with flash.py. I encountered the following error:

root@6.0.8.1-0006-build-linux-sdk:/drive# ./flash.py /dev/ttyACM1 p3710
2023-10-23 22:47:06 INFO : Flashing already set for dual bootchain
2023-10-23 22:47:06 INFO : Flash clean already disabled for persistent partitions
2023-10-23 22:47:06 INFO : Initiating pre-flash check
2023-10-23 22:47:06 INFO : Checking Serial Port Connection
2023-10-23 22:47:06 INFO : Serial Port found /dev/ttyACM1
2023-10-23 22:47:06 INFO : Running basic open/close tests on Serial Port Connection
2023-10-23 22:47:06 INFO : Serial Port is open
2023-10-23 22:47:06 INFO : Flushing input and output buffer, discard all content
2023-10-23 22:47:06 INFO : Serial Port is closed
2023-10-23 22:47:06 INFO : Checking available targets
2023-10-23 22:47:06 INFO : Checking Orin board connection
2023-10-23 22:47:06 INFO : Orin board with Device ID -- 0955:7045 found.
2023-10-23 22:47:06 INFO : Orin board device path is /dev/bus/usb/003/004
2023-10-23 22:47:06 INFO : Pre-flash check complete
2023-10-23 22:47:06 INFO : Flashing DRIVE OS Docker
2023-10-23 22:47:10 INFO : driveinstaller v2.0
2023-10-23 22:47:10 INFO : 
2023-10-23 22:47:10 INFO : SDK/PDK Installer and Flasher
2023-10-23 22:47:10 INFO : Run `./driveinstaller --help` for usage information.
2023-10-23 22:47:10 INFO : 
2023-10-23 22:47:10 INFO : Initializing board and OS configuration to Autonomous vehicle p3710 Linux Tegra A
2023-10-23 22:47:10 INFO : Manifest version 2.0
2023-10-23 22:47:10 INFO : 
2023-10-23 22:47:10 INFO : Could not fetch board revision. Re-try either by re-connecting board or make sure all serial port processes such as minicom are closed.
2023-10-23 22:47:10 INFO : Failed to bind partitions!
2023-10-23 22:47:10 INFO : driveinstaller cannot continue! Check the log file for details: /drive/driveinstaller/driveinstaller.log
2023-10-23 22:47:10 ERROR : Flashing failed, please contact provider with logs /drive_flashing/log_kui30bjxvz5nrpo9gw47a6y182qcslmd.txt and /drive/driveinstaller/driveinstaller.log.

The logs are as follows.

driveinstaller.log (545.6 KB)

log_kui30bjxvz5nrpo9gw47a6y182qcslmd.txt (1.4 KB)

Can you please help?

3

Please ensure that all serial port processes are closed. Alternatively, you can try rebooting the host system and then running the command. The error message indicates that it couldn’t fetch the board revision due to possible conflicts with open serial port processes, such as ‘minicom.’

[2023-10-23 22:44:01,981 root ERROR pdk_bind.py 121 21] Could not fetch board revision. Re-try either by re-connecting board or make sure all serial port processes such as minicom are closed.
4

Thanks for the prompt response. Updated the log:

driveinstaller.log (649.9 KB)

It still failed. Can you please help?

5

I have located the error messages in both the current log and the previous log. To resolve this issue, I recommend referring to the ‘Getting Started’ section in the ‘DRIVE AGX Orin Developer Kit Hardware Quick Start Guide.’ This guide provides detailed instructions on connecting USB cables properly.

[2023-10-23 23:00:33,853 root DEBUG utilities.py 294 146] ^[[01;31mCould not put Tegra-A in recovery^[[0m

6

Thanks for looking into this. @VickNV Issue resolved after changing the USB-C connection.

9

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