Announcing JetPack 5.0 Developer Preview with Jetson Linux 34.1

We are pleased to announce the release of JetPack 5.0 Developer Preview. This is a development release with a full compute stack update including CUDA 11.4, as well as Jetson Linux 34.1 with Linux Kernel 5.10, an Ubuntu 20.04 based root file system, a UEFI based bootloader, and OP-TEE as Trusted Execution Environment.

This release supports Jetson AGX Orin Developer Kit as well as Jetson AGX Xavier series and Jetson Xavier NX series developer kits and commercial modules.

JetPack 5.0 Developer Preview highlights include:

  • Support for Jetson AGX Orin Developer Kit
  • Support to emulate performance of production Jetson Orin NX series and Jetson AGX Orin series modules with Jetson AGX Orin Developer Kit
  • LTS Kernel 5.10
  • Ubuntu 20.04 based reference file system
  • OP-TEE Trusted Execution Environment
  • UEFI bootloader
  • Support for NVSCI: Provides utilities for streaming data packets between different applications and for interprocess communication (IPC)
  • New Jetson Power GUI: Tool for monitoring power and thermal status
  • New NVUtils Multimedia buffer management and buffer transformation API
  • NVIDIA Container Runtime no longer mounts user level libraries like CUDA, cuDNN and TensorRT from the host. These will instead need to be installed inside the container.

Please note that JetPack 5.0 Developer Preview is not intended for production use, and has known issues documented in the Jetson Linux release notes. Please read the release notes carefully.

JetPack 5.0 Developer Preview components:

  • Jetson Linux 34.1
  • CUDA 11.4.14
  • TensorRT 8.4.0 Early Access
  • cuDNN 8.3.2
  • VPI 2.0
  • OpenCV 4.5.4
  • Vulkan 1.3
  • Nsight Systems 2021.5
  • Nsight Graphics 2021.5
  • Nsight Compute 2021.2.4.1

Jetson Linux 34.1 Developer Guide: Welcome — Jetson Linux
Developer Guide 34.1 documentation

Please find TensorFlow and PyTorch wheels in Jetson Download Center

Install JetPack 5.0 Developer Preview via Debian package management tool, NVIDIA SDK Manager, or SD card image (for Jetson Xavier NX Developer Kit).

Following containers images are availalble on NGC:

The following items will be available shortly (we will add links as accordingly):


Hi NVidia Team

Nice to hear that the Developer Preview is out. Just one question, if we download via the SDK Manager for a specific target platform, does this change something inside the Linux_For_Tegra Folder? Meaning are for example the folders “JetPack_5.0_DP_Linux_JETSON_AGX_TARGETS”, “JetPack_5.0_DP_Linux_JETSON_TX2_TARGETS” and “JetPack_5.0_DP_Linux_JETSON_XAVIER_NX” identical?
As we have all the platform in use, we would like to know it one JetPack 5.0 Installation can be used for all targets.
Thank you.

Best regards

Hey, that is great news!
I am looking for the l4t-base:r34.1 container but could not find it on the container registry. Is there a different place cause its a developer preview or is it just not released yet?
If that’s the case, is there a timeline for that?

@lennartha the l4t base container is now available on NGC.


Is there a date for releasing the final version, which also includes deepstream 6.1? Thanks

1 Like

Hey nice to hear that the Dev Preview is finally out. Just one question: I applied for access to the preview at the release date but have still “approval pending”. In my account it says “we haven’t read your application yet” or something. So the question: how long does this approval process usually take or are there any points I missed and therefore don’t get early access? We currently have 15+ Jetsons AGX Xavier in our Lab and I would love to check compliance of JetPack 5.0 with our software and requirements, so that we can upgrade as fast as possible when the final release is out.

Thanks in advance

Hi, I think you are referring to the JetPack 5.0 Early Access program (which has passed, now that the Developer Preview is out). The Developer Preview doesn’t require any special approval - anyone can flash it using SDK Manager or the SD card image for Xavier NX.

@dusty_nv, oops - my fault, thanks for your clarification.