Originally I flashed the SD card with both Jetpack 5.1.3 and Jetpack 6.1 but when I power on the Jetson, the logo shows up for a second then the screen goes blank.
I then found out that I should use he SDKManager. So I have a VM running on Ubunto 20.04 and downlaoded and installed Jetpack 5.1.4, I have it in recovery mode, and it does show up when I run lsusb in the terminal. I then start Flahsing it, but it gets stuck at 99%, and the following erorrs show up in the sdkmanager terminal.
Not sure what the issue is. You see when I run sdkmanager it detects the board as Jetson orin nano, but I recently found out that when I power on the board and repeatedly press ESC, which takes me to a setup screen, which shows the device manager and boot manager. And I noticed that on the top of the screen abvove ythe UEFI firmware infromation it says Jetson Orin NX DevKit. Even though I know 100% that it is a jetson orin nano devkit. So now I am wondering could that be the issue.
I have also tried flashing it from the terminal by doing sudo ./flash.sh jetson-orin-nano-devkit mmcblk0p1 but after a while of running it, it ends with saying “failed flashing generic”.
Need help flahsing it because I have been at it for a while now with no success of being able to start working on my project.
Please do not share your sdkmanager log like this. There is a “EXPORT LOGS” button in your sdkmanger GUI, click it and attach the whole zip file here. We need full text log.
Ok thank you for the reply. Before I try the first step you gave me in which I would have to delete the virtualbox and restart with vmware. I have attached the log file like you asked and I am hoping I can solve it with the current setup. SDKM_logs_2025-01-09_23-05-46.zip (242.6 KB)
209 22:52:43.339 - Info: Copying nv_boot_control.conf to rootfs
1210 22:52:43.499 - Info: populating kernel to rootfs… done.
1211 22:52:43.499 - Info: populating initrd to rootfs… done.
1212 22:52:43.499 - Info: populating kernel_tegra234-p3767-0000-p3768-0000-a0.dtb to rootfs… done.
1213 22:52:43.499 - Info: Making system.img…
1214 22:52:46.079 - Info: Setting “FDT /boot/dtb/kernel_tegra234-p3767-0000-p3768-0000-a0.dtb” successfully in the extlinux.conf…done.
1215 22:52:46.079 - Info: populating rootfs from /home/vboxuser/nvidia/nvidia_sdk/JetPack_5.1.4_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/rootfs …
It is just running here and this one is the slowest part of preparing files when doing flash. I don’t know how long you waited here and stop the process. If it lasted for more than hours and still stuck here, then might be a problem. However, if you just stop it within 5 or 10 mins, then I think you should just wait for it.
I tried flashing it again and wated for well over an hour, but the process still gets stuck at 99%, and I encounter multiple errors. I’ve attached the exported log file.
As a side note, I noticed something unusual before flashing: when I powered on the device and connected it to a display, the boot screen identified the device as a “Jetson Orin NX.” However, SDK Manager correctly detects it as a “Jetson Orin Nano,” which matches the device I purchased. Given this discrepancy, could the issue be related to hardware or firmware rather than software? I’m wondering if there might be a mislabeling or defect with the device itself. SDKM_logs_2025-01-10_17-34-21.zip (215.4 KB)
I just double checked the log as your side note mentioned and it ineed looks a little weird in the flash log.
Would you might share the result of “ls /home/vboxuser/nvidia/nvidia_sdk/JetPack_5.1.4_Linux_JETSON_ORIN_NANO_TARGETS/Linux_for_Tegra/kernel/dtb/” on your host?
What you notice in the side note is a problematic behavior.
Your system is detected as a Orin NX and everything flashed to your board is for Orin NX but not Orin Nano.
To be more precisely, it is more like “firstly it is a Orin Nano” and then when the flash really started, it got detected as Orin NX again and wrong software got flashed to it.
It still fails to flash and I noticed the same thing you noticed in the log. When I ran the command in the terminal I noticed board ID, version, sku were all gone towards the end.
So now the only option I have is to redo everything with vmware?
Or would that be useless because the issue is with the device itself?
I don’t think the device has any problem here. It is more like the VM/VB things are not really supported as I told since the beginning.
What I would suggest is
Get a native x86 host and do above again. I have confidence that you won’t hit above issue.
If you don’t want to use a x86 host, maybe you could follow this page. 🚀 Initial Setup Guide - Jetson Orin Nano - NVIDIA Jetson AI Lab
Plug in the jetpack5.1.3 sdcard first and see if you can do this firmware update. If even jp5.1.3 cannot boot, maybe you could share serial console log and I can help check what is wrong there first.
If it was showing “Recovery Boot”, we can show you steps to make your unit boot normally from the SD card (or you can follow my comments in the above forum thread).
