Driver orin Dev kit flashing failed:- Encounter Errors while flashing using bootburn.py script

umit.eroglu · May 25, 2023, 7:28am

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

Put the target in recovery mode


I'm trying install DRIVE OS Linux Debian Packages via container but flashing fails when I use bootburn.py script 
Step 1:

Running following command on host
sudo minicom -D /dev/ttyACM1 
Running following commands on Aurix console
tegrarecovery x1 on 
tegrareset x1

Step 2:

root@6.0.6.0-0004-build-linux-sdk:/drive# drive-foundation/tools/flashtools/bootburn/bootburn.py -b p3710-10-s05 -B qspi
****** 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’]
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(3642)] : Bus 001 Device 008: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[bootburn]: [CheckRecoveryTargets(3600)] : No recovery-target found; Make sure the target device is connected to the
[bootburn]: [CheckRecoveryTargets(3601)] : host and is in recovery mode. Exiting
command line used was:
[‘drive-foundation/tools/flashtools/bootburn/bootburn.py’, ‘-b’, ‘p3710-10-s05’, ‘-B’, ‘qspi’]

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 286, in bootburn
bootburnLib.CheckRecoveryTargets()
File “/drive/drive-foundation/tools/flashtools/bootburn/…/bootburn_t23x_py/bootburn_lib.py”, line 3602, in CheckRecoveryTargets
AbnormalTermination(“ERROR_TARGET_RECOVERY”, nverror.NvError_ResourceError)
File “/drive/drive-foundation/tools/flashtools/bootburn/…/bootburn_t23x_py/flashtools_nverror.py”, line 249, in AbnormalTermination
raise OSError(errorCode)
OSError: 15
root@6.0.6.0-0004-build-linux-sdk:/drive#

Checking the Nvidia device after connecting host and target by running `lsusb’.

$ lsusb
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
Bus 002 Device 003: ID 0424:5807 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 002 Device 002: ID 2109:0820 VIA Labs, Inc. USB3.1 Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 04f3:2a64 Elan Microelectronics Corp. Touchscreen
Bus 001 Device 004: ID 1532:0256 Razer USA, Ltd Razer Blade
Bus 001 Device 003: ID 13d3:56d5 IMC Networks Integrated Camera
Bus 001 Device 008: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
Bus 001 Device 007: ID 8087:0026 Intel Corp.
Bus 001 Device 010: ID 2109:8888 VIA Labs, Inc.
Bus 001 Device 013: ID 03f0:0667 HP, Inc Integrated Camera
Bus 001 Device 012: ID 03f0:0269 HP, Inc
Bus 001 Device 011: ID 03f0:134a HP, Inc Optical Mouse
Bus 001 Device 009: ID 0424:2807 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 001 Device 006: ID 2109:2820 VIA Labs, Inc. USB2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Would you be able to tell me why I’m seen this error and tell me what’s the correct the command to flash the orin devkit?

umit.eroglu · May 25, 2023, 7:54am

I’m trying to flash the Orin devkit using the Docker container method

Welcome to minicom 2.7.1

OPTIONS: I18n
Compiled on Dec 23 2019, 02:06:26.
Port /dev/ttyACM1, 09:38:04

Press CTRL-A Z for help on special keys

MCU_FOH: Spi Transmit Started
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
MCU_FOH: MCU FOH : Power state notification for Orin reset
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: MCU FOH : Power state notification for Orin Power On
MCU_FOH: Spi Transmit Started

Please find logs located at ~/.nvsdkm
nvsdkm_driveinstaller_log.zip (281.1 KB)

SivaRamaKrishnaNV · May 25, 2023, 7:54am

Dear @umit.eroglu,
Please keep the board back in normal mode and follow Set Up DRIVE OS Linux with NVIDIA GPU Cloud (NGC) | NVIDIA Docs to flash using docker

umit.eroglu · May 25, 2023, 8:16am

Welcome to minicom 2.7.1

OPTIONS: I18n
Compiled on Dec 23 2019, 02:06:26.
Port /dev/ttyACM1, 09:56:24

Press CTRL-A Z for help on special keys

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
Reverting the the target in normal mode

MCU_FOH: MCU FOH : Power state notification for Orin reset
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: MCU FOH : Power state notification for Orin Power On

I’ve tried that way as well but it fails, see below

$ 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
root@6.0.6.0-0004-build-linux-sdk:/drive#
root@6.0.6.0-0004-build-linux-sdk:/drive#
root@6.0.6.0-0004-build-linux-sdk:/drive#
root@6.0.6.0-0004-build-linux-sdk:/drive#
root@6.0.6.0-0004-build-linux-sdk:/drive#
root@6.0.6.0-0004-build-linux-sdk:/drive#
root@6.0.6.0-0004-build-linux-sdk:/drive#
root@6.0.6.0-0004-build-linux-sdk:/drive#
root@6.0.6.0-0004-build-linux-sdk:/drive#
root@6.0.6.0-0004-build-linux-sdk:/drive#
root@6.0.6.0-0004-build-linux-sdk:/drive#
root@6.0.6.0-0004-build-linux-sdk:/drive#
root@6.0.6.0-0004-build-linux-sdk:/drive#
root@6.0.6.0-0004-build-linux-sdk:/drive#
root@6.0.6.0-0004-build-linux-sdk:/drive# ./flash.py /dev/ttyACM1 p3710
2023-05-25 08:01:48 INFO : Flashing already set for dual bootchain
2023-05-25 08:01:48 INFO : Flash clean already disabled for persistent partitions
2023-05-25 08:01:48 INFO : Initiating pre-flash check
2023-05-25 08:01:48 INFO : Checking Serial Port Connection
2023-05-25 08:01:48 INFO : Serial Port found /dev/ttyACM1
2023-05-25 08:01:48 INFO : Running basic open/close tests on Serial Port Connection
2023-05-25 08:01:48 INFO : Serial Port is open
2023-05-25 08:01:48 INFO : Flushing input and output buffer, discard all content
2023-05-25 08:01:48 INFO : Serial Port is closed
2023-05-25 08:01:48 INFO : Checking available targets
2023-05-25 08:01:48 INFO : Checking Orin board connection
2023-05-25 08:01:48 INFO : Orin board with Device ID – 0955:7045 found.
2023-05-25 08:01:48 INFO : Orin board device path is /dev/bus/usb/001/008
2023-05-25 08:01:48 INFO : Pre-flash check complete
2023-05-25 08:01:48 INFO : Flashing DRIVE OS Docker
2023-05-25 08:01:48 INFO : driveinstaller v2.0
2023-05-25 08:01:48 INFO :
2023-05-25 08:01:48 INFO : SDK/PDK Installer and Flasher
2023-05-25 08:01:48 INFO : Run ./driveinstaller --help for usage information.
2023-05-25 08:01:48 INFO :
2023-05-25 08:01:48 INFO : Initializing board and OS configuration to Autonomous vehicle p3710 Linux Tegra A
2023-05-25 08:01:48 INFO : Manifest version 2.0
2023-05-25 08:01:48 INFO :
2023-05-25 08:01:52 INFO : Could not fetch board revision. Re-try either by re-connecting board or make sure all serial port processes such as minicom are closed.
2023-05-25 08:01:52 INFO : Failed to bind partitions!
2023-05-25 08:01:52 INFO : driveinstaller cannot continue! Check the log file for details: /drive/driveinstaller/driveinstaller.log
2023-05-25 08:01:52 INFO :
2023-05-25 08:01:52 INFO :
2023-05-25 08:01:52 ERROR : Flashing failed, please contact provider with logs /drive_flashing/log_cmbp5ns9o6a41jdwf23hertkv7l08yiz.txt and /drive/driveinstaller/driveinstaller.log
2023-05-25 08:01:52 ERROR : Traceback (most recent call last):
File “./flash.py”, line 153, in
flash_config(args.board, args.aurixport, args.tegra, args.pct_variant, args.recovery_timeout)
File “./flash.py”, line 143, in flash_config
raise Exception(f’Error {proc.returncode} occurred’)
Exception: Error 140 occurred

root@6.0.6.0-0004-build-linux-sdk:/drive#

driveinstaller.log (74.3 KB)
log_cmbp5ns9o6a41jdwf23hertkv7l08yiz.txt (2.0 KB)

umit.eroglu · May 25, 2023, 8:43am

After rebooting the Orin Dev kit getting a different error shown below but still not able to flash it. I’ve attached the requested logs

~$ 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
root@6.0.6.0-0004-build-linux-sdk:/drive# ./flash.py /dev/ttyACM1 p3710
2023-05-25 08:35:18 INFO : Flashing already set for dual bootchain
2023-05-25 08:35:18 INFO : Flash clean already disabled for persistent partitions
2023-05-25 08:35:18 INFO : Initiating pre-flash check
2023-05-25 08:35:18 INFO : Checking Serial Port Connection
2023-05-25 08:35:18 INFO : Serial Port found /dev/ttyACM1
2023-05-25 08:35:18 INFO : Running basic open/close tests on Serial Port Connection
2023-05-25 08:35:18 INFO : Serial Port is open
2023-05-25 08:35:18 INFO : Flushing input and output buffer, discard all content
2023-05-25 08:35:18 INFO : Serial Port is closed
2023-05-25 08:35:18 INFO : Checking available targets
2023-05-25 08:35:18 INFO : Checking Orin board connection
2023-05-25 08:35:18 INFO : Orin board with Device ID – 0955:7045 found.
2023-05-25 08:35:18 INFO : Orin board device path is /dev/bus/usb/001/008
2023-05-25 08:35:18 INFO : Pre-flash check complete
2023-05-25 08:35:18 INFO : Flashing DRIVE OS Docker
2023-05-25 08:35:18 INFO : driveinstaller v2.0
2023-05-25 08:35:18 INFO :
2023-05-25 08:35:18 INFO : SDK/PDK Installer and Flasher
2023-05-25 08:35:18 INFO : Run ./driveinstaller --help for usage information.
2023-05-25 08:35:18 INFO :
2023-05-25 08:35:18 INFO : Initializing board and OS configuration to Autonomous vehicle p3710 Linux Tegra A
2023-05-25 08:35:18 INFO : Manifest version 2.0
2023-05-25 08:35:18 INFO :
2023-05-25 08:35:30 INFO : BOARD SKU : 940-63710-0010-D00
2023-05-25 08:35:30 INFO : Found matching board id p3710-10-s05 in 940-63710-0010-D00 sku
2023-05-25 08:35:30 INFO : Applying additional Bind opts
2023-05-25 08:35:34 INFO : Binding of partitions failed ! Check log for more details.
2023-05-25 08:35:34 INFO : Failed to bind partitions!
2023-05-25 08:35:34 INFO : driveinstaller cannot continue! Check the log file for details: /drive/driveinstaller/driveinstaller.log
2023-05-25 08:35:34 INFO :
2023-05-25 08:35:34 INFO :
2023-05-25 08:35:34 ERROR : Flashing failed, please contact provider with logs /drive_flashing/log_m82zybku5a1nrpvqogi4j6fxt7ldes3h.txt and /drive/driveinstaller/driveinstaller.log
2023-05-25 08:35:34 ERROR : Traceback (most recent call last):
File “./flash.py”, line 153, in
flash_config(args.board, args.aurixport, args.tegra, args.pct_variant, args.recovery_timeout)
File “./flash.py”, line 143, in flash_config
raise Exception(f’Error {proc.returncode} occurred’)
Exception: Error 140 occurred

root@6.0.6.0-0004-build-linux-sdk:/drive#
driveinstaller.log (91.6 KB)
log_m82zybku5a1nrpvqogi4j6fxt7ldes3h.txt (2.1 KB)

SivaRamaKrishnaNV · May 25, 2023, 1:37pm

Dear @umit.eroglu,
I notice below issue in logs

[2023-05-25 08:35:34,115 root DEBUG utilities.py 294 21] e[01;31mCould not put Tegra-A in recoverye[0m
[2023-05-25 08:35:34,115 root DEBUG utilities.py 294 21]
[2023-05-25 08:35:34,115 root DEBUG utilities.py 294 21] [bootburn]: [exit(82)] : Exception in critical section :<class ‘OSError’>
[2023-05-25 08:35:34,115 root DEBUG utilities.py 294 21]
[2023-05-25 08:35:34,115 root DEBUG utilities.py 294 21] e[01;31mException caught in bootburn e[0m
[2023-05-25 08:35:34,115 root DEBUG utilities.py 294 21] Traceback (most recent call last):

Can you manually check if the board can be set in recovery mode?

Connect to aurix console and run tegrarecovery x1 off and tegrareset x1 and check lsusb output on host
Connect to aurix console and run tegrarecovery x1 on and tegrareset x1 and check lsusb output on host # this set board in recovery mode and additional NVIDIA device is expected in lsusb output.

umit.eroglu · May 25, 2023, 1:52pm

Output for the 1 step
Connect to aurix console and run tegrarecovery x1 off and tegrareset x1 and check lsusb output on host

$ sudo minicom -D /dev/ttyACM1
[sudo] password for adc:
Sorry, try again.
[sudo] password for adc:

Welcome to minicom 2.7.1

OPTIONS: I18n
Compiled on Dec 23 2019, 02:06:26.
Port /dev/ttyACM1, 15:45:36

Press CTRL-A Z for help on special keys

tegrarecovery x1 off
Info: Executing cmd: xxtegrarecovery, argc: 2, args: x1 off
Error: Unknown command
Invalid Command
NvShell>tegrareset x1
Info: Executing cmd: tegrareset, argc: 1, args: x1
NvShell>INFO: MCU_PLTFPWRMGR: Reseting
MCU_FOH: MCU FOH : Power state notification for Orin reset
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: MCU FOH : Power state notification for Orin Power On
MCU_FOH: SOC error pin is de-asserted
MCU_FOH: SOC error pin is asserted
MCU_FOH: Spi Transmit Started
MCU_FOH: ErrReport: ErrorCode-0x1012 ReporterId-0xe00e Error_Attribute-0x0 Timestam0
MCU_FOH: ErrReport: ErrorCode-0x89abcdef ReporterId-0x8013 Error_Attribute-0x0 Time0
MCU_FOH: Periodic Report: KeyOfSeed-0xffff
MCU_FOH: Periodic Report[0]:SystemFailureId-0xabcd, MaturationState-0xef, Failure_A2
MCU_FOH: Periodic Report[9]:SystemFailureId-0x1234, MaturationState-0x56, Failure_Ae
MCU_FOH: ErrReport: ErrorCode-0x28c7 ReporterId-0xe04c Error_Attribute-0x0 Timestam8
MCU_FOH: ErrReport: ErrorCode-0x2855 ReporterId-0xe01d Error_Attribute-0x0 Timestam0
INFO : MCU_ISTMGR: IST Manager initialized to send/receive commands
MCU_FOH: ErrReport: ErrorCode-0x100c ReporterId-0xe00e Error_Attribute-0x0 Timestam0
MCU_FOH: ErrReport: ErrorCode-0x100c ReporterId-0x800e Error_Attribute-0x1002 Times8

$ lsusb
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
Bus 002 Device 003: ID 0424:5807 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 002 Device 002: ID 2109:0820 VIA Labs, Inc. USB3.1 Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 04f3:2a64 Elan Microelectronics Corp. Touchscreen
Bus 001 Device 004: ID 1532:0256 Razer USA, Ltd Razer Blade
Bus 001 Device 003: ID 13d3:56d5 IMC Networks Integrated Camera
Bus 001 Device 008: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
Bus 001 Device 007: ID 8087:0026 Intel Corp.
Bus 001 Device 010: ID 2109:8888 VIA Labs, Inc.
Bus 001 Device 013: ID 03f0:0667 HP, Inc Integrated Camera
Bus 001 Device 012: ID 03f0:0269 HP, Inc
Bus 001 Device 011: ID 03f0:134a HP, Inc Optical Mouse
Bus 001 Device 009: ID 0424:2807 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 001 Device 006: ID 2109:2820 VIA Labs, Inc. USB2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Output for the 2 step

Connect to aurix console and run tegrarecovery x1 on and tegrareset x1 and check lsusb output on host # this set board in recovery mode and additional NVIDIA device is expected in lsusb output.

$ sudo minicom -D /dev/ttyACM1
[sudo] password for adc:

Welcome to minicom 2.7.1

OPTIONS: I18n
Compiled on Dec 23 2019, 02:06:26.
Port /dev/ttyACM1, 15:47:24

Press CTRL-A Z for help on special keys

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
MCU_FOH: MCU FOH : Power state notification for Orin reset
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: MCU FOH : Power state notification for Orin Power On
MCU_FOH: Spi Transmit Started
MCU_FOH: SPI : E2E_P05Check Status : 7 : 0
ERROR: MCU_ERRHANDLER: McuFoh E2E Frame Error
MCU_FOH: SPI : E2E_P05Check Status : 7 : 0
MCU_FOH: SPI : E2E_P05Check Status : 7 : 0

lsusb
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter
Bus 002 Device 003: ID 0424:5807 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 002 Device 002: ID 2109:0820 VIA Labs, Inc. USB3.1 Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 04f3:2a64 Elan Microelectronics Corp. Touchscreen
Bus 001 Device 004: ID 1532:0256 Razer USA, Ltd Razer Blade
Bus 001 Device 003: ID 13d3:56d5 IMC Networks Integrated Camera
Bus 001 Device 008: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
Bus 001 Device 007: ID 8087:0026 Intel Corp.
Bus 001 Device 010: ID 2109:8888 VIA Labs, Inc.
Bus 001 Device 013: ID 03f0:0667 HP, Inc Integrated Camera
Bus 001 Device 012: ID 03f0:0269 HP, Inc
Bus 001 Device 011: ID 03f0:134a HP, Inc Optical Mouse
Bus 001 Device 009: ID 0424:2807 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 001 Device 006: ID 2109:2820 VIA Labs, Inc. USB2.0 Hub
Bus 001 Device 014: ID 0955:7023 NVIDIA Corp. APX
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

SivaRamaKrishnaNV · May 26, 2023, 4:29am

Dear @umit.eroglu,
I see the board can be set into recovery mode manually.
Could you take a look at Updating Drive OS via docker if it helps?

umit.eroglu · May 26, 2023, 7:01am

Well, that’s what I’m trying to do, install it via docker container and seen this problems.

SivaRamaKrishnaNV · May 26, 2023, 7:51am

Dear @umit.eroglu,

As the Tegra/Aurix console is accessible and the board can be manually set into recovery mode. I don’t see any reason for flashing failure. Similar issue was resolved by restarting host, target and check installing via docker. Did you try that?

Is it possible to check installing via sdkmanager to see if works?

umit.eroglu · May 26, 2023, 10:05am

I did reboot the host as well as Orin dev kit it and flashing still fails.
I did try to update via SDK manager and the flashing procedure fails as well.

SivaRamaKrishnaNV · May 26, 2023, 10:21am

Dear @umit.eroglu,
Could you please share ~/.nvsdkm/sdkm*.log and ~/.nvsdkm/logs

kayccc · June 2, 2023, 6:47am

Have you managed to get issue resolved or still need the support? Thanks

umit.eroglu · June 2, 2023, 8:07am

I think I’m ok for time being. If I need help will contact you again, thanks for the help so far.

system · June 27, 2023, 1:34am

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