Please provide the following info (tick the boxes after creating this topic): Software Version
[√] DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
Target Operating System
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 (940-63710-0010-200)
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 had a AGX Orin form our customer , i tried to flash AGX Orin form SDK Manager and Docker container ,but it was fail ,and i used the minicom to connect /dev/ttyACM1 , minicom no respond (type any key no respond) ,i change the TYPE C cable and host machine ,but it still fail ,how can I solve this problem？
Have you ever successfully accessed Aurix via ttyACM1 on any other devkit? Have you referred to Software Setup on the Linux Host?
Please try “Use a USB 2.0 port on the host PC used for flashing” mentioned in the release notes.
Also, after minicom connects to /dev/ttyACM1, please try switching off/on the power on the rear panel of the devkit and see if any messages show.
What did you see for the failure of docker flashing? any log?
According to this image and the logs you provided offline, it seems the application was waiting for you to input the password. Please delete ~/.nvsdm directory, try flashing with sdkmanager again and share us ~/.nvsdkm directory.
log_c6e8b013f868f7602e4eb8cdb9c8282a.txt (261 Bytes)
The attach file is the docker flash log ,the next step should be connect /dev/ttyACM1 successfully ,but connect fail ,so the screen hang on the below picture
Before flashing DRIVE OS 6.0.5, did the pre-flashed DRIVE OS work well?
If you can access NVIDIA Orin X1 via serial port or ssh, please follow Flashing AURIX from NVIDIA Orin and try if reflashing the aurix firmware helps with this issue.
This is our host machine , i usd the type C to type C cable to access the devkit and i tried to access the devkit by other type C to type A cable , but it still can’t open /dev/ttyACM1
My company is LEADTEK , these are our customer devkit ,and we talk about these issue form Email ,one can’t open /dev/ttyACM1 ,the other one can access the devkit via minicom ,but no extra usb device on lsusb output after type the “tegrarecovery on” and “thgraest x1”