I took a break from working on my Turing Pi 2, to try out the Orin Nano Dev Kit. I knew I wanted to run an SSD NVMe with my new Nano. (Inland QN322 1TB SSD NVMe PCIe Gen 3.0x4 M.2 2280 3D NAND QLC). So I created the SD Card with Etcher (just in case) and proceeded to try to follow the directions. I didn’t have a separate computer so I mistakenly used a VM (Virtual Box) and followed JetsonHacks directions. I had issues with the USB detection of the Nano when it was in forced recovery mode, until I put in the USB filter. I thought I had it all set, and flashed with JetsonHacks scripts. But I did get an error.
No flash flag enabled. Exiting saving flash command in flashcmd.txt *** no-flash flag enabled. Exiting now... *** User can run above saved command in factory environment without providing pkc and sbk keys to flash a device Save initrd flashing command parameters to /home/vboxuser/bootFromExternalStorage/R35.3.1/Linux_for_Tegra/tools/kernel_flash/ initrdflashparam.txt /tmp/tmp.PLyT4pvc8r ~/bootFromExternalStorage/R35.3.1/Linux_for_Tegra writing boot image config in bootimg.cfg extracting kernel in zImage extracting ramdisk in initrd.img /tmp/tmp.PLyT4pvc8r/initrd /tmp/tmp.PLyT4pvc8r ~/bootFromExternalStorage/R35.3.1/Linux_for_Tegra 55735 blocks cp: cannot stat '/home/vboxuser/bootFromExternalStorage/R35.3.1/Linux_for_Tegra/rootfs/lib/modules/5.10.104-tegra/kernel/drivers/mtd': No such file or directory Cleaning up...
But I took a break and then discovered when I came back, I could not get it to work. When ran the Nano, the default screen opened and asked for a language but then I must have hit the wrong key and voila, no more Jetson for me! I suspected the flash went up in smoke.
So I decided to try the SDK Manager, but again, can’t get passed 1) the recognizing the nano and 2) USB issues. I’ve tried multiple USBs etc, and discovered through the forums (thank you everyone!) that it’s likely something on the Nano was flashed or changed. Okay, gave up that dream.
So I thought, three days into this I’d just go with the SD care. Ha, they got me! Same issue. Can’t get it to boot passed the bios/start screens. It tries to boot off http or goes to the shell.
So I learned:
- The VM isn’t an option.
- Scripts on @JetsonHacks don’t work with VM. (VBox) and if you do use it, make sure to have enough hard drive space. I went through a few VMs to learn that)
- ACranky_Cyborg had a terrific idea that I’d love to try. (BLOG) - Boot from NVMe without using SDKManager or external Ubuntu PC (A solution that works) However the problem still remains 1) need to use SDK Manager and 2) Need 386 machine. (Where I am I have nothing but Macs and Raspberry Pi’s available) and 3) can’t use Cranky’s idea without an actual image on an SD card. (Any suggestion???) I don’t think it would work without a ‘working’ SD Card, which I don’t have because I need to use SDK manager to flash… which means I wouldn’t need Crankys solution then.
QUESTION OF THE DAY: Given all of this. I would like a solution. I’m no where near a microcenter. What would be the best, cheap option for a ‘minimal’ system to run Ubuntu that would work with the Nano Orin??? X86 is old and I see no interest in investing good money into a one-time use computer
Could I install SDK Manager on a Raspberry Pi 4 (8GB) with either 64 or 128 GB SD Card and use that to flash the Jetson?
What are other people doing to solve this problem?
Is there any solution to reset this without using SDK Manager so we can go back to the SD Cad?