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!
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
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.
After some tests, it looks like the precondition for this issue can be secure boot, please see explanation below:
jetpack 6.1 with secure boot, with jetson-orin-nano-devkit flag:
Could you share the kernel_tegra234-p3768-0000+p3767-0005-nv-super.dtbused in this case for further check?
Could you try to enable them one by one to clarify which one causes the issue?
Secureboot → Secureboot+UEFI secureboot → Secureboot + UEFI secureboot + Disk-Encryption
sorry, cannot perform it now, by 3 reason, restricted in time(specially I’ve solved the task) and few knowlegment in encryption, I just followed instruction from here for encryption:
and I am too afraid converting one additional jetson orin nano to brick, at it was before when I burned fuses for jetpack 6.1 as per instruction from jetpack 5…
Generally the topic can be closed, as I solved the initial blocking point. I’ve just checked how jetson-io config pins on not encrypted device:
Do you mean that this diff causing you hit “RuntimeError: No DTB found for NVIDIA Jetson Orin Nano Engineering Reference Developer Kit Super!” issue when you are using Jetson-IO with encrypted device?
No, this diff is not root cause of “RuntimeError: No DTB found for NVIDIA Jetson Orin Nano Engineering Reference Developer Kit Super!” error. This diff shall be done by Jetson-IO in runtime on device with encrypted disk, but I done this in Linux_for_Tegra/bootloader/generic/BCT/tegra234-mb1-bct-pinmux-p3767-dp-a03.dtsi file before flashing the encrypted device.
