JetPack6.2 super mode Orin NX/NANO can't use jetson-io.py

Hi NV_Team,

When we upgrade to JetPack6.2 super mode for Orin NX/Nano.

nvidia@nvidia-desktop:~$ cat /boot/extlinux/extlinux.conf
TIMEOUT 30
DEFAULT primary

MENU TITLE L4T boot options

LABEL primary
      MENU LABEL primary kernel
      LINUX /boot/Image
      INITRD /boot/initrd
      APPEND ${cbootargs} root=PARTUUID=a19afc82-0bae-49f1-b900-b5840bf3af96 rw rootwait rootfstype=ext4 mminit_loglevel=4 console=ttyTCU0,115200 firmware_class.path=/etc/firmware fbcon=map:0 nospectre_bhb video=efifb:off console=tty0

Can’t use config-by-hardware.py to configure dtbo and 40Pin

sudo /opt/nvidia/jetson-io/jetson-io.py (Failed)

But we can set dtbo by manually modify extlinux.conf

Hi Luna2020,

Are you using the devkit or custom board for Orin NX/Nano?

How did you upgrade to JP6.2?
Is there any error when you run jetson-io.py?

Hi KevinFFF,

We are using devkit for Orin Nano 8GB

Whole flash JetPack6.2 on my devkit with SDKManager.

Nothing appear after run jetson-io.py, but JP6.1 jetson-io.py works fine.

Do you have SD or NVMe connected on your board?
Please share the result of following commands for further check.

$ cat /etc/nv_tegra_release
$ cat /etc/nv_boot_control.conf
$ lsblk
$ df -h

Hi KevinFFF,

Please refer the following info.

nvidia@nvidia-desktop:~$ cat /etc/nv_tegra_release
# R36 (release), REVISION: 4.3, GCID: 38968081, BOARD: generic, EABI: aarch64, DATE: Wed Jan  8 01:49:37 UTC 2025
# KERNEL_VARIANT: oot
TARGET_USERSPACE_LIB_DIR=nvidia
TARGET_USERSPACE_LIB_DIR_PATH=usr/lib/aarch64-linux-gnu/nvidia
nvidia@nvidia-desktop:~$ cat /etc/nv_boot_control.conf
TNSPEC 3767-300-0003-R.1-1-1-jetson-orin-nano-devkit-super-
COMPATIBLE_SPEC 3767--0003--1--jetson-orin-nano-devkit-super-
TEGRA_BOOT_STORAGE nvme0n1
TEGRA_CHIPID 0x23
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0
nvidia@nvidia-desktop:~$ lsblk
NAME         MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0          7:0    0    16M  1 loop 
zram0        252:0    0   635M  0 disk [SWAP]
zram1        252:1    0   635M  0 disk [SWAP]
zram2        252:2    0   635M  0 disk [SWAP]
zram3        252:3    0   635M  0 disk [SWAP]
zram4        252:4    0   635M  0 disk [SWAP]
zram5        252:5    0   635M  0 disk [SWAP]
nvme0n1      259:0    0 232.9G  0 disk 
├─nvme0n1p1  259:1    0 231.4G  0 part /
├─nvme0n1p2  259:2    0   128M  0 part 
├─nvme0n1p3  259:3    0   768K  0 part 
├─nvme0n1p4  259:4    0  31.6M  0 part 
├─nvme0n1p5  259:5    0   128M  0 part 
├─nvme0n1p6  259:6    0   768K  0 part 
├─nvme0n1p7  259:7    0  31.6M  0 part 
├─nvme0n1p8  259:8    0    80M  0 part 
├─nvme0n1p9  259:9    0   512K  0 part 
├─nvme0n1p10 259:10   0    64M  0 part /boot/efi
├─nvme0n1p11 259:11   0    80M  0 part 
├─nvme0n1p12 259:12   0   512K  0 part 
├─nvme0n1p13 259:13   0    64M  0 part 
├─nvme0n1p14 259:14   0   400M  0 part 
└─nvme0n1p15 259:15   0 479.5M  0 part 
nvidia@nvidia-desktop:~$ df -h
Filesystem       Size  Used Avail Use% Mounted on
/dev/nvme0n1p1   227G   20G  196G  10% /
tmpfs            3.8G  172K  3.8G   1% /dev/shm
tmpfs            1.5G   27M  1.5G   2% /run
tmpfs            5.0M  4.0K  5.0M   1% /run/lock
/dev/nvme0n1p10   63M  110K   63M   1% /boot/efi
tmpfs            762M  108K  762M   1% /run/user/1000

Thanks for sharing the info.
It seems you have only NVMe SSD connected.

Have you also tried using the following command to flash the devkit?

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