Trying to install JetPack 4.6.1 from SDK Manager also installs 4.6.2

Autonomous Machines Jetson & Embedded Systems Jetson Nano
1

I’m working on a Jetson Nano project that requires a specific version of JetPack (4.6.1) and L4T (32.7.1). I’m using a Jetson Nano production module (eMMC, no SD card), and the component that requires these specific versions of JetPack and L4T is the Allied Vision CSI-2 Camera Driver (version 4.0.0).

I’m using the NVIDIA SDK Manager to flash the Jetson Nano, which is automatically detected by the SDK Manager. The SDK Manager flashing process seems to complete without any issue, and the Jetson Nano boots up as it should.

However, I’m getting an issue with the installation of the camera drivers, and ultimately the issue seems to stem from an unexpected bootloader file on the Jetson Nano. After flashing, it seems like some version of JetPack 4.6.2 has been unintentionally installed, and a number of the Debian NVIDIA packages on the Jetson Nano are version 32.7.2 instead of 32.7.1. I checked to see if the correct versions of JetPack and L4T had been installed with the reflash using the commands below:

JetPack Version: sudo apt-cache show nvidia-jetpack

Package: nvidia-jetpack
Version: 4.6.2-b5
Architecture: arm64
Maintainer: NVIDIA Corporation
Installed-Size: 194
Depends: nvidia-cuda (= 4.6.2-b5), nvidia-opencv (= 4.6.2-b5), nvidia-cudnn8 (= 4.6.2-b5), nvidia-tensorrt (= 4.6.2-b5), nvidia-visionworks (= 4.6.2-b5), nvidia-container (= 4.6.2-b5), nvidia-vpi (= 4.6.2-b5), nvidia-l4t-jetson-multimedia-api (>> 32.7-0), nvidia-l4t-jetson-multimedia-api (<< 32.8-0)
Homepage: http://developer.nvidia.com/jetson
Priority: standard
Section: metapackages
Filename: pool/main/n/nvidia-jetpack/nvidia-jetpack_4.6.2-b5_arm64.deb
Size: 29378
SHA256: 925f4abff97e6024d86cff3b9e132e7c7554d05fb83590487381b7e925d5b2bb
SHA1: e3ef727e87df5c331aece34508c110d57d744fe9
MD5sum: 7cb2e387af41bc8143ac7b6525af7794
Description: NVIDIA Jetpack Meta Package
Description-md5: ad1462289bdbc54909ae109d1d32c0a8

Package: nvidia-jetpack
Version: 4.6.1-b110
Architecture: arm64
Maintainer: NVIDIA Corporation
Installed-Size: 194
Depends: nvidia-cuda (= 4.6.1-b110), nvidia-opencv (= 4.6.1-b110), nvidia-cudnn8 (= 4.6.1-b110), nvidia-tensorrt (= 4.6.1-b110), nvidia-visionworks (= 4.6.1-b110), nvidia-container (= 4.6.1-b110), nvidia-vpi (= 4.6.1-b110), nvidia-l4t-jetson-multimedia-api (>> 32.7-0), nvidia-l4t-jetson-multimedia-api (<< 32.8-0)
Homepage: http://developer.nvidia.com/jetson
Priority: standard
Section: metapackages
Filename: pool/main/n/nvidia-jetpack/nvidia-jetpack_4.6.1-b110_arm64.deb
Size: 29366
SHA256: acfd9e75af780eab165361d61de4b4fe4974890864fe191060b402ac4c2f54d5
SHA1: a016568ac53705acc145a9f7e60505707bea259f
MD5sum: 79be976b184a8c885bd9169ea5b7fb7b
Description: NVIDIA Jetpack Meta Package
Description-md5: ad1462289bdbc54909ae109d1d32c0a8

L4T Version: cat /etc/nv_tegra_release

# R32 (release), REVISION: 7.1, GCID: 29818004, BOARD: t210ref, EABI: aarch64, DATE: Sat Feb 19 17:05:08 UTC 2022

Debian Package Versions: sudo apt list nvidia*

Listing... Done
nvidia-cg-doc/bionic 3.1.0013-3 all
nvidia-container/stable 4.6.2-b5 arm64
nvidia-container-csv-cuda/stable,now 10.2.460-1 arm64 [installed]
nvidia-container-csv-cudnn/stable,now 8.2.1.32-1+cuda10.2 arm64 [installed]
nvidia-container-csv-tensorrt/stable,now 8.2.1.8-1+cuda10.2 arm64 [installed]
nvidia-container-csv-visionworks/stable,now 1.6.0.501 arm64 [installed]
nvidia-container-runtime/stable,now 3.7.0-1 all [installed]
nvidia-container-toolkit/stable,now 1.7.0-1 arm64 [installed]
nvidia-cuda/stable 4.6.2-b5 arm64
nvidia-cuda-doc/bionic 9.1.85-3ubuntu1 all
nvidia-cudnn8/stable 4.6.2-b5 arm64
nvidia-docker2/stable,now 2.8.0-1 all [installed]
nvidia-jetpack/stable 4.6.2-b5 arm64
nvidia-l4t-3d-core/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-l4t-apt-source/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-l4t-bootloader/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-l4t-camera/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-l4t-configs/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-l4t-core/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-l4t-cuda/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-l4t-firmware/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-l4t-gputools/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-l4t-graphics-demos/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-l4t-gstreamer/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-l4t-init/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-l4t-initrd/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-l4t-jetson-io/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-l4t-jetson-multimedia-api/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-l4t-kernel/stable 4.9.253-tegra-32.7.2-20220420143418 arm64 [upgradable from: 4.9.253-tegra-32.7.1-20220219090432]
nvidia-l4t-kernel-dtbs/stable 4.9.253-tegra-32.7.2-20220420143418 arm64 [upgradable from: 4.9.253-tegra-32.7.1-20220219090432]
nvidia-l4t-kernel-headers/stable 4.9.253-tegra-32.7.2-20220420143418 arm64 [upgradable from: 4.9.253-tegra-32.7.1-20220219090432]
nvidia-l4t-libvulkan/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-l4t-multimedia/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-l4t-multimedia-utils/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-l4t-oem-config/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-l4t-tools/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-l4t-wayland/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-l4t-weston/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-l4t-x11/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-l4t-xusb-firmware/stable 32.7.2-20220420143418 arm64 [upgradable from: 32.7.1-20220219090432]
nvidia-opencv/stable 4.6.2-b5 arm64
nvidia-prime/bionic-updates 0.8.16~0.18.04.1 all
nvidia-settings/bionic-updates,bionic-security 470.57.01-0ubuntu0.18.04.1 arm64
nvidia-tensorrt/stable 4.6.2-b5 arm64
nvidia-visionworks/stable 4.6.2-b5 arm64
nvidia-vpi/stable 4.6.2-b5 arm64

For my project, I need JetPack 4.6.1 and all of the Debian packages to be the correct versions for L4T 32.7.1. Does anyone know why these other versions might be getting installed, and is there a way I can confirm that only the correct versions end up on my device? Thanks in advance.

3

Hello,

Do you mean if you install jp4.6.1 by sdkm, and then running apt commands to install jetpack, then it would install jp4.6.2 sdk to your device?

4

The best method to install another release would probably be to use the most recent JetPack/SDKM 4.x, and start it such that it allows selecting any release:
sdkmanager --archivedversions

Are you simply using a specific release, or are you using the recent release plus “--archivedversions”? My thought is that specifically selecting the version might enforce this, whereas using an older sdkmanager might automatically do something you don’t want. Not sure, but worth checking.

5

Hi Wayne, thanks for your response,

In the steps I’ve taken, there is no additional apt command to install JetPack; the jp4.6.1 is selected in the SDK Manager and flashed, then the commands above give the corresponding outputs without any other action. I’m not sure why flashing 4.6.1 would show anything on the device involving jp4.6.2 or L4T 32.7.2.

6

Hi linuxdev, thanks so much for writing,

I’m not sure if this answers your question exactly (if not, I apologize): I use the SDK Manager and, when presented with a list of JetPack versions to flash to the target board, the drop-down menu offers JetPack 4.6.1 (which is the one I want).

The version of SDK Manager I use is 1.8.0.10363. I’ve never launched the SDK Manager with sdkmanager --archivedversions, but if the JetPack version I want is already listed in the available versions, would the extra flag provide anything new?

7

Oh ok. So you mean you just click jp4.6.1 in sdkmanager to install sdk + OS, and it gives you 4.6.2 sdk?

What is the OS version here ? /etc/nv_tegra_release.

8

That seems to be the case. In the original post above, the output for /etc/nv_tegra_release is shown, which I think correctly shows L4T 32.7.1. However, when listing the JetPack version with sudo apt-cache show nvidia-jetpack, it lists jp4.6.2 above jp4.6.1.

9

I’m closing this topic due to there is no update from you for a period, assuming this issue was resolved.
If still need the support, please open a new topic. Thanks

Is this still an issue to support? Any result can be shared? Thanks