Drive OS Migration from 6.0.6 to 6.0.10

stefan65 · March 23, 2025, 4:31am

Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.10.0
DRIVE OS 6.0.8.1
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-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
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
2.1.0
other (2.2.0.12028 x86_64)

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

krishna@krishna:~/Desktop$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.5 LTS
Release: 22.04
Codename: jammy

Issue Description
I intend to upgrade my Orin DevKit from 6.0.6 to 6.0.10
I don’t see SDK Version shows up when I use SDK Manager to upgrade OS.
/dev/ttyASM0 is detected by SDK Manager.

Error String
No Error as such, but from screenshot I’m expecting new SDK version for 6.0.10 to appear so that we can initiate installation. Since SDK manager can proceed to next step, I’m blocked with installation.

Logs
Provide logs in text box instead of image

Please paste the complete application log here. If there are multiple logs, please use multiple text box

SivaRamaKrishnaNV · March 23, 2025, 6:34am

Dear @stefan65 ,
The last supported sdkmanager release is DRIVE OS 6.0.6. Please use docker container to flash DRIVE OS 6.0.10. Please see Install DRIVE OS 6.0.10.0 for NVIDIA Developer Users | NVIDIA Docs for details.

stefan65 · March 23, 2025, 10:23am

Hi Siva,
I got some confusion as the link above is not landing me to the right page to download..

I have docker container
nvcr.io/drive/driveos-sdk/drive-agx--linux--sdk-build-x86

Any specific container I have to download for flashing the Dev Kit with downloaded container.

Thanks
Krishna

stefan65 · March 23, 2025, 10:25am

sudo docker run -it --privileged --net=host -v /dev/bus/usb:/dev/bus/usb -v /drive_flashing:/drive_flashing nvcr.io/drive/driveos-sdk/drive-agx-orin-linux-aarch64-sdk-build-x86:latest

Is the above command you r suggesting ?

SivaRamaKrishnaNV · March 23, 2025, 12:30pm

Yes. Latest tag will latest available DRIVE OS release i.e DRIVE OS 6.0.10. Also, we tested docker containers on Ubuntu 20.04. if it does not work on your host, please check using Ubuntu 20.04
Let us know if you have any issues

stefan65 · March 23, 2025, 9:37pm

Siva,

Good progress, but eventually failed. Attached is the log.

sudo docker run -it --privileged --net=host -v /dev/bus/usb:/dev/bus/usb -v /home/krishna:/drive_flashing nvcr.io/drive/driveos-sdk/drive-agx-orin-linux-aarch64-sdk-build-x86:latest](http://nvcr.io/drive/driveos-sdk/drive-agx-orin-linux-aarch64-sdk-build-x86:latest
./flash.py /dev/ttyACM1 p3710

2025-03-23 21:27:34 INFO : Pre-flash check complete
2025-03-23 21:27:34 INFO : Flashing DRIVE OS Docker
2025-03-23 21:27:54 INFO : driveinstaller v2.0
2025-03-23 21:27:54 INFO :
2025-03-23 21:27:54 INFO : SDK/PDK Installer and Flasher
2025-03-23 21:27:54 INFO : Run ./driveinstaller --help for usage information.
2025-03-23 21:27:54 INFO :
2025-03-23 21:27:54 INFO : Initializing board and OS configuration to Autonomous Vehicle p3710 Linux Tegra A
2025-03-23 21:27:54 INFO : Manifest version 2.0
2025-03-23 21:27:54 INFO :
2025-03-23 21:27:54 INFO : BOARD SKU : 940-63710-0010-200
2025-03-23 21:27:54 INFO : Found matching board id p3710-10-s05 in 940-63710-0010-200 sku
2025-03-23 21:27:54 INFO : Applying additional Bind opts
2025-03-23 21:27:54 INFO : Binding of partitions failed ! Check log for more details.
2025-03-23 21:27:54 INFO : Failed to bind partitions!
2025-03-23 21:27:54 INFO : driveinstaller cannot continue! Check the log file for details: /drive/driveinstaller/driveinstaller.log
2025-03-23 21:27:54 ERROR : Flashing failed, please contact provider with logs /drive_flashing/log_ij1vm93elafdhrq8w7nspx4zyo6tbc2u.txt and /drive/driveinstaller/driveinstaller.log.

driveinstaller.log (28.2 KB)
log_ij1vm93elafdhrq8w7nspx4zyo6tbc2u.txt (1.4 KB)

stefan65 · March 24, 2025, 5:32am

lsusb output inside docker
Bus 003 Device 015: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator

root@6.0.10.0-0009-build-linux-sdk:/drive# ./drive-foundation/make/bind_partitions -b p3710-10-s05 linux
(All Good)

oot@6.0.10.0-0009-build-linux-sdk:/drive# ./drive-foundation/tools/flashtools/bootburn/bootburn.py -b p3710-10-s05 -B qspi --chain C
****** Starting bootburn/bootburn.py ********
********* Starting t23x bootburn py ********
Bootburn Starting with arguments [‘./drive-foundation/tools/flashtools/bootburn/bootburn.py’, ‘-b’, ‘p3710-10-s05’, ‘-B’, ‘qspi’, ‘–chain’, ‘C’]
logfile :: /drive/drive-foundation/tools/flashtools/bootburn_t23x_py/bootburn.txt
cwd in setBoardConfigPath :: /drive/drive-foundation/tools/flashtools/bootburn_t23x_py
trying hardware folder:
/drive/drive-foundation/platform-config/hardware/nvidia/platform/t23x/automotive/flashing/board_configs

cwd in loadBoardGoldenRegsFile :: /drive/drive-foundation/tools/flashtools/bootburn_t23x_py
Default Schema:/drive/drive-foundation/tools/flashtools/bootburn_t23x_py/nv-customer-data-schema.json

Check finished successfully
Done parsing command line

[bootburn]: [getListTargetsInRecovery(3975)] : Bus 003 Device 015: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[bootburn]: [CheckRecoveryTargets(3933)] : No recovery-target found; Make sure the target device is connected to the
[bootburn]: [CheckRecoveryTargets(3934)] : host and is in recovery mode. Exiting
command line used was:
[‘./drive-foundation/tools/flashtools/bootburn/bootburn.py’, ‘-b’, ‘p3710-10-s05’, ‘-B’, ‘qspi’, ‘–chain’, ‘C’]

ERROR_TARGET_RECOVERY

Exception caught in bootburn
Traceback (most recent call last):
File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn.py”, line 271, in bootburn
bootburnLib.CheckRecoveryTargets()
File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn_lib.py”, line 3935, in CheckRecoveryTargets
AbnormalTermination(“ERROR_TARGET_RECOVERY”, nverror.NvError_ResourceError)
File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/flashtools_nverror.py”, line 251, in AbnormalTermination
raise OSError(errorCode)
OSError: 15

SivaRamaKrishnaNV · March 24, 2025, 5:44am

Noticed “Could not put Tegra-A in recovery” message in log.
Could you share

the host and target connection pictures
Also share below output logs to see if additional NVIDIA device is noticed in recovery mode.

#Run below commands on aurix to set board in normal mode
>tegrarecovery x1 off
>tegrareset x1

#Run below command on host
$lsusb #output on host before setting target in recovery mode

#Run below commands on aurix to set board in normal mode
>tegrarecovery x1 on
>tegrareset x1

#Run below command on host
$lsusb #output on host after setting target in recovery mode

#Run below commands on aurix to set board in normal mode
>tegrarecovery x1 off
>tegrareset x1

stefan65 · March 24, 2025, 5:57am

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: MCU_PLTFPWRMGR: VRS11 PG Monitoring disable.
INFO: BtChn_Cfg: No valid next bootchain loaded
INFO: NVMCU_ORINPWRCTRL: Tegra x1 Boot Chain: B
MCU_FOH: SPI : E2E_P05Check Status : 7 : 0
ERROR: MCU_ERRHANDLER: McuFoh E2E Frame Error
INFO: MCU_PLTFPWRMGR: Tegra reset trigger is complete !
Command Executed
MCU_FOH: MCU FOH : Initiate SOC Error Pin Monitoring & SPI communication
MCU_FOH: SOC error pin is de-asserted
MCU_FOH: SOC error pin is asserted
MCU_FOH: Spi Transmit Started
MCU_FOH: SPI : E2E_P05Check Status : 7 : 0
MCU_FOH: ErrReport: ErrorCode-0x28da ReporterId-0xe04c Error_Attribute-0x0 Timestamp-0x600c691
MCU_FOH: ErrReport: ErrorCode-0x28d1 ReporterId-0xe04c Error_Attribute-0x0 Timestamp-0x600c979
MCU_FOH: ErrReport: ErrorCode-0x18540001 ReporterId-0x8001 Error_Attribute-0x0 Timestamp-0x600cc71
MCU_FOH: ErrReport: ErrorCode-0x9 ReporterId-0x800d Error_Attribute-0x0 Timestamp-0x600d0e9
MCU_FOH: ErrReport: ErrorCode-0x18540001 ReporterId-0x8001 Error_Attribute-0x0 Timestamp-0x614c729
MCU_FOH: Periodic Report: KeyOfSeed-0xffff
MCU_FOH: Periodic Report[0]:SystemFailureId-0xabcd, MaturationState-0xef, Failure_Attribute-0x22
MCU_FOH: Periodic Report[9]:SystemFailureId-0x1234, MaturationState-0x56, Failure_Attribute-0xee
INFO: SftyMon_IoHwAbs: PG_VRS11 monitoring started…
INFO : MCU_ISTMGR: IST Manager initialized to send/receive commands
INFO: MCU_SWC_FanControl: max_rpm fan2 : 0
INFO: MCU_SWC_FanControl: maxrpm of fan2 has more than 50 percent deviation against rated maxrpm
MCU_FOH: ErrReport: ErrorCode-0x18550080 ReporterId-0x8001 Error_Attribute-0x0 Timestamp-0x29be1aa1

root@6.0.10.0-0009-build-linux-sdk:/drive# lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0408:30c3 Quanta Computer, Inc. USB2.0 HD UVC WebCam
Bus 003 Device 017: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
Bus 003 Device 002: ID 0b05:19b6 ASUSTek Computer, Inc. N-KEY Device
Bus 003 Device 004: ID 8087:0033 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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: MCU_PLTFPWRMGR: VRS11 PG Monitoring disable.
INFO: BtChn_Cfg: No valid next bootchain loaded
INFO: NVMCU_ORINPWRCTRL: Tegra x1 Boot Chain: B
MCU_FOH: SPI : E2E_P05Check Status : 7 : 0
ERROR: MCU_ERRHANDLER: McuFoh E2E Frame Error
INFO: MCU_PLTFPWRMGR: Tegra reset trigger is complete !
Command Executed
MCU_FOH: MCU FOH : Initiate SOC Error Pin Monitoring & SPI communication
MCU_FOH: Spi Transmit Started
MCU_FOH: SPI : E2E_P05Check Status : 7 : 0
MCU_FOH: SPI : E2E_P05Check Status : 7 : 0
INFO: SftyMon_IoHwAbs: PG_VRS11 monitoring started…
INFO: MCU_SWC_FanControl: max_rpm fan2 : 0
INFO: MCU_SWC_FanControl: maxrpm of fan2 has more than 50 percent deviation against rated maxrpm

NvShell>MCU_FOH: SOC error pin is de-asserted
MCU_FOH: SOC error pin is asserted
MCU_FOH: ErrReport: ErrorCode-0x28da ReporterId-0xe04c Error_Attribute-0x0 Timestamp-0x604fece
MCU_FOH: ErrReport: ErrorCode-0x28d1 ReporterId-0xe04c Error_Attribute-0x0 Timestamp-0x60501be
MCU_FOH: ErrReport: ErrorCode-0x18540001 ReporterId-0x8001 Error_Attribute-0x0 Timestamp-0x60504be
MCU_FOH: ErrReport: ErrorCode-0x9 ReporterId-0x800d Error_Attribute-0x0 Timestamp-0x6050946
MCU_FOH: ErrReport: ErrorCode-0x18540001 ReporterId-0x8001 Error_Attribute-0x0 Timestamp-0x61aab7e
MCU_FOH: Periodic Report: KeyOfSeed-0xffff
MCU_FOH: Periodic Report[0]:SystemFailureId-0xabcd, MaturationState-0xef, Failure_Attribute-0x22
MCU_FOH: Periodic Report[9]:SystemFailureId-0x1234, MaturationState-0x56, Failure_Attribute-0xee

root@6.0.10.0-0009-build-linux-sdk:/drive# lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0408:30c3 Quanta Computer, Inc. USB2.0 HD UVC WebCam
Bus 003 Device 017: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
Bus 003 Device 002: ID 0b05:19b6 ASUSTek Computer, Inc. N-KEY Device
Bus 003 Device 004: ID 8087:0033 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

===================================================

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: MCU_PLTFPWRMGR: VRS11 PG Monitoring disable.
INFO: BtChn_Cfg: No valid next bootchain loaded
INFO: NVMCU_ORINPWRCTRL: Tegra x1 Boot Chain: B
MCU_FOH: SPI : E2E_P05Check Status : 7 : 0
ERROR: MCU_ERRHANDLER: McuFoh E2E Frame Error
INFO: MCU_PLTFPWRMGR: Tegra reset trigger is complete !
Command Executed
MCU_FOH: MCU FOH : Initiate SOC Error Pin Monitoring & SPI communication
MCU_FOH: SOC error pin is de-asserted
MCU_FOH: SOC error pin is asserted
MCU_FOH: Spi Transmit Started
MCU_FOH: SPI : E2E_P05Check Status : 7 : 0
MCU_FOH: ErrReport: ErrorCode-0x28da ReporterId-0xe04c Error_Attribute-0x0 Timestamp-0x6033779
MCU_FOH: ErrReport: ErrorCode-0x28d1 ReporterId-0xe04c Error_Attribute-0x0 Timestamp-0x6033a69
MCU_FOH: ErrReport: ErrorCode-0x18540001 ReporterId-0x8001 Error_Attribute-0x0 Timestamp-0x6033d61
MCU_FOH: ErrReport: ErrorCode-0x9 ReporterId-0x800d Error_Attribute-0x0 Timestamp-0x60341d1
MCU_FOH: ErrReport: ErrorCode-0x18540001 ReporterId-0x8001 Error_Attribute-0x0 Timestamp-0x616dcf1
MCU_FOH: Periodic Report: KeyOfSeed-0xffff
MCU_FOH: Periodic Report[0]:SystemFailureId-0xabcd, MaturationState-0xef, Failure_Attribute-0x22
MCU_FOH: Periodic Report[9]:SystemFailureId-0x1234, MaturationState-0x56, Failure_Attribute-0xee
INFO: SftyMon_IoHwAbs: PG_VRS11 monitoring started…
INFO : MCU_ISTMGR: IST Manager initialized to send/receive commands
INFO: MCU_SWC_FanControl: max_rpm fan2 : 0
INFO: MCU_SWC_FanControl: maxrpm of fan2 has more than 50 percent deviation against rated maxrpm
MCU_FOH: ErrReport: ErrorCode-0x18550080 ReporterId-0x8001 Error_Attribute-0x0 Timestamp-0x29bbc589

root@6.0.10.0-0009-build-linux-sdk:/drive# lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0408:30c3 Quanta Computer, Inc. USB2.0 HD UVC WebCam
Bus 003 Device 017: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
Bus 003 Device 002: ID 0b05:19b6 ASUSTek Computer, Inc. N-KEY Device
Bus 003 Device 004: ID 8087:0033 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID

Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

SivaRamaKrishnaNV · March 24, 2025, 6:09am

Noticed below connection is missing from Quick start guide - page 9,

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

Could you please connect it and retry flashing using flash.py

stefan65 · March 24, 2025, 6:26am

File not found.(Quick Start Guide). Can you attach the pdf ?

stefan65 · March 24, 2025, 6:28am

Got it.

stefan65 · March 24, 2025, 6:52am

Thanks Siva,
It worked!!

krishna@krishna:~$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 0408:30c3 Quanta Computer, Inc. USB2.0 HD UVC WebCam
Bus 003 Device 002: ID 0b05:19b6 ASUSTek Computer, Inc. N-KEY Device
Bus 003 Device 004: ID 8087:0033 Intel Corp.
Bus 003 Device 024: ID 0955:7023 NVIDIA Corp. APX
Bus 003 Device 022: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
Bus 003 Device 021: ID 343c:0000 xxxxxxxx USB Type-C Digital AV Adapter
Bus 003 Device 020: ID 05e3:0752 Genesys Logic, Inc. USB Storage
Bus 003 Device 019: ID 05e3:0618 Genesys Logic, Inc. USB2.0 Hub
Bus 003 Device 018: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 007: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
Bus 002 Device 006: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

oot@6.0.10.0-0009-build-linux-sdk:/drive# ./flash.py /dev/ttyACM1 p3710
2025-03-24 06:34:43 INFO : Initiating pre-flash check
2025-03-24 06:34:43 INFO : Checking Serial Port Connection
2025-03-24 06:34:43 INFO : Serial Port found /dev/ttyACM1
2025-03-24 06:34:43 INFO : Running basic open/close tests on Serial Port Connection
2025-03-24 06:34:43 INFO : Serial Port is open
2025-03-24 06:34:43 INFO : Flushing input and output buffer, discard all content
2025-03-24 06:34:43 INFO : Serial Port is closed
2025-03-24 06:34:43 INFO : Checking available targets
2025-03-24 06:34:43 INFO : Checking Orin board connection
2025-03-24 06:34:43 INFO : Orin board with Device ID – 0955:7045 found.
2025-03-24 06:34:43 INFO : Orin board device path is /dev/bus/usb/003/022
2025-03-24 06:34:43 INFO : Pre-flash check complete
2025-03-24 06:34:43 INFO : Flashing DRIVE OS Docker
2025-03-24 06:45:07 INFO : driveinstaller v2.0
2025-03-24 06:45:07 INFO :
2025-03-24 06:45:07 INFO : SDK/PDK Installer and Flasher
2025-03-24 06:45:07 INFO : Run ./driveinstaller --help for usage information.
2025-03-24 06:45:07 INFO :
2025-03-24 06:45:07 INFO : Initializing board and OS configuration to Autonomous Vehicle p3710 Linux Tegra A
2025-03-24 06:45:07 INFO : Manifest version 2.0
2025-03-24 06:45:07 INFO :
2025-03-24 06:45:07 INFO : Invalid response for Aurix command!
2025-03-24 06:45:07 INFO :
2025-03-24 06:45:07 INFO : Attempt 1 to re-send version command
2025-03-24 06:45:07 INFO :
2025-03-24 06:45:07 INFO : BOARD SKU : 940-63710-0010-200
2025-03-24 06:45:07 INFO : Found matching board id p3710-10-s05 in 940-63710-0010-200 sku
2025-03-24 06:45:07 INFO : Applying additional Bind opts
2025-03-24 06:45:07 INFO : Executing bind clean cmd make/bind_partitions -b p3710-10-s05 linux clean
2025-03-24 06:45:07 INFO : Executing bind cmd make/bind_partitions -b p3710-10-s05 linux
2025-03-24 06:45:07 INFO : Bind partitions done!
2025-03-24 06:45:07 INFO : Initializing SDK/PDK flasher for configuration
2025-03-24 06:45:07 INFO : Board: p3710
2025-03-24 06:45:07 INFO : Board type: ES
2025-03-24 06:45:07 INFO : Hypervisor config: linux
2025-03-24 06:45:07 INFO :
2025-03-24 06:45:07 INFO : bypassing inforrom for flashing cmd
2025-03-24 06:45:07 INFO : Pre flash script found! Calling scripts/linux_pre_flash.sh
2025-03-24 06:45:07 INFO : Running flash command: sudo -E /drive/drive-foundation//tools/flashtools/bootburn/bootburn.py -b p3710-10-s05 -B qspi -x /dev/ttyACM1
2025-03-24 06:45:07 INFO : This may take a few minutes
2025-03-24 06:45:07 INFO : Flashing completed successfully
2025-03-24 06:45:07 INFO : See logs at /drive_flashing/log_hcxs74drezijv856tb9wfgo32akynlp0.txt and /drive/driveinstaller/driveinstaller.log

$ ls -al /usr/local/driveworks
driveworks/ driveworks-5.20/

Thanks Siva.

system · April 7, 2025, 6:53am

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Driver orin Dev kit flashing failed:- Encounter Errors while flashing using bootburn.py script DRIVE AGX Orin General drive-platform-setup	14	1194	June 2, 2023
Drive AGX instaltion failed with SDK Manager DRIVE AGX Orin General drive-platform-setup	41	1981	August 30, 2023
Flash failed. Orin no more recoverable or flashable DRIVE AGX Orin General drive-platform-setup	14	630	February 12, 2024
Sdkmanager Drive Orin Flash OS 6.0.6 fails DRIVE AGX Orin General drive-platform-setup	21	1342	September 12, 2023
Failed to flash Drive OS 6.0.10: Unable to read BCT DRIVE AGX Orin General drive-platform-setup	14	78	April 7, 2025
DRIVE Installer failed with status 140 DRIVE AGX Orin General drive-platform-setup	38	2148	March 17, 2023
DriveOS 6.0.4 Flashing Failures DRIVE AGX Orin General drive-platform-setup	36	3025	March 14, 2023
Failing to flash single bootchain with a different DRIVEOS DRIVE AGX Orin General drive-platform-setup	5	48	December 18, 2024
DRIVE Installer failed with status 140 DRIVE AGX Orin General drive-platform-setup	10	841	September 12, 2023
Flashing Drive AGX Orin fails DRIVE AGX Orin General drive-platform-setup	42	2139	August 3, 2023

Drive OS Migration from 6.0.6 to 6.0.10

Related topics