Hi, I have a problem with my Jetson Orin Nano 4GB, I just purchased it two weeks ago… was trying to reset factory data and by mistake I just selected the “reset” option inside the BIOS, help me with a solution please. Then I enter “continue” and my screen goes black.
Hi espochtesis,
Are you using the devkit or custom board for Orin Nano?
The “Continue” and “Reset” option should be fine to be used.
Continue means keep booting up the board.
Reset means reset the board and boot up again.
Could you share the serial console log for further check?
I am using a devkit, where can I find the serial console log?
For Orin Nano devkit, please refer to the following instruction to get serial console log.
Jetson Nano & NX Style - Serial Debug Console - JetsonHacks
I have tried the steps in the recommended video but it won’t let me boot from the NVME flash drive, probably the drivers that recognize the NVME flash drive are not working. Help me with a video or instructions on how to format the NVME or SSD, make the proper partitions to reinstall the JetPack system.
We would like to check the serial console log for the boot issue.
To re-install the Jetpack on the devkit, you can get a standalone Ubuntu host PC and use SDK Manager.
I should be the simplest method to get it flashed and boot.
The notepad is all the serial console log of the Jetson Orin Nano, I noticed that the messages vary every time I start the UART communication, please help me by solving the problem, Thank you.
serial_console_jetson.txt (80.7 KB)
Is this Orin Nano one with an SD card only, or does it also have eMMC? I see things look good until it tries to mount a filesystem. It ends looking for eMMC (mmcblk01):
[ 16.405207] mount /dev/mmcblk0 /mnt
mount: /mnt: special device /dev/mmcblk0 does not exist.
[ 16.411224] Failed to mount /dev/mmcblk0 on the /mnt
It is mounting to “/mnt”, but if there is code in “/boot” of eMMC, then it can’t do that. It really looks like it is incorrectly set up to use external media (apparently there is an NVMe that does work). Note that sometimes boot will chain load, and use eMMC “/boot” content, then switch over to the NVMe. There may also be changes required in any initrd to change boot device. I think this is just a question of incorrect filesystem mounting while working with external media.
My Jetson Orin Nano does not have SD or eMMC. So the only bootable device would be NVME.
Developer kits have an SD card on the module itself (not the carrier board). All other Nanos (including original, TX2, Xavier and Orin) all have eMMC. Do you mean that only the NVMe was prepared? The actual setup for NVMe changes depending on model. If you have a dev kit you might not have an SD card inserted, but the slot definitely exists under the module, and procedure changes depending on model. There are no other options.
Do you have any other solution? the Jetson Orin still won’t start, it stays on a black screen or how can I mount the boot drive correctly?
[ 3.605157] Mount initrd as rootfs and enter recovery mode
From the log you shared, it seems booting into recovery kernel
Have you tried to use standalone Ubuntu host PC for SDK Manager to flash the NVMe SSD?
Beware that Jetsons do not have a “traditional” BIOS. Almost every computer you know of has an actual hardware BIOS with its own operating system. It does things like bringing up power rails and clocks in the correct order before finding an entry point for the boot chain. Jetsons have this entirely in software (thus they consume less power and exist with a smaller footprint). For a model with eMMC, this content is in partitions in the eMMC; for an SD card dev kit model, this is in QSPI memory. Every time you flash the Jetson it also flashes that content, and unlike a desktop PC, normal install of an o/s also performs the equivalent of a BIOS flash.
Since the BIOS is not a traditional “in hardware” BIOS, it also means that some of the boot parameters are set at the time of flash, and not set by the BIOS. Eventually it gets to the same UEFI that a traditional BIOS would get to, but setting it up to do so differs. You might end up needing to flash again if the original flash was incorrect.
An added twist on this is that we don’t know if this is really a developer’s kit. You said it doesn’t have eMMC or SD. This cannot be correct. The module itself, which mounts on the carrier board will always have one of these:
- No SD card on the bottom of the module, but eMMC.
- An SD card slot on the bottom of the module, and no eMMC.
There are no other possibilities to those two conditions; one of them must be true, and the other must be false. Setting up boot and knowing the correct commands makes knowing which it is critical. Take a very very close look at the module itself. Look at the edge of the module PC board. One of the long edges will show some sort of SD card (or micro SD) slot which is under the PCB, but above the carrier board. If not, then you are guaranteed you must have eMMC, even if you don’t use it. If you have an SD card model, then only the o/s goes on the SD card. For external media, the o/s goes on the external device, except there might be software on the SD card /boot which helps in chain loading to the external device. This latter means you won’t be able to boot the external device without the SD card.
Now if it turns out you have some particular model of module, you will still have some third party manufacturer’s carrier board. Only the dev kit with the SD card slot comes with the dev kit carrier board. All other modules require adding a separate carrier board. Those third party carrier boards also have customizations (most of the time, not always) that require yet different flash commands and/or software (software difference is usually firmware, the device tree). There is no way to provide correct information if we are working with different hardware than we think it is. Most answers would end up wrong in some minor detail. Describing the specific hardware is extremely important.
Ok I understand, surely the Jetson Orin Nano has eMMC, I checked that there is no port to insert an SD card and it also seems that this happens with the new Jetson (here I attach an image showing the resources on board). To come to a solution I will provide all the data I have from my purchase, I hope it will be useful:
- Jetson Orin Nano 4 Gb Dev-kit.
- System Firmware version 36.3.0
-Date: 06-05-2024
-Jetpack 6.0
I’m thinking this is a third party carrier board rather than a developer’s kit carrier board, but I have not seen enough of them to identify from this picture. If there is a micro-SD slot, then it would be underneath the module on the edge which is closest to the carrier board edge (the edge without components to get in the way of the micro-SD). You’d see the slot lining up exactly with the edge of the module such that looking straight down on it would hide the slot, but looking underneath the module you’d see evidence that there is a micro-SD slot. If that is not present, then you have both a commercial module (meaning it is sold separately and not as a developer’s kit; not to be confused with “industrial” model), and a third party carrier board.
In the case of a third party carrier board with a commercial module (no SD card on the module; no commercial module has an SD card, they all have eMMC and any SD card slot would be on the carrier board itself), the software you need is provided by the third party carrier board manufacturer. It is possible that the carrier board design exactly matches the NVIDIA reference design, in which case this works with NVIDIA’s software. Here are the possibilities:
- The carrier board exactly matches NVIDIA’s design. The third party manufacturer will state that you can use NVIDIA’s flash software.
- The third party might offer a patch which is applied to NVIDIA’s flash software, and from then on you can flash with that (normally this patch is in the form of a device tree and perhaps a
.conffile). - The third party will tell you to use their software (which is basically a patched NVIDIA flash software).
Identifying what hardware you have is the only way to proceed.