Please provide the following info (check/uncheck the boxes after creating this topic): Software Version
DRIVE OS Linux 5.2.6
DRIVE OS Linux 5.2.6 and DriveWorks 4.0
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
other
Hi, I am unable to flash my Drive AGX with Drive OS 5.2.6 from the sdkmanager. Previously, it would get stuck at 99.88% flashing and would not progress, asking me if I wanted to skip this process because it was taking a long time. I restarted my sdkmanager but now it says /dev/ttyUSB3 is opened by another application. No minicom windows are open on my host PC though. I have tried uninstalling Drive OS 5.2.6 and then reinstalling it but it gives me the same issues where first the flashing gets stuck and then I can’t try again after stopping it because /dev/ttyUSB3 is opened by another application. Any suggestions?
Hi, @atseng
I assume you’re seeing “Could not fetch board revision. Re-try either by re-connecting board or make sure all serial port processes such as minicom are closed.” as in the below topic.
Please restart your host system and try again.
I don’t see that error. However, I restarted my host system and got the same issues. First, there was the message “Installation of ‘Flash Xavier A+B in parallel’ is taking longer than expected. Do you want to continue installing this package?”. After I clicked no and tried to flash it again, I got the /dev/ttyUSB3 error. Here is my output log for reference. SDKM_logs_DRIVE_OS_5.2.6_SDK_Linux_for_DRIVE_AGX_Developer_Kit_2021-11-02_20-56-50.zip (271.3 KB)
I have clicked yes before and there doesn’t appear to be any progress and then the message about taking longer than expected pops up again so it appears that the process seems to be stuck.
I also have the same issue when trying to flash the target. After restart the host PC, the " /dev/ttyUSB3 error" disappeared, but the flashing progress stuck at 99%. I also noticed that there is an error about ttyUSB3, I guess it could be related with the issue.