JetPack 4.5 – L4T 32.5 is now available!
The big news? Boot from USB or NVMe! You should check it out. Here’s the official blurb from NVIDIA, note the Webinars on Feb. 9 and Feb. 11, 2021:
We are pleased to announce JetPack 4.5 1, a production release supporting Jetson AGX Xavier series, Jetson Xavier NX, Jetson TX2 series, Jetson TX1, and Jetson Nano.
JetPack 4.5 includes VPI 1.0, Security features including enhanced secure boot and support for full disk encryption, enhanced bootloader functionality, and a new way of flashing Jetson devices using NFS.
We will be hosting a webinar on Feb 9th for an in-depth overview of JetPack 4.5 features where we will also demo select features and answer any questions you may have. Please register here.
Learn how to implement computer vision and image processing pipelines using VPI by registering to the webinar we will be hosting on Feb 11th
Highlights of JetPack 4.5 are:
- First Production release of Vision Programming Interface (VPI).
- Support for Docker 19.03.
- Support for installing JetPack components on Linux host computer using Debian package management tool.
- Support for loading kernel, device tree and initrd from the root file system on USB drive or NVMe. Refer to release notes 2 for more details.
- UBoot version updated to v2020.04.
- Boot firmware for all Jetson Nano developer kits updated to relocate boot firmware to integrated QSPI-NOR. Developer kits will use microSD Cardsolely or OS/app storage after this change
- All Jetson Nano Developer Kits will now show a warning screen if no microSD Card is inserted. It will attempt to boot from other supported media after showing this warning screen.
Visit JetPack 4.5 1 and L4T 32.5 page for more details.
JetPack 4.5 components:
- L4T R32.5
- CUDA 10.2
- cuDNN 8.0
- TensorRT 7.1.3
- VisionWorks 1.6
- OpenCV 4.1.1
- Vulkan 1.2
- VPI 1.0 (First Production Release)
- Nsight Systems 2020.4
- Nsight Graphics 2020.5
- Nsight Compute 2019.3
Install JetPack 4.5 using SDK Manager or SD card image (for Jetson Nano 2GB Developer Kit and Jetson Nano Developer Kit ) or upgrade via Debian package management tool (refer instructions from here)
Notes: (We will update this announcement accordingly when we take care of below notes)
- Containers for JetPack 4.5 will be hosted on NGC shortly!
- VPI 1.0 documentation will be available on Jan 22nd.
It seems that Jetson Xavier NX cannot boot from NVMe:
Reading in Developer Guide:
Flashing to a NVMe Drive
Applies to: Jetson Nano, Jetson TX2 series, and Jetson TX1 devices only
That is not my understanding. Flashing to NVMe is a different process for the Xavier NX and AGX Xavier. See: https://docs.nvidia.com/jetson/archives/l4t-archived/l4t-325/index.html#page/Tegra%20Linux%20Driver%20Package%20Development%20Guide/flashing.html#wwpID0E0BI0HA
It seems, you need to boot from NFS to follow that procedure.
I’d be eternally grateful if someone can figure out the steps to take for the Jetson Xavier NX to get booting from NVME to work and write an easy to follow guide on how to do this.
The current set of instructions that are being pointed to are way too complex for this simple soul to figure out.
I’ve asked for a simple guide on how to achieve boot from NVMe on the Jetson Xavier NX and onbe of the developers from NVIDIA responded that this isn’t supported yet on the NX. They are working on making this work on the next JetPack release. The reason for this was that the NX uses a different bootmanager (CBoot i.s.o UBoot) and they need to write the correct modifications for that one.
I tried to upgrade via Debian package management tool,but I saw that the new components haven’t been installed.
1) I have been using the JetsonHacks article on booting from the nvme SSD on my NX using rootOnNVME. It works well except when we have these major updates. I then go back and boot from the the SD card by removing the /etc/setssdroot.conf and reboot to the SD card.
2) Update of Jetson NX involves what is discussed in the following link as to go to JetPack4.5:
3) I then go back to step 1 and appears to be good to go to be running everything off of my SSD again.
Is there a better way to approach this?