Screen black out in Drive AGX Orin

Autonomous Vehicles DRIVE AGX Orin DRIVE AGX Orin General
1

DRIVE OS Version: 6.0.6

Issue Description: Flashed DRIVE AGX board with DRIVE OS 6.0.6. The flashing process completed successfully, and the login screen appeared. During an apt update operation, the display froze, and shortly after, the screen became completely blurred. Since then, the board is unresponsive — nothing works on the display.

Connected to the board via the micro-USB debug port (ACM0). In debug mode, the console continuously outputs the following error

ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001
ufshcd_handle_errors(): UECDL value 0x80000001

Current Status:

  • SDK Manager shows the board as greyed out (cannot interact).

  • Able to access NvShell through debug mode on another device.

  • Unable to boot or perform any operations on the DRIVE AGX board.

Request:

Need guidance on:

  • Whether this is a hardware issue or a recoverable software/flash problem.

  • Steps to recover the board and resolve the UFS error.

2

Requesting urgent reply and steps to recover. `

3

Could you please turnoff and on power supply with few seconds gap. Please share host and target connection picture. Confirm if Tegra and aurix console are accessible first? If accessible, check reflashing the target and share the logs.

1 Like
4

Hello @SivaRamaKrishnaNV ,

Thanks for the reply.

  1. Power Cycle:
    I have completely powered off the DRIVE AGX Orin board, waited for a few seconds, and powered it back on. The issue persists — the display remains blurred and unresponsive.

  2. Host and Target Connection:

    • Host PC is connected to the DRIVE AGX Orin via the micro-USB debug port.

    • I am accessing the Aurix console through PuTTY on ACM0.

  3. Aurix and Tegra Console Accessibility:

    • Aurix: Accessible via NvShell.

    • Tegra: Confirmed accessible in recovery mode. After running tegrarecovery in NvShell, the host detects the device:

      lsusb | grep NVIDIA
Bus 001 Device 006 ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator

  4. Re-flashing:
    I have re-flashed the board using SDK Manager with DRIVE OS 6.0.6. The flash completed successfully, and the login screen appeared. However, after performing apt update, the display froze and became blurred again.
    After reboot, the board is stuck, and the Aurix console continuously outputs:

    ufshcd_handle_errors(): UECDL value 0x80000001

I can share the full flashing logs if needed.

Please advise on next steps.

Thank You.

5

There should be two wire connection between host and target. Please check Getting Started section in https://developer.nvidia.com/drive-agx-orin-hardware-quick-start-guide

It indicates the board is in normal mode and not recovery mode.

Is the board working well and Tegra, Aurix console accessible before trying to flash?
Is the board used in office premises are inside car?

7

Hello @SivaRamaKrishnaNV ,

1) Two‑wire connection (host ↔ target):
Yes, both required connections are in place per the Hardware Quick Start Guide:

  • Micro‑USB (DEBUG) → Aurix console

  • USB‑C (LEFT port) → Tegra flashing/recovery

2) Current USB enumeration / Recovery mode:
After running tegrareset followed by tegrarecovery in NvShell, the host now shows:

>>> lsusb | grep -i nvidia

Bus 001 Device 005: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator

Bus 001 Device 006: ID 0955:7023 NVIDIA Corp. APX

3) Was the board working before flashing; console accessibility?

  • Before the issue, the board flashed successfully with DRIVE OS 6.0.6. It booted to the login screen and was operational.

  • Aurix console is accessible (NvShell via ACM0).

  • Tegra is accessible in recovery mode now (as above).

  • The failure occurs after normal usage (e.g., running sudo apt update), where the display froze, then went black, and we began seeing repeated kernel logs:

    ufshcd_handle_errors(): UECDL value 0x80000001

4) Environment (office vs car):
The system is used in an office environment with stable power and grounding (not inside a car).

Thanks.

8

@SivaRamaKrishnaNV Kindly review my previous response and provide the necessary solution at the earliest. This issue is significantly affecting our planned activities, and I request your support on high priority.

Thanks.

9

This indicates, board can go into recovery mode.

Are you able to flash the board now with out any issue? When flashing thr board using sdkmanager, keep the board back in normal mode(run tegrarecovery x1 off & tegrareset x1 on Aurix console). Also, do you have any dependency on DOS 6.0.6.
If not, please check flashing DOS 6.0.10 using docker Install DRIVE OS 6.0.10.0 for NVIDIA Developer Users | NVIDIA Docs

10

Dear @SivaRamaKrishnaNV ,

I am suing the below command to start the image as provided in the documentation( Set Up DRIVE OS Linux with NVIDIA GPU Cloud (NGC) | NVIDIA Docs ):

sudo docker run -it --rm --privileged --net=host
-v /dev/bus/usb:/dev/bus/usb
-v ${WORKSPACE}:/home/nvidia

Flash is failed with error code:

”root@6.0.10.0-0009-build-linux-sdk:/drive# ./flash.py /dev/ttyACM1 p3710
2026-01-12 13:35:22 INFO : Initiating pre-flash check
2026-01-12 13:35:22 INFO : Checking Serial Port Connection
2026-01-12 13:35:22 INFO : Serial Port found /dev/ttyACM1
2026-01-12 13:35:22 INFO : Running basic open/close tests on Serial Port Connection
2026-01-12 13:35:22 INFO : Serial Port is open
2026-01-12 13:35:22 INFO : Flushing input and output buffer, discard all content
2026-01-12 13:35:22 INFO : Serial Port is closed
2026-01-12 13:35:22 INFO : Checking available targets
2026-01-12 13:35:22 INFO : Checking Orin board connection
2026-01-12 13:35:22 INFO : Orin board with Device ID – 0955:7023 found.
2026-01-12 13:35:22 INFO : Orin board with Device ID – 0955:7045 found.
2026-01-12 13:35:22 INFO : Orin board device path is /dev/bus/usb/001/022
2026-01-12 13:35:22 INFO : Orin board device path is /dev/bus/usb/001/013
2026-01-12 13:35:22 INFO : Pre-flash check complete
2026-01-12 13:35:22 INFO : Flashing DRIVE OS Docker

2026-01-12 13:35:39 INFO : driveinstaller v2.0
2026-01-12 13:35:39 INFO :
2026-01-12 13:35:39 INFO : SDK/PDK Installer and Flasher
2026-01-12 13:35:39 INFO : Run ./driveinstaller --help for usage information.
2026-01-12 13:35:39 INFO :
2026-01-12 13:35:39 INFO : Initializing board and OS configuration to Autonomous Vehicle p3710 Linux Tegra A
2026-01-12 13:35:39 INFO : Manifest version 2.0
2026-01-12 13:35:39 INFO :
2026-01-12 13:35:39 INFO : BOARD SKU : 940-63710-0010-100
2026-01-12 13:35:39 INFO : Found matching board id p3710-10-s05 in 940-63710-0010-100 sku
2026-01-12 13:35:39 INFO : Applying additional Bind opts
2026-01-12 13:35:39 INFO : Binding of partitions failed ! Check log for more details.
2026-01-12 13:35:39 INFO : Failed to bind partitions!
2026-01-12 13:35:39 INFO : driveinstaller cannot continue! Check the log file for details: /drive/driveinstaller/driveinstaller.log
2026-01-12 13:35:39 ERROR : Flashing failed, please contact provider with logs /drive_flashing/log_5wb9ncspdgmu4jl32ez1t60aoq78ryhi.txt and /drive/driveinstaller/driveinstaller.log.
root@6.0.10.0-0009-build-linux-sdk:/drive#
root@6.0.10.0-0009-build-linux-sdk:/drive#”

Adding the error log as stored in driveinstaller.log please check below:

”[2026-01-12 13:28:43,545 root DEBUG log_setup.py 62 25] Logging to file: /drive/driveinstaller/driveinstaller.log
[2026-01-12 13:28:43,545 root DEBUG log_setup.py 63 25] This log is being continued by a new invocation of driveinstaller!
[2026-01-12 13:28:43,545 root INFO driveinstaller 806 25] driveinstaller v2.0

SDK/PDK Installer and Flasher
Run ./driveinstaller --help for usage information.

[2026-01-12 13:28:43,545 root DEBUG driveinstaller 812 25] Executing DRIVEInstaller with args [‘–configjson’, ‘/drive/driveinstaller/manifests/install_pdk_config/config.json.set’, ‘–installtype’, ‘bindflash’, ‘–pdkinstalledpath’, ‘/drive’, ‘–boardtype’, ‘ES’, ‘–consoleout’, ‘enable’, ‘–port’, ‘/dev/ttyACM1’]
[2026-01-12 13:28:43,546 root DEBUG driveinstaller 485 25] Target JSON dump : [‘linux’, ‘qnx’, ‘android’, ‘linux-android’]
[2026-01-12 13:28:43,546 root DEBUG driveinstaller 488 25] Master manifest JSON dump {‘version’: 2.0, ‘config_name’: ‘Autonomous Vehicle p3710 Linux Tegra A’, ‘input_config’: {‘sdk_manifest’: ‘common_driveos_config.json’, ‘product_manifests’: , ‘board_platform’: ‘p3710’, ‘hyp_config’: ‘linux’, ‘opt-args’: , ‘bind-opts’: }}
[2026-01-12 13:28:43,546 root INFO driveinstaller 489 25] Initializing board and OS configuration to Autonomous Vehicle p3710 Linux Tegra A
[2026-01-12 13:28:43,546 root INFO driveinstaller 491 25] Manifest version 2.0

[2026-01-12 13:28:43,546 root DEBUG driveinstaller 499 25] product list
[2026-01-12 13:28:43,546 root DEBUG driveinstaller 503 25] target_os is : linux :
[2026-01-12 13:28:43,546 root DEBUG driveinstaller 505 25] target_config sequence linux
[2026-01-12 13:28:43,546 root DEBUG driveinstaller 511 25] SDK manifest JSON dump {‘version’: ‘2.0’, ‘pdkinstall_config’: {‘supported_hostos’: [‘18.04’, ‘20.04’], ‘product_type’: ‘drive’, ‘platform_type’: ‘’, ‘board_mappings’: ‘board_config.json’, ‘multi_os’: {}, ‘envdata’: [{‘name’: ‘NV_INSTALL_LICENSE_BYPASS’, ‘value’: ‘Destination Tegra Dominance’}, {‘name’: ‘_NV_NON_INTERACTIVE’, ‘value’: ‘YES’}], ‘prerun’: ‘_pre_install.sh’, ‘foundation_runfiles’: [‘nv-driveos-foundation-gcc-bootlin-gcc9.3-aarch64*_amd64.deb’, ‘nv-driveos-linux-initramfs*_amd64.deb’], ‘os_map’: }}
[2026-01-12 13:28:43,546 root DEBUG utilities.py 377 25] Setting environment data …
[2026-01-12 13:28:43,546 root DEBUG utilities.py 380 25] Setting environment variable NV_INSTALL_LICENSE_BYPASS to Destination Tegra Dominance
[2026-01-12 13:28:43,546 root DEBUG utilities.py 380 25] Setting environment variable _NV_NON_INTERACTIVE to YES
[2026-01-12 13:28:43,546 root DEBUG driveinstaller 521 25] Board platform set to p3710
[2026-01-12 13:28:43,547 root DEBUG driveinstaller 525 25] Supported boards with inforom [‘p3710’, ‘p3663’, ‘p4024’, ‘p3730’]
[2026-01-12 13:28:43,547 root DEBUG driveinstaller 531 25] Board manifest JSON dump {‘version’: ‘2.0’, ‘InstallModes’: [‘full’, ‘host’, ‘bind’, ‘flash’, ‘bindflash’, ‘recovery’, ‘reset’, ‘install’, ‘download’, ‘makeplatformpkg’, ‘flashplatformpkg’, ‘boardname’], ‘BoardTypes’: [‘ES’, ‘INT’], ‘FOUNDATION_DIR’: ‘drive-foundation’}
[2026-01-12 13:28:43,547 root DEBUG driveinstaller 534 25] Supported boards are [‘18.04’, ‘20.04’]
[2026-01-12 13:28:43,547 root DEBUG driveinstaller 537 25] Board types supported .. [‘ES’, ‘INT’]
[2026-01-12 13:28:43,547 root DEBUG driveinstaller 539 25] Install Modes supported .. [‘full’, ‘host’, ‘bind’, ‘flash’, ‘bindflash’, ‘recovery’, ‘reset’, ‘install’, ‘download’, ‘makeplatformpkg’, ‘flashplatformpkg’, ‘boardname’]
[2026-01-12 13:28:43,547 root DEBUG driveinstaller 648 25] Product OS list : [‘linux’]
[2026-01-12 13:28:43,547 root DEBUG driveinstaller 653 25] Install product config list : [‘linux’]
[2026-01-12 13:28:43,547 root DEBUG driveinstaller 557 25] sdk raw foundation runlist = [‘nv-driveos-foundation-gcc-bootlin-gcc9.3-aarch64*_amd64.deb’, ‘nv-driveos-linux-initramfs*_amd64.deb’]

[2026-01-12 13:28:43,547 root DEBUG driveinstaller 558 25] sdk repo list =

[2026-01-12 13:28:43,547 root DEBUG driveinstaller 559 25] sdk raw target OS runlist =

[2026-01-12 13:28:43,547 root DEBUG driveinstaller 560 25] sdk host raw runlist =

[2026-01-12 13:28:43,547 root DEBUG driveinstaller 561 25] Multi layer SDK/PDK list :
[2026-01-12 13:28:43,547 root DEBUG driveinstaller 562 25] sdk host raw runlist =

[2026-01-12 13:28:43,547 root DEBUG driveinstaller 579 25] Full sdk/pdk raw target install list = [‘nv-driveos-foundation-gcc-bootlin-gcc9.3-aarch64*_amd64.deb’, ‘nv-driveos-linux-initramfs*_amd64.deb’]

[2026-01-12 13:28:43,547 root DEBUG driveinstaller 580 25] Full sdk/pdk host side install list =

[2026-01-12 13:28:43,547 root DEBUG driveinstaller 581 25] Full nop data list =

[2026-01-12 13:28:43,548 root DEBUG driveinstaller 814 25] Parsed CLI arguments: Namespace(config_json=‘/drive/driveinstaller/manifests/install_pdk_config/config.json.set’, sudo_pwd=b’‘, install_type=‘bindflash’, pdk_debpath=’/drive/driveinstaller’, pdk_installedpath=‘/drive/’, board_type=‘ES’, board_platform=‘p3710’, chip_revision=None, sku_num=None, sku_version=None, output_path=None, config_file=None, git_top_path=‘’, port=‘/dev/ttyACM1’, hyp_config=‘linux’, run_list=[‘nv-driveos-foundation-gcc-bootlin-gcc9.3-aarch64*_amd64.deb’, ‘nv-driveos-linux-initramfs*_amd64.deb’], target_os=‘linux’, target_config=‘linux’, supported_os=None, supported_boardtypes=[‘ES’, ‘INT’], supported_boards=None, install_modes=[‘full’, ‘host’, ‘bind’, ‘flash’, ‘bindflash’, ‘recovery’, ‘reset’, ‘install’, ‘download’, ‘makeplatformpkg’, ‘flashplatformpkg’, ‘boardname’], supported_hosts=None, run_hostlist=, host_env=, platform=‘’, product=‘drive’, fnd_path=‘/drive/drive-foundation’, pdk_installpath=‘/drive/driveinstaller/pdk_extract/’, csle_out=‘enable’, version=‘2.0\n’, prerun_script=‘_pre_install.sh’, is_safety=False, target_user=None, target_pwd=None, log_path=‘/drive/driveinstaller’, log_name=‘driveinstaller.log’, eula_accept=‘0’, map_list=None, nop_list=, repo_list=, core_list=, ngc_resource=None, supported_hostos=[‘18.04’, ‘20.04’])
[2026-01-12 13:28:43,548 root DEBUG pdk_bind.py 90 25] InfoROM supported boards [‘p3710’, ‘p3663’, ‘p4024’, ‘p3730’]
[2026-01-12 13:28:43,548 root DEBUG inforom_data_handler.py 84 25] pcbrevision_offset- 108 :
[2026-01-12 13:28:43,548 root DEBUG inforom_data_handler.py 85 25] pcbrevision_size- 2 :
[2026-01-12 13:28:43,549 root DEBUG inforom_data_handler.py 86 25] min_Inforom_version- 6 :
[2026-01-12 13:28:43,549 root DEBUG inforom_data_handler.py 87 25] supported_Inforom_version- 6 :
[2026-01-12 13:28:43,549 root DEBUG inforom_data_handler.py 88 25] Inforom_version_size- 1 :
[2026-01-12 13:28:43,549 root DEBUG inforom_data_handler.py 89 25] Inforom_version_offset- 67 :
[2026-01-12 13:28:43,549 root DEBUG inforom_data_handler.py 128 25] In get_Inforom_dump() /dev/ttyACM1
[2026-01-12 13:28:43,644 root DEBUG inforom_data_handler.py 134 25] Accessing /dev/ttyACM1
[2026-01-12 13:28:43,645 root DEBUG utilities.py 395 25] Spawning child process with args [‘/usr/bin/sudo’, ‘chmod’, ‘777’, ‘/dev/ttyACM1’]
[2026-01-12 13:28:43,749 root DEBUG inforom_data_handler.py 136 25] Opening serial port …
[2026-01-12 13:28:43,750 root DEBUG inforom_data_handler.py 139 25] Aurix port /dev/ttyACM1 is open
[2026-01-12 13:28:49,858 root DEBUG inforom_data_handler.py 120 25] response on /dev/ttyACM1 = [b’version\r\n’, b’Info: Executing cmd: version, argc: 0, args: \r\n’, b’DRIVE-V6.0.9-P3710-AFW-Aurix-StepB-5.14.15\r\n’, b’Command Executed\r\n’, b’NvShell>\r\n’, b’NvShell>‘]
[2026-01-12 13:28:49,858 root DEBUG inforom_data_handler.py 150 25] Aurix version response is version
Info: Executing cmd: version, argc: 0, args:
DRIVE-V6.0.9-P3710-AFW-Aurix-StepB-5.14.15
Command Executed
NvShell>
NvShell>
[2026-01-12 13:28:55,970 root DEBUG inforom_data_handler.py 120 25] response on /dev/ttyACM1 = [b’inforomdump\r\n’, b’Info: Executing cmd: inforomdump, argc: 0, args: \r\n’, b’\r\n’, b’54 41 4F 01 00 40 00 40 1F 53 \r\n’, b’59 53 40 00 31 4D 53 80 00 57 \r\n’, b’53 00 20 1F FF FF FF FF FF FF \r\n’, b’FF FF FF FF FF FF FF FF FF FF \r\n’, b’FF FF FF FF FF FF FF FF FF FF \r\n’, b’FF FF FF FF FF FF FF FF FF FF \r\n’, b’FF FF FF 2A 53 59 53 06 00 40 \r\n’, b’00 27 12 22 20 30 30 31 2D 30 \r\n’, b’31 30 30 2D 30 31 37 33 36 2D \r\n’, b’30 34 39 00 00 00 00 00 00 41 \r\n’, b’4E 33 36 30 37 30 30 32 32 32 \r\n’, b’35 32 34 31 00 00 00 41 4E 41 \r\n’, b’4E 00 00 00 00 FF FF 4C 31 4D \r\n’, b’53 02 00 78 00 30 30 34 2D 30 \r\n’, b’30 30 30 2D 38 31 37 33 36 2D \r\n’, b’39 39 36 00 00 00 00 00 00 04 \r\n’, b’41 41 4E 33 30 30 39 35 30 32 \r\n’, b’32 38 34 32 34 31 00 00 00 00 \r\n’, b’00 00 00 41 4E 01 15 63 2D B0 \r\n’, b’48 00 00 05 FF FF FF FF FF FF \r\n’, b’FF FF FF FF FF FF FF FF FF FF \r\n’, b’FF FF FF FF FF FF FF FF FF FF \r\n’, b’FF FF FF FF FF FF FF FF FF FF \r\n’, b’FF FF FF FF FF FF FF FF FF FF \r\n’, b’FF FF FF FF FF FF FF 40 FF FF \r\n’, b’FF FF FF FF FF FF \r\n’, b’Command Executed\r\n’, b’NvShell>\r\n’, b’NvShell>']
[2026-01-12 13:28:55,970 root DEBUG inforom_data_handler.py 166 25] inforomdump

[2026-01-12 13:28:55,970 root DEBUG inforom_data_handler.py 166 25] Info: Executing cmd: inforomdump, argc: 0, args:

[2026-01-12 13:28:55,970 root DEBUG inforom_data_handler.py 166 25]

[2026-01-12 13:28:55,970 root DEBUG inforom_data_handler.py 166 25] 54 41 4F 01 00 40 00 40 1F 53

[2026-01-12 13:28:55,970 root DEBUG inforom_data_handler.py 166 25] 59 53 40 00 31 4D 53 80 00 57

[2026-01-12 13:28:55,970 root DEBUG inforom_data_handler.py 166 25] 53 00 20 1F FF FF FF FF FF FF

[2026-01-12 13:28:55,970 root DEBUG inforom_data_handler.py 166 25] FF FF FF FF FF FF FF FF FF FF

[2026-01-12 13:28:55,970 root DEBUG inforom_data_handler.py 166 25] FF FF FF FF FF FF FF FF FF FF

[2026-01-12 13:28:55,970 root DEBUG inforom_data_handler.py 166 25] FF FF FF FF FF FF FF FF FF FF

[2026-01-12 13:28:55,970 root DEBUG inforom_data_handler.py 166 25] FF FF FF 2A 53 59 53 06 00 40

[2026-01-12 13:28:55,970 root DEBUG inforom_data_handler.py 166 25] 00 27 12 22 20 30 30 31 2D 30

[2026-01-12 13:28:55,970 root DEBUG inforom_data_handler.py 166 25] 31 30 30 2D 30 31 37 33 36 2D

[2026-01-12 13:28:55,970 root DEBUG inforom_data_handler.py 166 25] 30 34 39 00 00 00 00 00 00 41

[2026-01-12 13:28:55,970 root DEBUG inforom_data_handler.py 166 25] 4E 33 36 30 37 30 30 32 32 32

[2026-01-12 13:28:55,970 root DEBUG inforom_data_handler.py 166 25] 35 32 34 31 00 00 00 41 4E 41

[2026-01-12 13:28:55,970 root DEBUG inforom_data_handler.py 166 25] 4E 00 00 00 00 FF FF 4C 31 4D

[2026-01-12 13:28:55,970 root DEBUG inforom_data_handler.py 166 25] 53 02 00 78 00 30 30 34 2D 30

[2026-01-12 13:28:55,970 root DEBUG inforom_data_handler.py 166 25] 30 30 30 2D 38 31 37 33 36 2D

[2026-01-12 13:28:55,970 root DEBUG inforom_data_handler.py 166 25] 39 39 36 00 00 00 00 00 00 04

[2026-01-12 13:28:55,971 root DEBUG inforom_data_handler.py 166 25] 41 41 4E 33 30 30 39 35 30 32

[2026-01-12 13:28:55,971 root DEBUG inforom_data_handler.py 166 25] 32 38 34 32 34 31 00 00 00 00

[2026-01-12 13:28:55,971 root DEBUG inforom_data_handler.py 166 25] 00 00 00 41 4E 01 15 63 2D B0

[2026-01-12 13:28:55,971 root DEBUG inforom_data_handler.py 166 25] 48 00 00 05 FF FF FF FF FF FF

[2026-01-12 13:28:55,971 root DEBUG inforom_data_handler.py 166 25] FF FF FF FF FF FF FF FF FF FF

[2026-01-12 13:28:55,971 root DEBUG inforom_data_handler.py 166 25] FF FF FF FF FF FF FF FF FF FF

[2026-01-12 13:28:55,971 root DEBUG inforom_data_handler.py 166 25] FF FF FF FF FF FF FF FF FF FF

[2026-01-12 13:28:55,971 root DEBUG inforom_data_handler.py 166 25] FF FF FF FF FF FF FF FF FF FF

[2026-01-12 13:28:55,971 root DEBUG inforom_data_handler.py 166 25] FF FF FF FF FF FF FF 40 FF FF

[2026-01-12 13:28:55,971 root DEBUG inforom_data_handler.py 166 25] FF FF FF FF FF FF

[2026-01-12 13:28:55,971 root DEBUG inforom_data_handler.py 166 25] Command Executed

[2026-01-12 13:28:55,971 root DEBUG inforom_data_handler.py 166 25] NvShell>

[2026-01-12 13:28:55,971 root DEBUG inforom_data_handler.py 166 25] NvShell>
[2026-01-12 13:28:55,973 root DEBUG inforom_data_handler.py 178 25] closed successfully
[2026-01-12 13:28:55,973 root DEBUG inforom_data_handler.py 190 25] Inforom data length: [‘54’, ‘41’, ‘4F’, ‘01’, ‘00’, ‘40’, ‘00’, ‘40’, ‘1F’, ‘53’, ‘59’, ‘53’, ‘40’, ‘00’, ‘31’, ‘4D’, ‘53’, ‘80’, ‘00’, ‘57’, ‘53’, ‘00’, ‘20’, ‘1F’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘2A’, ‘53’, ‘59’, ‘53’, ‘06’, ‘00’, ‘40’, ‘00’, ‘27’, ‘12’, ‘22’, ‘20’, ‘30’, ‘30’, ‘31’, ‘2D’, ‘30’, ‘31’, ‘30’, ‘30’, ‘2D’, ‘30’, ‘31’, ‘37’, ‘33’, ‘36’, ‘2D’, ‘30’, ‘34’, ‘39’, ‘00’, ‘00’, ‘00’, ‘00’, ‘00’, ‘00’, ‘41’, ‘4E’, ‘33’, ‘36’, ‘30’, ‘37’, ‘30’, ‘30’, ‘32’, ‘32’, ‘32’, ‘35’, ‘32’, ‘34’, ‘31’, ‘00’, ‘00’, ‘00’, ‘41’, ‘4E’, ‘41’, ‘4E’, ‘00’, ‘00’, ‘00’, ‘00’, ‘FF’, ‘FF’, ‘4C’, ‘31’, ‘4D’, ‘53’, ‘02’, ‘00’, ‘78’, ‘00’, ‘30’, ‘30’, ‘34’, ‘2D’, ‘30’, ‘30’, ‘30’, ‘30’, ‘2D’, ‘38’, ‘31’, ‘37’, ‘33’, ‘36’, ‘2D’, ‘39’, ‘39’, ‘36’, ‘00’, ‘00’, ‘00’, ‘00’, ‘00’, ‘00’, ‘04’, ‘41’, ‘41’, ‘4E’, ‘33’, ‘30’, ‘30’, ‘39’, ‘35’, ‘30’, ‘32’, ‘32’, ‘38’, ‘34’, ‘32’, ‘34’, ‘31’, ‘00’, ‘00’, ‘00’, ‘00’, ‘00’, ‘00’, ‘00’, ‘41’, ‘4E’, ‘01’, ‘15’, ‘63’, ‘2D’, ‘B0’, ‘48’, ‘00’, ‘00’, ‘05’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘40’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’, ‘FF’]
[2026-01-12 13:28:55,973 root DEBUG inforom_data_handler.py 191 25] In get_Target_uniqueId()
[2026-01-12 13:28:55,973 root DEBUG inforom_data_handler.py 192 25] Inforom data length: 256
[2026-01-12 13:28:55,973 root DEBUG inforom_data_handler.py 205 25] Found InfoROM header : OAT
[2026-01-12 13:28:55,973 root DEBUG inforom_data_handler.py 213 25] version data : 6
[2026-01-12 13:28:55,973 root DEBUG inforom_data_handler.py 224 25] InfoROM version is 6
[2026-01-12 13:28:55,973 root INFO inforom_data_handler.py 234 25] BOARD SKU : 940-63710-0010-100
[2026-01-12 13:28:55,973 root DEBUG inforom_data_handler.py 239 25] pcbrevision_str : 232
[2026-01-12 13:28:55,973 root DEBUG inforom_data_handler.py 242 25] Board lookup 3710
[2026-01-12 13:28:55,974 root DEBUG inforom_data_handler.py 256 25] BOM file : /drive/drive-foundation/platform-config/hardware/nvidia/platform/t23x/automotive/flashing/board_configs/baseboard_sku_mapping.json
[2026-01-12 13:28:55,974 root DEBUG inforom_data_handler.py 263 25] {‘p3710-10-a01’: [‘940-63710-0010-TS1’, ‘940-63710-0010-TS2’, ‘940-63710-0010-A00’, ‘940-63710-0010-000’], ‘p3710-12-a01’: [‘940-63710-0012-TS1’, ‘940-63710-0012-TS2’, ‘940-63710-0012-A00’], ‘p3710-10-a03’: [‘940-63710-0010-TS3’, ‘940-63710-0010-B00’], ‘p3710-12-a03’: [‘940-63710-0012-TS3’, ‘940-63710-0012-B00’], ‘p3710-10-a04’: [‘940-63710-0010-TS4’, ‘940-63710-0010-C00’], ‘p3710-12-a04’: [‘940-63710-0012-TS4’, ‘940-63710-0012-C00’], ‘p3710-10-s05’: [‘940-63710-0010-TS5’, ‘940-63710-0010-D00’, ‘940-63710-0010-RC1’, ‘940-63710-0010-100’, ‘940-63710-0010-200’, ‘940-63710-0010-300’, ‘670-63710-0010-000’], ‘p3710-12-s05’: [‘940-63710-0012-TS5’, ‘940-63710-0012-D00’, ‘940-63710-0012-RC1’, ‘694-63710-0012-RC1’, ‘694-63710-0012-D00’, ‘694-63710-0012-100’, ‘940-63710-0012-100’, ‘670-63710-0012-000’], ‘p3710-20-a01’: [‘940-63710-0020-TS2’], ‘p3663-a01’: [‘940-63663-0000-100’], ‘p3663-01-a02’: [‘940-63663-0001-200’], ‘p3663-02-a02’: [‘940-63663-0002-200’], ‘p4024-a00-a’: [‘940-14024-0000-A00’, ‘940-14024-0000-TS1’, ‘940-14024-0000-TS2’, ‘940-14024-0000-TS3’, ‘940-14024-0000-B00’, ‘940-14024-0000-C00’, ‘670-14024-0000-000’], ‘p4024-a00-b’: [‘940-14024-0000-A00’, ‘940-14024-0000-TS1’, ‘940-14024-0000-TS2’, ‘940-14024-0000-TS3’, ‘940-14024-0000-B00’, ‘940-14024-0000-C00’, ‘670-14024-0000-000’]}
[2026-01-12 13:28:55,974 root DEBUG inforom_data_handler.py 265 25] p3710-10-a01
[2026-01-12 13:28:55,974 root DEBUG inforom_data_handler.py 266 25] [‘940-63710-0010-TS1’, ‘940-63710-0010-TS2’, ‘940-63710-0010-A00’, ‘940-63710-0010-000’]
[2026-01-12 13:28:55,974 root DEBUG inforom_data_handler.py 265 25] p3710-12-a01
[2026-01-12 13:28:55,974 root DEBUG inforom_data_handler.py 266 25] [‘940-63710-0012-TS1’, ‘940-63710-0012-TS2’, ‘940-63710-0012-A00’]
[2026-01-12 13:28:55,974 root DEBUG inforom_data_handler.py 265 25] p3710-10-a03
[2026-01-12 13:28:55,974 root DEBUG inforom_data_handler.py 266 25] [‘940-63710-0010-TS3’, ‘940-63710-0010-B00’]
[2026-01-12 13:28:55,974 root DEBUG inforom_data_handler.py 265 25] p3710-12-a03
[2026-01-12 13:28:55,974 root DEBUG inforom_data_handler.py 266 25] [‘940-63710-0012-TS3’, ‘940-63710-0012-B00’]
[2026-01-12 13:28:55,974 root DEBUG inforom_data_handler.py 265 25] p3710-10-a04
[2026-01-12 13:28:55,974 root DEBUG inforom_data_handler.py 266 25] [‘940-63710-0010-TS4’, ‘940-63710-0010-C00’]
[2026-01-12 13:28:55,974 root DEBUG inforom_data_handler.py 265 25] p3710-12-a04
[2026-01-12 13:28:55,974 root DEBUG inforom_data_handler.py 266 25] [‘940-63710-0012-TS4’, ‘940-63710-0012-C00’]
[2026-01-12 13:28:55,974 root DEBUG inforom_data_handler.py 265 25] p3710-10-s05
[2026-01-12 13:28:55,974 root DEBUG inforom_data_handler.py 266 25] [‘940-63710-0010-TS5’, ‘940-63710-0010-D00’, ‘940-63710-0010-RC1’, ‘940-63710-0010-100’, ‘940-63710-0010-200’, ‘940-63710-0010-300’, ‘670-63710-0010-000’]
[2026-01-12 13:28:55,974 root INFO inforom_data_handler.py 268 25] Found matching board id p3710-10-s05 in 940-63710-0010-100 sku
[2026-01-12 13:28:55,974 root DEBUG inforom_data_handler.py 102 25] sku- {‘p3710’: {}} :
[2026-01-12 13:28:55,975 root DEBUG inforom_data_handler.py 109 25] PCB revision : p3710-10-s05 :
[2026-01-12 13:28:55,975 root DEBUG pdk_bind.py 123 25] Board PCB revision is p3710-10-s05
[2026-01-12 13:28:55,975 root DEBUG pdk_bind.py 150 25] {‘min_ver’: 6, ‘recommended_ver’: 6, ‘header_info’: ‘OAT’, ‘start_byte’: ‘54’, ‘total_size’: 256, ‘validate_board’: ‘yes’, ‘pcbtosku’: ‘yes’, ‘tool’: ‘make/bind_partitions’, ‘fetch_board’: ‘yes’, ‘sku_rev_map’: {‘p3710’: {}}, ‘lookup_table’: [{‘offset’: 108, ‘name’: ‘pcb’, ‘size’: 2, ‘format’: ‘ascii’}, {‘offset’: 67, ‘name’: ‘version’, ‘size’: 1, ‘format’: ‘ascii’}, {‘offset’: 75, ‘name’: ‘skuinfo’, ‘size’: 18, ‘format’: ‘ascii’}]}
[2026-01-12 13:28:55,975 root INFO pdk_bind.py 155 25] Applying additional Bind opts
[2026-01-12 13:28:55,975 root DEBUG pdk_bind.py 156 25] [‘p3710-10-s05’]
[2026-01-12 13:28:55,975 root DEBUG utilities.py 124 25] Created new temporary directory: /tmp/pdkinstall-tmp-ylez18y7-bind
[2026-01-12 13:28:55,975 root DEBUG utilities.py 320 25] pwd is /drive/driveinstaller
[2026-01-12 13:28:55,976 root DEBUG utilities.py 327 25] Executing board_find_cmd python3 /drive/drive-foundation/tools/flashtools/bootburn/bootburn.py --find_board_name -x /dev/ttyACM1
[2026-01-12 13:29:00,420 root DEBUG pdk_bind.py 216 25] Bind partitions failed !
Traceback (most recent call last):
File “module/pdk_bind.py”, line 161, in pdk_bind
File “utils/utilities.py”, line 329, in find_board_name
File “subprocess.py”, line 373, in check_call
subprocess.CalledProcessError: Command ‘python3 /drive/drive-foundation/tools/flashtools/bootburn/bootburn.py --find_board_name -x /dev/ttyACM1’ returned non-zero exit status 75.
[2026-01-12 13:29:00,420 root ERROR pdk_bind.py 217 25] Binding of partitions failed ! Check log for more details.
[2026-01-12 13:29:00,420 root DEBUG utilities.py 294 25] ****** Starting bootburn/bootburn.py ********
[2026-01-12 13:29:00,420 root DEBUG utilities.py 294 25] ********* Starting t23x bootburn py ********
[2026-01-12 13:29:00,420 root DEBUG utilities.py 294 25] Bootburn Starting with arguments [‘/drive/drive-foundation/tools/flashtools/bootburn/bootburn.py’, ‘–find_board_name’, ‘-x’, ‘/dev/ttyACM1’]
[2026-01-12 13:29:00,420 root DEBUG utilities.py 294 25] logfile :: /drive/drive-foundation/tools/flashtools/bootburn_t23x_py/bootburn.txt
[2026-01-12 13:29:00,420 root DEBUG utilities.py 294 25] cwd in setBoardConfigPath :: /drive/drive-foundation/tools/flashtools/bootburn_t23x_py
[2026-01-12 13:29:00,420 root DEBUG utilities.py 294 25] e[01;33m trying hardware folder:
[2026-01-12 13:29:00,420 root DEBUG utilities.py 294 25] /drive/drive-foundation/platform-config/hardware/nvidia/platform/t23x/automotive/flashing/board_configse[0m
[2026-01-12 13:29:00,420 root DEBUG utilities.py 294 25]
[2026-01-12 13:29:00,420 root DEBUG utilities.py 294 25] Default Schema:/drive/drive-foundation/tools/flashtools/bootburn_t23x_py/nv-customer-data-schema.json
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25]
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25] [bootburn]: [GetInfoRom(620)] : Read skuinfo from InfoRom…
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25] [bootburn]: Execute command on Aurix serial port
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25] [bootburn]: [CheckFirmwareisAFW(600)] : AFW firmware found
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25] [bootburn]: [setTargetConfigt23xInfoRomInfo(720)] : 940-63710-0010-100
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25] [bootburn]: [setTargetConfigt23xInfoRomInfo(721)] : None
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25] [bootburn]: [setTargetConfigt23xInfoRomInfo(728)] : ****** s_InforomSkuVersion 100
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25] [bootburn]: [setTargetConfigt23xInfoRomInfo(729)] : ****** s_InforomProdInfo 940-63710-0010
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25] [bootburn]: [findTargetBaseBoardName(767)] : baseBoardName found :: p3710-10-s05
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25] [bootburn]: [findBaseBoardName(3907)] : Detected baseboard with default ChipSku :: p3710-10-s05
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25] [bootburn]: [updateFindBoardData(337)] : Connected Board Name details :: baseBoard name - p3710-10-s05
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25] [bootburn]: [GetTegrasAssocWithAurix(507)] : Setting Tegra-A on hold…
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25] [bootburn]: [GetTegrasAssocWithAurix(509)] : Done
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 001 Device 013: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25] [bootburn]: [GetTegrasAssocWithAurix(534)] : Setting Tegra-A in recovery…
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25] [bootburn]: [GetTegrasAssocWithAurix(538)] : Done
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 001 Device 013: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25] [bootburn]: [GetTegrasAssocWithAurix(552)] : retrying board recovery check…
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 001 Device 013: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25] [bootburn]: [getListTargetsInRecovery(3975)] : Bus 001 Device 021: ID 0955:7023 NVIDIA Corp. APX
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25] p3710-10-s05
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25] logfile :: /drive/drive-foundation/tools/flashtools/bootburn_t23x_py/bootburnTegra-A.txt
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25] cwd in setBoardConfigPath :: /drive/drive-foundation/tools/flashtools/bootburn_t23x_py
[2026-01-12 13:29:00,421 root DEBUG utilities.py 294 25] e[01;33m trying hardware folder:
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25] /drive/drive-foundation/platform-config/hardware/nvidia/platform/t23x/automotive/flashing/board_configse[0m
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25]
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25] cwd in loadBoardGoldenRegsFile :: /drive/drive-foundation/tools/flashtools/bootburn_t23x_py
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25] Default Schema:/drive/drive-foundation/tools/flashtools/bootburn_t23x_py/nv-customer-data-schema.json
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25]
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25] Check finished successfully
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25] Done parsing command line
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25]
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25] [bootburn]: [setTargetConfigt23xInfoRomInfo(720)] : 940-63710-0010-100
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25] [bootburn]: [setTargetConfigt23xInfoRomInfo(721)] : None
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25] [bootburn]: [setTargetConfigt23xInfoRomInfo(728)] : ****** s_InforomSkuVersion 100
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25] [bootburn]: [setTargetConfigt23xInfoRomInfo(729)] : ****** s_InforomProdInfo 940-63710-0010
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25] [bootburn]: [validateTargetBoardName(752)] : boardName p3710-10-s05 matches with the connected board
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25] [bootburnTegra-A]: [GetTargetECID(792)] : Target BR_CID: 0x80012344705DD1A018000000190202C0
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25]
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25] [bootburnTegra-A]: [GetTargetECID(793)] : Target ECID: 0x4705DD1A018000000190202C0
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25]
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25] [bootburnTegra-A]: [CheckFuseForAuthentication(810)] : Target Authentication State : SHA-2
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25] [bootburnTegra-A]: [GenAdbSerialNum(558)] : ADB serial number is 8S2TQ6G1G00000CG40M0
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25] [bootburnTegra-A]: [CheckForDeviceType(908)] : Detected ES production device type
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25] *** in targetConfig, s_BrickOnTCFFlashingFail not found in board_config ***
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25] *** in targetConfig, s_BrickOnFirmwareFlashingFail not found in board_config ***
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25] *** in targetConfig, s_BrickOnFirmwareFlashingFail not found in board_config ***
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25] [bootburnTegra-A]: [BootRCM_CreateFlash(719)] : Creating images - rcm-flash
[2026-01-12 13:29:00,422 root DEBUG utilities.py 294 25] [bootburnTegra-A]: Creating rcm-flash images
[2026-01-12 13:29:00,423 root DEBUG utilities.py 294 25] [bootburnTegra-A]: [BootRCM_CreateFlash(735)] : flashingCFG :: /drive/drive-foundation/tools/flashtools/flashing_kernel/flashing_configs/t23x/quickboot_flashing.cfgself.targetConfig.p_OutDirPath :: /drive/drive-foundation/tools/flashtools/bootburn_t23x_py/__temp_t234/Tegra-A-0943eecc0ad
[2026-01-12 13:29:00,423 root DEBUG utilities.py 294 25] [bootburnTegra-A]: [SkuBlobGen(1505)] : prodInfo :: 940-63710-0010*
[2026-01-12 13:29:00,423 root DEBUG utilities.py 294 25] [bootburnTegra-A]: [SkuBlobGen(1506)] : skuVersion :: 100*
[2026-01-12 13:29:00,423 root DEBUG utilities.py 294 25] [bootburnTegra-A]: [executeShellCommand(163)] : shell command – /drive/drive-foundation/tools/flashtools/flash/nvskuinfo --inbct bct_BR.bct --outbct bct_BR.bct --chip 0x23 --skipValidate -t s --customer-data-blob signed_customer_data.bin failed
[2026-01-12 13:29:00,423 root DEBUG utilities.py 294 25] [bootburnTegra-A]: [executeShellCommand(165)] : Output: Killed
[2026-01-12 13:29:00,423 root DEBUG utilities.py 294 25] :[D]: ./tegrasign_v3.py --sha sha512 --file temp_buffer_file.bin --offset 0 --length 3584 --block 262144
[2026-01-12 13:29:00,423 root DEBUG utilities.py 294 25] :[E]: SignBinaryBlockSize : 975: Error ResourceError (0x9)
[2026-01-12 13:29:00,423 root DEBUG utilities.py 294 25] :[E]: tegrasign invocation failed:[E]: SignBuffer : 1072: Error ResourceError (0x9)
[2026-01-12 13:29:00,423 root DEBUG utilities.py 294 25] :[E]: Failed to Sign BCT:[E]: NvskuinfoUpdateBct : 544: Error ResourceError (0x9)
[2026-01-12 13:29:00,423 root DEBUG utilities.py 294 25] :[E]: Can’t Sign Br Bct:[E]: nvskuinfo_t23x : 728: Error ResourceError (0x9)
[2026-01-12 13:29:00,423 root DEBUG utilities.py 294 25] :[E]: Write output BCT failed
[2026-01-12 13:29:00,423 root DEBUG utilities.py 294 25] :[E]: nvskuinfo : 458: Error ResourceError (0x9)
[2026-01-12 13:29:00,423 root DEBUG utilities.py 294 25]
[2026-01-12 13:29:00,423 root DEBUG utilities.py 294 25] [bootburnTegra-A]: [executeShellCommand(172)] : Return code: 9
[2026-01-12 13:29:00,423 root DEBUG utilities.py 294 25] [bootburnTegra-A]: [SkuBlobGen(1535)] : Incorrect argument to nvskuflash. Exiting
[2026-01-12 13:29:00,423 root DEBUG utilities.py 294 25] command line used was:
[2026-01-12 13:29:00,423 root DEBUG utilities.py 294 25] [‘/drive/drive-foundation/tools/flashtools/bootburn/bootburn.py’, ‘–find_board_name’, ‘-x’, ‘/dev/ttyACM1’]
[2026-01-12 13:29:00,423 root DEBUG utilities.py 294 25]
[2026-01-12 13:29:00,423 root DEBUG utilities.py 294 25]
[2026-01-12 13:29:00,423 root DEBUG utilities.py 294 25] e[01;31ms_ERROR_TOOL_NVSKUFLASH - Incorrect argument to nvskuflashe[0m
[2026-01-12 13:29:00,423 root DEBUG utilities.py 294 25]
[2026-01-12 13:29:00,423 root DEBUG utilities.py 294 25]
[2026-01-12 13:29:00,424 root DEBUG utilities.py 294 25]
[2026-01-12 13:29:00,424 root DEBUG utilities.py 294 25] e[01;31mException 75 raised in bootburn_active e[0m
[2026-01-12 13:29:00,424 root DEBUG utilities.py 294 25] [bootburnTegra-A]: [updateFindBoardData(337)] : Connected Board Name details :: baseBoard name - p3710-10-s05
[2026-01-12 13:29:00,424 root DEBUG utilities.py 294 25] Traceback (most recent call last):
[2026-01-12 13:29:00,424 root DEBUG utilities.py 294 25] File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn.py”, line 141, in bootburn_active
[2026-01-12 13:29:00,424 root DEBUG utilities.py 294 25] bootburnOrin.BootRCM_CreateFlash(“rcm-flash”, l_findBoardOnly=True)
[2026-01-12 13:29:00,424 root DEBUG utilities.py 294 25] File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn_orin.py”, line 738, in BootRCM_CreateFlash
[2026-01-12 13:29:00,424 root DEBUG utilities.py 294 25] self.CreateVDKImages(flashingCFG, self.targetConfig.p_OutDirPath, l_operation)
[2026-01-12 13:29:00,424 root DEBUG utilities.py 294 25] File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn_orin.py”, line 333, in CreateVDKImages
[2026-01-12 13:29:00,424 root DEBUG utilities.py 294 25] self.GenerateImage(self.storageCfgParser.cfgFileList, l_Operation, operationPath)
[2026-01-12 13:29:00,424 root DEBUG utilities.py 294 25] File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn_lib.py”, line 2380, in GenerateImage
[2026-01-12 13:29:00,424 root DEBUG utilities.py 294 25] bctDefines = self.GenerateAllBCTs(l_Image, partitionList, chain)
[2026-01-12 13:29:00,424 root DEBUG utilities.py 294 25] File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn_orin.py”, line 402, in GenerateAllBCTs
[2026-01-12 13:29:00,424 root DEBUG utilities.py 294 25] self.generateBct(bctDefines, operation, outputDir)
[2026-01-12 13:29:00,424 root DEBUG utilities.py 294 25] File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn_orin.py”, line 382, in generateBct
[2026-01-12 13:29:00,424 root DEBUG utilities.py 294 25] self.SkuBlobGen(brBctFile)
[2026-01-12 13:29:00,424 root DEBUG utilities.py 294 25] File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/bootburn_lib.py”, line 1537, in SkuBlobGen
[2026-01-12 13:29:00,424 root DEBUG utilities.py 294 25] AbnormalTermination(errorMsg, nverror.NvError_InvalidArgument)
[2026-01-12 13:29:00,424 root DEBUG utilities.py 294 25] File “/drive/drive-foundation/tools/flashtools/bootburn/../bootburn_t23x_py/flashtools_nverror.py”, line 251, in AbnormalTermination
[2026-01-12 13:29:00,424 root DEBUG utilities.py 294 25] raise OSError(errorCode)
[2026-01-12 13:29:00,424 root DEBUG utilities.py 294 25] OSError: 75
[2026-01-12 13:29:00,424 root INFO runner.py 37 25] Failed to bind partitions!
[2026-01-12 13:29:00,424 root DEBUG runner.py 39 25] Error on line 972
[2026-01-12 13:29:00,425 root DEBUG runner.py 40 25] Exception info: Exception Type <class ‘module.errors.FailedToBindPartitionsError’>, Traceback <traceback object at 0x7d7ca06f5740>
[2026-01-12 13:29:00,425 root INFO runner.py 42 25] driveinstaller cannot continue! Check the log file for details: /drive/driveinstaller/driveinstaller.log
[2026-01-12 13:29:00,425 root DEBUG runner.py 62 25] Cleaning up…
[2026-01-12 13:29:00,425 root DEBUG utilities.py 137 25] Deleting temporary directories…
[2026-01-12 13:29:00,425 root DEBUG utilities.py 139 25] Deleting /tmp/pdkinstall-tmp-ylez18y7-bind
[2026-01-12 13:29:00,425 root DEBUG runner.py 64 25] Closing the log file.”

FYI
lsusb | grep NVIDIA
Bus 001 Device 025: ID 0955:7023 NVIDIA Corp. APX
Bus 001 Device 013: ID 0955:7045 NVIDIA Corp. Tegra On-Platform Operator

Please check properly and provide proper solution

Thanks.

12

Could you please check private message?

13

From the discussion via PM, the board already has DRIVE OS 6.0.10 and able to access the target console via ssh.
Instructions to test GUI samples via VNC is given at Driveworks 5.14 issue with DRIVE AGX Orin

Regarding the below error

This indicates data Link Layer error, specifically indicating that a NAC (Not-Acknowledge) frame was received at the data link layer. It is not expected to impact system functionality. These errors are benign and can be safely ignored unless accompanied by system instability or data transfer failures.

Try using ssh console to access the target and test GUI output of application via VNC.

14

Dear @SivaRamaKrishnaNV @kayccc

Thanks for the support.

The board is up and running and I am able to access internet through Ethernet cable.

I was trying to install Network Manager and enable it to access Wi-Fi. I have tried several methods, still Wi-Fi is not accessible.

Requesting you to provide proper steps so that I can connect through Wi-Fi.

Regards,

Amit

15

Wifi is not supported on DOS 6.0.10

Wifi is not supported. Please see DriveOS 6.0.10 Network Wifi and Bluetooth connectivity issue

1 Like
17

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