JetPack 6.1 is now out and about in the world! This version of JetPack is for the NVIDIA Jetson Orin series, and will not work on earlier Jetsons. I’m especially interested in faster Argus library performance. Here’s the info lifted from the NVIDIA Jetson Developers Forum. Note that on the NVIDIA site there’s additional information and quick start install info:
We are pleased to announce the production release of JetPack 6.1. JetPack 6.1 packages Jetson Linux 36.4 with Linux Kernel 5.15 and Ubuntu 22.04 based root file system. The Jetson AI stack in JetPack 6.1 includes CUDA 12.6, cuDNN 9.3, TensorRT 10.3, VPI 3.2, DLA 3.1 and DLFW 24.0. This release supports all NVIDIA Jetson Orin modules and developer kits.
Highlights of JetPack 6.1:
- Upgraded compute stack with CUDA 12.6, TensorRT 10.3, cuDNN 9.3, VPI 3.2. DLA 3.1 and DLFW 24.0
- Camera: Enhanced Argus library, reducing CPU utilization by up to 40%
- Security: Support for Firmware-based Trusted Platform Module (fTPM) on the Orin platform. Refer to the security page for all security features.
- Software support for the PCN 211361 and fixes for various security vulnerabilities.
Installation:
You can install JetPack 6.1 with any of the methods below:
- SDK Manager: You can do a fresh install of JetPack 6.1 using SDK Manager.
- Debian Package: If you have JetPack 6 already installed on Jetson AGX Orin Developer Kit or Jetson Orin Nano Developer Kit, you can upgrade to JetPack 6.1 using APT. Refer to the steps here
- SD Card: If you are using Jetson Orin Nano Developer Kit, you can download the SD Card image from JetPack 6.1 page and use Balena Etcher to prepare the SD Card with JetPack 6.1
- Manual Flashing: If you prefer to install using the command line, you can flash Jetson device from a linux host by following steps here. Once Jetson Linux is flashed, you can install the compute stack using SDK Manager (using linux host) or by running “sudo apt update” followed by “sudo apt install nvidia-jetpack” on Jetson.
JetPack 6.1 Components:
- Jetson Linux 36.4
- CUDA 12.6
- TensorRT 10.3
- cuDNN 9.3
- VPI 3.2
- DLA 3.1
- DLFW 24.0
- Vulkan 1.3
- Nsight Systems v2024.5
- Nsight Graphics v2024.2
- Nsight Compute v2023.2 as part of the CUDA Toolkit
SDK Support:
- DeepStream 7.1 (coming in Q4 ‘24)
- Isaac ROS 3.0 (coming soon)
- Holoscan 2.6 (coming in Nov ‘24)
Containers: Containers will soon be available on JetPack 6.1. We will update the announcement as containers are made available.
JetPack 6 Resources:
Conclusion
As usual, make sure you have your backups made before upgrading. The best bits of the new release information are in the Release Notes, so make sure you read through those to find out what got fixed and new features added. Check it out!
8 Responses
I have come to the conclusion that this upgrade is too buggy to actually use. I realize that is a bit harsh and I need to explain. I upgrade my jetson to 6.1, After the upgrade, jtop shows the libraries have been upgraded, but it also says that the jetpack is not installed.
I teach a class with this jetson, and use nsight-compute. Nsight-compute consistely crashed on cuda examples that it had work fine with. I recompiled the examples, and discovered the recompiled code worked fine by itself, but nsight compute ran until the very end and then crashed. It offered to send a report to invidia. It did this for several cuda program that work fine by itself. (perhaps nsight compute also changes and requires some other compilation argument that was different?).
Is there a way to roll back the installation to the previous version?
I was fortunate that I as a instructor I have several versions of the jetson orin nano, and I was able to continue teaching with the older version of the jetpack.
The “JetPack not installed” issue is due to jtop not recognizing the new version. jtop needs to be upgraded. Because jtop (jetson-stats) is community maintained (not from NVIDIA), it usually takes a little while before the issue is resolved after a JetPack release. If needed, you can look at the source code and add the new release if really needed.
I don’t have enough experience with Nsight, but it probably is suffering the same type of issue and needs to be upgraded. You can check on the official NVIDIA forums to see what the NVIDIA engineers have to say.
I don’t know of any easy way to downgrade other than flashing the whole device. Sorry to hear you’re having issues.
Thank you for getting back to me this quickly. Jetpack 6.0 used nsight-compute version 2023.2.2. Jetpack 6.1 used version 2024.3.1. I will send a message off to nvidia to see if they can recommend a fix.
I wanted to add a comment. I filed a question about this on the Nvidia web site. On the same site they announced the Jetpack 6.1 and said that : JetPack 6.1 includes NVIDIA Nsight Compute v2023.2 as part of the CUDA Toolkit 12.2. The update that we installed had v2024.3.1. I am hoping to hear how I might role back nsight-compute on the jetson.
Interesting. That’s probably the source of the issues that you are experiencing. Hopefully NVIDIA can help you through the roll back process.
It seems that the problem is continuing with jetpack 6.2. The upgrade from 6.0 to 6.1 broke the nsight-compute version. I was hoping that installing jetpack 6.2 would have taken care of the problem. Jetpack 6.2 has ncu-ui version 2024.3.1. If I just run ncu on the cuda program, it does report the performance of the GPU. If i try to run ncu-ui it crashes. Also if I generate a report(ncu-rep) file it also crashes. The error is rather long, and I will append it to this message. Nvidia has a link to this type of error, but does not present a solution. The Nvidia jetpack 6.2 page does not even reference version 2024.3.1 for that jetpack. Their page seems to reference the older 2023 version (from jetpack 6.0) as the expected version. I can use some hint on how to get around this. I teach a computer architecture class, and we distributed multiple jetson orin nano’s to the class. We can’t have them reinstall jetpack 6.2 (and wipe their system) as a solution.
Here is the error dump:
Reason: SIGABRT
Address: 0x3e800140cf9
Thread 0 (crashed)
[0] libc.so.6 + 0x7f1f0
[1] libc.so.6 + 0x7f1d8
[2] libc.so.6 + 0x3a678
[3] libc.so.6 + 0x2712c
[4] libc.so.6 + 0x732fc
[5] libc.so.6 + 0x89568
[6] libc.so.6 + 0x8b2b0
[7] libc.so.6 + 0x8dc70
[8] libstdc++.so.6 + 0xb869c
[9] libstdc++.so.6 + 0xb875c
[10] libRebelPlugin.so + 0x13f5e58
[11] libRebelPlugin.so + 0x7172cc
[12] libQt6Core.so.6 + 0x351670
[13] libQt6Core.so.6 + 0x351670
[14] libQt6Core.so.6 + 0x351670
[15] libQt6Core.so.6 + 0x31fbe0
[16] libQt6Widgets.so.6 + 0x41fc74
[17] libRebelPlugin.so + 0x7e5650
[18] libQt6Widgets.so.6 + 0x446670
[19] libQt6Widgets.so.6 + 0x1dfef4
[20] libQt6Widgets.so.6 + 0x25c66c
[21] libQt6Widgets.so.6 + 0x3f5020
[22] libQt6Core.so.6 + 0x128784
[23] libQt6Widgets.so.6 + 0x19828c
[24] libQt6Widgets.so.6 + 0x199b20
[25] libQt6Core.so.6 + 0x128468
[26] libQt6Widgets.so.6 + 0x1d2e54
[27] libQt6Widgets.so.6 + 0x1edf14
[28] libQt6Widgets.so.6 + 0x1ee298
[29] libQt6Widgets.so.6 + 0x1e060c
[30] libQt6Widgets.so.6 + 0x2eeadc
[31] libQt6Widgets.so.6 + 0x1982ac
[32] libQt6Widgets.so.6 + 0x199b20
[33] libQt6Core.so.6 + 0x128468
[34] libQt6Core.so.6 + 0x1295bc
[35] libQt6Core.so.6 + 0x374ad0
[36] libglib-2.0.so.0 + 0x55a6c
[37] libglib-2.0.so.0 + 0xaaeb8
[38] libglib-2.0.so.0 + 0x52f10
[39] libQt6Core.so.6 + 0x374544
[40] libQt6Core.so.6 + 0x131650
[41] libQt6Core.so.6 + 0x128b54
[42] libAppLib.so + 0xbb680
[43] libc.so.6 + 0x274c8
[44] ncu-ui.bin + 0x6318
Thread 1
[0] libc.so.6 + 0xdbe38
[1] libc.so.6 + 0xdbe18
[2] libglib-2.0.so.0 + 0xaae54
[3] libglib-2.0.so.0 + 0x52f10
[4] libQt6Core.so.6 + 0x374544
[5] libQt6Core.so.6 + 0x131650
[6] libQt6Core.so.6 + 0x21e970
[7] libQt6DBus.so.6 + 0x30a40
[8] libQt6Core.so.6 + 0x28b674
[9] libc.so.6 + 0x7d5b4
Thread 2
[0] libc.so.6 + 0xdbe38
[1] libc.so.6 + 0xdbe18
[2] libxcb.so.1 + 0xc1ec
[3] libxcb.so.1 + 0xdbb4
[4] libQt6XcbQpa.so.6 + 0x51dfc
[5] libQt6Core.so.6 + 0x28b674
[6] libc.so.6 + 0x7d5b4
Thread 3
[0] libc.so.6 + 0x79de8
[1] libc.so.6 + 0x79dc4
[2] libc.so.6 + 0x7c8e8
[3] libTPSConnectionPlugin.so + 0xbf5b8
[4] libc.so.6 + 0x7d5b4
Thread 4
[0] libc.so.6 + 0xe607c
[1] libc.so.6 + 0xe6054
[2] libTPSConnectionPlugin.so + 0xc33d0
[3] libc.so.6 + 0x7d5b4
Thread 5
[0] libc.so.6 + 0x79de8
[1] libc.so.6 + 0x79dc4
[2] libc.so.6 + 0x7c8e8
[3] libRebelPlugin.so + 0x13bceec
[4] libRebelPlugin.so + 0x593578
[5] libc.so.6 + 0x7d5b4
Thread 6
[0] libc.so.6 + 0xdbe38
[1] libc.so.6 + 0xdbe18
[2] libglib-2.0.so.0 + 0xaae54
[3] libglib-2.0.so.0 + 0x52f10
[4] libQt6Core.so.6 + 0x374560
[5] libQt6Core.so.6 + 0x131650
[6] libQt6Core.so.6 + 0x21e970
[7] libQt6Core.so.6 + 0x28b674
[8] libc.so.6 + 0x7d5b4
Thread 7
[0] libc.so.6 + 0x79de8
[1] libc.so.6 + 0x79dc4
[2] libc.so.6 + 0x7cbfc
[3] libQt6Core.so.6 + 0x295714
[4] libQt6Core.so.6 + 0x29546c
[5] libQt6Core.so.6 + 0x28f0b4
[6] libQt6Core.so.6 + 0x28b674
[7] libc.so.6 + 0x7d5b4
Thread 8
[0] libc.so.6 + 0xdbe38
[1] libc.so.6 + 0xdbe18
[2] libglib-2.0.so.0 + 0xaae54
[3] libglib-2.0.so.0 + 0x52f10
[4] libQt6Core.so.6 + 0x374544
[5] libQt6Core.so.6 + 0x131650
[6] libQt6Core.so.6 + 0x21e970
[7] libQt6Core.so.6 + 0x28b674
[8] libc.so.6 + 0x7d5b4
Thread 9
[0] libc.so.6 + 0x79de8
[1] libc.so.6 + 0x79dc4
[2] libc.so.6 + 0x7cbfc
[3] libQt6Core.so.6 + 0x295714
[4] libQt6Core.so.6 + 0x29546c
[5] libQt6Core.so.6 + 0x28f0b4
[6] libQt6Core.so.6 + 0x28b674
[7] libc.so.6 + 0x7d5b4
Thread 10
[0] libc.so.6 + 0x79de8
[1] libc.so.6 + 0x79dc4
[2] libc.so.6 + 0x7cbfc
[3] libQt6Core.so.6 + 0x295714
[4] libQt6Core.so.6 + 0x29546c
[5] libQt6Core.so.6 + 0x28f0b4
[6] libQt6Core.so.6 + 0x28b674
[7] libc.so.6 + 0x7d5b4
Thread 11
[0] libc.so.6 + 0x79de8
[1] libc.so.6 + 0x79dc4
[2] libc.so.6 + 0x7cbfc
[3] libQt6Core.so.6 + 0x295714
[4] libQt6Core.so.6 + 0x29546c
[5] libQt6Core.so.6 + 0x28f0b4
[6] libQt6Core.so.6 + 0x28b674
[7] libc.so.6 + 0x7d5b4
Thread 12
[0] libc.so.6 + 0x79de8
[1] libc.so.6 + 0x79dc4
[2] libc.so.6 + 0x7cbfc
[3] libQt6Core.so.6 + 0x295714
[4] libQt6Core.so.6 + 0x29546c
[5] libQt6Core.so.6 + 0x28f0b4
[6] libQt6Core.so.6 + 0x28b674
[7] libc.so.6 + 0x7d5b4
Thread 13
[0] libc.so.6 + 0x79de8
[1] libc.so.6 + 0x79dc4
[2] libc.so.6 + 0x7cbfc
[3] libQt6Core.so.6 + 0x295714
[4] libQt6Core.so.6 + 0x29546c
[5] libQt6Core.so.6 + 0x28f0b4
[6] libQt6Core.so.6 + 0x28b674
[7] libc.so.6 + 0x7d5b4
Thread 14
[0] libc.so.6 + 0x79de8
[1] libc.so.6 + 0x79dc4
[2] libc.so.6 + 0x7cbfc
[3] libQt6Core.so.6 + 0x295714
[4] libQt6Core.so.6 + 0x29546c
[5] libQt6Core.so.6 + 0x28f0b4
[6] libQt6Core.so.6 + 0x28b674
[7] libc.so.6 + 0x7d5b4
This sounds like something is fundamentally wrong. Unfortunately I’m not much help here, this appears to be something that’s part of the NVIDIA stack I don’t have access to. As far as I know, the only real recourse is to bring it up in the Jetson forums and ask for help. Good luck on your project!
I did what you suggested, and posted a comment to the Nvidia forum:
https://forums.developer.nvidia.com/t/nsight-compute-ncu-ui-failure-on-jetpack-6-2-jetson-orin-nano/326397/2
Nvidia made the suggestion that I update the cuda toolbox. I have some concerns that I was not sure if jetpack 6.2 could handled cuda 2.8. I did try something earlier that allowed me to run ncu-ui on jetpack 6.2. I teach a graduate advanced computer architecture class where we loan the students jetson orin nano’s. The jetson that I used last semester was still operating jetpack 6.0. I was able to copy the nsight-compute directory (2023.2.2) and install it on the newer jetpack 6.2 system. I was able to run ncu-ui correctly.
I also updated the cuda toolbox, and it installed cuda 2.8 on the jetpack 6.2 system. The nsight compute version was 2025.1.1. I was able to also run that correctly on the system. Since my compilation did not modify the make file (cuda samples). It was set to the upper limit of cuda 2.6 and not cuda 2.8. The ncu-ui reported that the code was only cuda 2.6. I suppose the next step should be to recompile it to cuda 2.8 and see if it still works.
I asked Nvidia if they thought having jetpack 6.2 would be a problem with the newer cuda toolbox. Hopefully they will let me know.