Drive AGX instaltion failed with SDK Manager

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

This what i am doing:
usb before reset:
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

Running on the board:
NvShell>tegrarecovery x1 off
Info: Executing cmd: tegrarecovery, argc: 2, args: x1 off
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-0x4ea20b8
MCU_FOH: ErrReport: ErrorCode-0x1802 ReporterId-0xe00e Error_Attribute-0x0 Timestamp-0x4ea2d10
MCU_FOH: ErrReport: ErrorCode-0x1800 ReporterId-0x8013 Error_Attribute-0x89abcdef Timestamp-0x4ea39b8
MCU_FOH: ErrReport: ErrorCode-0x1 ReporterId-0x800b Error_Attribute-0x0 Timestamp-0x4ea5308
MCU_FOH: ErrReport: ErrorCode-0x1 ReporterId-0x800c Error_Attribute-0x0 Timestamp-0x4ea5488
MCU_FOH: ErrReport: ErrorCode-0x28cb ReporterId-0x8001 Error_Attribute-0x34000008 Timestamp-0x4f9c4e8
MCU_FOH: ErrReport: ErrorCode-0x28cb ReporterId-0x8001 Error_Attribute-0x4c000008 Timestamp-0x5018690
MCU_FOH: ErrReport: ErrorCode-0x2000 ReporterId-0xe004 Error_Attribute-0x0 Timestamp-0x8aa65d0
MCU_FOH: ErrReport: ErrorCode-0x28cb ReporterId-0x8001 Error_Attribute-0x38000001 Timestamp-0xc91eed0
INFO : MCU_ISTMGR: IST Manager initialized to send/receive commands

Usb after the reset:
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

The USB C cable is conneced to the closest port to the ethernet port.
Thanks
Oren

‘tegrarecovery x1 on’ and then ‘tegrareset x1’. Thanks.

Please share the result of the steps. Thanks.

Dear @oren.s ,
Could you provide any update?

HI,

I have decides to try on a fresh computer, so it took some time to organise it.
This it what i am doing:

  1. I have installed a new sdk manager.
  2. on ttyACM1 (nvshell) i ran:
    NvShell>tegrarecovery x1 off
    Info: Executing cmd: tegrarecovery, argc: 2, args: x1 off
    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-0x4e5dd02
    MCU_FOH: ErrReport: ErrorCode-0x1802 ReporterId-0xe00e Error_Attribute-0x0 Timestamp-0x4e5e95a
    MCU_FOH: ErrReport: ErrorCode-0x1800 ReporterId-0x8013 Error_Attribute-0x89abcdef Timestamp-0x4e5f61a
    MCU_FOH: ErrReport: ErrorCode-0x1 ReporterId-0x800b Error_Attribute-0x0 Timestamp-0x4e60f82
    MCU_FOH: ErrReport: ErrorCode-0x1 ReporterId-0x800c Error_Attribute-0x0 Timestamp-0x4e61102
    MCU_FOH: ErrReport: ErrorCode-0x28cb ReporterId-0x8001 Error_Attribute-0x34000008 Timestamp-0x4f57152
    MCU_FOH: ErrReport: ErrorCode-0x28cb ReporterId-0x8001 Error_Attribute-0x4c000008 Timestamp-0x5001602
    MCU_FOH: ErrReport: ErrorCode-0x28c7 ReporterId-0xe04c Error_Attribute-0x0 Timestamp-0x8a52d4a
    MCU_FOH: ErrReport: ErrorCode-0x2000 ReporterId-0xe004 Error_Attribute-0x0 Timestamp-0x8a53212
    MCU_FOH: ErrReport: ErrorCode-0x28cb ReporterId-0x8001 Error_Attribute-0x38000001 Timestamp-0xc91e792

NvShell>INFO : MCU_ISTMGR: IST Manager initialized to send/receive commands
3. i logged out of the serial
4. installing sdk manager 6.0.6


5. lsusb:
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 004: ID 048d:5702 Integrated Technology Express, Inc. ITE Device
Bus 001 Device 005: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I have both micros usb and usn type c cables connected(the type c cable is connected to the port near the network cable)
6. the installation returned the below error: 10:34:34 INFO: Flash DRIVE OS - flash: chromium-codecs-ffmpeg-extra gstreamer1.0-vaapi

10:34:34 INFO: Flash DRIVE OS - flash: libgstreamer-plugins-bad1.0-0 libva-wayland2

10:34:34 INFO: Flash DRIVE OS - flash: Use ‘sudo apt autoremove’ to remove them.

10:34:35 INFO: Flash DRIVE OS - flash: The following NEW packages will be installed:

10:34:35 INFO: Flash DRIVE OS - flash: python-is-python3

10:34:35 INFO: Flash DRIVE OS - flash: 0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded.

10:34:35 INFO: Flash DRIVE OS - flash: Need to get 2,364 B of archives.

10:34:35 INFO: Flash DRIVE OS - flash: After this operation, 10.2 kB of additional disk space will be used.

10:34:35 INFO: Flash DRIVE OS - flash: Get:1 Index of /ubuntu focal/main amd64 python-is-python3 all 3.8.2-4 [2,364 B]

10:34:35 INFO: Flash DRIVE OS - flash: Fetched 2,364 B in 0s (13.1 kB/s)

10:34:35 INFO: Flash DRIVE OS - flash: Selecting previously unselected package python-is-python3.

10:34:36 INFO: Flash DRIVE OS - flash: (Reading database … (Reading database … 5% (Reading database … 10% (Reading database … 15% (Reading database … 20% (Reading database … 25% (Reading database … 30% (Reading database … 35% (Reading database … 40% (Reading database … 45% (Reading database … 50% (Reading database … 55% (Reading database … 60% (Reading database … 65% (Reading database … 70% (Reading database … 75% (Reading database … 80% (Reading database … 85% (Reading database … 90% (Reading database … 95% (Reading database … 100% (Reading database … 236505 files and directories currently installed.)

10:34:36 INFO: Flash DRIVE OS - flash: Preparing to unpack …/python-is-python3_3.8.2-4_all.deb …

10:34:36 INFO: Flash DRIVE OS - flash: Unpacking python-is-python3 (3.8.2-4) …

10:34:36 INFO: Flash DRIVE OS - flash: Setting up python-is-python3 (3.8.2-4) …

10:34:37 INFO: Flash DRIVE OS - flash: Adding user platforms@EYESIGHT.local' to group dialout’ …

10:34:37 INFO: Flash DRIVE OS - flash: Adding user platforms@EYESIGHT.local to group dialout

10:34:37 INFO: Flash DRIVE OS - flash: Done.

10:34:37 INFO: Flash DRIVE OS - flash: # mount targetfs img to update the EULA metadata and unmount on exit

10:34:37 INFO: Flash DRIVE OS - flash: sudo mount -t ext4 ${NV_WORKSPACE}/drive-linux/filesystem/targetfs.img ${NV_WORKSPACE}/drive-linux/filesystem/targetfs

10:34:37 INFO: Flash DRIVE OS - flash: trap “sudo umount -l ${NV_WORKSPACE}/drive-linux/filesystem/targetfs.img” EXIT

10:34:37 INFO: Flash DRIVE OS - flash: # Must lazy umount after operations on rootfs image before running new Build-FS instance.

10:34:37 INFO: Flash DRIVE OS - flash: # Check for errors in umount as it is a pre-req for next step.

10:34:37 INFO: Flash DRIVE OS - flash: # Clear trap if umount is good.

10:34:37 INFO: Flash DRIVE OS - flash: sudo umount -l ${NV_WORKSPACE}/drive-linux/filesystem/targetfs.img

10:34:38 INFO: Flash DRIVE OS - flash: host sudo password for platforms@EYESIGHT.local:

10:34:38 INFO: Flash DRIVE OS - flash: This script must be run with root privileges!

10:34:38 INFO: Flash DRIVE OS - flash: driveinstaller v2.0

10:34:38 INFO: Flash DRIVE OS - flash: SDK/PDK Installer and Flasher

10:34:38 INFO: Flash DRIVE OS - flash: Run ./driveinstaller --help for usage information.

10:34:38 INFO: Flash DRIVE OS - flash: Initializing board and OS configuration to Autonomous vehicle p3710 Linux Tegra A

10:34:38 INFO: Flash DRIVE OS - flash: Manifest version 2.0

10:34:38 INFO: Flash DRIVE OS - flash: [target] target sudo password for nvidia:

10:34:55 INFO: Flash DRIVE OS - flash: BOARD SKU : 940-63710-0010-D00

10:34:55 INFO: Flash DRIVE OS - flash: Found matching board id p3710-10-s05 in 940-63710-0010-D00 sku

10:34:55 INFO: Flash DRIVE OS - flash: Applying additional Bind opts

10:35:03 INFO: Flash DRIVE OS - flash: Binding of partitions failed ! Check log for more details.

10:35:03 INFO: Flash DRIVE OS - flash: Failed to bind partitions!

10:35:03 INFO: Flash DRIVE OS - flash: driveinstaller cannot continue! Check the log file for details: /home/platforms@EYESIGHT.local/.nvsdkm/driveinstaller.log

10:35:03 INFO: Flash DRIVE OS - flash: [ Component Install Finished with Error ]

10:35:03 INFO: Flash DRIVE OS - flash: [host] [ 20.24 MB used. Disk Avail: 350.95 GB ]

10:35:03 INFO: Flash DRIVE OS - flash: [ NV_DRIVE_FLASH_DRIVE_COMP Install took 29s ]

10:35:03 ERROR: Flash DRIVE OS - flash: command terminated with error

10:35:03 SUMMARY: Flash DRIVE OS - flash: First Error: Installation failed.
driveinstaller.log (80.9 KB)
sdkm.db (288 KB)
sdkm.log (886.3 KB)
sdkm-2023-05-30-10-02-27.log (886.3 KB)
sdkm_download.log (115.7 KB)

Logs attached

Thanks,
Oren

Dear @oren.s,
It looks like bind partition is failing.
Do you see any issue on target before you flash DRIVE OS 6.0.6?

HI,

No. it had happened on two computeres.
which partition is it trying to bind?
Thanks,
Oren

Dear @oren.s,
Could you clarify below things before we make new suggestion?

  1. Is the target booting correctly and are you able to access Tegra and aurix console via minicom
  2. What is the DRIVE OS version on target before you flash?
  3. Did you check flash using docker? If not, please give a try.