Drive AGX instaltion failed with SDK Manager

Autonomous Vehicles DRIVE AGX Orin DRIVE AGX Orin General
22

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

23

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

Please share the result of the steps. Thanks.

24

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

25

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

sdk_6.0.6
sdk_6.0.61400×900 165 KB

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

26

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?

27

HI,

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

28

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.
29
  1. yes.
    i can logon on
    /dev/ttyACM0(linux)
    /dev/ttyACM1(nvshell)
    /dev/ttyACM2 - no access
    /dev/ttyACM3 - no access
  2. I dont know what i had before the upgrdade. it’s a new board and we nevet got to use it.
  3. yes. i have tried using docker. look at my post from the May 16

Thanks,
Oren

30

Dear @oren.s,
Please run cat /etc/nvidia/version-ubuntu-rootfs.txt on Tegra linux console to confirm the DRIVE OS version.

You seems to be using a different command for installation via docker. Please check Set Up DRIVE OS Linux with NVIDIA GPU Cloud (NGC) | NVIDIA Docs

31

This is what i get:
nvidia@tegra-ubuntu:~$ cat /etc/nvidia/version-ubuntu-rootfs.txt
6.0.3.0-30270381

Thanks
Oren

34

Dear @oren.s,
May I know if you are flashing the board first time after you receive.
Per Requirements for Your Development Environment | NVIDIA Docs ,

6.0.3-> 6.0.6 is not a valid migration path. Please check flashing 6.0.4 using sdamanager/docker.

35

HI,

no. i have tried flashing it many times.
The first flash didnt end well(no gui) and since then we were not able ti flash it back without error.

Thanks,
Oren

36

hi,

Should i follow this: Set Up DRIVE OS Linux with NVIDIA GPU Cloud (NGC) | NVIDIA Docs and no use the sdk manager?

Thanks
Oren

37

Dear @oren.s,
Please check with sdkmanager first. If it does not work, you may pull DRIVE OS 6.0.4 image from NGC to check flashing.

38

HI,

I am trying with the sdk manager, and i got many error.

6.0.4
6.0.41392×894 217 KB

I will look for the image.
This is the error log:
08:41:38 INFO: DRIVE OS SDK Master Deb - target_image: Package nv-driveos-foundation-release-sdk-flash-data-6.0.4.0-31009903 is not configured yet.

08:41:38 ERROR: DRIVE OS SDK Master Deb - target_image: dpkg: error processing package nv-driveos-foundation-release-sdk-6.0.4.0-31009903 (–configure):

08:41:38 INFO: DRIVE OS SDK Master Deb - target_image: dependency problems - leaving unconfigured

08:41:38 INFO: DRIVE OS SDK Master Deb - target_image: Setting up nv-driveos-common-build-fs-17.1.7-2063a38a (17.1.7-2063a38a) …

08:41:38 INFO: DRIVE OS SDK Master Deb - target_image: dpkg: dependency problems prevent configuration of nv-driveos-linux-oss-minimal-sdk-6.0.4.0-31006010:

08:41:38 INFO: DRIVE OS SDK Master Deb - target_image: nv-driveos-linux-oss-minimal-sdk-6.0.4.0-31006010 depends on nv-driveos-linux-oss-minimal-sdk-kernel-6.0.4.0-31006010; however:

08:41:38 INFO: DRIVE OS SDK Master Deb - target_image: Package nv-driveos-linux-oss-minimal-sdk-kernel-6.0.4.0-31006010 is not configured yet.

08:41:38 INFO: DRIVE OS SDK Master Deb - target_image: nv-driveos-linux-oss-minimal-sdk-6.0.4.0-31006010 depends on nv-driveos-linux-oss-minimal-sdk-core-6.0.4.0-31006010; however:

08:41:38 INFO: DRIVE OS SDK Master Deb - target_image: Package nv-driveos-linux-oss-minimal-sdk-core-6.0.4.0-31006010 is not configured yet.

08:41:38 ERROR: DRIVE OS SDK Master Deb - target_image: dpkg: error processing package nv-driveos-linux-oss-minimal-sdk-6.0.4.0-31006010 (–configure):

08:41:38 INFO: DRIVE OS SDK Master Deb - target_image: dependency problems - leaving unconfigured

08:41:38 INFO: DRIVE OS SDK Master Deb - target_image: Setting up nv-driveos-foundation-release-sdk-flash-tools-6.0.4.0-31009903 (6.0.4.0-31009903) …

08:41:38 ERROR: DRIVE OS SDK Master Deb - target_image: No apport report written because MaxReports is reached already

08:41:44 INFO: DRIVE OS SDK Master Deb - target_image: Reading package nv-driveos-foundation-release-sdk-flash-tools-6.0.4.0-31009903

08:41:44 INFO: DRIVE OS SDK Master Deb - target_image: Installing package from /opt/nvidia/driveos/6.0.4.0/31009903/drive-foundation to /home/platforms@EYESIGHT.local/nvidia/nvidia_sdk/DRIVE_OS_6.0.4_SDK_Linux_DRIVE_AGX_ORIN_DEVKITS/DRIVEOS//drive-foundation

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: Installing t186ref foundation package

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: Installation completed.

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: Errors were encountered while processing:

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: nv-driveos-linux-oss-src-6.0.4.0-31006010

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: nv-driveos-foundation-gcc-bootlin-gcc9.3-armv7-eabihf–glibc–stable-2020.08-1

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: nv-driveos-foundation-gcc-bootlin-gcc9.3-armv5-eabi–glibc–stable-2020.08-1

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: nv-driveos-linux-nv-minimal-sdk-usermode-buildfs-6.0.4.0-31006010

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: nv-driveos-foundation-release-sdk-flash-data-6.0.4.0-31009903

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: nv-driveos-foundation-release-sdk-core-flash-tools-6.0.4.0-31009903

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: nv-driveos-linux-nv-minimal-sdk-base-6.0.4.0-31006010

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: nv-driveos-linux-oss-minimal-sdk-core-6.0.4.0-31006010

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: nv-driveos-linux-nv-minimal-sdk-usermode-compute-6.0.4.0-31006010

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: nv-driveos-linux-oss-minimal-sdk-kernel-6.0.4.0-31006010

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: nv-driveos-linux-nv-minimal-sdk-usermode-graphics-6.0.4.0-31006010

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: nv-driveos-linux-initramfs-6.0.4.0-31006010

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: nv-driveos-linux-nv-minimal-sdk-6.0.4.0-31006010

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: nv-driveos-foundation-toolchains-9.3.0

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: nv-driveos-foundation-release-sdk-core-flash-data-6.0.4.0-31009903

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: nv-driveos-linux-driveos-core-ubuntu-20.04-rfs-6.0.4.0-31006010

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: nv-driveos-build-sdk-linux-6.0.4.0-31010564

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: nv-driveos-foundation-release-sdk-virtualization-6.0.4.0-31009903

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: nv-driveos-linux-nv-minimal-sdk-usermode-nvstreams-6.0.4.0-31006010

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: nv-driveos-foundation-release-sdk-6.0.4.0-31009903

08:41:47 INFO: DRIVE OS SDK Master Deb - target_image: nv-driveos-linux-oss-minimal-sdk-6.0.4.0-31006010

08:41:48 ERROR: DRIVE OS SDK Master Deb - target_image: E: Sub-process /usr/bin/dpkg returned an error code (1)

08:41:48 INFO: DRIVE OS SDK Master Deb - target_image: [ Package Install Finished with Error ]

08:41:48 INFO: DRIVE OS SDK Master Deb - target_image: [host] [ 6.59 GB released. Disk Avail: 314.45 GB ]

08:41:48 INFO: DRIVE OS SDK Master Deb - target_image: [ NV_DRIVE_MASTER_DEB_SDK_COMP Install took 4m3s ]

08:41:48 ERROR: DRIVE OS SDK Master Deb - target_image: command terminated with error

08:41:48 SUMMARY: DRIVE OS SDK Master Deb - target_image: First Error: Failed to install debian repository file [host]

Download folder:

39

@oren.s
To ensure the system can be set into recovery mode, we kindly request you to follow these steps:

  1. Execute the following commands on the aurix console (through /dev/ttyACM1):
    NvShell> tegrarecovery x1 on
    NvShell> tegrareset x1

  2. Execute the following commands on the host machine and provide us with their outputs:
    $ lsusb
    $ dmesg -T

Additionally, it would be helpful if you could let us know if you received a USB C cable with the system. If you did, please use it to connect the Ubuntu Host PC to the LEFT USB Type-C port on the Developer System.

By providing us with the requested outputs and information, we will be able to further assist you in resolving the issue. Thank you for your cooperation.

40

cable connection nvidia
cable connection nvidia1920×2560 632 KB

HI,

I have connected the USB cable supplied in the box as in the attached image.
lsusb before board reset:
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

nvshell log
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-0x4fa20bd
MCU_FOH: ErrReport: ErrorCode-0x1802 ReporterId-0xe00e Error_Attribute-0x0 Timestamp-0x4fa2475
MCU_FOH: ErrReport: ErrorCode-0x1800 ReporterId-0x8013 Error_Attribute-0x89abcdef Timestamp-0x4fa311d
MCU_FOH: ErrReport: ErrorCode-0x1 ReporterId-0x800b Error_Attribute-0x0 Timestamp-0x4fa8815
MCU_FOH: ErrReport: ErrorCode-0x1 ReporterId-0x800c Error_Attribute-0x0 Timestamp-0x4fa899d
MCU_FOH: ErrReport: ErrorCode-0x28cb ReporterId-0x8001 Error_Attribute-0x34000008 Timestamp-0x50066c5
MCU_FOH: ErrReport: ErrorCode-0x28cb ReporterId-0x8001 Error_Attribute-0x4c000008 Timestamp-0x500d2a5
MCU_FOH: ErrReport: ErrorCode-0x28c7 ReporterId-0xe04c Error_Attribute-0x0 Timestamp-0x8afe565
MCU_FOH: ErrReport: ErrorCode-0x2000 ReporterId-0xe004 Error_Attribute-0x0 Timestamp-0x8afea1d
MCU_FOH: ErrReport: ErrorCode-0x28cb ReporterId-0x8001 Error_Attribute-0x38000001 Timestamp-0xca21e1d
INFO : MCU_ISTMGR: IST Manager initialized to send/receive commands

After nvshell commands, running on host(pc):
You can see the logs in the attached nvidia_dmesg.txt
nvidia_dmesg.txt (228.2 KB)

Thanks,
Oren

42

Dear @oren.s,
Could you share below info to assist you furthur.

  1. Could you share your serial number. You may share via PM if can not be shared publicly?
  2. Is the system worked well when received ? Were you able to successfully flash the board in past before you see this issue? We would like to know what happened in between when you tried to flash 6.0.3 to 6.0.6. You just want to upgrade the DRIVE OS version and hence you attempted flashing or you notice any issue on target and checking flashing to fix it?
  3. Is the system used in bench(office table) all the time or used in vehicle as well?
  4. Do you notice any damage to USB port?
  5. Is it possible to get remote access to your machine?
43

HI,

  1. my serial number is:
    S/N: 1413022000227
    Model:P3710
  2. HI, it never worked, it didnt come with any os installed. We were never able to flash it correctly.
  3. Only on an office table.
  4. no. the USB ports looks ok from what i can see.
  5. i will check with our IT. Will AnyDesk work for you?

Thanks,
Oren

44

It seems the board already has DRIVE OS 6.0.3 before you try flashing and you are able to access via minicom.

it never worked, it didnt come with any os installed

What do you mean by it never worked? Are you referring to flashing was never worked or the board has issues?