DRIVE AGX Orin Flashing issue /dev/ttyACM1 not found on host

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.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
We are encountering an error during the flashing process of the NVIDIA Drive AGX Orin using SDK Manager(2.2.0-> only on this version DRIVE OS 6.0.6 available) on a host Linux PC. The device is connected via an original USB-A to USB-C cable. The Drive AGX Orin is successfully forced into recovery mode and is visible in the lsusb output on the host. A notification also confirms that the device is detected in recovery mode, and we select the DRIVE Orin device from the list. However, during STEP 03 of the flashing process, we receive the error: ‘/dev/ttyACM1 not found on host’.

Screenshot from 2025-05-22 08-57-27
Screenshot from 2025-05-22 08-57-271850×1045 268 KB

We have performed the following troubleshooting steps:

  • Ensured the cdc_acm kernel module is loaded (sudo modprobe cdc_acm)
  • Added the user to the dialout group and re-logged in (sudo usermod -a -G dialout $USER)

Despite these actions, the issue persists.

Error String
‘/dev/ttyACM1 not found on host’

2

After trying all cable options and tricks, we managed to flash successfully only with this setup: USB-C to USB-C cable + microUSB connected, and forced recovery mode activated manually. With this combination, the OS 6.0.6 image flashed successfully.

1 Like
3

Glad the issue is resolved. Thanks for update @marko.vucicevic

4

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