We are pleased to announce JetPack 4.4 Developer Preview supporting Jetson AGX Xavier series, Jetson Xavier NX, Jetson TX2 series, Jetson TX1, and Jetson Nano. (JetPack 4.3 remains the latest production release.)
JetPack 4.4 key features include support for Jetson Xavier NX module, new versions of CUDA, TensorRT and cuDNN, and support for the upcoming DeepStream 5.0 Developer Preview.
Support for Generic Timestamping Engine (GTE) for Jetson AGX Xavier and Jetson Xavier NX
Support for Dynamic Frequency Scaling (DFS) for Video Image Compositor (VIC) using actmon
SE (Security Engine) samples to demonstrate hardware backed authentication and encryption capabilities of Jetson TX2 series, Jetson AGX Xavier and Jetson Xavier NX modules.
Utility to fuse multiple Jetson modules simultaneously
Option to specify APP partition size on the microSD card during initial configuration at first boot of Jetson Nano Developer Kit
JetPack 4.4 components:
L4T R32.4.2
CUDA 10.2
cuDNN 8.0.0 (Developer Preview)
TensorRT 7.1.0 (Developer Preview)
VisionWorks 1.6
OpenCV 4.1
Vulkan 1.2
VPI 0.2.0 (Developer Preview)
Nsight Systems 2020.2
Nsight Graphics 2020.1
Nsight Compute 2019.3
Existing installations of JetPack 4.3 can be upgraded in-place to JetPack 4.4 Developer Preview without re-flashing the device. For more information about upgrading JetPack via the Debian package management tool, please refer to the JetPack documentation here.
Tested nv-jetson-nano-sd-card-image-r32.4.2 on new Jetson Nano (Developer Kit - B01). Image ran very sluggish, turned out Xserver was restarting in the background. Logging showed nvgpu errors. Logging in via console (serial/ssh/virtual) would work as long as no xsession was started. Note: running vulkaninfo would result in similar nvgpu errors in the system log.
After multiple tries with two different SD-cards I decided to load nv-jetson-nano-sd-card-image-r32.3.1 - this works fine.
when i attempt to use this new version during the initial boot when it reaches the configuration screen about âwho are youâ the screen locks up and will not allow any data entry, neither the keyboard nor the mouse have any effect on this screen.
Hi,
Can you share the steps you have followed?
Have you done a complete flash?
Also, if possible please share the kernel or system log whatever you can capture.
Hi,
When jetpack 4.2 upgraded to jetpack 4.4, The libraries of installed in the jetpack 4.2 is remain in the new upgraded jetpack? or need to reinstall the packages for upgraded jetpack again?
i had successfully downloaded this image file from the website
nv-jetson-nano-sd-card-image-r32.4.2.zip
i reformatted a SD card in windows 10 and used
balenaEtcher-Portable-1.5.70
to successfully place the image on the SD card
these are the same procudres i had used in the past for all previous SDK card images
as i said previously when booting for the first time with this new SDK card i had the system lock up for data entry on the âwho are youâ portion of the configuration.
there was no way to progress beyond that point, so essentially the system is unusable.
when i put my 32.3.1 SD card back in the system boots satisfactorily so it does not seem to be any hardware issue
i tried recreating the 32.4.2 image sd card three different times, all appearing to work successfully and all ending in the same configuration failure.
at this point i cannot interact with the system in any fashion, so i donât know how to collect any additional data.
unless you can explain some way out of this lockup and tell me how to gather what information you might want.
Iâve been working on getting a script together to do almost like a JetPack but based on Debian. I have gotten it to work, but I had to edit the flash.sh script for it to work due to using a compressed filesystem. The removal of hardcoding the SIZE prevented me from getting to to work any other way.
Line 163 went from:
rootfs_size=$(du -ms â${rfs_dir}â | awk â{print $1}â)
to
rootfs_size=$(du -ms --apparent-size â${rfs_dir}â | awk â{print $1}â)
Setting up nvidia-l4t-bootloader (32.4.2-20200408182156) âŠ
3448-300---1--jetson-nano-qspi-sd-mmcblk0p1
Starting bootloader post-install procedure.
ERROR. Procedure for bootloader 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
Errors were encountered while processing:
nvidia-l4t-bootloader
E: Sub-process /usr/bin/dpkg returned an error code (1)
and
xxx:~$ sudo apt-get install nvidia-jetpack
Reading package lists... Done
Building dependency tree
Reading state information... Done
nvidia-jetpack is already the newest version (4.4-b144).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up nvidia-l4t-bootloader (32.4.2-20200408182156) ...
3448-300---1--jetson-nano-qspi-sd-mmcblk0p1
Starting bootloader post-install procedure.
ERROR. Procedure for bootloader 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
Errors were encountered while processing:
nvidia-l4t-bootloader
E: Sub-process /usr/bin/dpkg returned an error code (1)
Did someone encountered this error before, and if so, what was the solution?
I have to upgrade six boards. First dist-upgrade one was successful. The above encountered was my second board.
And my third + fourth board:
Errors were encountered while processing:
nvidia-l4t-bootloader
E: Sub-process /usr/bin/dpkg returned an error code (1)
Edited apt sources and running upgrade process on my Xavier. Stuffâs backed up and on external storage. Download is slow AF, but I think thatâs cause my connectionâs got the 'rona. Itâs been up and down this whole week, breaking all sorts of things for myself and spouse. I hear âputain de connexion de merde!â from the other office :D
Everything seems to be going smoothly. I have a bunch of stuff mounted on nvme (/usr, /home, /var/lib/docker, and so on). It wants to update /etc/apt/sources.list.d/nvidia-l4t-apt-source.list. Iâm letting it. And rebooting. And it works, and I can see there is some stuff that was broken before that is now fixed. Thank you, Nvidia. I wasnât expecting that quick a fix.
Edit: This is really sweet. No SDKM required. Thank you for this apt based OTA approach! Please donât change it!
So great to see the release,
We see a mention of deepstream 5 release,
Will the deepstream 4 still work with tensorrt 7 ?
we want to use onnx opset 10 models with deepstream.
As a reminder when using Jetson Nano Developer Kit with a large SD card â use the script @ Jetson Nano sd card partitions can not extend - #38 by Lufus
to resize the APP partition to use the full size of the SD card. A fix via GParted is required afterwards. GParted will alert you to do that when opened.
@WayneWWW Is the resize of SD card during first bootup expected for GA release of JetPack 4.4? Just as in previous JetPack GA.