JetPack 4.2.1 - L4T R32.2 release for Jetson Nano, Jetson TX1/TX2, and Jetson AGX Xavier

NVIDIA is excited to have released JetPack 4.2.1 and L4T R32.2, the latest production release including new features and improvements for Jetson Nano, Jetson TX1/TX2, and Jetson AGX Xavier! See the Key Features for a list of highlights, including: headless configuration, NVIDIA Indicator Applet for nvpmodel performance mode switching, improved memory availability, Jetson Zoo, and NVIDIA Container Runtime with Docker Integration.

Jetson Nano Developer Kit users can download and re-flash the updated SD card image and follow the steps in Getting Started with Jetson Nano.

Optionally, the NVIDIA SDK Manager can be used to install JetPack 4.2.1, including developer tools with support for cross-compilation.

JetPack 4.2.1 components:

  • L4T R32.2 (K4.9)
  • Ubuntu 18.04 LTS aarch64
  • CUDA 10.0.326
  • cuDNN 7.5.0.66
  • TensorRT 5.1.6.1
  • VisionWorks 1.6
  • OpenCV 3.3.1
  • Nsight Systems 2019.4
  • Nsight Graphics 2019.2
  • SDK Manager 0.9.13

Download JetPack…https://developer.nvidia.com/embedded/jetpack
Release Notes…https://docs.nvidia.com/jetson/jetpack/release-notes/index.html
L4T Release Notes…https://developer.nvidia.com/embedded/dlc/Tegra_Linux_Driver_Package_Release_Notes_R32.2.0_GA.pdf

Thanx Dusty

access times are .27 for both

I have the intel wifi with bluetooth no probs there either. I have also mounted a mybook 3T with no probs.

Does Nvidia have a mirror for the Jetpack 4.2.1?

Where is the source code? Say:

https://developer.nvidia.com/embedded/dlc/l4t-jetson-driver-package-32-2-jetson-nano ?

Thanks for providing updates. I would like to provide feedback.

It seems that the new update in SDKmanager flashing installation for Jetson Nano would not resolve the issue that the root disk file size would be restricted to 14 GB despite there are more disk space available in the SD card.

The new SD card image does not change its version name, but it is 12.6GB after unzip, while the previous version is in 5+ GB. Could you confirm this? It would be better to have version name change, e.g. just release date change would be better.

Thanks.

Hello, does the kernel in this release have any modifications compared to the last release or are they identical in terms of features?

I have a patched kernel that I made that includes full apparmor support i.e:

AppArmor status: apparmor is enabled and all features are available

It is also patched to support Fuse mounts in non-init user namespace however I have yet to test this feature fully.

These patches would be a nice addition to this L4T release but if the kernel is different it obviously won’t work.

Thanks,
Chris.

If I use the SD card image to install OS on the Jetson Nano, then I cannot flash the Jetson Nano Nvidia Container Runtime and Multimedia API to the device. If I use the SDK Manager to flash the OS image, then i have the constraint that the root device size is only 14 GB.

17:10:57 INFO : NVIDIA Container Runtime with Docker integration (Beta) : exit status 1
17:10:57 INFO : NVIDIA Container Runtime with Docker integration (Beta) : [ Package Install Finished with Error ]
17:10:57 ERROR : NVIDIA Container Runtime with Docker integration (Beta) : NV_DOCKER_TARGET_POST_INSTALL_COMP command scp -q -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no /tmp/tmp_NV_DOCKER_TARGET_POST_INSTALL_COMP.sh vaitl@192.168.86.183:~; ssh -t -q -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no vaitl@192.168.86.183 "~/tmp_NV_DOCKER_TARGET_POST_INSTALL_COMP.sh && rm -f ~/tmp_NV_DOCKER_TARGET_POST_INSTALL_COMP.sh" finished with error
17:10:57 INFO : NVIDIA Container Runtime with Docker integration (Beta) :
17:10:57 INFO : NVIDIA Container Runtime with Docker integration (Beta) : [ 88.00 KB used. Disk Avail: 281.70 GB ]
17:10:57 INFO : NVIDIA Container Runtime with Docker integration (Beta) : [ NV_DOCKER_TARGET_POST_INSTALL_COMP Install took 55s ]
17:10:57 INFO : NVIDIA Container Runtime with Docker integration (Beta) : command scp -q -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no /tmp/tmp_NV_DOCKER_TARGET_POST_INSTALL_COMP.sh vaitl@192.168.86.183:~; ssh -t -q -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no vaitl@192.168.86.183 "~/tmp_NV_DOCKER_TARGET_POST_INSTALL_COMP.sh && rm -f ~/tmp_NV_DOCKER_TARGET_POST_INSTALL_COMP.sh" finished with error

after you flash it try resizing the app partition on the sdcard with gparted on the host pc.

How long should I be stuck on “Applying changes Waiting for unattended-upgr to exit” ? It’s been about 20 minutes.

the jetson nano sdcard image linked above links to 32.1.1 image not 32.2 image.

Is this correct?

Is there an sdcard image for the nano for 32.2 or do we have to download the bsp package and sample file system?

Can take an hour or so depending on your bandwidth.

But I just flashed 4.2.1 to a Nano, and it took only a few minutes. Are you sure that you are using the 4.2.1 version and not 4.2? 4.2 took a long time for me as well. But 4.2.1 should be up to date with all packages.

Hi Mr. Chris, try this link for the updated image for JetPack 4.2.1 (fixed this in the post above):

https://developer.nvidia.com/jetson-nano-sd-card-image-r322

If you use the updated SD card image, the NVIDIA Container Runtime and L4T Multimedia API should come pre-installed, and you should be able to use full SD card capacity for your OS partition.

Here are the L4T sources for Nano:

https://developer.nvidia.com/embedded/dlc/public_sources_Nano

Hi Mr. Chris, as with most L4T releases, there have been fixes and other improvements to the kernel - you can see the changes by browsing the log of the ‘tegra-l4t-r32.2.0’ tree on the L4T kernel git here:

http://nv-tegra.nvidia.com/gitweb/?p=linux-4.9.git;a=summary

It’s also recommended to consult the L4T Release Notes for other important notes and features.

Thanks for the update! I will check it out later today. Are the DeepStream components included?

We are shooting to release DeepStream 4.0 next week, and you will be able to install it on-top of existing JetPack 4.2.1 SD card image or have NVIDIA SDK Manager install it as well.