Problem installing Jetpack 2.3 for Jetson TK1
 

Hi,

Our team (1277) are just getting into vision processing and decided to buy a TK1. I have tried installing Jetpack 2.3 on my ubuntu laptop but the install fails - it can't find arm32 ubuntu packages! It seems like this is a bit of deal breaker for the TK1 if arm32 ubuntu packages are no longer available.

Admittedly we have a big learning curve to go through here, but can anyone point us in the right direction with this? Did we make a mistake buying the TK1?

Thanks - Paul

Re: Problem installing Jetpack 2.3 for Jetson TK1
 

I would suggest following the jetpack installation guide. Missing packages is a symptom of not following that guide completely from what I've seen on the Nvidia embedded forums.

As for if you've made a mistake with the TK1. It's a great platform and more and more teams are using is successfully. That being said, I always tell teams who want to 'get started' with vision processing to start with the examples provided by FIRST/WPI and the GRIP program. It's not as sexy/cool/exciting but it is the right place to start. Once you have the basics down then a raspberry pi, kangaroo PC, Jetson, or android device is a solid way to progress.

Make sure you thoroughly read through the installation guide and if you're still stuck then post some output and logs so we can help you out a bit.

Re: Problem installing Jetpack 2.3 for Jetson TK1
 

I followed the instructions here for a host install. Here's the installation logs for visionworks. Note the lack of arm32 package repos, the signature error, and warnings that none of the visionworks libraries could be 'authenticated'. The last line indicates it errored out and I couldn't find libvisionworks* in any of the library locations.

If I try and find arm32 ubuntu packages manually, they are not listed. For example at http://packages.ubuntu.com/search?keywords=search

Re: Problem installing Jetpack 2.3 for Jetson TK1
 

What version of Ubuntu are you trying to install this on?

I believe 14.04 is required.

It looks like you are missing a GPG key for one of the repos to me. That could be because the repo no longer exists, it wasn't added correctly to your repo list, or an OS version mismatch.

If you are on 14.04 theb try running apt-get update and apt-get upgrade before the install. Make sure to reboot after to pick up any kernel updates. If those commands produce similar output then post that please.

Re: Problem installing Jetpack 2.3 for Jetson TK1
 

Worked like a charm. Thanks for your help!

Re: Problem installing Jetpack 2.3 for Jetson TK1
 

Sweet! Also, what worked? ;)

Re: Problem installing Jetpack 2.3 for Jetson TK1
 

I take it back. It didn't work like a charm.

First, to answer your question I did apt-get update and upgrade and reboot and run again.

So I only ran the host install, because I didn't have the TK1 around. When I finally got my hands on the TK1 again, I ran the TK1 part of the install and I was back to square 1, like it had never worked in the first place.

I've given up trying to install it. I posted on the nvidia developer forums where the response was basically 'We have an exact copy of the software here and ours is working fine'.

I've gone down the route of trying to get GRIP working on it, using some old instructions I found on this forum here. They are clearly out of date, but it is possible to figure out the intent and move from there (although I am currently stuck there too).

I have to say: Don't buy this board. Nothing I try to do with it works, including:

• Adding a wifi device driver.
• Using ufw
• Adding and using vnc
• Installing Jetpack
• Building GRIP (this latter is a great learning experience and I haven't totally given up yet, despite my experience with all of the above)

There are a couple of problems that seem to exist:

The first is that Nvidia seem to have moved on to the TX1. The TK1 doesn't get much love.

The second is that using an arm based device as a native build environment is still a novelty. Most packages and instructions for using them assume you are cross-compiling on something else. They also often assume you are cross compiling for Android.

The third is that no one seems to explain (or know?) the purpose of all of the various build options (compiler switches, compiler options, tool options etc). They generally just seem to be messing with the incantations until something seems to work, then finally it doesn't.