wow, NV, are your tutorial docs and install instructions lacking. I’m a noob for this stuff, but getting the SD card loaded with the right image, and getting the Orin Nano booted, is really difficult, to say the least. I’m running Windows 11, and while I downloaded the 6.0 Jet Pack and successfully got it onto the Orin Nano, the orin won’t boot with the card in its slot. I do see it boot to bios, but if I try to boot the OS, it just stays blank indefinitely. I read some blurb that the QSPI bootloaders need to be updated vis sdkmanager, but iit is totally unobvious how to run sdkmanager from my windows machine. Running it from docker seems ridiculous, but then again, installing WSL2 and downloading the .deb file seems equally odd. Plus, am I supposed to “install” the update to the micro SD card while it’s attached to my PC via a card reader, or am I supposed to attempt to install it while the nano is connected to my computer via a USB cable? The docs do not spell this out.
You absolutely MUST have a native Ubuntu 20.04 or 22.04 64 bit Linux PC. No ARM, no 32 bit, no virtual machine. Install sdkmanager, and everything works.
well, I read the MUST and it’s all caps, so I’m assuming you’re emphatic enough to back it up in future replies. So WHY does it MUST be a 64-bit PC? I SHOULD be able to place the boot bits on the micro SD, shove it into the Orin Nano and “off we go”. WHY is the process of “updating the QSPI boot drivers” so difficult? Plus, you didn’t spell out: Is it trying to update the drivers that are on the Micro SD card, the ones that allow the Orin to boot off it, as part of the bootstrapping process (in which case it should be easy to just modify those files), or does it need to update some bit of firmware on the Orin Nano itself and need to do it over a COM port? The Orin has a process where it tries to boot off PXE off the network. Can I somehow put the image out there on my network?
They processor cores you see are not the first ones to start. The SOC has got a whole bunch of processors and cores invisible to you, and the Boot and Power Management Processor is the one that starts the LInux cores from QSPI. Updating the QSPI requires the BPMP to enter a special recovery mode where it receives the update data via USB0. This needs to take place before the Linux cores have been started. It’s just the way NVidia designed it, and things like cryptography and secure boot etc play a role here, so the whole protocol is undocumented.
The proper way to do this is via SDK manager from a physical Ubuntu 64 Bit PC.
Okay, set up the Ubunto x64 laptop. Orin Nano is sitting there with Micro SD in it. connected to the Unbuntu laptop w/ USB 3.0 cable. using lsusb from command line doesn’t show a connected nano. (I’m no Linux user, yet). I installed the sdkmanager and ran it, and it doesn’t show Target Hardware as seeing any Orin connected. I don’t know if the Orin is supposed to be ‘found’ by the fact it has an ethernet cable plugged into it, or if it should be connected via USB. Nor do I see this in any of the documentation… I couldn’t get the two to connect, so I fooled around in the Orin’s BIOS and set it to some kind of “boot recovery” partition instead of the normal one. I also tried shorting FC_REC to GND, but it wasn’t clear if I was supposed to boot it with that jumper connected, or just short it briefly then reboot, or WHAT.
Tie FORCE_REC to GND.
Power on Orin
There should be a NVidia USB device
remove FORCE_REC-GND connection
Treat the forced recovery mode pins (short) as if it is the shift key on a keyboard and you have several keys which might use capital letters. You hold the shift (recovery) down (shorted), tap a key that uses shift, and then let go of the shift (recovery) key. What recovery buttons/short modifies is either (A) the power on, or (B) the power reset. So you modify either cold power on by having recovery during the power on, or you modify reset by having the recovery held while tapping the power reset.
I figured it out: bug in sdkmanagers UI. I had Orin nano connected by usb. I’m in the main page and Orin wasn’t in recovery mode. I shorted the pins and reset the device and then pressed the UI refresh button next to the hardware to flash. No identification. I manually selected the Orin development kit, went to the next page in the UI, as if I was going to start downloading, then pressed the back page. The Orin detection immediately popped up and was happily detecting my kit. It all installed fine.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.