I wanted to clarify something about models available…
Note that L4T (Ubuntu plus NVIDIA drivers) is what actually gets flashed, and that JetPack/SDK Manager is a flash tool used to perform that flash. The release versions are tied together though, so specifying a release of JetPack/SDKM generally implies a release of L4T.
There are actually both the older Nano (which I think you probably have since this forum is for that, plus you mentioned B01), and also an Orin version (which is much newer). Your “Nano” (if it is Orin I’d use that in its name, but “Nano” by itself to me usually means the older release) can be flashed up to L4T R32.x. The Orin can work with L4T R34.x+.
L4T and JetPack/SDKM releases are listed here (note that JetPack is the GUI part, and SDKM is a network utility attached to JetPack; originally it was just JetPack, then network and helper utilities were added):
For a Nano, you usually want your host PC to be Ubuntu 18.04.
A Nano dev kit is an SD card model whereby the SD card slot is directly mounted to the module; there is no eMMC on this model. Third party kits usually have eMMC, and any SD card slot is on the carrier board itself. All of the above links assume a dev kit. Third party models generally have a modification of the NVIDIA version of the flash software.
Nano dev kits have the operating system installed to the SD card, but there is a lot of boot content, along with the equivalent of what a BIOS would do, in QSPI memory. QSPI is on the module itself. The flash software can generate SD cards, but flashing a Nano dev kit implies updating the QSPI memory with a recovery mode Nano attached to the host PC and running the JetPack/SDKM software. Not all releases of SD card software are compatible with all releases of the QSPI content, so you’d almost always be advised to start with flashing the QSPI and perhaps generating an SD card for that release (some SD card releases work across a few QSPI releases, but it is better to just flash the QSPI if you change your SD card version and you don’t know if they are compatible).
The fact that Jetsons (and most embedded systems) don’t have a real BIOS is why they need a host PC to flash. eMMC models get everything from the flash software, not just the boot/BIOS content. I’ll advise going to the L4T releases in the earlier URL, pick the newest R32.x release, and go to that; then use the SDKM download from that page, going to an Ubuntu 18.04 host PC.
If you don’t have an Ubuntu 18.04 host PC, then dual boot is your best bet (but make sure you have plenty of disk space formatted as ext4). Some people make VMs work, but this is often frustrating since they don’t handle USB correctly (you’d need to ask the VM support for how to make the USB work correctly if USB disconnects and reconnects).
