NOTE: This all sort of applies the same for both Nano and TX1, but I am wording for Nano since this is the Nano forum.
I’m not sure if I am just reading the language incorrectly or not, but the Nano would be the target. Host would have to be a desktop PC format amd64/x86_64 Ubuntu. The result of this would install to the Nano when run for flashing the Nano.
The actual flash software is available only in binary form and is not publicly available. There are no options for running this flash software anywhere except on a regular host PC (to emphasize, the GUI requires Ubuntu 18.04 PC, but command line flash works from most any Linux PC using any distribution). It is a common topic in the forum to talk about options for self-flash (doesn’t really exist). The more recent L4T releases (the part which actually gets flashed to the Jetson) are able to do release upgrades via packages and thus avoid needing a host PC for version upgrades. Older L4T releases do not have that ability.
I usually use Fedora, and so I cannot use the GUI (I have a dual atom 10" laptop running Ubuntu 18.04 I can remote display to Fedora if I have to). Command line flash works quite well from virtually any Linux PC.
You can download the “driver package” and “sample root filesystem” without JetPack/SDKM. A list of releases are here (you may need to log in, and then go there again…only the more recent release allows future upgrades without SDKM):
In the case of using JetPack/SDKM, if you know where to look, there is a file called “
repository.json”. This contains a base URL address, and various locations to download specific content. You can in fact download these manually. In the case of “
.deb” files for packages to optionally install to the Jetson, then after flash you can copy these to the Jetson and manually install them with
apt. The nice part about SDKM/JetPack is that it understands dependencies and install orders…if you do this manually you may need to experiment to find the correct install order.
Tip: If you use
dpkg to install, and name several
.deb files at the same time, then
dpkg is at least smart enough to correctly order install for those particular packages. Using
apt-get adds resolving dependencies over the internet.
Issues with not being in recovery mode are often due to using a charger cable instead of the dev kit cable, or using a VM (VMs don’t handle USB correctly unless you configure them to).