Hi Team,
SDK manager opening with –show all version and –archived-version command not listing that Jetpack 6.0.0. Please clarify how to do this.
Thank you
What version did you see there?
it just list down jetpack versions 6.2.1, 6.2, 6.1 and 5.xxx but no 6.0
JetPack/SDK Manager is really just a front end to the actual flash software (which used to be purely command line long ago). What actually gets flashed is L4T, which in turn is what you’d call Ubuntu after adding the NVIDIA drivers. Normally there is a release of JetPack with each L4T release, and the default is that release of JetPack to one release of L4T unless you specify different. When you are looking for JetPack 6.0 you are really looking for L4T R36.3. There was a “developer preview” as well, which is not normally used, it is L4T R36.2.
You can find a list of JetPack releases, along with the relevant L4T version here:
https://developer.nvidia.com/embedded/jetpack-archive
Or you can go straight to the L4T release (which then also shows the JetPack/SDKM release):
https://developer.nvidia.com/embedded/jetson-linux-archive
As new JetPacks get added, “in theory”, the old ones are accessible via the “--archived-versions”, but some might get left out. In particular, a DP (Developer Preview) probably gets left out. The command line content would probably still be available, although it isn’t as convenient. So do you really want L4T R36.3? Or maybe developer preview L4T R36.2?
I need L4TR36.3 and if this gets available from SDK manager it would be easy to flash it directly. How to get this available? I tried with –archived-version from command line but no luck.
Someone from NVIDIA would have to check on that, maybe @kayccc or @WayneWWW. If you are ok to use command line, then you could go to the L4T R36.3 content, download the “driver package” and “sample root filesystem”, and then:
- Unpack the driver package as a regular user. This creates subdirectory “
Linux_for_Tegra/”. - In “
Linux_for_Tegra/rootfs/” unpack the sample rootfs as root. - From “
Linux_for_Tegra/”, run “sudo ./apply_binaries.sh”.
That above needs to be run only once. You can flash as many times as you want now on command line.
Look at these files in “Linux_for_Tegra/”:
ls jetson*.conf
If you remove the “.conf” suffix, then the remaining name is a flash target. For example, “jetson-agx-xavier-devkit.conf” is target “jetson-agx-xavier-devkit”. The name will be a combination of the module type and the carrier board (obviously a “devkit” is for developer’s kits, and not for third party carrier boards).
There are different instructions if you are flashing external devices, e.g., an NVMe. For eMMC flash it would go something like this:
sudo ./flash.sh jetson-agx-xavier-devkit mmcblk0p1
(the mmcblk0p1 is eMMC)
If you have trouble with this, then you can log it and post the log here:
sudo ./flash.sh jetson-agx-xavier-devkit mmcblk0p1 2>&1 | tee log_flash.txt
This doesn’t add components to the desktop PC, and will be missing some optional components, but those can be added with apt-get.
I would say just follow linuxdev’s comment or just upgrade to later Jetpack.
It is not good idea to still use JP6.0 when we already had lots of known bug fixed in later release.
Yes I got it. Decided to go with JP6.2.1 itself.
Thank you