I’ve been battling against my new Jetson Orin Nano 8GB Dev Kit for a few days now and have finally reached a point where I don’t know how to proceed.
I don’t have access to a Linux-native machine, so I’m running an Oracle VM and have followed all steps shown in this thread.
The process I’m going through to flash is: open SDKmanager with dev kit plugged in and in forced recovery mode (using a jumper between “FC REC” and GND) >>> get through steps 1 and 2 >>> when downloading has finished and final menu screen comes up, remove jumper and select “Manual” mode, with Runtime selected as the OEM configuration and NVMe as the storage device, as per the thread linked above.
I’ve attached the most recent logs. Interestingly on this try, on the final menu window I was prompted to create a new username and password (between “OEM Configuration” and “Storage”), but this option wasn’t there on previous attempts (note that I had just increased the VM’s available RAM from 4GB to 16GB so that might be related).
I massively appreciate any guidance. I’d really prefer to use the SSD for booting rather than a microSD card.
we do not officially support flashing on a VM.
If you do need to boot from SSD, you may use the SD card image as mentioned by @kayccc,
make sure it can boot up, and copy the rootfs to the SSD with tools like this:
As it happens, I went to try both of these this morning and my Jetson refuses to boot… after powering on I get the NVIDIA splashscreen and nothing else. I’ve left it for over an hour and nothing happens… I’ll pick up a faster + bigger microSD and hopefully the system will be usable then.
NVMe SSDs has gotten very cheap recently, and you may consider buy one. They should be way faster than SD cards.
Yep - I’ve got one, and have been trying to get it to be the main boot device, but I don’t have access to a Linux computer. I tried setting up a dual-boot on my PC but it didn’t work. I’m planning on getting a new computer in the next few months (which will be dual-boot) so I’m thinking of just suffering the slow speeds until then.
Whenever you have a boot problem like that, be sure to get a serial console boot log. Serial console logs include boot content from long before the actual Linux kernel ever loads. It’ll show details the local monitor does not show.
Finally was able to get the Dev Kit to boot from NVMe by sacrificing Windows 10 from my (semi) old PC and booting Ubuntu 20.04 from it. Certainly not an ideal solution, but at least now I have a Linux computer on hand for all the other robotics tasks that require it.