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
Target Operating System
Linux
QNX
other
Hardware Platform
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
other
SDK Manager Version
1.9.1.10844
other (1.9.3.10904)
Host Machine Version
native Ubuntu 18.04
other
Hi,
I encountered the following error while flashing Drive Xavier.
Is there any solution for this?
thanks.
21:53:37 INFO: Flash Xavier A+B in parallel - flash: Sending bct and prerequisite binaries
21:53:37 INFO: Flash Xavier A+B in parallel - flash: '/home/glad/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DRIVE_AGX_XAVIER/DRIVEOS/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/../../../..//firmwares/bin/t19x/mb1/mb1_t194_prod.bin' -> '/home/glad/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DRIVE_AGX_XAVIER/DRIVEOS/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/_temp_dump/_temp_dump_h4GjIulimo/flash-images/mb1.bin'
21:53:37 INFO: Flash Xavier A+B in parallel - flash: Generating MEM BCT files
21:53:37 INFO: Flash Xavier A+B in parallel - flash: Flashing process exited with error 5
21:53:37 ERROR: Flash Xavier A+B in parallel - flash: command terminated with error
**21:53:38 SUMMARY: Flash Xavier A+B in parallel - flash: First Error: Installation failed.**
21:53:38 DEBUG: running command < true >
Here is my full log.
SDKM_logs_DRIVE_Software_10.0_(rev._2)_Linux_for_DRIVE_AGX_Xavier_2025-01-23_21-16-33.zip (1.6 MB)
Dear @jaeikb38,
What is the current DRIVE release on target?
Also, see Error 5 during flashing helps?
I’m not sure if I fully understood the question, but currently, the target device (Xavier) had Drive OS 5.2.0 installed initially. However, I have been repeatedly trying different methods to install Drive Software 10.0 (rev.2). As a result, no specific version is functioning properly at the moment.
And,
In this topic, it is instructed to place the modified dtb file in the path:
~/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DDPX/DRIVEOS/drive-t186ref-foundation/tools/host/flashtools/flash/t18x/rcmkernel.
However, in my environment, the folder name is DRIVE_Software_10.0_Linux_OS_DRIVE_AGX_XAVIER instead of DRIVE_Software_10.0_Linux_OS_DDPX.
Can I use the same file in this case?
Thank you for your response and support.
Dear @jaeikb38,
Could you provide any update?
Sorry for the late reply.
I have tried flashing multiple times with the zip file from Error 5 during flashing.
As shown below, the error 5 issue has not been resolved.
18:34:20.369 - info: NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP@DDPX: command options used = -b e3550b03-t194 -B qspi -x /dev/ttyUSB15 --updtcfga gos1-fs:dirname:/home/glad/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DRIVE_AGX_XAVIER/DRIVEOS/drive-t186ref-linux/targetfs_a --updtcfgb gos1-fs:dirname:/home/glad/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DRIVE_AGX_XAVIER/DRIVEOS/drive-t186ref-linux/targetfs_b -w
18:34:20.369 - info: NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP@DDPX:
18:34:20.369 - info: NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP@DDPX: ------------ Stack Trace ------------
18:34:20.369 - info: NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP@DDPX: stack frame 0 - 329 AbnormalTermination /home/glad/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DRIVE_AGX_XAVIER/DRIVEOS/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/bootburn_lib.sh
18:34:20.369 - info: NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP@DDPX: stack frame 1 - 48 CheckUSBServiceInit /home/glad/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DRIVE_AGX_XAVIER/DRIVEOS/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/bootburn_adb.sh
18:34:20.369 - info: NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP@DDPX: stack frame 2 - 2942 FlashImages /home/glad/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DRIVE_AGX_XAVIER/DRIVEOS/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/bootburn_lib.sh
18:34:20.447 - info: NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP@DDPX: stack frame 3 - 404 source /home/glad/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DRIVE_AGX_XAVIER/DRIVEOS/drive-t186ref-foundation/tools/host/flashtools/bootburn_t19x/bootburn_active.sh
18:34:20.447 - info: NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP@DDPX: stack frame 4 - 1270 main /home/glad/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DRIVE_AGX_XAVIER/DRIVEOS/drive-t186ref-foundation//tools/host/flashtools/bootburn_t19x/bootburn.sh
18:34:20.447 - info: NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP@DDPX: -------------------------------------
18:34:20.448 - info: NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP@DDPX:
18:34:20.448 - info: NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP@DDPX: Tool OutPut:
18:34:20.448 - info: NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP@DDPX: Bus 001 Device 050: ID 0955:7019 NVidia Corp.
18:34:20.448 - info: NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP@DDPX: Bus 001 Device 051: ID 0955:7100 NVidia Corp. Tegra Device
18:34:20.448 - info: NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP@DDPX: Tool OutPut to stderr:
18:34:20.448 - info: NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP@DDPX: Bus 001 Device 050: ID 0955:7019 NVidia Corp.
18:34:20.448 - info: NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP@DDPX: Bus 001 Device 051: ID 0955:7100 NVidia Corp. Tegra Device
18:34:20.448 - info: NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP@DDPX: error-adb-timeout
18:34:20.776 - info: NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP@DDPX:
18:34:20.776 - info: NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP@DDPX: Flashing process exited with error 5
18:34:20.859 - info: NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP@DDPX: Error in flashing!
18:34:20.859 - info: NV_FLASH_XAVIER_PDKFLASH_PARALLEL_COMP@DDPX: pdkinstaller cannot continue! Check the log file for details: /home/glad/nvidia/nvidia_sdk/DRIVE_Software_10.0_Linux_OS_DRIVE_AGX_XAVIER/DRIVEOS/pdkinstaller/pdkinstaller.log
I’m not sure what the exact issue is, but I suspect that Xavier B might not be functioning normally.
Please check the full log below and guide me on how to resolve this issue.
SDKM_logs_DRIVE_Software_10.0_(rev._2)_Linux_for_DRIVE_AGX_Xavier_2025-02-06_18-02-47.zip (2.5 MB)
Thanks.
What exactly does “current DRIVE release” mean?
Is it the version installed on the target or the one I’m trying to install?
Current version on target (Tegra A and Tegra B). Can you check flashing individual tegra and also change USB port and cables?
Is there a clear way to check the current version on the target device?
I will verify the process of flashing each Tegra module individually and provide an update afterward.
However, I have already tried both USB 3.0 A-to-A and USB 2.0 A-to-A cables, as well as different USB ports on the host.
Please connect to target using minicom or ssh and run cat /etc/nvidia/version-ubuntu-rootfs.txt
To flash an individual Tegra, I attempted to use Drive OS 5.2.6 because Drive Software 10.0 did not provide an option for flashing individual Tegra modules.
As a result, Tegra A was successfully flashed, but Tegra B was not.
Additionally, Tegra B is not responding in Minicom, even though the Minicom settings are correct.
Please check the logs and captures below.
Thanks.
The full log about flashing tegra A :
SDKM_logs_DRIVE_OS_5.2.6_SDK_Linux_for_DRIVE_AGX_Xavier_2025-02-11_22-53-48.zip (1.2 MB)
The full log about flashing tegra B :
SDKM_logs_DRIVE_OS_5.2.6_SDK_Linux_for_DRIVE_AGX_Xavier_2025-02-12_12-17-41.zip (1.2 MB)
Minicom settings :
Tegra A on minicom :
Tegra B on minicom :
Is tegra B working earlier?
Could you try accessing tegra B from Tegra A using ssh nvidia@10.42.0.29 ? Can you reset tegra B/aurix from aurix console and see if can be accessed? Please refer to https://docs.nvidia.com/drive/drive-os-5.2.6.0L/drive-os/index.html#page/DRIVE_OS_Linux_SDK_NGC_Development_Guide/MCU%20Setup%20and%20Configuration/mcu_console_usage.html#wwconnect_header
Please try below commands
tegrarecovery x2 off
tegrarecovery x1 off
aurixreset
tegrareset x1
Please check flashing Tegra B after running these commands to see if helps?
No, the result is the same even after executing the command.
I also cannot connect from Tegra A to Tegra B via SSH.
Dear @jaeikb38 ,
I suspect some issue with tegra B. Earlier, is it used in office premises? When did you notice issue with access to tegra B?
It is installed and used in the trunk of the car.
I have been trying flashing since December 2024, but I only recently realized that there is an issue with accessing Tegra B.
Kindly review HW errata https://developer.download.nvidia.com/driveworks/secure/docs/hardware_docs/DE-08933-001_v09.pdf (especially #5) and Mechnical installation guide to see if recommendations are followed correctly.
Also, can you share below command output logs on aurix console
showvoltages
tegrareset x1
tegrareset x2
poweroff
poweron
My Autrix console does not have a command called ‘showvoltages.’
Additionally, the logs for other commands are shown below.
NvShell>showvoltages
Info: Executing cmd: showvoltages, argc: 0, args:
Error: Unknown command
Invalid Command
NvShell>tegrareset x1
Info: Executing cmd: tegrareset, argc: 1, args: x1
INFO: PSM_ModMgr: Reseting
INFO: PSM_PwrCtrl: COM Exp card is not detected
INFO: PSM_PwrCtrl: COM Exp is not released from reset
INFO: PSM_PwrCtrl: Tegra x1 Boot Chain: A
INFO: PSM_ModMgr: Command Executed
NvShell>tegrareset x2
Info: Executing cmd: tegrareset, argc: 1, args: x2
INFO: PSM_ModMgr: Reseting
INFO: PSM_PwrCtrl: COM Exp card is not detected
INFO: PSM_PwrCtrl: COM Exp is not released from reset
INFO: PSM_PwrCtrl: Tegra x2 Boot Chain: A
INFO: PSM_ModMgr: Command Executed
NvShell>poweroff
Info: Executing cmd: poweroff, argc: 0, args:
NvShell>INFO: PSM_ModMgr: Powering off
Stop task Nvptp_Task_88E6321_2
Stop task Nvptp_Task_88E6321_1
Stop Nvptp_Task_SJA1105Q
INFO: PSM_EthInit: Ethernet peripherals de-initialized
INFO: PSM_EthInit: Linkup status is not active
INFO: PSM_EthInit: Linkup status is not active
INFO: PSM_IoHwAbs: X1 shutdown notification triggered
INFO: PSM_IoHwAbs: X2 shutdown notification triggered
INFO: PSM_ModMgr: Command executed
NvShell>poweron
Info: Executing cmd: poweron, argc: 0, args:
INFO: PSM_ModMgr: Powering up
INFO: PSM_ModMgr: Powering up
INFO: PSM_IoHwAbs: Power On sequence Triggered.
INFO: PSM_IoHwAbs: Waiting for Voltages to drop below safe margin of 80mV -
INFO: SftyMon_tmon: Temperature sensor initialized
Forced Power On after 30sec timeout
INFO: PSM_PwrCtrl: Detect 2nd Harness is not connected.
INFO: PSM_PwrCtrl: If you are using DGPU, please contact your hardware INFO: PSM_PwrCtrl: representative to get 2nd harness cable
INFO: PSM_PwrCtrl: Configured BootStraps for X1 as QSPI
INFO: PSM_PwrCtrl: Configured BootStraps for X2 as QSPI
INFO: PSM_PwrCtrl: Tegra x1 Boot Chain: A
INFO: PSM_PwrCtrl: Tegra x2 Boot Chain: A
INFO: PSM_PwrCtrl: COM Exp card not detected
INFO: PSM_PwrCtrl: COM Exp card not detected
Init NXP
INFO: PSM_EthInit: Linkup status is not active
INFO: PSM_EthInit: Sja1105Q Link Active
Init Marvell
Init stbm
init_nxp_switch
Applying multicast address filter in Eth_Drv
Initial 88Q2112
Initial 88Q2112 A0 silicon slave address 01
Initial 88Q2112 A0 silicon slave address 02
Initial 88Q2112 A0 silicon slave address 03
Initial 88Q2112 A0 silicon slave address 04
Initial 88Q2112 A0 silicon slave address 05
Initial 88Q2112 A0 silicon slave address 06
Initial 88Q2112 A0 silicon slave address 07
Initial 88e6321_1
Enable 88E6321-1 VLAN
Initial 88e6321_1 port 1 in SGMII Mode.
Initial 88e6321_2
switch 2 DSA Only
Enable VLAN on 88Q5050 for OTA
Default 5050 init for VLAN
INFO: PSM_ModMgr: Command executed
From flashing logs, it looks like HW issue with Tegra B.
Could you provide any suggestions on further diagnosing the hardware issue with Tegra B or recommend steps to resolve it?
Dear @jaeikb38 ,
Could you please check private message
