Previously, I was able to get the headless with no monitor attached and set up to work on an Orin-NX 16GB custom board, following these steps.
As I like to upgrade the Jetpack to 6.x, I was unable to revert and get the attached monitor (DP port) to display the contents. When Jetson Orin NX powered up, the monitor only displayed the NVIDIA Logo, and then after it went black, the monitor switched to another input source.
I have uninstalled the xserver-xorg-video-dummy and reverted the conf files.
I noticed my Xorg.0.log file was dated 2024, Jan 31, enabling the full log in Xorg, but it does not change the log or update the log file.
Xorg.0.log (30.6 KB)
/etc/X11/xorg.conf
xorg.conf (692 Bytes)
/etc/X11/xorg.conf.d/tegra-drm-outputclass.conf
tegra-drm-outputclass.conf.log (283 Bytes)
/etc/gdm3/custom.conf
custom.conf.txt (607 Bytes)
Monitor resolution is 1600x900 60Hz
~$ xrandr
Screen 0: minimum 0 x 0, current 3760 x 960, maximum 32768 x 32768
default connected primary 3760x960+0+0 994mm x 253mm
3760x960 0.00*
~$ cat /etc/X11/default-display-manager
/usr/sbin/gdm3
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.6 LTS
Release: 20.04
Codename: focal
deb https://repo.download.nvidia.com/jetson/common r35.3 main
deb https://repo.download.nvidia.com/jetson/t234 r35.3 main
~$ sudo apt-cache show nvidia-jetpack
Package: nvidia-jetpack
Version: 5.1.1-b56
Architecture: arm64
Maintainer: NVIDIA Corporation
Installed-Size: 194
Depends: nvidia-jetpack-runtime (= 5.1.1-b56), nvidia-jetpack-dev (= 5.1.1-b56)
Homepage: http://developer.nvidia.com/jetson
Priority: standard
Section: metapackages
Filename: pool/main/n/nvidia-jetpack/nvidia-jetpack_5.1.1-b56_arm64.deb
Size: 29304
SHA256: 7b6c8c6cb16028dcd141144b6b0bbaa762616d0a47aafa3c3b720cb02b2c8430
SHA1: 387e4e47133c4235666176032af0f2ec86461dbb
MD5sum: 0a8692031bf35cc46f7a498e2937bda9
Description: NVIDIA Jetpack Meta Package
Description-md5: ad1462289bdbc54909ae109d1d32c0a8
Hi,
We can follow the steps and set up correctly on developer kit. Do you re-flash the system to Jetpack 6.2?
No, because I foresee I need to verify the Jetpack upgrade result or any issues during the process from the monitor. So, I need to get the physical monitor connection working before attempting the Jetpack upgrade.
Could this be what I am facing?
vnc server was not able to start by itself, I have to use a command to start it. After it is connected, it shows a black screen on vnc client.
~$ /usr/lib/vino/vino-server
17/06/2025 16:53:24 rfbProcessClientNormalMessage: ignoring unknown encoding type 24
17/06/2025 16:53:24 rfbProcessClientNormalMessage: ignoring unknown encoding type 22
17/06/2025 16:53:24 rfbProcessClientNormalMessage: ignoring unknown encoding type 21
17/06/2025 16:53:24 rfbProcessClientNormalMessage: ignoring unknown encoding type 15
17/06/2025 16:53:24 rfbProcessClientNormalMessage: ignoring unknown encoding type -314
17/06/2025 16:53:24 Enabling NewFBSize protocol extension for client Panasonic-CF33.mshome.net
17/06/2025 16:53:24 Pixel format for client Panasonic-CF33.mshome.net:
17/06/2025 16:53:24 32 bpp, depth 24, little endian
17/06/2025 16:53:24 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
17/06/2025 16:53:24 no translation needed
17/06/2025 16:53:24 rfbProcessClientNormalMessage: ignoring unknown encoding type 24
17/06/2025 16:53:24 rfbProcessClientNormalMessage: ignoring unknown encoding type 22
17/06/2025 16:53:24 rfbProcessClientNormalMessage: ignoring unknown encoding type 21
17/06/2025 16:53:24 rfbProcessClientNormalMessage: ignoring unknown encoding type 15
17/06/2025 16:53:24 rfbProcessClientNormalMessage: ignoring unknown encoding type -314
17/06/2025 16:53:24 Enabling NewFBSize protocol extension for client Panasonic-CF33.mshome.net
17/06/2025 16:53:24 rfbProcessClientNormalMessage: ignoring unknown encoding type 24
17/06/2025 16:53:24 rfbProcessClientNormalMessage: ignoring unknown encoding type 22
17/06/2025 16:53:24 rfbProcessClientNormalMessage: ignoring unknown encoding type 21
17/06/2025 16:53:24 rfbProcessClientNormalMessage: ignoring unknown encoding type 15
17/06/2025 16:53:24 rfbProcessClientNormalMessage: ignoring unknown encoding type -314
17/06/2025 16:53:24 Enabling NewFBSize protocol extension for client Panasonic-CF33.mshome.net
Error while displaying notification bubble: Error calling StartServiceByName for org.freedesktop.Notifications: Process org.freedesktop.Notifications exited with status 1
~$ lspci | grep -i nvidia
0001:00:00.0 PCI bridge: NVIDIA Corporation Device 229e (rev a1)
0004:00:00.0 PCI bridge: NVIDIA Corporation Device 229c (rev a1)
0008:00:00.0 PCI bridge: NVIDIA Corporation Device 229c (rev a1)
~$ sudo cat /etc/nv_tegra_release
# R35 (release), REVISION: 3.1, GCID: 32827747, BOARD: t186ref, EABI: aarch64, DATE: Sun Mar 19 15:19:21 UTC 2023
~$ cat /var/log/Xorg.0.log | grep EE
[ 17.542] Current Operating System: Linux orinnx-1of3 5.10.104-tegra #1 SMP PREEMPT Sun Mar 19 07:55:28 PDT 2023 aarch64
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 17.559] (EE) Screen 1 deleted because of no matching config section.
[ 17.567] (II) Initializing extension MIT-SCREEN-SAVER
After moving nvidia-l4t-apt-source.list slowly from r35.3->r35.4->r35.5->r35.6, it seems there is a good chance to recover the physical DP port connection signal.
/etc/X11/xorg.conf.t194_ref new conf introduced
xorg.conf.t194_ref.txt (1.1 KB)
How do I add a new mode created using xrandr?
Oh dear, no way to do it.
~$ gtf 1600 900 60
# 1600x900 @ 60.00 Hz (GTF) hsync: 55.92 kHz; pclk: 119.00 MHz
Modeline "1600x900_60.00" 119.00 1600 1696 1864 2128 900 901 904 932 -HSync +Vsync
~$ xrandr --newmode "1600x900_60.00" 119.00 1600 1696 1864 2128 900 901 904 932 -HSync +Vsync
~$ xrandr --addmode Screen 0 "1600x900_60.00"
~$ xrandr --addmode DP-0 "1600x900_60.00"
~$ xrandr --addmode HDMI-0 "1600x900_60.00"
xrandr: cannot find output "Screen" "Screen-0" "DP-0" "HDMI-0"
~$ xrandr
Screen 0: minimum 0 x 0, current 1440 x 960, maximum 32768 x 32768
default connected primary 1440x960+0+0 994mm x 253mm
1440x960 0.00*
~$ sudo apt-cache show nvidia-jetpack
Package: nvidia-jetpack
Version: 5.1.5-b11
Architecture: arm64
Maintainer: NVIDIA Corporation
Installed-Size: 194
Depends: nvidia-jetpack-runtime (= 5.1.5-b11), nvidia-jetpack-dev (= 5.1.5-b11)
Homepage: http://developer.nvidia.com/jetson
Priority: standard
Section: metapackages
Filename: pool/main/n/nvidia-jetpack/nvidia-jetpack_5.1.5-b11_arm64.deb
Size: 29300
SHA256: 6d2a8716f57b840d9aa6a4493d71e5ace82cd82bd58e589857856b28dba3e420
SHA1: ef65c88bb4cc56074458426273b1ad7461e49644
MD5sum: 04602fccb306209b5e53f731b94c5bfd
Description: NVIDIA Jetpack Meta Package
Description-md5: ad1462289bdbc54909ae109d1d32c0a8
Package: nvidia-jetpack
Version: 5.1.4-b17
Architecture: arm64
Maintainer: NVIDIA Corporation
Installed-Size: 194
Depends: nvidia-jetpack-runtime (= 5.1.4-b17), nvidia-jetpack-dev (= 5.1.4-b17)
Homepage: http://developer.nvidia.com/jetson
Priority: standard
Section: metapackages
Filename: pool/main/n/nvidia-jetpack/nvidia-jetpack_5.1.4-b17_arm64.deb
Size: 29298
SHA256: 5439dabb8d7a097c215602f7cd11773e4745c5e7d5841d9a0a2551a58b82883e
SHA1: b0c2faa6a9d14e056e394625a11a1a8ed8780327
MD5sum: 05fc4b73de35fd33a535fb887c1947ee
Description: NVIDIA Jetpack Meta Package
Description-md5: ad1462289bdbc54909ae109d1d32c0a8
~$ sudo cat /etc/nv_tegra_release
# R35 (release), REVISION: 6.2, GCID: 40633251, BOARD: t186ref, EABI: aarch64, DATE: Fri May 16 02:08:18 UTC 2025
Hi,
It seems like versions of the deb packages do not match so the system is in unknown status. Is there a chance to completely re-flash the system?
Is there a way to confirm before this big re-flash effort?
Is the effort comparable to flashing it to Jetpack 6.2?
Without a healthy DisplayPort signal and monitor, will it going to be more challenging to re-flash?
I have another board, and I am still able to do headless VNC. I slowly upgraded the board B to r35.6.2. Then I compared their BSP differences. Board A is the problem board.
Is there any insight to potentially fix it without reflashing?
Hi,
Status of the board is unique so we may not be able to suggest next. It is better to re-flash it.
Where is the step-by-step guide?
Can I go directly to Jetpack 6.2 (R36.4.3)?
Hi,
Please follow the steps in
Quick Start — NVIDIA Jetson Linux Developer Guide
Steps are like:
- Download and extract the packages to have Linux_for_Tegra folder ready
- Connect developer kit to host PC through type-A to C adapter, and let developer kit enter recovery mode
- Run initrd command to flash the system image
I cannot find steps for Orin NX, am I correct I should follow the command for Jetson Orin Nano Developer Kit (NVMe):?
Or are you referring to this?
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -p "-c ./bootloader/generic/cfg/flash_t234_qspi.xml" -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --network usb0 jetson-orin-nano-devkit external
Hi,
The developer kit is Orin NX module + Orin Nano carrier board. Please run this command to flash it:
> Jetson Orin Nano Developer Kit (NVMe):
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 \
-c tools/kernel_flash/flash_l4t_t234_nvme.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" \
--showlogs --network usb0 jetson-orin-nano-devkit internal
Actually, after rearranging them, both are quite identical except for the words “internal” and “external” at the end.
One example comes with a period “.” and your suggestion does not, do you foresee any issue?
And do you know why Waveshare recommend external and not internal?
Hi,
The option is applied for AGX Orin modules which have internal eMMC. For Orin NX and Orin Nano, it does not take effect. Please set either external or internal.
Can I also take this opportunity to get the super Mode into ORIN NX 16GB​ (SUPER) for this board? Am I correct that the board supported, and I can use this command jetson-orin-nano-devkit-super?
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 \
-c tools/kernel_flash/flash_l4t_t234_nvme.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" \
--showlogs --network usb0 jetson-orin-nano-devkit-super external
Hi,
The mode can be enabled on developer kit. On custom board, there is further requirement and please check product design guide:
Jetson Download Center | NVIDIA Developer
See if the custom board meets the requirement.
I think so, the screen grab from Waveshare indicated -super.
@DaneLLL ,
Is the failure because of this? Recovery mode is confirmed. Please install the Secureboot package to use initrd flash for fused board
And, how do users accept the agreement when using this script (l4t_create_default_user.sh)? I tried using the mouse pointer, no use; I tried using the Tab key, no use.
$ sudo ./tools/l4t_create_default_user.sh -u jetson -p jetson1 -a
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 \
-p "-c ./bootloader/generic/cfg/flash_t234_qspi.xml" -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml \
--showlogs --network usb0 jetson-orin-nano-devkit-super external
[ 0.0275 ] ERROR: failed to read rcm_state
[ 0.3412 ] ERROR: might be timeout in USB write.
[ 10.4852 ] Error: try getting custinfo fail. Moving on
Error: Return value 3
Error: failed to generate images
$ lsusb
Bus 004 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 006: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive
**Bus 003 Device 010: ID 0955:7323 NVIDIA Corp. APX**
Bus 003 Device 004: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
Bus 003 Device 003: ID 046d:c315 Logitech, Inc. Classic Keyboard 200
Bus 003 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
Bus 003 Device 005: ID 8087:0026 Intel Corp. AX201 Bluetooth
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
Please install the Secureboot package to use initrd flash for fused board
# Entry added by NVIDIA initrd flash tool
/home/rac/arc/orin_nano/Linux_for_Tegra/tools/kernel_flash/tmp 127.0.0.1(rw,nohide,insecure,no_subtree_check,async,no_root_squash)
rpcbind: another rpcbind is already running. Aborting
Export list for localhost:
/home/rac/arc/orin_nano/Linux_for_Tegra/tools/kernel_flash/tmp 127.0.0.1
/home/rac/arc/orin_nano/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --no-flash --external-device nvme0n1p1 -p -c ./bootloader/generic/cfg/flash_t234_qspi.xml -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --network usb0 jetson-orin-nano-devkit-super external
************************************
* *
* Step 1: Generate flash packages *
* *
************************************
Create folder to store images to flash
Generate image for internal storage devices
Generate images to be flashed
ADDITIONAL_DTB_OVERLAY="" /home/rac/arc/orin_nano/Linux_for_Tegra/flash.sh --no-flash --sign -c ./bootloader/generic/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit-super external
###############################################################################
# L4T BSP Information:
# R36 , REVISION: 4.3
# User release: 0.0
###############################################################################
ECID is 0x80012344705DD7827800000019FF00C0
copying device_config(/home/rac/arc/orin_nano/Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-device-p3767-0000.dts)... done.
copying misc_config(/home/rac/arc/orin_nano/Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-misc-p3767-0000.dts)... done.
copying emc_fuse_dev_params(/home/rac/arc/orin_nano/Linux_for_Tegra/bootloader/generic/BCT/tegra234-br-bct-diag-boot.dts)... done.
copying minratchet_config(/home/rac/arc/orin_nano/Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-ratchet-p3767-0000.dts)... done.
Existing emcfuse(/home/rac/arc/orin_nano/Linux_for_Tegra/bootloader/fuse_t234.xml) reused.
./tegraflash.py --chip "0x23" --applet "/home/rac/arc/orin_nano/Linux_for_Tegra/bootloader/mb1_t234_prod.bin" --skipuid --cfg readinfo_t234_min_prod.xml --dev_params tegra234-br-bct-diag-boot.dts --device_config tegra234-mb1-bct-device-p3767-0000.dts --misc_config tegra234-mb1-bct-misc-p3767-0000.dts --bins "mb2_applet applet_t234.bin" --minratchet_config tegra234-mb1-bct-ratchet-p3767-0000.dts --cmd "readfuses fuse_t234.bin fuse_t234.xml; dump eeprom cvm cvm.bin; dump try_custinfo custinfo_out.bin; reboot recovery"
Welcome to Tegra Flash
version 1.0.0
Type ? or help for help and q or quit to exit
Use ! to execute system commands
[ 0.0267 ] Reading fuses
[ 0.0271 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 0.0273 ] File rcm_state open failed
[ 0.0275 ] ERROR: failed to read rcm_state
[ 0.0275 ]
[ 0.0322 ] tegrasign_v3.py --key None --getmode mode.txt
[ 0.0323 ] Assuming zero filled SBK key
[ 0.0277 ] Pre-processing config: tegra234-mb1-bct-device-p3767-0000.dts
[ 0.0764 ] Pre-processing config: tegra234-mb1-bct-misc-p3767-0000.dts
[ 0.0937 ] Pre-processing config: tegra234-mb1-bct-ratchet-p3767-0000.dts
[ 0.1040 ] Parsing partition layout
[ 0.1048 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[ 0.1075 ] Kernel DTB used: None
[ 0.1075 ] WARNING: dce base dtb is not provided
[ 0.1075 ] Parsing partition layout
[ 0.1080 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[ 0.1090 ] Creating list of images to be signed
[ 0.1098 ] Generating ratchet blob
[ 0.1098 ] Generating coldboot mb1-bct
[ 0.1106 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct.cfg --misc tegra234-mb1-bct-misc-p3767-0000_cpp.dtb --device tegra234-mb1-bct-device-p3767-0000_cpp.dtb --minratchet tegra234-mb1-bct-ratchet-p3767-0000_cpp.dtb --ratchet_blob ratchet_blob.bin
[ 0.1110 ] MB1-BCT version: 0.13
[ 0.1156 ] Parsing config file :tegra234-mb1-bct-device-p3767-0000_cpp.dtb
[ 0.1158 ] Added Platform Config 9 data with size :- 100
[ 0.1158 ]
[ 0.1158 ] Parsing config file :tegra234-mb1-bct-ratchet-p3767-0000_cpp.dtb
[ 0.1158 ]
[ 0.1158 ] Updating mb1-bct with firmware information
[ 0.1160 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo readinfo_t234_min_prod.xml.bin
[ 0.1167 ] tegrahost_v2 --chip 0x23 0 --align mb1_cold_boot_bct_MB1_aligned.bct
[ 0.1170 ] Generating SHA2 Hash for mb1bct
[ 0.1262 ] Sha saved in mb1_cold_boot_bct_MB1_aligned.sha
[ 0.1267 ] Sha saved in mb1_cold_boot_bct_MB1.sha
[ 0.1223 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --ratchet_blob ratchet_blob.bin --appendsigheader mb1_cold_boot_bct_MB1_aligned.bct zerosbk
[ 0.1225 ] adding BCH for mb1_cold_boot_bct_MB1_aligned.bct
[ 0.1276 ] tegrasign_v3.py --key None --list mb1_cold_boot_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.1277 ] Assuming zero filled SBK key
[ 0.1287 ] Warning: pub_key.key is not found
[ 0.1243 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_cold_boot_bct_MB1_aligned_sigheader.bct.encrypt mb1_cold_boot_bct_MB1_aligned_sigheader.bct.hash zerosbk
[ 0.1248 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --ratchet_blob ratchet_blob.bin --list images_list.xml zerosbk
[ 0.1250 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[ 0.1263 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[ 0.1265 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[ 0.1297 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[ 0.1300 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[ 0.1338 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[ 0.1340 ] adding BCH for mb2_t234_aligned.bin
[ 0.1366 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[ 0.1449 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[ 0.1451 ] adding BCH for mb2_t234_aligned.bin
[ 0.1552 ] Filling MB1 storage info
[ 0.1552 ] Parsing dev params for multi chains
[ 0.1599 ] Generating br-bct
[ 0.1601 ] Updating dev and MSS params in BR BCT
[ 0.1601 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[ 0.1605 ] Updating bl info
[ 0.1607 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin
[ 0.1608 ] WARNING: boot chain is not completed. set to 0
[ 0.1613 ] Generating signatures
[ 0.1659 ] tegrasign_v3.py --key None --list images_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.1660 ] Assuming zero filled SBK key
[ 0.1706 ] Warning: pub_key.key is not found
[ 0.1661 ] Parsing dev params for multi chains
[ 0.1662 ] Generating br-bct
[ 0.1663 ] Updating dev and MSS params in BR BCT
[ 0.1663 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[ 0.1667 ] Updating bl info
[ 0.1669 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[ 0.1671 ] WARNING: boot chain is not completed. set to 0
[ 0.1677 ] Generating SHA2 Hash
[ 0.1727 ] Sha saved in br_bct_BR.sha
[ 0.1681 ] Get Signed section of bct
[ 0.1683 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --listbct bct_list.xml
[ 0.1687 ] Signing BCT
[ 0.1733 ] tegrasign_v3.py --key None --list bct_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.1734 ] Assuming zero filled SBK key
[ 0.1744 ] Sha saved in br_bct_BR.sha
[ 0.1745 ] Warning: pub_key.key is not found
[ 0.1699 ] Updating BCT with signature
[ 0.1701 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesig bct_list_signed.xml
[ 0.1702 ] Offset :4608 Len :3584
[ 0.1705 ] Generating SHA2 Hash
[ 0.1751 ] tegrasign_v3.py --key None --list bct_list.xml --sha sha512
[ 0.1752 ] Assuming zero filled SBK key
[ 0.1752 ] Assuming zero filled SBK key
[ 0.1763 ] Sha saved in br_bct_BR.sha
[ 0.1718 ] Updating BCT with SHA2 Hash
[ 0.1720 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesha bct_list_signed.xml
[ 0.1722 ] Offset :4608 Len :3584
[ 0.1725 ] Offset :68 Len :8124
[ 0.1726 ] Generating coldboot mb1-bct
[ 0.1728 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct.cfg --misc tegra234-mb1-bct-misc-p3767-0000_cpp.dtb --device tegra234-mb1-bct-device-p3767-0000_cpp.dtb --minratchet tegra234-mb1-bct-ratchet-p3767-0000_cpp.dtb --ratchet_blob ratchet_blob.bin
[ 0.1730 ] MB1-BCT version: 0.13
[ 0.1746 ] Parsing config file :tegra234-mb1-bct-device-p3767-0000_cpp.dtb
[ 0.1748 ] Added Platform Config 9 data with size :- 100
[ 0.1748 ]
[ 0.1748 ] Parsing config file :tegra234-mb1-bct-ratchet-p3767-0000_cpp.dtb
[ 0.1748 ]
[ 0.1748 ] Updating mb1-bct with firmware information
[ 0.1750 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo readinfo_t234_min_prod.xml.bin
[ 0.1757 ] tegrahost_v2 --chip 0x23 0 --align mb1_cold_boot_bct_MB1_aligned.bct
[ 0.1760 ] Generating SHA2 Hash for mb1bct
[ 0.1813 ] Sha saved in mb1_cold_boot_bct_MB1_aligned.sha
[ 0.1819 ] Sha saved in mb1_cold_boot_bct_MB1.sha
[ 0.1775 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --ratchet_blob ratchet_blob.bin --appendsigheader mb1_cold_boot_bct_MB1_aligned.bct zerosbk
[ 0.1777 ] adding BCH for mb1_cold_boot_bct_MB1_aligned.bct
[ 0.1829 ] tegrasign_v3.py --key None --list mb1_cold_boot_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.1830 ] Assuming zero filled SBK key
[ 0.1838 ] Warning: pub_key.key is not found
[ 0.1796 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_cold_boot_bct_MB1_aligned_sigheader.bct.encrypt mb1_cold_boot_bct_MB1_aligned_sigheader.bct.hash zerosbk
[ 0.1802 ] Generating recovery mb1-bct
[ 0.1805 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct.cfg --misc tegra234-mb1-bct-misc-p3767-0000_cpp.dtb --device tegra234-mb1-bct-device-p3767-0000_cpp.dtb --minratchet tegra234-mb1-bct-ratchet-p3767-0000_cpp.dtb --ratchet_blob ratchet_blob.bin
[ 0.1807 ] MB1-BCT version: 0.13
[ 0.1825 ] Parsing config file :tegra234-mb1-bct-device-p3767-0000_cpp.dtb
[ 0.1826 ] Added Platform Config 9 data with size :- 100
[ 0.1827 ]
[ 0.1827 ] Parsing config file :tegra234-mb1-bct-ratchet-p3767-0000_cpp.dtb
[ 0.1827 ]
[ 0.1827 ] Updating mb1-bct with firmware information
[ 0.1829 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct_MB1.bct --recov --updatefwinfo readinfo_t234_min_prod.xml.bin
[ 0.1835 ] tegrahost_v2 --chip 0x23 0 --align mb1_bct_MB1_aligned.bct
[ 0.1838 ] Generating SHA2 Hash for mb1bct
[ 0.1889 ] Sha saved in mb1_bct_MB1_aligned.sha
[ 0.1893 ] Sha saved in mb1_bct_MB1.sha
[ 0.1849 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --ratchet_blob ratchet_blob.bin --appendsigheader mb1_bct_MB1_aligned.bct zerosbk
[ 0.1851 ] adding BCH for mb1_bct_MB1_aligned.bct
[ 0.1902 ] tegrasign_v3.py --key None --list mb1_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[ 0.1903 ] Assuming zero filled SBK key
[ 0.1909 ] Warning: pub_key.key is not found
[ 0.1866 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_bct_MB1_aligned_sigheader.bct.encrypt mb1_bct_MB1_aligned_sigheader.bct.hash zerosbk
[ 0.1871 ] Info: Skip generating mem_bct because sdram_config is not defined
[ 0.1871 ] Info: Skip generating mem_bct because sdram_config is not defined
[ 0.1871 ] Copying signatures
[ 0.1873 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[ 0.1901 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[ 0.1902 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[ 0.1902 ] Boot Rom communication
[ 0.1904 ] tegrarcm_v2 --new_session --chip 0x23 0 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader.bin.encrypt --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
[ 0.1906 ] BR_CID: 0x80012344705DD7827800000019FF00C0
[ 0.2759 ] Sending bct_br
[ 0.3412 ] ERROR: might be timeout in USB write.
Error: Return value 3
Command tegrarcm_v2 --new_session --chip 0x23 0 --uid --download bct_br br_bct_BR.bct --download mb1 mb1_t234_prod_aligned_sigheader.bin.encrypt --download psc_bl1 psc_bl1_t234_prod_aligned_sigheader.bin.encrypt --download bct_mb1 mb1_bct_MB1_sigheader.bct.encrypt
[ 10.4741 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 10.4757 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 10.4771 ] Retrieving board information
[ 10.4776 ] tegrarcm_v2 --chip 0x23 0 --oem platformdetails chip chip_info.bin
[ 10.4786 ] Retrieving EEPROM data
[ 10.4786 ] tegrarcm_v2 --oem platformdetails eeprom cvm /home/rac/arc/orin_nano/Linux_for_Tegra/bootloader/cvm.bin --chip 0x23 0
[ 10.4802 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 10.4817 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 10.4825 ] Dumping customer Info
[ 10.4830 ] tegrarcm_v2 --chip 0x23 0 --oem dump bct tmp.bct
[ 10.4843 ] tegrabct_v2 --brbct tmp.bct --chip 0x23 0 --custinfo /home/rac/arc/orin_nano/Linux_for_Tegra/bootloader/custinfo_out.bin
[ 10.4848 ] File tmp.bct open failed
[ 10.4852 ] Error: try getting custinfo fail. Moving on
[ 10.4852 ] Rebooting to recovery mode
[ 10.4857 ] tegrarcm_v2 --chip 0x23 0 --ismb2
[ 10.4865 ] Rebooting to recovery mode
[ 10.4869 ] tegrarcm_v2 --chip 0x23 0 --reboot recovery
Parsing board information failed.
Error: failed to generate images
Cleaning up...
Hi,
Looks like the device is booted to Ubuntu instead of entering recovery mode. Please do
- Power off the device
- Put on jumper
- Power on the device
- Connect it to host PC thorough type-C to A cable
- Run $ lsusb on host PC to check status
I have follow your step 1 to 4.
I checked and confirm is under recovery mode.
Bus 003 Device 010: ID 0955:7323 NVIDIA Corp. APX
