Flashing error using SDK Manager

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)

Target Operating System

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)

SDK Manager Version

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

I am trying to install and flash the latest Drive Orin SDK of DRIVE OS 6.0.6 on the Orin kit through SDK manager.
The host components are installed successfully but during the flashing step on the target getting error on the sdk manager screen.

Attaching the logs for the same. Kindly check and confirm.

SDKM_logs_DRIVE_OS_6.0.6_SDK_Linux_for_DRIVE_AGX_Orin_DevKits_2023-08-01_18-51-48.zip (143.7 KB)

I saw the following messages from your ‘NV_DRIVE_FLASH_DRIVE_COMP.log’ file.
Please try again right after rebooting your host system (so no minicom running in the background). In case the issue persists, please provide the ‘~/.nvsdkm/driveinstaller.log’ file for our further analysis.

Could not fetch board revision. Re-try either by re-connecting board or make sure all serial port processes such as minicom are closed.
Failed to bind partitions!
driveinstaller cannot continue! Check the log file for details: /home/adascoe/.nvsdkm/driveinstaller.log

Hi @VickNV,

I tried the solution you suggested, but still facing the same issue.
Attaching the logs again for your anaylsis.
SDKM_logs_DRIVE_OS_6.0.6_SDK_Linux_for_DRIVE_AGX_Orin_DevKits_2023-08-09_13-01-32.zip (151.9 KB)
driveinstaller.log (50.3 KB)

Dear @saurabh.sinalkar,

  1. Is the system working well before flashing?

  2. What is the DRIVE OS version on target currently? Please see requirements at Requirements for Your Development Environment | NVIDIA Docs

  3. Lets make sure if the board can be set in recovery mode.
    (i) run lsusb on host
    (ii) run tegrarecovery x1 on & tegrareset x1 on aurix console
    (iii) run lsusb on host again to see if there is additional NVIDIA device

  1. Yes the system is working with the shipped Drive OS, we were able to accept the license agreement and login in to the system using graphical interface.

  2. The Drive OS version is, i have checked all the development requirements, all the host components are installed successfully, the issue occurs only while flashing the target.

  3. I am able to login to aurix console on port /dev/ttyACM1 but cannot input any commands of recovery and resetting, only the following attached screen is visible.

Tegra console is getting accessed on port /dev/ttyACM0 without any issues.

Dear @saurabh.sinalkar,
Why you can not enter command on aurix console? Do you see any error on aurix console? Could you attach the aurix console output?

Dear @SivaRamaKrishnaNV ,

The screenshot attached in the previous reply is the aurix console output.
I am not able to input any commands in the console.

I see /dev/ttyACM0 in attached picture. Tegra console is on /dev/ttyACM1?

Yes Tegra console is on /dev/ttACM1 and aurix is on /dev/ttyACM0 which is opposite to what is mentioned in the documentation.

This appears to be data from a GNSS device. Could you kindly provide the output of the following command:

$ ls -l /dev/ttyACM*

Dear @SivaRamaKrishnaNV @VickNV,

I am able to access aurix console now, and i confirmed that the board can be set into recovery mode & i am able to see an additional device once reset is set. The port to access aruix shell was /dev/ttyACM2.

I am still facing issues in flashing the device. Attaching the drive installer logs.
Kindly suggest the further steps.
driveinstaller.log (269.8 KB)

To troubleshoot the flashing issue, please try removing the GNSS device. This will help ensure that ttyACM0 is dedicated to Orin and ttyACM1 is reserved for Aurix. After doing so, attempt the flashing process again.

Hi @VickNV ,

It is difficult to remove the GNSS device as its been used for different purpose.

Is there some other mechanism through which we can dedicatedly assign ACM0 and ACM1 ports to Orin and Aurix respectively in Ubuntu 20 which is the expected port assignment for flashing instead of the current default port assignment of ACM1 and ACM2 to Orin and Aurix respectively?

To address the port assignment issue, you can follow Install DRIVE OS Linux Docker Containers from NGC and flash the devkit using the command below (assuming Aurix is on ttyACM2 on your host):

$ ./flash.py /dev/ttyACM2 p3710

Alternatively, you could consider using a different host system that doesn’t have the GNSS device attached to it for flashing the devkit.

Dear @SivaRamaKrishnaNV & @VickNV,

We were able to flash the latest OS using a different host system. which didn’t had any default ACM port assigned.

Thanks for the support.

1 Like

Dear @saurabh.sinalkar,
Thank you for update.

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