No DTB found for NVIDIA Jetson Orin Nano Engineering Reference Developer Kit Super!

Hello,

Maybe can you share with me other link for bug reports?

I’ve flashed Jetson Orin Nano Devkit(BOARDID=3767 BOARDSKU=0005) with Jetpack 6.2(L4T 36.4.3) with jetson-orin-nano-devkit-super

Now the command sudo /opt/nvidia/jetson-io/config-by-function.py function --list all, reports error:
RuntimeError: No DTB found for NVIDIA Jetson Orin Nano Engineering Reference Developer Kit Super!

Can you share a solution for this behavior, with jetpack 6.1 and jetson-orin-nano-devkit everything works fine.

Note:
Command sudo /opt/nvidia/jetson-io/jetson-io.py does not work at all.

Thank you in advance

Hello @oleg.burmistr

Could you please take a look at the workaround in Jetson Orin Nano 8GB Developer Kit not letting me run jetson-io.py - #8 by liviolima80 ?

Let us know how it goes!

Regards!
Eduardo Salazar
Embedded SW Engineer at RidgeRun

Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com/
Website: www.ridgerun.com

Jetson-IO issue of super board config should be fixed in the latest Jetpack 6.2(r36.4.3).

Could you share the commands how did you flash JP6.2 on Orin Nano devkit?

Hello, sorry for late response.
The workaround from Jetson Orin Nano 8GB Developer Kit not letting me run jetson-io.py - #8 by liviolima80 ?
does not helped me.

@KevinFFF steps are:
Edit Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-pinmux-p3767-dp-a03.dtsi according with suggestion from

:
$Generating keys
sudo ./apply_binaries.sh
sudo ./tools/l4t_flash_prerequisites.sh
python3 ./source/optee/samples/hwkey-agent/host/tool/gen_ekb/gen_ekb.py -chip t234 -oem_k1_key kek_optee.key -in_sym_key sym_t234.key -in_sym_key2 ./sym2_t234.key -in_auth_key auth_t234.key -out bootloader/eks_t234.img
sudo ./odmfuse.sh -i 0x23 -k rsa.pem -S sbk.key -X fuse.xml --noburn jetson-orin-nano-devkit

sudo BOARDID=3767 BOARDSKU=0005 ./tools/kernel_flash/l4t_initrd_flash.sh --network usb0 -u ./rsa.pem -v ./sbk.key --uefi-keys uefi_keys/uefi_keys.conf --uefi-enc sym_t234.key --no-flash --showlogs -p “-c bootloader/generic/cfg/flash_t234_qspi.xml” jetson-orin-nano-devkit-super internal
sudo cp bootloader/eks_t234_sigheader_encrypt.img.signed ./tools/kernel_flash/images/internal/

sudo BOARDID=3767 BOARDSKU=0005 ROOTFS_ENC=1 ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs -u ./rsa.pem -v ./sbk.key --no-flash --external-device nvme0n1p1 -i sym2_t234.key --uefi-keys uefi_keys/uefi_keys.conf --uefi-enc sym_t234.key -c ./tools/kernel_flash/flash_l4t_t234_nvme_rootfs_enc_my.xml -S 100GiB --external-only --append --network usb0 jetson-orin-nano-devkit-super external
sudo BOARDID=3767 BOARDSKU=0005 ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs -u rsa.pem -v sbk.key --uefi-keys uefi_keys/uefi_keys.conf --uefi-enc sym_t234.key --network usb0 --flash-only

sorry, now I understand what this time I copied edited tegra234-mb1-bct-pinmux-p3767-dp-a03.dtsi from jetpack 6.1(L4T36.4.1) instead of editing it from L4T36.4.3
and use jetson-orin-nano-devkit instead of jetson-orin-nano-devkit-super of sudo ./odmfuse.sh
I don’t think I will have time to perform flash once again in next few days. Maybe you would suggest any other updates in these steps. As soon as I will flash, I’ll provide results.
Thank you in advance

Do you want to enable super mode in your case?
If so, please just use jetson-orin-nano-devkit-super as board config during flash.

From the flash command you shared, do you enable disk-encryption, Secureboot and UEFI secureboot in your case and your board has been fused?

Hello @KevinFFF ,
Yes, we need disck-encryption, secureboot and uefi secureboot,.
In commands I shared, I use –noburn to sudo ./odmfuse.sh because the device was flashed before with Jetpack6.1. now I reflash it with Jetpack6.2 specially to have possibility to enable super power mode.

As you can see all flashed commands use jetson-orin-nano-devkit-super as board configuration. I copied all shared steps directly from bash script I use to flash devices. And super power mode is available, just I cannot config pins to command it via Jetson.GPIO.

If you have those requirements for security, please use the original key files during flash.

Do you mean Jetson-IO or Jetson.GPIO?
Do you mean that you can flash the board successfully but just can not configure the pins through config-by-function.py with JP6.2?

Please share the result of cat /etc/nv_tegra_release on your board.

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

Yes, I do

library on python (import Jetson.GPIO as GPIO)

We can not reproduce this issue on Orin Nano devkit with JP6.2.

Do you have another devkit to verify if it would work with the following command to flash the board?

$ 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

and run Jetson-IO with the following command after boot up.

$ sudo /opt/nvidia/jetson-io/jetson-io.py