JetPack 5.1 with Jetson Linux 35.2.1 Released

We are very pleased to announce that JetPack 5.1 is now released!

JetPack 5.1 is a production release with added support for Jetson Orin NX 16GB production module. It also supports Jetson AGX Orin 32GB, Jetson AGX Orin Developer Kit, Jetson AGX Xavier series, Jetson Xavier NX series as well as Jetson AGX Xavier Developer Kit and Jetson Xavier NX Developer Kit.

JetPack 5.1 includes Jetson Linux 35.2.1 with new security and OTA features as well as enhancements for Multimedia, Camera and Display. Below are the top highlights for JetPack 5.1. Please refer to JetPack 5.1 page for full lists of features:

  • Adds support for Jetson Orin NX 16GB production module
  • Security
  • Over The Air Updates:
    • Image Based OTA tools with A/B support to upgrade Jetson AGX Xavier or Jetson Xavier NX modules running JetPack 4.x releases
    • Image Based OTA tools to upgrade Jetson Orin modules will be released with the next release
  • Display
    • Fixes for HDMI 2.0 and DP compliance
  • Camera
    • Support for AR1335 YUV camera
    • Enhanced support for simultaneous V4l2 and Argus
    • New Argus Demosaic (argus_demosaicOutput sample) to output RGB supported on Orin
    • New Argus RAW reprocessing (syncStereoRawReprocess sample) to read Bayer raw images from file & provide reprocessed YUV output to file
    • Updated Argus SyncSensorCalibrationData extension with enhanced EEPROM Calibration data to support Camera Module Serial Number, and IMU Noise Parameters
  • MultiMedia
    • TAQ( Temporal Adaptive Quantization) support is extended to H264 encoder

JetPack 5.1 Components:

  • Jetson Linux 35.2.1
  • CUDA 11.4.19
  • TensorRT 8.5.2
  • cuDNN 8.6.0
  • VPI 2.2
  • OpenCV 4.5.4
  • Vulkan 1.3
  • Nsight Systems 2022.5
  • Nsight Graphics 2022.6
  • Nsight DLD/Compute 2022.2

To upgrade from previous JetPack 5 Releases:

To upgrade from previous JetPack 5 releases, first edit /etc/apt/sources.list.d/nvidia-l4t-apt-source.list to point to the 35.2 repo (just change the version to r35.2 in both lines). Next, use the following commands, then physically reboot the system:

sudo apt update

sudo apt dist-upgrade

sudo apt install --fix-broken -o Dpkg::Options::="--force-overwrite"

If you encounter an error, please use the following 3 commands and re-attempt the upgrade (do not reboot the device after running below command and before re-attempting the upgrade)

sudo parted /dev/mmcblk0 -s rm 4

sudo parted /dev/mmcblk0 -s resizepart 3 67.9MB

sudo parted /dev/mmcblk0 mkpart -s A_reserved_on_user 67.9MB 101MB

Please select “Ignore” when prompted and “ext2” as the file system type.

Resources:

Note: Some of the links in Jetson Linux 35.2.1 page in Downloads section do not follow the normal convention. For example: https://developer.nvidia.com/downloads/r35releasev21-sources-ubuntufocal-l4taarch64srctbz2

Instead of

https://developer.nvidia.com/downloads/r35_release_v2.1/sources/ubuntu_focal-l4t_aarch64_src.tbz2

This is due to an issue in our posting tool and we plan to fix it within a week so that our links can follow the convention as before.

Note:

Following items will be made live soon. We will update this thread when they are available:

  • Jetson Xavier NX SD Card Image
  • Containers for JetPack 5.1 on NGC
1 Like

I have a Xavier NX developer kit that was freshly flashed with 5.0.2 (with the NVME SSD for the root filesystem).

If I do an apt-get update and apt-get dist-upgrade, things break:

Setting up nvidia-l4t-bootloader (35.2.1-20230121191456) ...
3668-100---1--jetson-xavier-nx-devkit-qspi-
Info. Installing mtdblock.
Info. Active boot storage: nvme0n1
Info. Legacy mode: true
INFO. Dump nv_boot_control.conf:
TNSPEC 3668-200-0000-H.0-1-2-jetson-xavier-nx-devkit-qspi-
COMPATIBLE_SPEC 3668-100---1--jetson-xavier-nx-devkit-qspi-
TEGRA_LEGACY_UPDATE true
TEGRA_BOOT_STORAGE nvme0n1
TEGRA_EMMC_ONLY false
TEGRA_CHIPID 0x19
TEGRA_OTA_BOOT_DEVICE /dev/mtdblock0
TEGRA_OTA_GPT_DEVICE /dev/mtdblock0
Starting bootloader post-install procedure.
INFO. Installing mtdblock.
Starting legacy update procedure.
ERROR. Procedure for bl_only_payload update FAILED.
Cannot install package. Exiting...
dpkg: error processing package nvidia-l4t-bootloader (--configure):
 installed nvidia-l4t-bootloader package post-installation script subprocess returned error exit status 1

Tracing this back to the actual script that is failing:

/opt/ota_package# nv_update_engine -f bl_update_payload
Nvidia A/B-Redundancy Update tool Version 2.2
Start running: /usr/sbin/nv_bootloader_payload_updater --forced-bl-update /opt/ota_package/bl_update_payload
Start running: /opt/nvidia/l4t-bootloader-config/nv-l4t-bootloader-config.sh -c
3668-100---1--jetson-xavier-nx-devkit-qspi-
Got update payload: /opt/ota_package/bl_update_payload
Tegra User Block Device: /dev/disk/by-partlabel
Tegra Boot Block Device: /dev/mtdblock0
Tegra GPT Block Device: /dev/mtdblock0
HEADER: MAGIC NVIDIA__BLOB__V3
HEX_VALUE 16975394
BLOB_SIZE 48852384
HEADER_SIZE 48
NUMBER_OF_ELEMENTS 19
HEADER_TYPE 0
UNCOMP_SIZE 48852384
MB1_RATCHET_LV 0
MTS_RATCHET_LV 0
ROLLBACK_FUSE_LV 0
Device TN Spec: 3668-200-0000-H.0-1-2-jetson-xavier-nx-devkit-qspi-
Device Compatible Spec: 3668-100---1--jetson-xavier-nx-devkit-qspi-
Can't find matching TN Spec in OTA Blob!
GPT update failed. Status: 3
/usr/sbin/nv_bootloader_payload_updater --forced-bl-update Failed.
Forced bootloader update is failed

Is updating a Xavier NX dev kit suppossed to work? Can I still fix this without reflashing?

@KoenKepler out of the box, the APT upgrade mechanism we support is for the default devkit configuraiton, which is the case of Jetson Xavier NX developer kit is SDCard for storage. To upgrade with NVMe as root file system, it may require some additional steps. My colleagues should be able to help here.

I am having trouble with installing 5.1 as well. I have 5.0.2 backed up in a saved directory (calling it baseline_sdk_5.0.2) and can command line flash it (sudo ./flash.sh jetson-xavier-nx-devkit-emmc mmcblk0p1) without issue.

I deleted the Jetpack_5.0.2_… directory so to start clean for the 5.1 version. Using the SDK gui, I downloaded the 5.1 and flashed it both with the gui and cli command above. After flashing on the devkit, when I check the /etc/nv_tegra_release file, it still states 5.0.2 (R35 (release) version- 1.0).
It appears it is still flashing the 5.0.2 version. How can I force it to flash Jetpack 5.1?

My ultimate goal is to tar up the whole JetPack directory, move it other Ubuntu host PCs and flash via command without using the GUI (like I can do with my baseline 5.0.2).

Thanks!

Update:

We found an issue when installing JetPack using SDK Manager where Jetson Multimedia installation was not succesfull. We have fixed the issue.
If you had already tried JetPack 5.1 installation using SDK Manager, please uninstall JetPack 5.1 using the SDK Manager menu in the left-bottom in the SDK Manager main GUI. Then close and re-open the SDK Manager, download and install JetPack 5.1 again.

Also note that the nvidia-jetpack metapackage is now avaialable in the APT repo. If you want to install JetPack after installing Jetson Linux 32.5.1 using APT, then just follow the familiar commands:

sudo apt update
sudo apt install nvidia-jetpack

Hi,
We saw similar problem mostly on devices with external storage.
If you are flashing a Jetson device with external storage, please make sure it’s booted to the storage you flashed on after flashing.
Jetson devices would not automatic change the boot order after flashing, this needs to done manually as for now.