Sunday 9 December 2018

How to install JetPack 3.3 on Ubuntu 18.04 and flash Jetson TX2

In July this year NVIDIA released JetPack 3.3 - currently the latest stable/production version of JetPack. Some of its features are:
This is the last JetPack that will be supporting Jetson TX2 and TX1 Developer Kits. JetPack 4.1.1 Developer Preview supports only new Jetson AGX Xavier Developer Kit but it will not be supporting TX2 or TX1).

Although official release notes for JetPack 3.3 state that supported Ubuntu on the host is 16.04, I had no issues installing this version of JetPack (and later flashing TX2) on my Ubuntu 18.04 with details:

~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic

I downloaded from NVIDIA Developer Center, added execution permission and ran it as non-admin (installer prompts user for elevated privilege only when necessary). If you run it as super user, installer will show you an error: 

Installer unpacks its content into a directory whcih has the following content: 

~/Downloads/JetPack$ ls

Although I got the following message as was running the installer on Ubuntu 18.04, I clicked "Yes" and had no issues during the process:

These are the screenshots of the successful JetPack 3.3 installation on Ubuntu 18.04 and flashing Jetson TX2:

It takes couple of seconds for Component Manager to download repo information, do version checks and show the current state of packages:

At this point I actually stopped the installation as wanted to do flashing of TX a bit later. This is possible as Component Manager will pick up and show the current state of all packages upon JetPack installer re-launch:

Now I pressed ENTER to resume the installation.

Just like before, I verified that all has completed successfully on TX2 by running some of installed CUDA demo examples (e.g. rendering ocean surface - "OceanFFT"). 

1 comment:

Tommi said...

I tried this and encountered problem: When installer was asking Yes/No to continue, Yes just exited the installer.

On my environment Ubuntu 18.04 had some -problem which was solved by following instructions here

After this, installer started.