Hi,
can anyone tell me why it is not showing SDK Version on SDK Manager when i connect Jetson Nano Developer kit using Micro USB to Ubuntu 22.04 for flashing purpose.
L4T is what actually gets flashed, and this is Ubuntu plus NVIDIA drivers. JetPack is just a GUI front end to the flash software (the “driver package” is what performs the actual flash, and this is essentially a driver for a custom USB device…in recovery mode Jetsons are such a device). JetPack only shows valid release combinations, which I will explain more about below.
The actual driver package is command line only. This is capable of flashing using a very wide range of host PCs, e.g., I used to use Fedora and the driver package, on command line, works on Fedora.
As soon as you add the GUI (JetPack), you will find that the GUI is supported on a limited set of host PC Ubuntu releases. The fact that JetPack came up shows your Ubuntu 22.04 host PC is valid with JetPack. This does not imply that this release of JetPack is valid with an older Nano.
The version of L4T which is valid for your Nano is not valid with your release of JetPack/SDK Manager. This is why you don’t see the Nano…version intersection of “JetPack+Nano L4T release+host PC release” leaves nothing. The host PC is visible because JetPack has components it can install.
If you backed off your host PC version to 20.04, then you would see the Nano. If you were to flash on command line, then this too would be able to flash (command line flash does leave out some features though).
You could go to the L4T release URL:
https://developer.nvidia.com/linux-tegra
Then you could manually download the “driver package” and “sample root filesystem”. Manual unpacking would allow command line flash:
- Unpack the driver package without
sudo. This produces a “Linux_for_Tegra/” subdirectory. - Go to “
Linux_for_Tegra/rootfs/”. - Unpack the sample rootfs with
sudo. cdback toLinux_for_Tegra/.- Run “
sudo ./apply_binaries.sh”. - This is now ready for as many flashes as you want without repeating the above.
If, within Linux_for_Tegra/, you look at this command:
ls -l jetson*.conf
…you will find all command line flash targets. You just leave off the .conf, and it is a target. The “jetson-” names are more human readable names pointing at files that are named after the module plus carrier board combinations, but they do the same thing.
You have to understand that if you have an SD card model of developer’s kit, then the targets differ from eMMC models. The boot content, and much of the “equivalent of a BIOS” content are in QSPI memory. If you use a pre-canned SD card, then you would still flash the QSPI target for your Nano (this flashes the actual module, but not the SD card). The memory you name when flashing an SD card Nano dev kit is mmcblk1p1 (if eMMC, then it would be mmcblk0p1). Example, if the Jetson is connected and in recovery mode:
sudo ./flash jetson-nano-qspi mmcblk1p1
Some targets are named after devkit as well, which are valid.
Optional packages, e.g. CUDA, would need to be manually installed via an apt-get command as well.
Hi ,
I have downloaded driver package and sample root filesystem for R32.7.4 which i need to install on my Jetson nano developer kit .
but in Linux_for_Tegra i am unable to find rootfs and when i enter sudo ./apply_binaries.sh it says command not found .
Can you explain me step by step ?
The driver package and sample rootfs install to a separate Linux host PC, and not directly to the Jetson. That host PC is then used to flash the Jetson when it is in recovery mode.
It is the unpacking of the “driver package” on the host PC which creates the Linux_for_Tegra/ subdirectory. This should create a lot of files within Linux_for_Tegra/, and other than a README type file in it, a blank Linux_for_Tegra/rootfs/. It appears that the unpacking of the driver package has failed.
The driver package file has the name jetson-210_linux_r32.7.4_aarch64.tbz2. If you go to some directory (I will use ~/Downloads/ as an example, but I recommend putting in its own location, e.g., ~/nvidia/), then unpacking is like this:
tar xvfj jetson-210_linux_r32.7.4_aarch64.tbz2
(requires the file to be in ~/Downloads)
Once this is done, you can cd Linux_for_Tegra and run “ls” and it should show lots of content. If your host PC ran out of disk space, then content would be missing. If you first “cd ~/Downloads”, what do you see from “df -H -T .” (the ‘.’ is important, it is an alias for “the current directory”)?
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.