Custom dtbo is not added to the rootfs

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
1

Hi Forum,

I was in the progress of adding new custom dtbo into the BSP of the Jetson Orin Nano Development Kit as below :

In the source folder (path/to/jetson-orin-bsp-jp6x/build/):

hardware/nvidia/t23x/nv-public/overlay/tegra234-p3767-camera-p3768-ap1302_ar0234-cam0-2lane-overlay.dts
hardware/nvidia/t23x/nv-public/overlay/tegra234-p3767-camera-p3768-ap1302_ar0234-cam1-4lane-overlay.dts
kernel-devicetree/generic-dts/dtbs/tegra234-p3767-camera-p3768-ap1302_ar0234-cam1-4lane-overlay.dtbo
kernel-devicetree/generic-dts/dtbs/tegra234-p3767-camera-p3768-ap1302_ar0234-cam0-2lane-overlay.dtbo

Then copied them to the SDK install folder (path/to/SDK_installs/JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/) ad per the Kernel Customization Guide :

kernel/dtb/tegra234-p3767-camera-p3768-ap1302_ar0234-cam1-4lane-overlay.dtbo
kernel/dtb/tegra234-p3767-camera-p3768-ap1302_ar0234-cam0-2lane-overlay.dtbo

However, after flashing, the above dbto did neither appear in the rootfs, expectedly in path/to/SDK_installs/JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/rootfs/boot/ nor in the /boot/ folder of the running board. BY consequence, the jetson-io utility could not see them

I even executed the following command :
sudo ./tools/l4t_update_initrd.sh

prior the flashing command :
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" --showlogs --network usb0 jetson-orin-nano-devkit internal

but it was still the same

I saw from How to Update customized DTBs Directly in the Jetson Orin Nano Dev. Kit - #3 by KevinFFF that :

The dtb in use is depending on the board config. (you can check the board config or flash log to know what’s the final dtb loaded for your board). It may load lots of dtbs and combine to one dtb (dtbfile).

Attached is the flash log :
flash_1-8_0_20250720-171355.log (48.1 KB)

I am not quite sure what is missing as configuration. Please help me!

Thanks in advance and best regards,
Khang

3

Hi Khang,

This log only includes the process when you are flashing the board directly.
We would also want to check the log when you were generating the pacakge.

Please put them into SDK_installs/JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/kernel/dtb/ instead.
You may also need to specify them in board config so that they would be loaded.
In your case, please check OVERLAY_DTB_FILE in p3767.conf.common

4

Hi @KevinFFF,

We would also want to check the log when you were generating the pacakge.

As said, I followed the instruction of Kernel Customization Guide, could you clarify when or where to get the log of package generation, please?

Please put them into SDK_installs/JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/kernel/dtb/ instead.

They were there indeed :

kernel/dtb/tegra234-p3767-camera-p3768-ap1302_ar0234-cam1-4lane-overlay.dtbo
kernel/dtb/tegra234-p3767-camera-p3768-ap1302_ar0234-cam0-2lane-overlay.dtbo

You may also need to specify them in board config so that they would be loaded.
In your case, please check OVERLAY_DTB_FILE in p3767.conf.common

As I used the jetson-orin-nano-devkit as the board configuration in the flash command, I modified it to add the custom DTBO as below :

$ vi jetson-orin-nano-devkit.conf

TBCDTB_FILE="${DTB_FILE}";
OVERLAY_DTB_FILE+=",tegra234-p3768-0000+p3767-0000-dynamic.dtbo";
+OVERLAY_DTB_FILE+=",tegra234-p3767-camera-p3768-ap1302_ar0234-cam0-2lane-overlay.dtbo,tegra234-p3767-camera-p3768-ap1302_ar0234-cam1-4lane-overlay.dtbo";

The difference I observed were that the DTBO files were also copied to bootloader/ folder as below :

bootloader/tegra234-p3767-camera-p3768-ap1302_ar0234-cam1-4lane-overlay.dtbo 
bootloader/tegra234-p3767-camera-p3768-ap1302_ar0234-cam0-2lane-overlay.dtbo
kernel/dtb/tegra234-p3767-camera-p3768-ap1302_ar0234-cam1-4lane-overlay.dtbo
kernel/dtb/tegra234-p3767-camera-p3768-ap1302_ar0234-cam0-2lane-overlay.dtbo

However, there were still not present in the /boot/ folder of the running board. Should they be flashed in the QSPI in this case? However, jetson-io utility seemed to to find/see them.

5

This instruction is to build the DTB.

Before you run the command to flash the board directly, you need to generate the package.
Please refer to <Linux_for_Tegra>/tools/kernel_flash/README_initrd_flash.txt for details.

jetson-orin-nano-devkit.conf will include p3767.conf.common
It’s okay that you configure them in jetson-orin-nano-devkit.conf. Please specify them in the same line.

It is expected that they are copied to bootloader during flash.
Please refer to your flash log to check if your custom overlay dtbo(tegra234-p3767-camera-p3768-ap1302_ar0234-cam1-4lane-overlay.dtbo) included.

6

For Jetpack-6.2, I do not know other method than sudo ./tools/l4t_update_initrd.sh for updating the initramf after copying/installing the newly compile Image as well as modules. Could you elaborate more, please?

It’s okay that you configure them in jetson-orin-nano-devkit.conf. Please specify them in the same line.

I used OVERLAY_DTB_FILE+= rather OVERLAY_DTB_FILE=

7

l4t_update_initrd.sh is used to update the initramfs.
After you finisht that, please refer to Workflow 11: Generate images for internal device and external device seperately then flash to flash the device. I would like to check the log in each steps.

8

Hi @KevinFFF,

There’s multiple processes in the Workflow 11, and the examples are for the Xavier :

Workflow 11: Generate images for internal device and external device seperately
then flash

The flashing tool supports a three-step process: "to generate images for an
internal device, then generate them for an external device, then flash.
This is enabled by using the "append" option. Four examples below show how it
works.

Example 1: Generate a normal root filesystem configuration for the internal device
, then generate an encrypted root filesystem for the external device, then flash

1. Put the device into recovery mode, then generate a normal root
filesystem for the internal device:
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash jetson-xavier internal
(Or if you want to generate the image offline, then you can use:
$ sudo BOARDID=2888 BOARDSKU=004 FAB=400 ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash jetson-xavier internal
)

2. Put the device into recovery mode, then generate an encrypted
filesystem for the external device:
$ sudo ROOTFS_ENC=1 ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash \
            --external-device nvme0n1p1 \
            -S 8GiB -c ./tools/kernel_flash/flash_l4t_nvme_rootfs_enc.xml \
            --external-only --append jetson-xavier external
(Or if you want to generate the image offline, then you can use:
$ sudo BOARDID=2888 BOARDSKU=0004 FAB=400 ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash \
            --external-device nvme0n1p1 \
            -S 8GiB -c ./tools/kernel_flash/flash_l4t_nvme_rootfs_enc.xml \
            --external-only --append jetson-xavier external
)


3. Put the device into recovery mode, then flash both images:
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only


Example 2: In this example, you want to boot Jetson Xavier NX SD from an
attached NVMe SSD. The SD card does not need to be plugged in. You can also
apply this if you don't want to use the emmc on the Jetson Xavier NX emmc.

1. Put the device into recovery mode, then generate qspi only images
for the internal device:
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash jetson-xavier-nx-devkit-qspi internal

Note: The board name given here is not jetson-xavier-nx-devkit or
jetson-xavier-nx-devkit-emmc so that no SD card or eMMC images are generated.


2. Put the device into recovery mode, then generate a normal
filesystem for the external device:
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash \
            --external-device nvme0n1p1 \
            -c ./tools/kernel_flash/flash_l4t_external.xml \
            --external-only --append jetson-xavier-nx-devkit external

3. Put the device into recovery mode, then flash both images:
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only


Example 3: we create a massflash package with encrypted internal image and
normal external image with the --append option

1. Put the device into recovery mode, then generate encrypted rootfs
images for the internal device:
$ sudo ROOTFS_ENC=1 ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash jetson-xavier internal

2. Put the device into recovery mode, then generate a normal
filesystem for the external device, and create a massflash package capable of
flashing two devices simultaneously:

$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash \
            --external-device nvme0n1p1 \
            -S 8GiB -c ./tools/kernel_flash/flash_l4t_external.xml \
            --external-only --massflash 2 --append jetson-xavier external

3. Put two devices into recovery mode, then flash two devices:
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only --massflash 2


Example 4: Generate an encrypted root filesystem configuration for the internal device
, then generate an encrypted root filesystem for the external device, then flash

1. Put the device into recovery mode, then generate an encrypted root
filesystem for the internal device:
$ sudo ROOTFS_ENC=1 ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash jetson-xavier internal

Second step: Put the device into recovery mode, then generate an encrypted
filesystem for the external device:
$ sudo ROOTFS_ENC=1 ./tools/kernel_flash/l4t_initrd_flash.sh --no-flash \
            --external-device nvme0n1p1 \
            -S 8GiB -c ./tools/kernel_flash/flash_l4t_nvme_rootfs_enc.xml \
            --external-only --append jetson-xavier external

Third step: Put the device into recovery mode, then flash both images:
$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --flash-only

What are exactly the process(es) that you want me to do and provide the log(s), please ?

9

You can replace jetson-xavier with jetson-orin-nano-devkit since you are using Jetson Orin Nano devkit.

Okay, please just run the following single command to flash the devkit and share the full flash log.

$ sudo ADDITIONAL_DTB_OVERLAY_OPT="BootOrderNvme.dtbo" ./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 internal
10

Hi @KevinFFF,

I got following error with your suggested command :

Writing esp partition done
writing item=11, 9:0:recovery_alt, 487870464, 83886080, , , fixed-<reserved>-11, 
[ 32]: l4t_flash_from_kernel: Warning: skip writing recovery_alt partition as no image is specified
writing item=12, 9:0:recovery-dtb_alt, 571756544, 524288, , , fixed-<reserved>-12, 
[ 32]: l4t_flash_from_kernel: Warning: skip writing recovery-dtb_alt partition as no image is specified
writing item=13, 9:0:esp_alt, 572280832, 67108864, , , fixed-<reserved>-13, 
[ 33]: l4t_flash_from_kernel: Warning: skip writing esp_alt partition as no image is specified
writing item=14, 9:0:UDA, 639401984, 419430400, , , fixed-<reserved>-14, 
[ 33]: l4t_flash_from_kernel: Skip writing UDA partition
writing item=15, 9:0:reserved, 1058832384, 502792192, , , fixed-<reserved>-15, 
[ 33]: l4t_flash_from_kernel: Warning: skip writing reserved partition as no image is specified
writing item=16, 9:0:APP, 1561624576, 59641638912, , , expand-<reserved>-1, 
Formatting APP partition /dev/nvme0n1p1 ...
mke2fs 1.46.5 (30-Dec-2021)
Discarding device blocks: done                            
Creating filesystem with 124645641 4k blocks and 31162368 inodes
Filesystem UUID: 6b3702ec-80fa-49b6-91f4-7f7c1261a1c2
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
	4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 
	102400000

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done     

Formatting APP parition done
Formatting APP partition /dev/nvme0n1p1 ...
tar --checkpoint-action="ttyout=Hit %s checkpoint #%u%*\r" -x -I 'zstd -T0' -pf /mnt/external/system.img  --warning=no-timestamp --numeric-owner --xattrs --xattrs-include=*  -C  /tmp/ci-X5V2grhpKe
Flash failure
Either the device cannot mount the NFS server on the host or a flash command has failed. Check your network setting (VPN, firewall,...) to make sure the device can mount NFS server. Debug log saved to /tmp/tmp.SP0kNkLoLB. You can access the target's terminal through "sshpass -p root ssh root@fc00:1:1:0::2" 
Cleaning up...

And the /tmp/tmp.SP0kNkLoLB :

showmount -e
Export list for ASUS-MINIPC-PN64:
/home/ontrak/Workspace/Ref/Platforms/Nvidia/Jetson/SDK/install/JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/rootfs                    fc00:1:1::/48
/home/ontrak/Workspace/Ref/Platforms/Nvidia/Jetson/SDK/install/JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/tools/kernel_flash/images fc00:1:1::/48
/home/ontrak/Workspace/Ref/Platforms/Nvidia/Jetson/SDK/install/JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/tools/kernel_flash/tmp    127.0.0.1
systemctl status nfs-kernel-server
â—Ź nfs-server.service - NFS server and services
     Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor preset: enabled)
     Active: active (exited) since Thu 2025-07-24 21:02:07 +07; 7min ago
    Process: 1130301 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
    Process: 1130302 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited, status=0/SUCCESS)
   Main PID: 1130302 (code=exited, status=0/SUCCESS)

Thg 7 24 21:02:06 ASUS-MINIPC-PN64 systemd[1]: Starting NFS server and services...
Thg 7 24 21:02:07 ASUS-MINIPC-PN64 systemd[1]: Finished NFS server and services.
blkid
/dev/nvme0n1p4: UUID="d1174521-00a4-400e-88bc-702de5783cff" TYPE="swap" PARTUUID="a9712fcb-48ab-4e25-bc83-e06e613e4c3e"
/dev/nvme0n1p2: UUID="5f4b4f6f-739e-4950-9227-8a122fba28e4" TYPE="ext4" PARTUUID="59dce8e9-0a19-41e4-aef2-10c462ff980c"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop5: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/nvme0n1p1: UUID="6EAA-356B" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="3fbf1491-cf52-4a8e-b5b1-35f6341e0d09"
/dev/nvme0n1p3: UUID="b4c3a209-fd91-40fe-ab5c-04ad6103a044" TYPE="ext4" PARTUUID="bc1831b6-f53f-48b1-b4f8-6ef54bac80e8"
/dev/sda1: UUID="8EC1-4DB3" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="b5cce681-16b3-4652-ab41-53b01862676b"
/dev/sda3: UUID="308AC2248AC1E706" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="cb2b7b63-2ea0-4c2b-b17b-a39dd6f0256f"
/dev/sda4: UUID="E0B465DBB465B4A6" TYPE="ntfs" PARTUUID="547c865f-050f-46c3-a6de-826a3d892356"
/dev/loop9: TYPE="squashfs"
/dev/loop8: TYPE="squashfs"
/dev/loop10: TYPE="squashfs"
/dev/loop12: TYPE="squashfs"
/dev/loop11: TYPE="squashfs"
/dev/sda2: PARTLABEL="Microsoft reserved partition" PARTUUID="560c48d8-cd59-4843-a9c1-24e577e2940a"
df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            7,7G     0  7,7G   0% /dev
tmpfs           1,6G  2,2M  1,6G   1% /run
/dev/nvme0n1p2  201G   24G  168G  13% /
tmpfs           7,7G  5,1M  7,7G   1% /dev/shm
tmpfs           5,0M  4,0K  5,0M   1% /run/lock
tmpfs           7,7G     0  7,7G   0% /sys/fs/cgroup
/dev/loop0      128K  128K     0 100% /snap/bare/5
/dev/loop2       64M   64M     0 100% /snap/core20/2582
/dev/loop1       74M   74M     0 100% /snap/core22/2010
/dev/loop3      517M  517M     0 100% /snap/gnome-42-2204/202
/dev/loop4      347M  347M     0 100% /snap/gnome-3-38-2004/119
/dev/loop5      350M  350M     0 100% /snap/gnome-3-38-2004/143
/dev/loop6       46M   46M     0 100% /snap/snap-store/638
/dev/loop7       13M   13M     0 100% /snap/snap-store/1216
/dev/loop9       50M   50M     0 100% /snap/snapd/24792
/dev/loop8       51M   51M     0 100% /snap/snapd/24718
/dev/loop10      92M   92M     0 100% /snap/gtk-common-themes/1535
/dev/loop12      74M   74M     0 100% /snap/core22/2045
/dev/loop11      64M   64M     0 100% /snap/core20/2599
/dev/nvme0n1p1  511M  6,1M  505M   2% /boot/efi
/dev/nvme0n1p3  733G  640G   56G  92% /home
tmpfs           1,6G  128K  1,6G   1% /run/user/1000
Checking folder /home/ontrak/Workspace/Ref/Platforms/Nvidia/Jetson/SDK/install/JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/rootfs
drwxr-xr-x 18 root   root     4096 Thg 7  23 14:00 rootfs
Checking folder /home/ontrak/Workspace/Ref/Platforms/Nvidia/Jetson/SDK/install/JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/tools/kernel_flash/images
drwxr-xr-x  4 root   root    4096 Thg 7  24 21:01 images
-rwxrwxr-x  1 ontrak ontrak 20243 Thg 1   8  2025 l4t_create_images_for_kernel_flash.sh
iptables -vL -t filter
Chain INPUT (policy ACCEPT 5599K packets, 3605M bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain FORWARD (policy DROP 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination
    0     0 DOCKER-USER  all  --  any    any     anywhere             anywhere
    0     0 DOCKER-FORWARD  all  --  any    any     anywhere             anywhere
    0     0 ACCEPT     all  --  any    wlx00e030000416  192.168.55.0/24      anywhere
    0     0 ACCEPT     all  --  wlx00e030000416 any     anywhere             192.168.55.0/24      state RELATED,ESTABLISHED

Chain OUTPUT (policy ACCEPT 4276K packets, 2912M bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain DOCKER (1 references)
 pkts bytes target     prot opt in     out     source               destination
    0     0 DROP       all  --  !docker0 docker0  anywhere             anywhere

Chain DOCKER-BRIDGE (1 references)
 pkts bytes target     prot opt in     out     source               destination
    0     0 DOCKER     all  --  any    docker0  anywhere             anywhere

Chain DOCKER-CT (1 references)
 pkts bytes target     prot opt in     out     source               destination
    0     0 ACCEPT     all  --  any    docker0  anywhere             anywhere             ctstate RELATED,ESTABLISHED

Chain DOCKER-FORWARD (1 references)
 pkts bytes target     prot opt in     out     source               destination
    0     0 DOCKER-CT  all  --  any    any     anywhere             anywhere
    0     0 DOCKER-ISOLATION-STAGE-1  all  --  any    any     anywhere             anywhere
    0     0 DOCKER-BRIDGE  all  --  any    any     anywhere             anywhere
    0     0 ACCEPT     all  --  docker0 any     anywhere             anywhere

Chain DOCKER-ISOLATION-STAGE-1 (1 references)
 pkts bytes target     prot opt in     out     source               destination
    0     0 DOCKER-ISOLATION-STAGE-2  all  --  docker0 !docker0  anywhere             anywhere

Chain DOCKER-ISOLATION-STAGE-2 (1 references)
 pkts bytes target     prot opt in     out     source               destination
    0     0 DROP       all  --  any    docker0  anywhere             anywhere

Chain DOCKER-USER (1 references)
 pkts bytes target     prot opt in     out     source               destination
    0     0 RETURN     all  --  any    any     anywhere             anywhere
~                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    
~                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    
~                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    
~                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    
~

Then it gave error on the flash command that I often used :

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" --showlogs --network usb0 jetson-orin-nano-devkit internal
Please install the Secureboot package to use initrd flash for fused board
# Entry added by NVIDIA initrd flash tool
/home/ontrak/Workspace/Ref/Platforms/Nvidia/Jetson/SDK/install/JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS/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/ontrak/Workspace/Ref/Platforms/Nvidia/Jetson/SDK/install/JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/tools/kernel_flash/tmp 127.0.0.1
/home/ontrak/Workspace/Ref/Platforms/Nvidia/Jetson/SDK/install/JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --no-flash --external-device nvme0n1p1 -c tools/kernel_flash/flash_l4t_external.xml -p -c bootloader/t186ref/cfg/flash_t234_qspi.xml --showlogs --network usb0 jetson-orin-nano-devkit internal
************************************
*                                  *
*  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/ontrak/Workspace/Ref/Platforms/Nvidia/Jetson/SDK/install/JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/flash.sh --no-flash --sign  -c bootloader/t186ref/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit internal

###############################################################################
# L4T BSP Information:
# R36 , REVISION: 4.3
# User release: 0.0
###############################################################################
ECID is 0x80012344705E015B8000000016FE81C0
copying device_config(/home/ontrak/Workspace/Ref/Platforms/Nvidia/Jetson/SDK/install/JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-device-p3767-0000.dts)... done.
copying misc_config(/home/ontrak/Workspace/Ref/Platforms/Nvidia/Jetson/SDK/install/JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-misc-p3767-0000.dts)... done.
copying emc_fuse_dev_params(/home/ontrak/Workspace/Ref/Platforms/Nvidia/Jetson/SDK/install/JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/generic/BCT/tegra234-br-bct-diag-boot.dts)... done.
copying minratchet_config(/home/ontrak/Workspace/Ref/Platforms/Nvidia/Jetson/SDK/install/JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-ratchet-p3767-0000.dts)... done.
Existing emcfuse(/home/ontrak/Workspace/Ref/Platforms/Nvidia/Jetson/SDK/install/JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/fuse_t234.xml) reused.
./tegraflash.py --chip "0x23" --applet "/home/ontrak/Workspace/Ref/Platforms/Nvidia/Jetson/SDK/install/JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS/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.0119 ] Reading fuses
[   0.0126 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   0.0132 ] File rcm_state open failed
[   0.0134 ] ERROR: failed to read rcm_state
[   0.0134 ] 
[   0.0141 ] tegrasign_v3.py --key None --getmode mode.txt
[   0.0143 ] Assuming zero filled SBK key
[   0.0137 ] Pre-processing config: tegra234-mb1-bct-device-p3767-0000.dts
[   0.0178 ] Pre-processing config: tegra234-mb1-bct-misc-p3767-0000.dts
[   0.0238 ] Pre-processing config: tegra234-mb1-bct-ratchet-p3767-0000.dts
[   0.0276 ] Parsing partition layout
[   0.0282 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.0292 ] Kernel DTB used: None
[   0.0292 ] WARNING: dce base dtb is not provided

[   0.0292 ] Parsing partition layout
[   0.0298 ] tegraparser_v2 --pt readinfo_t234_min_prod.xml.tmp
[   0.0305 ] Creating list of images to be signed
[   0.0310 ] Generating ratchet blob
[   0.0311 ] Generating coldboot mb1-bct
[   0.0315 ] 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.0321 ] MB1-BCT version: 0.13

[   0.0342 ] Parsing config file :tegra234-mb1-bct-device-p3767-0000_cpp.dtb 
[   0.0343 ] Added Platform Config 9 data with size :- 100
[   0.0344 ] 
[   0.0344 ] Parsing config file :tegra234-mb1-bct-ratchet-p3767-0000_cpp.dtb 
[   0.0344 ] 
[   0.0345 ] Updating mb1-bct with firmware information
[   0.0350 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo readinfo_t234_min_prod.xml.bin
[   0.0365 ] tegrahost_v2 --chip 0x23 0 --align mb1_cold_boot_bct_MB1_aligned.bct
[   0.0371 ] Generating SHA2 Hash for mb1bct
[   0.0388 ] Sha saved in mb1_cold_boot_bct_MB1_aligned.sha
[   0.0398 ] Sha saved in mb1_cold_boot_bct_MB1.sha
[   0.0398 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --ratchet_blob ratchet_blob.bin --appendsigheader mb1_cold_boot_bct_MB1_aligned.bct zerosbk
[   0.0404 ] adding BCH for mb1_cold_boot_bct_MB1_aligned.bct
[   0.0416 ] tegrasign_v3.py --key None --list mb1_cold_boot_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.0417 ] Assuming zero filled SBK key
[   0.0428 ] Warning: pub_key.key is not found
[   0.0429 ] 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.0439 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --ratchet_blob ratchet_blob.bin --list images_list.xml zerosbk
[   0.0444 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[   0.0450 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[   0.0452 ] MB1: Nvheader already present is mb1_t234_prod_aligned.bin
[   0.0479 ] Header already present for mb1_t234_prod_aligned_sigheader.bin
[   0.0480 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[   0.0506 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[   0.0507 ] adding BCH for mb2_t234_aligned.bin
[   0.0522 ] MB1: Nvheader already present is psc_bl1_t234_prod_aligned.bin
[   0.0597 ] Header already present for psc_bl1_t234_prod_aligned_sigheader.bin
[   0.0598 ] adding BCH for mb2_t234_aligned.bin
[   0.0682 ] Filling MB1 storage info
[   0.0682 ] Parsing dev params for multi chains
[   0.0735 ] Generating br-bct
[   0.0742 ] Updating dev and MSS params in BR BCT
[   0.0743 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[   0.0751 ] Updating bl info
[   0.0760 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin
[   0.0767 ] WARNING: boot chain is not completed. set to 0
[   0.0772 ] Generating signatures
[   0.0779 ] tegrasign_v3.py --key None --list images_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.0782 ] Assuming zero filled SBK key
[   0.0902 ] Warning: pub_key.key is not found
[   0.0897 ] Parsing dev params for multi chains
[   0.0897 ] Generating br-bct
[   0.0903 ] Updating dev and MSS params in BR BCT
[   0.0903 ] tegrabct_v2 --dev_param tegra234-br-bct-diag-boot_cpp.dtb --brbct br_bct.cfg --chip 0x23 0
[   0.0911 ] Updating bl info
[   0.0916 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updateblinfo readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[   0.0921 ] WARNING: boot chain is not completed. set to 0
[   0.0926 ] Generating SHA2 Hash
[   0.0941 ] Sha saved in br_bct_BR.sha
[   0.0935 ] Get Signed section of bct
[   0.0940 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --listbct bct_list.xml
[   0.0945 ] Signing BCT
[   0.0953 ] tegrasign_v3.py --key None --list bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.0954 ] Assuming zero filled SBK key
[   0.0972 ] Sha saved in br_bct_BR.sha
[   0.0974 ] Warning: pub_key.key is not found
[   0.0967 ] Updating BCT with signature
[   0.0974 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesig bct_list_signed.xml
[   0.0978 ] Offset :4608 Len :3584
[   0.0980 ] Generating SHA2 Hash
[   0.0987 ] tegrasign_v3.py --key None --list bct_list.xml --sha sha512
[   0.0990 ] Assuming zero filled SBK key
[   0.0990 ] Assuming zero filled SBK key
[   0.1016 ] Sha saved in br_bct_BR.sha
[   0.1012 ] Updating BCT with SHA2 Hash
[   0.1019 ] tegrabct_v2 --brbct br_bct_BR.bct --chip 0x23 0 --updatesha bct_list_signed.xml
[   0.1025 ] Offset :4608 Len :3584
[   0.1027 ] Offset :68 Len :8124
[   0.1027 ] 
[   0.1028 ] Generating coldboot mb1-bct
[   0.1035 ] 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.1043 ] MB1-BCT version: 0.13

[   0.1057 ] Parsing config file :tegra234-mb1-bct-device-p3767-0000_cpp.dtb 
[   0.1060 ] Added Platform Config 9 data with size :- 100
[   0.1060 ] 
[   0.1060 ] Parsing config file :tegra234-mb1-bct-ratchet-p3767-0000_cpp.dtb 
[   0.1060 ] 
[   0.1060 ] Updating mb1-bct with firmware information
[   0.1066 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_cold_boot_bct_MB1.bct --updatefwinfo readinfo_t234_min_prod.xml.bin
[   0.1082 ] tegrahost_v2 --chip 0x23 0 --align mb1_cold_boot_bct_MB1_aligned.bct
[   0.1089 ] Generating SHA2 Hash for mb1bct
[   0.1107 ] Sha saved in mb1_cold_boot_bct_MB1_aligned.sha
[   0.1117 ] Sha saved in mb1_cold_boot_bct_MB1.sha
[   0.1118 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --ratchet_blob ratchet_blob.bin --appendsigheader mb1_cold_boot_bct_MB1_aligned.bct zerosbk
[   0.1124 ] adding BCH for mb1_cold_boot_bct_MB1_aligned.bct
[   0.1136 ] tegrasign_v3.py --key None --list mb1_cold_boot_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.1137 ] Assuming zero filled SBK key
[   0.1149 ] Warning: pub_key.key is not found
[   0.1148 ] 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.1157 ] Generating recovery mb1-bct
[   0.1165 ] 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.1171 ] MB1-BCT version: 0.13

[   0.1191 ] Parsing config file :tegra234-mb1-bct-device-p3767-0000_cpp.dtb 
[   0.1192 ] Added Platform Config 9 data with size :- 100

[   0.1193 ] Parsing config file :tegra234-mb1-bct-ratchet-p3767-0000_cpp.dtb 
[   0.1194 ] Updating mb1-bct with firmware information
[   0.1201 ] tegrabct_v2 --chip 0x23 0 --mb1bct mb1_bct_MB1.bct --recov --updatefwinfo readinfo_t234_min_prod.xml.bin
[   0.1213 ] tegrahost_v2 --chip 0x23 0 --align mb1_bct_MB1_aligned.bct
[   0.1219 ] Generating SHA2 Hash for mb1bct
[   0.1235 ] Sha saved in mb1_bct_MB1_aligned.sha
[   0.1244 ] Sha saved in mb1_bct_MB1.sha
[   0.1244 ] tegrahost_v2 --chip 0x23 0 --magicid MBCT --ratchet_blob ratchet_blob.bin --appendsigheader mb1_bct_MB1_aligned.bct zerosbk
[   0.1248 ] adding BCH for mb1_bct_MB1_aligned.bct
[   0.1260 ] tegrasign_v3.py --key None --list mb1_bct_MB1_aligned_sigheader.bct_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.1261 ] Assuming zero filled SBK key
[   0.1273 ] Warning: pub_key.key is not found
[   0.1273 ] tegrahost_v2 --chip 0x23 0 --updatesigheader mb1_bct_MB1_aligned_sigheader.bct.encrypt mb1_bct_MB1_aligned_sigheader.bct.hash zerosbk
[   0.1281 ] Info: Skip generating mem_bct because sdram_config is not defined
[   0.1281 ] Info: Skip generating mem_bct because sdram_config is not defined
[   0.1281 ] Copying signatures
[   0.1288 ] tegrahost_v2 --chip 0x23 0 --partitionlayout readinfo_t234_min_prod.xml.bin --updatesig images_list_signed.xml
[   0.1317 ] mb1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[   0.1318 ] psc_bl1_t234_prod_aligned_sigheader.bin.encrypt filename is from images_list
[   0.1318 ] Boot Rom communication
[   0.1324 ] 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.1329 ] BR_CID: 0x80012344705E015B8000000016FE81C0
[   0.1604 ] Sending bct_br
[   0.2036 ] Sending mb1
[   0.2042 ] Sending psc_bl1
[   0.2169 ] Sending bct_mb1
[   0.2234 ] Boot Rom communication completed
[   0.2269 ] tegrahost_v2 --chip 0x23 0 --align applet_t234_aligned.bin
[   0.2311 ] tegrahost_v2 --chip 0x23 0 --magicid MB2A --ratchet_blob ratchet_blob.bin --appendsigheader applet_t234_aligned.bin zerosbk
[   0.2330 ] adding BCH for applet_t234_aligned.bin
[   0.2482 ] tegrasign_v3.py --key None --list applet_t234_aligned_sigheader.bin_list.xml --pubkeyhash pub_key.key --sha sha512
[   0.2484 ] Assuming zero filled SBK key
[   0.2519 ] Warning: pub_key.key is not found
[   0.2542 ] tegrahost_v2 --chip 0x23 0 --updatesigheader applet_t234_aligned_sigheader.bin.encrypt applet_t234_aligned_sigheader.bin.hash zerosbk
[   0.2606 ] Sending mb2_applet...

[   0.2618 ] tegrarcm_v2 --chip 0x23 0 --pollbl --download applet applet_t234_sigheader.bin.encrypt
[   0.2626 ] BL: version 1.4.0.4-t234-54845784-e89ea9bc last_boot_error: 0
[   0.4476 ] Sending applet
[   0.5451 ] completed
[   0.5459 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   0.5465 ] MB2 Applet version 01.00.0000
[   0.7354 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   0.7378 ] MB2 Applet version 01.00.0000
[   0.7663 ] Parsing fuse info as per xml file
[   0.7682 ] tegraparser_v2 --chip 0x23 0 --get_fuse_names fuse_t234.xml read_fuse_names.txt
[   0.7698 ] MagicId=0x45535546 version=0x2
[   0.7701 ] trying to read fuse with MB2 Applet
[   0.7719 ] tegraparser_v2 --chip 0x23 0 --read_fusetype PublicKeyHash read_fuse.bin
[   0.7762 ] tegrarcm_v2 --oem readfuses __fuse_read_scatter.bin read_fuse.bin
[   0.7781 ] MB2 Applet version 01.00.0000
[   0.8497 ] Saved read fuses in file __fuse_read_scatter.bin
[   0.8554 ] Fuse read successful
[   0.8570 ] tegraparser_v2 --chip 0x23 0 --read_fusetype PkcPubkeyHash1 read_fuse.bin
[   0.8582 ] tegrarcm_v2 --oem readfuses __fuse_read_scatter.bin read_fuse.bin
[   0.8588 ] MB2 Applet version 01.00.0000
[   0.9459 ] Saved read fuses in file __fuse_read_scatter.bin
[   0.9518 ] Fuse read successful
[   0.9551 ] tegraparser_v2 --chip 0x23 0 --read_fusetype PkcPubkeyHash2 read_fuse.bin
[   0.9594 ] tegrarcm_v2 --oem readfuses __fuse_read_scatter.bin read_fuse.bin
[   0.9607 ] MB2 Applet version 01.00.0000
[   1.0383 ] Saved read fuses in file __fuse_read_scatter.bin
[   1.0439 ] Fuse read successful
[   1.0456 ] tegraparser_v2 --chip 0x23 0 --read_fusetype BootSecurityInfo read_fuse.bin
[   1.0471 ] tegrarcm_v2 --oem readfuses __fuse_read_scatter.bin read_fuse.bin
[   1.0477 ] MB2 Applet version 01.00.0000
[   1.1231 ] Saved read fuses in file __fuse_read_scatter.bin
[   1.1289 ] Fuse read successful
[   1.1330 ] tegraparser_v2 --chip 0x23 0 --read_fusetype ArmJtagDisable read_fuse.bin
[   1.1371 ] tegrarcm_v2 --oem readfuses __fuse_read_scatter.bin read_fuse.bin
[   1.1385 ] MB2 Applet version 01.00.0000
[   1.2104 ] Saved read fuses in file __fuse_read_scatter.bin
[   1.2161 ] Fuse read successful
[   1.2184 ] tegraparser_v2 --chip 0x23 0 --read_fusetype SecurityMode read_fuse.bin
[   1.2202 ] tegrarcm_v2 --oem readfuses __fuse_read_scatter.bin read_fuse.bin
[   1.2208 ] MB2 Applet version 01.00.0000
[   1.2938 ] Saved read fuses in file __fuse_read_scatter.bin
[   1.2997 ] Fuse read successful
[   1.3030 ] tegraparser_v2 --chip 0x23 0 --read_fusetype SwReserved read_fuse.bin
[   1.3068 ] tegrarcm_v2 --oem readfuses __fuse_read_scatter.bin read_fuse.bin
[   1.3080 ] MB2 Applet version 01.00.0000
[   1.3819 ] Saved read fuses in file __fuse_read_scatter.bin
[   1.3875 ] Fuse read successful
[   1.3893 ] tegraparser_v2 --chip 0x23 0 --read_fusetype DebugAuthentication read_fuse.bin
[   1.3905 ] tegrarcm_v2 --oem readfuses __fuse_read_scatter.bin read_fuse.bin
[   1.3910 ] MB2 Applet version 01.00.0000
[   1.4783 ] Saved read fuses in file __fuse_read_scatter.bin
[   1.4841 ] Fuse read successful
[   1.4883 ] tegraparser_v2 --chip 0x23 0 --read_fusetype OdmInfo read_fuse.bin
[   1.4921 ] tegrarcm_v2 --oem readfuses __fuse_read_scatter.bin read_fuse.bin
[   1.4935 ] MB2 Applet version 01.00.0000
[   1.5660 ] Saved read fuses in file __fuse_read_scatter.bin
[   1.5718 ] Fuse read successful
[   1.5739 ] tegraparser_v2 --chip 0x23 0 --read_fusetype OdmId read_fuse.bin
[   1.5761 ] tegrarcm_v2 --oem readfuses __fuse_read_scatter.bin read_fuse.bin
[   1.5769 ] MB2 Applet version 01.00.0000
[   1.6507 ] Saved read fuses in file __fuse_read_scatter.bin
[   1.6562 ] Fuse read successful
[   1.6590 ] tegraparser_v2 --chip 0x23 0 --read_fusetype OdmLock read_fuse.bin
[   1.6622 ] tegrarcm_v2 --oem readfuses __fuse_read_scatter.bin read_fuse.bin
[   1.6635 ] MB2 Applet version 01.00.0000
[   1.7380 ] Saved read fuses in file __fuse_read_scatter.bin
[   1.7440 ] Fuse read successful
[   1.7477 ] tegraparser_v2 --chip 0x23 0 --read_fusetype ReservedOdm0 read_fuse.bin
[   1.7514 ] tegrarcm_v2 --oem readfuses __fuse_read_scatter.bin read_fuse.bin
[   1.7528 ] MB2 Applet version 01.00.0000
[   1.8259 ] Saved read fuses in file __fuse_read_scatter.bin
[   1.8318 ] Fuse read successful
[   1.8359 ] tegraparser_v2 --chip 0x23 0 --read_fusetype ReservedOdm1 read_fuse.bin
[   1.8402 ] tegrarcm_v2 --oem readfuses __fuse_read_scatter.bin read_fuse.bin
[   1.8417 ] MB2 Applet version 01.00.0000
[   1.9138 ] Saved read fuses in file __fuse_read_scatter.bin
[   1.9196 ] Fuse read successful
[   1.9232 ] tegraparser_v2 --chip 0x23 0 --read_fusetype ReservedOdm2 read_fuse.bin
[   1.9273 ] tegrarcm_v2 --oem readfuses __fuse_read_scatter.bin read_fuse.bin
[   1.9287 ] MB2 Applet version 01.00.0000
[   2.0060 ] Saved read fuses in file __fuse_read_scatter.bin
[   2.0117 ] Fuse read successful
[   2.0135 ] tegraparser_v2 --chip 0x23 0 --read_fusetype ReservedOdm3 read_fuse.bin
[   2.0147 ] tegrarcm_v2 --oem readfuses __fuse_read_scatter.bin read_fuse.bin
[   2.0152 ] MB2 Applet version 01.00.0000
[   2.1027 ] Saved read fuses in file __fuse_read_scatter.bin
[   2.1084 ] Fuse read successful
[   2.1125 ] tegraparser_v2 --chip 0x23 0 --read_fusetype ReservedOdm4 read_fuse.bin
[   2.1163 ] tegrarcm_v2 --oem readfuses __fuse_read_scatter.bin read_fuse.bin
[   2.1178 ] MB2 Applet version 01.00.0000
[   2.1899 ] Saved read fuses in file __fuse_read_scatter.bin
[   2.1956 ] Fuse read successful
[   2.1975 ] tegraparser_v2 --chip 0x23 0 --read_fusetype ReservedOdm5 read_fuse.bin
[   2.1989 ] tegrarcm_v2 --oem readfuses __fuse_read_scatter.bin read_fuse.bin
[   2.1995 ] MB2 Applet version 01.00.0000
[   2.2739 ] Saved read fuses in file __fuse_read_scatter.bin
[   2.2795 ] Fuse read successful
[   2.2814 ] tegraparser_v2 --chip 0x23 0 --read_fusetype ReservedOdm6 read_fuse.bin
[   2.2827 ] tegrarcm_v2 --oem readfuses __fuse_read_scatter.bin read_fuse.bin
[   2.2832 ] MB2 Applet version 01.00.0000
[   2.3581 ] Saved read fuses in file __fuse_read_scatter.bin
[   2.3639 ] Fuse read successful
[   2.3679 ] tegraparser_v2 --chip 0x23 0 --read_fusetype ReservedOdm7 read_fuse.bin
[   2.3714 ] tegrarcm_v2 --oem readfuses __fuse_read_scatter.bin read_fuse.bin
[   2.3722 ] MB2 Applet version 01.00.0000
[   2.4465 ] Saved read fuses in file __fuse_read_scatter.bin
[   2.4523 ] Fuse read successful
[   2.4560 ] tegraparser_v2 --chip 0x23 0 --read_fusetype Sku read_fuse.bin
[   2.4599 ] tegrarcm_v2 --oem readfuses __fuse_read_scatter.bin read_fuse.bin
[   2.4613 ] MB2 Applet version 01.00.0000
[   2.5341 ] Saved read fuses in file __fuse_read_scatter.bin
[   2.5397 ] Fuse read successful
[   2.5415 ] tegraparser_v2 --chip 0x23 0 --read_fusetype Uid read_fuse.bin
[   2.5427 ] tegrarcm_v2 --oem readfuses __fuse_read_scatter.bin read_fuse.bin
[   2.5433 ] MB2 Applet version 01.00.0000
[   2.6181 ] Saved read fuses in file __fuse_read_scatter.bin
[   2.6239 ] Fuse read successful
[   2.6261 ] tegraparser_v2 --chip 0x23 0 --read_fusetype OptEmcDisable read_fuse.bin
[   2.6279 ] tegrarcm_v2 --oem readfuses __fuse_read_scatter.bin read_fuse.bin
[   2.6287 ] MB2 Applet version 01.00.0000
[   2.7026 ] Saved read fuses in file __fuse_read_scatter.bin
[   2.7084 ] Fuse read successful
[   2.7127 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   2.7147 ] MB2 Applet version 01.00.0000
[   2.7444 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   2.7459 ] MB2 Applet version 01.00.0000
[   2.7920 ] Retrieving board information
[   2.7934 ] tegrarcm_v2 --chip 0x23 0 --oem platformdetails chip chip_info.bin
[   2.7946 ] MB2 Applet version 01.00.0000
[   2.8377 ] Saved platform info in chip_info.bin
[   2.8431 ] Chip minor revision: 1
[   2.8432 ] Bootrom revision: 0x7
[   2.8432 ] Ram code: 0x3
[   2.8433 ] Chip sku: 0xd5
[   2.8433 ] Chip Sample: prod
[   2.8442 ] Retrieving EEPROM data
[   2.8442 ] tegrarcm_v2 --oem platformdetails eeprom cvm /home/ontrak/Workspace/Ref/Platforms/Nvidia/Jetson/SDK/install/JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/cvm.bin --chip 0x23 0
[   2.8449 ] MB2 Applet version 01.00.0000
[   2.8904 ] Saved platform info in /home/ontrak/Workspace/Ref/Platforms/Nvidia/Jetson/SDK/install/JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/bootloader/cvm.bin
[   2.9258 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   2.9268 ] MB2 Applet version 01.00.0000
[   2.9547 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   2.9555 ] MB2 Applet version 01.00.0000
[   3.0017 ] Dumping customer Info
[   3.0029 ] tegrarcm_v2 --chip 0x23 0 --oem dump bct tmp.bct
[   3.0038 ] MB2 Applet version 01.00.0000
[   3.0498 ] 0000000054220302: E> NV3P_SERVER: Failed to get address for br bct from nv3p helper.
[   3.1282 ] 
[   3.1282 ] 
[   3.1282 ] Error: try getting custinfo fail. Moving on
[   3.1284 ] Rebooting to recovery mode
[   3.1314 ] tegrarcm_v2 --chip 0x23 0 --ismb2
[   3.1645 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[   3.1660 ] MB2 Applet version 01.00.0000
[   3.2112 ] Booting to recovery mode
[   3.2144 ] tegrarcm_v2 --chip 0x23 0 --reboot recovery
[   3.2161 ] MB2 Applet version 01.00.0000
Board ID(3767) version(301) sku(0003) revision(F.1)
Preset RAMCODE is 3
Chip SKU(00:00:00:D5) ramcode(3) fuselevel(fuselevel_production) board_FAB(301)
emc_opt_disable_fuse:(0)
Error: missing cfgfile ().

Usage: sudo ./flash.sh [options] generic internal
    options:
        -c <cfgfile> ---------- Flash partition table config file.
        -d <dtbfile> ---------- device tree file.
        -f <flashapp> --------- Path to flash application (tegraflash.py)
        -h -------------------- print this message.
        -i <enc rfs key file>-- key for disk encryption support.
        -k <partition id> ----- partition name or number specified in flash.cfg.
        -m <mts preboot> ------ MTS preboot such as mts_preboot_si.
        -n <nfs args> --------- Static nfs network assignments
                                <Client IP>:<Server IP>:<Gateway IP>:<Netmask>
        -o <odmdata> ---------- ODM data.
        -r -------------------- skip building and reuse existing system.img.
        -t <tegraboot> -------- tegraboot binary such as nvtboot.bin
        -u <PKC key file>------ PKC key used for odm fused board.
        -v <SBK key file>------ Secure Boot Key (SBK) key used for ODM fused board.
        -w <wb0boot> ---------- warm boot binary such as nvtbootwb0.bin
        -x <tegraid> ---------- Tegra CHIPID.
        -B <boardid> ---------- BoardId.
        -C <cmdline> ---------- Kernel commandline arguments.
                                WARNING:
                                Each option in this kernel commandline gets
                                higher preference over the values set by
                                flash.sh. In case of NFS booting, this script
                                adds NFS booting related arguments, if -i option
                                is omitted.
        -F <flasher> ---------- Flash server such as cboot.bin.
        -G <file name> -------- Read partition and save image to file.
        -I <initrd> ----------- initrd file. Null initrd is default.
        -K <kernel> ----------- Kernel image file such as zImage or Image.
        -L <bootloader> ------- Bootloader such as cboot.bin or u-boot-dtb.bin.
        -M <mts boot> --------- MTS boot file such as mts_si.
        -N <nfsroot> ---------- i.e. <my IP addr>:/my/exported/nfs/rootfs.
        -R <rootfs dir> ------- Sample rootfs directory.
        -S <size> ------------- Rootfs size in bytes. Valid only for internal
                                rootdev. KiB, MiB, GiB short hands are allowed,
                                for example, 1GiB means 1024 * 1024 * 1024 bytes.
        -T <ext num sectors> ---The number of the sectors of the external storage device.
                                The default value is 119537664 if this option is not set.
        -U <int num sectors> ---The number of the sectors of the internal storage device.
                                The default value is 119537664 if this option is not set.
        -Z -------------------- Print configurations and then exit.
        --no-flash ------------ perform all steps except physically flashing the board.
                                This will create a system.img.
                                If combined with --rcm-boot, the command will generate rcmboot_blob.
        --external-device------ Generate flash images for external devices
        --sparseupdate--------- only flash partitions that have changed. Currently only support SPI flash memory
        --no-systemimg -------- Do not create or re-create system.img.
        --bup ----------------- Generate bootloader update payload(BUP).
        --single-image-bup <part name> Generate specified single image BUP, this must work with --bup.
        --bup-type <type> ----- Generate specific type bootloader update payload(BUP), such as bl or kernel.
        --multi-spec----------- Enable support for building multi-spec BUP.
        --clean-up------------- Clean up BUP buffer when multi-spec is enabled.
        --usb-instance <id> --- Specify the USB instance to connect to;
                                <id> = USB port path (e.g. 3-14).
        --no-root-check ------- Typical usage of this script require root permissions.
                                Pass this option to allow running the script as a
                                regular user, in which case only specific combinations
                                of command-line options will be functional.
        --uefi-keys <keys_conf> Specify UEFI keys configuration file.
        --rcm-boot ------------ Do RCM boot instead of physically flashing the board.
        --sign ---------------- Sign images and store them under "bootloader/signed"
                                directory. The board will not be physically flashed.
        --image --------------- Specify the image to be written into board.
        --boot-chain-flash <c>  Flash only a specific boot chain (ex. "A, "B", "all").
                                Defaults to "all", inputs are case insensitive.
                                Not suitable for production.
        --boot-chain-select <c> Specify booting chain (ex. "A" or "B") after the board is flashed.
                                Defaults to "A", inputs are case insensitive.
        --pv-crt -------------- The certificate for the key that is used to sign cpu_bootloader
        --with-systemimg ------ Generate system images also when using -k option
        --pv-enc <enc_key>----- The encryption key that is used to encrypt cpu_bootloader.
        --uefi-enc <uefi_enc_key> Key file (0x19: 16-byte; 0x23: 32-byte) to encrypt UEFI payloads
        --uda-dir-------------- Directory to store user data that will be encrypted in UDA partition.
        --generic-passphrase -- Use generic passphrase for disk encryption.
        --disable-random-iv --- Disable generation of random IV, SALT1, SALT2 and DERSTR.
        --read-info ----------- Read and display board related info, fuse info (based on fuse_t234.xml),
                                and EEPROM content.
        --reuse-uuid ---------  Reuse uuid which is already generated first time.
        --qspi-only  ---------  Flash QSPI device only.
        --gen-rcmdump --------  Generate rcmdump_blob

Error: failed to generate images
Cleaning up...
11

Hi again,

From now on, I am not able to flash the board any more, either with the command line or with the SDK Manager. Below is the error of flashing with the SDK Manager :
SDKM_logs_JetPack_6.2_(rev._1)_Linux_for_Jetson_Orin_Nano_8GB_2025-07-24_22-19-40.zip (280.0 KB)

12

Hi @KevinFFF,

To update, if I uninstall the JetPack_6.2_Linux_JETSON_ORIN_NANO_TARGETS and re-install it again, I can re-flash the board both with SDK Manager and the command line.

What was the problem with your previous suggested command ? Do you need me to do more tests and / or provide more logs?

Best Regards,
Khang.

13

You should replace t186ref with generic as you are using Jetpack 6.x.

I think the previous command I provided should work as we’ve verified it working on the Orin Nano devkit.

14

Hi @KevinFFF,

Thanks for your feedback.

I think the previous command I provided should work as we’ve verified it working on the Orin Nano devkit.

Did you mean with or without the replacement from t186ref to generic with Jetpack 6.x?

Thanks,
Khang

15

For Jetpack 6.x, you should use generic instead.

1 Like
17

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