JetPack 3.3 — L4T R28.2.1 Release for Jetson TX1/TX2

We’re pleased to announce that JetPack 3.3 is now available for Jetson TX2/TX2i and Jetson TX1!

The highlight of this release is TensorRT 4.0, enabling support for TensorFlow’s TensorRT integration feature. Also, cuDNN has a small update to support the new TensorRT version, and all other JetPack components remain unchanged from JetPack 3.2.1. Please view the Release Notes.

JetPack 3.3 components:

  • L4T R28.2.1 (TX2/TX2i)
  • L4T R28.2    (TX1)
  • CUDA 9.0
  • cuDNN 7.1.5
  • TensorRT 4.0
  • VisionWorks 1.6

Download JetPack…
Release Notes…
L4T Release Notes…
L4T R28.2.1 Page…
L4T Archive Page…

Release notes are still only for JetPack3.2.1. Will there be separate release notes? I assume the L4T notes are the same, but I was thinking perhaps JetPack itself has new release notes.

Hi linuxdev, if you check again, the Release Notes should be for JetPack 3.3.

Hi dusty_nv!

Does the new Jetpack include the Python-API for TensorRT 4?


Looks like it has the same CUDA 9.0 as previous releases… Is there a timeline for releasing a new CUDA libraries with fix for >4GB continues memory allocation issue on aarch64 platform?


The Python API for TensorRT isn’t supported on Jetson, so it isn’t included, however many Python-based models can be imported (via the UFF and new ONNX exporters), and TensorFlow-TensorRT integration is available (TF-TRT).

The CUDA version is CUDA 9.0.252. We don’t have a timeline available for CUDA 10 on Jetson TX2.


We have one Jetson TX1 and one Jetson TX2. To update to JetPack 3.3 for the two verson, do we need only to download once ?

Or is-it needed to download 2 versions ?


JetPack is just a front end. It’ll download whatever is current for that JetPack version for whichever device it is flashing.

That said, the earlier releases had different software between the TX1 and TX2. More recent releases (which JetPack3.3 will use) share the same sample rootfs. You’ll find JetPack creates a TX1 and TX2 directory during the flash of the TX1 or TX2, respectively.

linuxdev is correct, you only need to download the JetPack installer once regardless of if you are on Jetson TX1, TX2, or TX2i. JetPack will then allow you to select which device you are using, and will automatically download the appropriate packages for you to your host PC as linuxdev mentioned.


Thanks for reply. I flashed my TX2.

One other question: I used “sudo apt-get update” and after “sudo apt-get upgrade”. More 500 packages seem to have to be updated.

Should i do these upgrades ? Or is-it better to use the version flashed on jetson TX2 to avoid conflicts ?

Thanks for reply.

You may say if you have run these commands on host or on Jetson.
If it was on Jetson, you may upgrade, as long as you keep with Ubuntu16.
Also note that big upgrades sometimes make compiz cache wrong. So, if after rebooting your user cannot log in (GUI start fails or it start without some bars), then just login as the other user (if you’ve upgraded as user nvidia, then use user ubuntu) and delete compiz cache for user nvidia (or user ubuntu if you upgraded as user ubuntu):

sudo rm -r /home/<your_user_who_made_upgrade>/.cache/compizconfig-1

You should always update. But…before you reboot, be sure this shows all ok:

sha1sum -c /etc/nv_tegra_release

There are actually two copies of, and one can get overwritten (it is a rare update). If this happens simply copy the “ok” one to the bad one. Failing to do so before rebooting means the GUI won’t work until it is put back in place. The two specific lines of that command:

/usr/lib/xorg/modules/extensions/ OK
/usr/lib/aarch64-linux-gnu/tegra/ OK

If a package update got in the way, it will be the xorg module one which went bad. So:

sudo cp /usr/lib/aarch64-linux-gnu/tegra/ /usr/lib/xorg/modules/extensions/

Even if this momentarily kills the GUI, you still have ssh, serial console, and the regular console from CTRL-ALT-F2.

It is a bad idea to run without updates.

can I get support DeepStream 1.5 for JetPack 3.3 ?