I am not new to SOC, linux or even flashing images. I did get a new Super Jetson Nano Orin developer board and are never able to read the Jetpack 6.1 rev 1boot image.
I used different SD cards SDHC and SDXC with either exFAT or FAT32 file system before the flash.
I always end up in the UEFI shell as the SD card is just not being read.
We had a recent update to the nvidia/JetsonOrinNano-start home page.
So now the instructions say Initial Setup Guide for Jetson Orin Nano Developer Kit
That you have to check the UEFI is > 36.0 .
In case of my out of the box Super Orin developer kit I get 3.0-32616947 built on 2/21/2023. So this is out of range.
This new instructions using an older version disk image JP513-orin-nano-sd-card-image_b29. And the great surprise - with a newly flashed SD I get one step further … Now the UEFI works to start a bash shell and dies there with the JP 5.13 image.
So this is still an unmitigated disaster of a rollout in my book. It might be a very old rededicated leftover kit from vendor, but up to now a waste of my time.
It will not boot a 6.x image if the boot loader is setup for 5.x image.
The 6.1 rev1 image does enable the “super speed” option.
You will have to use their sdkmanager to flash it, that is the simplest way to go. After the bootloader is updated you can boot any of the 6.x images / install nvme etc.
Also, it takes a long time to boot, it seems like they are booting then booting again. Why??? I don’t know yet.
The 5.x image is said to be used to flash the UEFI and upgrade to >36.0 and then use the 6.1 rev 1 SD. This is a new procedure that does not require a separate Ubuntu running computer to flash the UEFI.
This is the Super Orin Nano dev kit and no I do not want to install ubuntu on another computer to flash the device that was delivered to me 12/20/2024 in a state that makes it unusable out of the box.
Please read the updated instructions and notice that they say use the 5.13 …b12 image to do this without SDK manager.
Yes, you can follow the updated instructions to upgrade the UEFI version without sdk manager.
If you’re using Ubuntu, the SDK Manager is an alternative and recommended method.
I will start a new entry to just document the failure of the jetpack 5.13 image method if you do not see something in the serial console logs that explains why UEFI fails to go beyond a failed bash.
The attached putty logs show 2 attempts to start the device and get into a bash shell. The output to screen is so fast - that I have no way to capture it.
Ready for any suggestion to how to capture it.
I am assuming you are on the linux debug port. Use gtkterm along with ttl adapter and select the option to log. You will have a readout of most of the boot.
I am using the RX/TX of the serial console log and the putty logs show what happens with device initialization. When the UEFI boot process kicks in the output is only seen on the HDMI port/not on the serial console. Thx for the suggestion.
I’m think I’m in the same boat. First attempted the 6.X rev1 image and it booted stating there was no network connection then jumped to a Shell prompt where I couldn’t do much of anything. From there I found this thread and followed the link and tried using the 5.1.3 image, only for it to boot into a blank screen.
Haven’t tried to hook into the serial port myself as I have to dig out a serial cable from the abyss, but I’m on UEFI Firmware 3.0-32616947 built on 2024-02-21T18:13:46+00:00
Also in blatant agreement with @moyo101 – this onboarding is far from ideal.
Is the Bash shell similar to bash-5.0#?
Based on your log, it seems to be functioning normally. Have you noticed any errors displayed on the HDMI port?
Hi David,
I have only been able to external screen shot the HDMI output - so see the attached screenshots of pre and after starting shell.
As it only takes 1.7 seconds before initialization of Linux kernel fails.
The only obvious error i see is that it complains about a missing network driver. Tried with or without internet cable attache.
Regarding SDK manager - did you ever tried a raspberry PI 5.0 Unix to use your SDK Manager?
With our internal review, we confirmed that the super mode configuration is flashed to QSPI and other partitions during the flashing process. Therefore, the SD card upgrade method is currently unable to enable super mode.
To enable super mode, please use a physical Ubuntu (or dual boot) and install SDK Manager to flash the device.
We apologize for any inconvenience this may cause.
Just today, on 10th Jan 2025 I received the Jetson Orin Nano Super kit. I am getting the same issue - unable to boot.
Tried with Jetpack 6.1 on SD. It went to shell prompt
Reformatted SD, flashed SD again with same Jetpack 6.1 image. Same issue - shell prompt.
Then reformatted SD and flashed with 5.1.3 version ( JP513-orin-nano-sd-card-image_b29.zip). Screen goes blank with blinking light and nothing on it.
Checked all boot sequences (always SD as the first boot device).
Same error.
My device’s firmware is also the same old 3.0-32616947 built in 2023.
I am not happy with the fact that Nvidia knew this issue and still sent the old firmware (2023) in 2025 which cannot boot any of the images (neither 6.1 or 5.1.3).
I am stuck here now on Friday late night (actually Saturday now as it is half past midnight European hour).
Can NVIDIA provide me with the resolution asap on this please ? I really need to test a certain solution asap.
How should I make it work ? (note: I do not have any Ubuntu PC and neither I want one).
I am getting the same issue described here. I followed the Get Started Guide to the exact letter for creating a microSD card on my Windows PC. When I insert the microSD card and turn on the Jetson Orin Nano Super Developer Kit, it just goes to the shell prompt. Embarassing that NVIDIA is shipping devices that don’t work out of the box. I have to flash the firmware to make it work? Lol. Nice one guys.
I will try the SDK Manager option and see if that works.
Okay, I was able to resolve the boot issue. I used SDK Manager (installed on a spare Linux computer) to flash the Jetson Orin Nano following the instructions here:
I’m a BRAND NEW Nvidia product owner and I can tell you, this is certainly NOT the way I anticipated starting my journey with these products.
Given the huge pile of cash the company is currently sitting on, I intend to proceed with filing a class action lawsuit given our current (circa 2025.01.12) experience with all the Jetson Nano Orin “Super” Development Kits that we as hard paying customers have received thus far.
I do not own another PC with Ubuntu installed so CANNOT take the SDK Manager route. Therefore, again, given all the cash the company is currently sitting on they can easily afford to refund our funds (multiplied by 100x) given all the headaches and troubles a lot of us have been through to date and only to realize we’re in receipt of a NON-WORKING product
For those reading this comment that are utilizing Balena Etcher to flash your SD card on a Windows based machine, you’ll notice as well that MANY additional partitions are “created” during the validation phase of the flashing process (this is the last step - image actually DOES get transferred to SD card). This happens because Windows doesn’t recognize the image format so the thing NOT to do is continue formatting all those randomly created “partitions” as you’d be essentially removing the image from the SD Card. This is NOT a Balena Etcher issue (see: Etcher broke my USB stick … or did it?), but as noted by @DavidDDD this is indeed a Nvidia issue. Why this wasn’t tested thoroughly before Mr. Jensen Huang made his gleeful Nano Super announcement in December’24 is anyone’s guess.
Again, sad to say, lawsuit is coming. You WILL be hearing from my attorneys.
