We are pleased to announce JetPack 4.5, 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).
Yes, this is the one that I was reffering to doing sudo do-release-upgrade
on JP 4.4.1 OS.
it worked somehow to certain extent [ at least it boots/ operates somehow ] , also ROS2 foxy seems to build from apt package manager
ooking in indexes: https://pypi.org/simple, https://developer.download.nvidia.com/compute/redist/jp/v45
ERROR: Could not find a version that satisfies the requirement tensorflow
ERROR: No matching distribution found for tensorflow
after flashing oem-setup doesnāt complete. just gets hold after user creation menu
also, folks are asking how to get to U-boot dialog given NVME flashing has taken place
given there is no m.2 slot on host PC how should flash to nvme happen?
However, it seems direct nvme flashing for NX/ AGX is still not supported?
Hello , i have upgraded my Xavier AGX with a Kernel for some CSI-MIPI-Cameras i am using .
I donāt want to flash the board with fresh copy of jetpack 4.5 , how do i go about upgrading to Jetpack 4.5 , retaining my AGX Xavier Configuration .
As per the doc OTA Updates the listed packages in the docs . Is there any way, i can choose not to update certain parts, like i do not want to update kernel-DTBās , as i have already flashed my kernel with certain Nvidia Compatible hardware like MIPI-CSI Cameras and i do not want to go over the process of reflashing the kernel with Cmaera Drivers yet again !
Hello
I am trying to install Jetpack 4.5 cleanly to my Xavier AGX using SDKManager1.4 which was released newly.
SDKManager failed to install CUDA/CUDA-X AI and others after flashing jetson OS.
By checking Terminal log, i found out that apt-get update does not work.
error logs are below.
Any help will be appreciatedā¦
ammr@xavier45:~$ sudo apt-get update
Get:1 file:/var/cuda-repo-10-2-local-10.2.89 InRelease
Ign:1 file:/var/cuda-repo-10-2-local-10.2.89 InRelease
Get:2 file:/var/cuda-repo-10-2-local-10.2.89 Release [574 B]
Get:2 file:/var/cuda-repo-10-2-local-10.2.89 Release [574 B]
Ign:3 https://repo.download.nvidia.com/jetson/common r32.5 InRelease
Ign:4 https://repo.download.nvidia.com/jetson/t194 r32.5 InRelease
Err:5 https://repo.download.nvidia.com/jetson/common r32.5 Release
Could not handshake: An unexpected TLS packet was received. [IP: 157.197.97.27 443]
Err:7 https://repo.download.nvidia.com/jetson/t194 r32.5 Release
Could not handshake: An unexpected TLS packet was received. [IP: 157.197.97.27 443]
Hit:8 Index of /ubuntu-ports bionic InRelease
Get:9 Index of /ubuntu-ports bionic-updates InRelease [88.7 kB]
Hit:10 Index of /ubuntu-ports bionic-backports InRelease
Hit:11 Index of /ubuntu-ports bionic-security InRelease
Get:12 Index of /ubuntu-ports bionic-updates/main arm64 Packages [1,176 kB]
Get:13 Index of /ubuntu-ports bionic-updates/universe arm64 Packages [1,496 kB]
Reading package listsā¦ Done
E: The repository āhttps://repo.download.nvidia.com/jetson/common r32.5 Releaseā does not have a Release file.
N: Updating from such a repository canāt be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository āhttps://repo.download.nvidia.com/jetson/t194 r32.5 Releaseā does not have a Release file.
N: Updating from such a repository canāt be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Flashing for NFS as root and Flashing from NFS features both requires booting into root file system hosted on NFS. Sometime due to the speed of network and the PC that NFS is hosted on, one might see that booting into NFS appears to get stuck for a long time while bringing up OEM-Config.
As a work around one can disable OEM-Config and create a default user which will make the boot to NFS file system by-pass the OEM-Config step.
One can follow the instructions at section Configuring NFS Root on Linux Host to configure the NFS server but add below step to disable OEM-Config after creating the root file system but before copying the root file system to NFS (refer to Setting Up the Root File System instruction on creating a root file system )
Step to disable OEM-Config and create a default username and password:
@suhash Thank you for sharing!
it works with the user creation script after copying the rootfs reated by sdkmanager atx86_64 host PC to jetson ssd over the network so that jetson boot will happen from other jetson. also it is handy as it also allows to chroot to the other jetson filesystem from local jetson
I would like to check out the docs to see if it is worth upgrading, since I heavily rely on opencv types, and the new release is advertised to have better interop.
Is there an updated ETA? Right now I feel like a small child at christmas, checking every morning only to be disappointed :(