Drive AGX instaltion failed with 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)
DRIVE OS 6.0.4 SDK
other

Target Operating System
Linux
QNX
other

Hardware Platform
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
1.9.2.10884
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

HI,

I have tried to install the my board with the SDK manager.
The sticker says, DRIVE AGX ORIN and that’s what i have chosen in the SDK Manager page.
SDKM_logs_DRIVE_OS_6.0.6_SDK_Linux_for_DRIVE_AGX_Orin_DevKits_2023-04-27_10-51-55.zip (109.4 KB)

Dear @oren.s,
Please see if the discussion in AGX Orin Initial Setup helps.
Also, If this machine has previous DRIVE OS releases, please remove them using sdkmanager before installing new release.

HI,

Yes. i can access both ttyACM0 and ttyACM1.
The driverInatller.log file ios attached.

Thanks,
Oren
driveinstaller.log (333.5 KB)

HI,

i have tried to reinstall the board., and i get the below error:
[2023-05-01 08:57:07,401 root DEBUG utilities.py 294 2408428] [bootburn]: [findTargetBaseBoardName(763)] : baseBoardName found :: p3710-10-s05
[2023-05-01 08:57:07,401 root DEBUG utilities.py 294 2408428] [bootburn]: [findBaseBoardName(3574)] : Detected baseboard with default ChipSku :: p3710-10-s05
[2023-05-01 08:57:07,401 root DEBUG utilities.py 294 2408428] [bootburn]: [updateFindBoardData(354)] : Connected Board Name details :: baseBoard name - p3710-10-s05
[2023-05-01 08:57:07,401 root DEBUG utilities.py 294 2408428] [bootburn]: [GetTegrasAssocWithAurix(507)] : Setting Tegra-A on hold…
[2023-05-01 08:57:07,401 root DEBUG utilities.py 294 2408428] [bootburn]: [GetTegrasAssocWithAurix(509)] : Done
[2023-05-01 08:57:07,401 root DEBUG utilities.py 294 2408428] [bootburn]: [getListTargetsInRecovery(3642)] : Bus 003 Device 033: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2023-05-01 08:57:07,401 root DEBUG utilities.py 294 2408428] [bootburn]: [GetTegrasAssocWithAurix(534)] : Setting Tegra-A in recovery…
[2023-05-01 08:57:07,402 root DEBUG utilities.py 294 2408428] [bootburn]: [GetTegrasAssocWithAurix(538)] : Done
[2023-05-01 08:57:07,402 root DEBUG utilities.py 294 2408428] [bootburn]: [getListTargetsInRecovery(3642)] : Bus 003 Device 033: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2023-05-01 08:57:07,402 root DEBUG utilities.py 294 2408428] [bootburn]: [GetTegrasAssocWithAurix(548)] : No valid Tegra-A … must have a primary SOC
[2023-05-01 08:57:07,402 root DEBUG utilities.py 294 2408428] command line used was:
[2023-05-01 08:57:07,402 root DEBUG utilities.py 294 2408428] [‘/home/orensanderovich/nvidia/nvidia_sdk/DRIVE_OS_6.0.6_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/drive-foundation/tools/flashtools/bootburn/bootburn.py’, ‘–find_board_name’, ‘-x’, ‘/dev/ttyACM1’]
[2023-05-01 08:57:07,402 root DEBUG utilities.py 294 2408428]
[2023-05-01 08:57:07,402 root DEBUG utilities.py 294 2408428]
[2023-05-01 08:57:07,402 root DEBUG utilities.py 294 2408428] e[01;31mCould not put Tegra-A in recoverye[0m
[2023-05-01 08:57:07,402 root DEBUG utilities.py 294 2408428]
[2023-05-01 08:57:07,402 root DEBUG utilities.py 294 2408428] [bootburn]: [exit(82)] : Exception in critical section :<class ‘OSError’>
[2023-05-01 08:57:07,402 root DEBUG utilities.py 294 2408428]
[2023-05-01 08:57:07,402 root DEBUG utilities.py 294 2408428] e[01;31mException caught in bootburn e[0m
[2023-05-01 08:57:07,402 root DEBUG utilities.py 294 2408428] Traceback (most recent call last):
[2023-05-01 08:57:07,403 root DEBUG utilities.py 294 2408428] File “/home/orensanderovich/nvidia/nvidia_sdk/DRIVE_OS_6.0.6_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/drive-foundation/tools/flashtools/bootburn/…/bootburn_t23x_py/bootburn.py”, line 286, in bootburn
[2023-05-01 08:57:07,403 root DEBUG utilities.py 294 2408428] bootburnLib.CheckRecoveryTargets()
[2023-05-01 08:57:07,403 root DEBUG utilities.py 294 2408428] File “/home/orensanderovich/nvidia/nvidia_sdk/DRIVE_OS_6.0.6_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/drive-foundation/tools/flashtools/bootburn/…/bootburn_t23x_py/bootburn_lib.py”, line 3587, in CheckRecoveryTargets
[2023-05-01 08:57:07,403 root DEBUG utilities.py 294 2408428] self.aurix.GetTegrasAssocWithAurix(self.targetConfig.s_AurixPort)
[2023-05-01 08:57:07,403 root DEBUG utilities.py 294 2408428] File “/home/orensanderovich/nvidia/nvidia_sdk/DRIVE_OS_6.0.6_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/drive-foundation/tools/flashtools/bootburn/…/bootburn_t23x_py/bootburn_aurix.py”, line 549, in GetTegrasAssocWithAurix
[2023-05-01 08:57:07,403 root DEBUG utilities.py 294 2408428] AbnormalTermination(“Could not put {} in recovery”.format(name), nverror.NvError_ResourceError)
[2023-05-01 08:57:07,403 root DEBUG utilities.py 294 2408428] File “/home/orensanderovich/nvidia/nvidia_sdk/DRIVE_OS_6.0.6_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/drive-foundation/tools/flashtools/bootburn/…/bootburn_t23x_py/flashtools_nverror.py”, line 249, in AbnormalTermination
[2023-05-01 08:57:07,403 root DEBUG utilities.py 294 2408428] raise OSError(errorCode)
[2023-05-01 08:57:07,403 root DEBUG utilities.py 294 2408428] OSError: 15
[2023-05-01 08:57:07,403 root INFO runner.py 37 2408428] Failed to bind partitions!
[2023-05-01 08:57:07,404 root DEBUG runner.py 39 2408428] Error on line 958
[2023-05-01 08:57:07,404 root DEBUG runner.py 40 2408428] Exception info: Exception Type <class ‘module.errors.FailedToBindPartitionsError’>, Traceback <traceback object at 0x7f78f4aa1788>
[2023-05-01 08:57:07,404 root INFO runner.py 45 2408428] driveinstaller cannot continue! Check the log file for details: /home/orensanderovich/.nvsdkm/driveinstaller.log
[2023-05-01 08:57:07,404 root DEBUG runner.py 62 2408428] Cleaning up…
[2023-05-01 08:57:07,404 root DEBUG utilities.py 137 2408428] Deleting temporary directories…
[2023-05-01 08:57:07,404 root DEBUG utilities.py 139 2408428] Deleting /tmp/pdkinstall-tmp-qhuxi9jz-bind
[2023-05-01 08:57:07,404 root DEBUG runner.py 64 2408428] Closing the log file.

This is the second install attempt.
driveinstaller.log (212.5 KB)

Dear @oren.s,
I see below error in driveinstaller.log

[bootburn]: [GetTegrasAssocWithAurix(548)] : No valid Tegra-A … must have a primary SOC
[2023-04-27 10:52:30,863 root DEBUG utilities.py 294 1381398] command line used was:
[2023-04-27 10:52:30,864 root DEBUG utilities.py 294 1381398] [‘/home/orensanderovich/nvidia/nvidia_sdk/DRIVE_OS_6.0.6_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS/drive-foundation/tools/flashtools/bootburn/bootburn.py’, ‘–find_board_name’, ‘-x’, ‘/dev/ttyACM1’]
[2023-04-27 10:52:30,864 root DEBUG utilities.py 294 1381398]
[2023-04-27 10:52:30,864 root DEBUG utilities.py 294 1381398]
[2023-04-27 10:52:30,864 root DEBUG utilities.py 294 1381398] e[01;31mCould not put Tegra-A in recoverye[0m
[2023-04-27 10:52:30,864 root DEBUG utilities.py 294 1381398]
[2023-04-27 10:52:30,864 root DEBUG utilities.py 294 1381398] [bootburn]: [exit(82)] : Exception in critical section :<class ‘OSError’>

Does the board has any issue with Tegra before flashing? Could you manually check connectiing to tegraA and run tegrarecovery x1 on & tegrareset x1 and confirm if it works?

HI,

II am trying to run tegrarecovery x1 on on:
I ran the commands on ttyACM1:
NvShell>tegrarecovery x1 on
Info: Executing cmd: tegrarecovery, argc: 2, args: x1 on
Command Executed
NvShell>tegrareset x1
Info: Executing cmd: tegrareset, argc: 1, args: x1
NvShell>INFO: MCU_PLTFPWRMGR: Reseting
INFO: BtChn_Cfg: No valid next bootchain loaded
INFO: NVMCU_ORINPWRCTRL: Tegra x1 Boot Chain: A
INFO: MCU_PLTFPWRMGR: Tegra reset trigger is complete !
Command Executed
MCU_FOH: ErrReport: ErrorCode-0x28cb ReporterId-0x8001 Error_Attribute-0x30000008 Timestamp-0x4d7a18c
MCU_FOH: ErrReport: ErrorCode-0x1802 ReporterId-0xe00e Error_Attribute-0x0 Timestamp-0x4d7ade4
MCU_FOH: ErrReport: ErrorCode-0x1800 ReporterId-0x8013 Error_Attribute-0x89abcdef Timestamp-0x4d7ba8c
MCU_FOH: ErrReport: ErrorCode-0x1 ReporterId-0x800b Error_Attribute-0x0 Timestamp-0x4d7d3e4
MCU_FOH: ErrReport: ErrorCode-0x1 ReporterId-0x800c Error_Attribute-0x0 Timestamp-0x4d7d564
MCU_FOH: ErrReport: ErrorCode-0x28cb ReporterId-0x8001 Error_Attribute-0x34000008 Timestamp-0x4e7416c
MCU_FOH: ErrReport: ErrorCode-0x28cb ReporterId-0x8001 Error_Attribute-0x4c000008 Timestamp-0x4f1cd6c
MCU_FOH: ErrReport: ErrorCode-0x28c7 ReporterId-0xe04c Error_Attribute-0x0 Timestamp-0x85d64b4
MCU_FOH: ErrReport: ErrorCode-0x2000 ReporterId-0xe004 Error_Attribute-0x0 Timestamp-0x85d697c
MCU_FOH: ErrReport: ErrorCode-0x28cb ReporterId-0x8001 Error_Attribute-0x38000001 Timestamp-0xc4fafb4
INFO : MCU_ISTMGR: IST Manager initialized to send/receive commands
when i press enter i get back into the shell
What’s next?
Thanks,
Oren

Dear @oren.s,
Do you an additional Nvidia device in lsusb on host after you set the target in recovery mode.

tegrarecovery x1 off # on aurix
tegrareset x1 # On aurix
`lsusb` # host
tegrarecovery x1 on # on aurix
tegrareset x1 # On aurix
`lsusb` # host.  This should show additional Nvidia device entry

Do you see any issue on target and hence you want to flash the target to see if it fix the issue?

HI
After running on aurix:
tegrarecovery x1 off
tegrareset x1
the host reboots
This is what i get on the host after i write lsusb:
vidia@tegra-ubuntu:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The problemis that i dont see gui. how and all insraltions had failed.
Should i install it now?

Dear @oren.s,
Did you check flashing again after running tegrareset command on aurix? May I know the status?
Also, I suggested to check run lsusb on host and not on target(Drive AGX instaltion failed with SDK Manager - #8 by SivaRamaKrishnaNV) . Please confirm if you see an additional NVIDIA device after setting the board in recovery mode.

Note that, the board should be normal mode(run tegrarecovery x1 off && tegrareset x1 on aurix) before trying to flash using sdkmanager. I would also recommend you try flash via docker container to avoid host system related issues.

HI,

I have reflahed the board after the tegrarecovrery. The flahshing still fails.
SDKM_logs_DRIVE_OS_6.0.6_SDK_Linux_for_DRIVE_AGX_Orin_DevKits_2023-05-11_08-46-38.zip (189.3 KB)
I am attahcing logs

This is the lsusb on the host:
lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 8087:0a2a Intel Corp.
Bus 001 Device 005: ID 0bda:8152 Realtek Semiconductor Corp. RTL8152 Fast Ethernet Adapter
Bus 001 Device 004: ID 045e:078c Microsoft Corp. USB Keyboard
Bus 001 Device 003: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 Optical USB Mouse]
Bus 001 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I have there NVIDIA device.

Thanks
Oren

Dear @oren.s,
Lets check below things

  1. Do you see an addition device on host after setting the board in recovery mode and running lsusb on host like mentioned in Drive AGX instaltion failed with SDK Manager - #8 by SivaRamaKrishnaNV. This confirms if the board has any issue.
  2. Please set the board in normal mode(run tegrarecovery x1 off and tegrareset x1 on Aurix) , close all serial connection to target and check flash using docker container to avoid issues related to host system state.
  3. Also, please confirm if the board has any issue before you try flashing. This help to understand the board status and further guidance be provided to resolve the issue.

HI,

  1. No. on the host i dont see any additional nvidia devices:
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 006: ID 8087:0a2a Intel Corp.
    Bus 001 Device 005: ID 0bda:8152 Realtek Semiconductor Corp. RTL8152 Fast Ethernet Adapter
    Bus 001 Device 004: ID 045e:078c Microsoft Corp. USB Keyboard
    Bus 001 Device 003: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 Optical USB Mouse]
    Bus 001 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  2. how do i flash using thw docker container? can i get the docker run command from theSDK?

  3. How can see issues? dmesg?

Thanks,
Oren

  1. Please refer to DriveOS 6.0.4 Flashing Failures - #25 by Keelung and check if your connection is correct. Have you ever flashed on any devkit successfully? Have you followed * DRIVE AGX Orin Developer Kit Hardware Quick Start Guide?
  2. Please refer to Install DRIVE OS Linux Docker Containers from NGC.
  3. Can the devkit boot up? What DRIVE OS version does the current devkit?

Hi,

I have done the following:
I have done the following:

  1. On the host i ran lsusb:
    lsusb
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 006: ID 8087:0a2a Intel Corp.
    Bus 001 Device 005: ID 0bda:8152 Realtek Semiconductor Corp. RTL8152 Fast Ethernet Adapter
    Bus 001 Device 004: ID 045e:078c Microsoft Corp. USB Keyboard
    Bus 001 Device 003: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 Optical USB Mouse]
    Bus 001 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    As can be seen there is only one NVIDIA device on the list
  2. on /dev/ttyACM1:
  3. tegrarecovery x1 off
  4. tegrareset x1
  5. disconncted the serial connection.
  6. install with docker:
    docker run -it --rm sdkmanager:1.9.2.10889-Ubuntu_20.04 --staylogin true --cli install --sudopassword CIP-52-42-WS-NN --checkforupdates true --product Jetson --version 6.0.6 --targetos Linux --host --target DRIVE_AGX_ORIN_DEVKITS --flash all

And i got the below error:
Jetson version 6.0.6 does not support Linux target OS on DRIVE_AGX_ORIN_DEVKITS

should i use an older version?
I am using:
docker run -it --rm sdkmanager:1.9.2.10889-Ubuntu_20.04 --ver
1.9.2.10889

I have also tried installing an older version:
docker run -it --rm sdkmanager:1.9.2.10889-Ubuntu_20.04 --staylogin true --cli install --sudopassword CIP-52-42-WS-NN --checkforupdates true --product Jetson --version 5.1.1 --targetos Linux --host --target JETSON_AGX_ORIN_TARGETS --flash all --additionalsdk ‘DeepStream 6.2’

I got the below error on the terminal log:
This can be validated by running the ‘lsusb’ command on your host, and look for (NVIDIA Corp). │
│ 1. Choose whether to put your Jetson AGX Orin modules into Force Recovery Mode via Manual Setup ││error: Could not detect correct NVIDIA Jetson device connected to USB. Verify that: │
│ or Automatic Setup. Choose Automatic Setup only if the device has already been flashed and is ││1. The device is connected to this host machine with a USB cable. │
│ currently running. ││2. Correct target is selected in STEP 1.

After this error and trying again, i ran on the lsusb on the host:
lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 8087:0a2a Intel Corp.
Bus 001 Device 005: ID 0bda:8152 Realtek Semiconductor Corp. RTL8152 Fast Ethernet Adapter
Bus 001 Device 004: ID 045e:078c Microsoft Corp. USB Keyboard
Bus 001 Device 003: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 Optical USB Mouse]
Bus 001 Device 010: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
As you ca see, the NVIDIA exists…

The board is connected via the micro usb port

Thanks,
Oren

You didn’t see any device with ‘0955:7023’ IDs from ‘lsusb’ command after putting the device into recovery mode by executing ‘tegrarecovery x1 on’ and ‘tegrareset x1’.
So I want to make sure you have correctly set up your devkit. Please help answer my questions below.

Have you ever flashed on any devkit successfully? Have you followed DRIVE AGX Orin Developer Kit Hardware Quick Start Guide? Could you share an image for the connections on the rear panel of your devkit?

Where did you get the command? Don’t you use a DRIVE devkit? Why is there ‘Jetson’ in the command?

In the meantime, Updating Drive OS via docker - #16 by 0xdeadbeef resolved the developer not able to enter recovery mode. You may try if it also helps on your side.

@VickNV and @oren.s , i am using a nvidia ngc docker . I directly used the flash.py script with right arguments.

Make sure that no serial ports used from the orin device while doing flashing. The best approach is to do a clean start on both devkit and host side and try using the flash script, Thats worked for me.

1 Like

HI

I have done:
tegrarecovery x1 off
tegrareset x1

Those are the lsusb i get on my linux hos:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 8087:0a2a Intel Corp.
Bus 001 Device 008: ID 0bda:8152 Realtek Semiconductor Corp. RTL8152 Fast Ethernet Adapter
Bus 001 Device 003: ID 045e:078c Microsoft Corp. USB Keyboard
Bus 001 Device 006: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

there is no device id 0955:7023

Those are the instructions:
3. Connect the USB Type-A-to-USB Type-C Cable (or USB Type-C-to-USB Type-C Cable
depending on your Host PC) from the Ubuntu Host PC to the LEFT USB Type-C port on the
Developer System (for flashing). Do NOT connect the RIGHT USB Type-C port.
4. Connect a DisplayPort Monitor to the DisplayPort labeled (optional).

The left usb c means the one closer ro the ethernet port? I have been trying to flash without any usb-c cable. do i need one?

BTW
when i connect the usb c porst, i dont see any new USB device.

Thanks
Oren

You should try putting the device into recovery mode by executing ‘tegrarecovery x1 on’ and ‘tegrareset x1’ and then check ‘0955:7023’ device.

Yes, the one closer to the Ethernet port. You need this connection to the flash process.

Once you have it connected, you can check if lsusb can detect it after executing ‘tegrarecovery x1 on’ and ‘tegrareset x1’ can put it into recovery mode, or you can go ahead trying install DRIVE OS with SDK Manager (it will do everything by itself).

HI,

I have connected as seen in the picture

  1. I have two cables connected:
    microUSB as serial
    usb C to USB from nvidia to host
  2. i ran:
    NvShell>tegrarecovery x1
    Info: Executing cmd: tegrarecovery, argc: 1, args: x1
    Command Executed
    NvShell>tegrarecovery x1
    Info: Executing cmd: tegrarecovery, argc: 1, args: x1
    Command Executed
    NvShell>
    Those are the my USB ports(only one NVIDIA)
    Bus 002 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. 4-Port USB 3.0 Hub
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 005: ID 8087:0a2a Intel Corp.
    Bus 001 Device 009: ID 0bda:8152 Realtek Semiconductor Corp. RTL8152 Fast Ethernet Adapter
    Bus 001 Device 014: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 Optical USB Mouse]
    Bus 001 Device 012: ID 0955:7045 NVIDIA Corp.
    Bus 001 Device 013: ID 045e:078c Microsoft Corp. 4-Port USB 2.0 Hub
    Bus 001 Device 010: ID 0bda:5411 Realtek Semiconductor Corp. 4-Port USB 2.0 Hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Logs are attached

Thanks,
Oren
SDKM_logs_DRIVE_OS_6.0.6_SDK_Linux_for_DRIVE_AGX_Orin_DevKits_2023-05-21_08-46-13.zip (143.4 KB)

The USB-C to usb cable is working properly on my phone.
BTW the nvidia devide is new, so we bever mnaged to make it work…

Thanks,
Oren

Your second command was incorrect. You should execute ‘tegrareset x1’.

I saw the following messages in your logs so I would suggest you the steps:

  1. follow Repair and Uninstall to uninstall your current DRIVE OS on your host system
  2. reboot/power cycle both your host system and target devkit
  3. install/flash DRIVE OS 6.0.6 with sdkmanager

Please share the logs from sdkmanager if the steps still don’t work on your side.

08:45:00.296 - error: The /dev/ttyACM1 is opened by another application. Please close it before retry flashing.

08:47:53.821 - error: NV_DRIVE_FLASH_DRIVE_COMP@DRIVE_AGX_ORIN_DEVKITS: sed: can’t read ./driveinstaller/manifests/install_pdk_config/av_orin_p3710_driveos_linux_tegraA_install_config.json: No such file or directory