JetPack 2.2.1 for for L4T r21.5 install issues

I downloaded and set execute permission for the JetPack-L4T-2.2.1-linux-x64.run file. After running on an Ubuntu 14.04 64-bit os, I select the TK1 (also tired with the other 2 options) than the JatPacK L4T Component Manager window is totally empty.

I tried to run it while the TK1 is not connected (USB), connected while in recovery mode, and connected and logged in, it is newly flashed with Linux For Tegra R21.5 https://developer.nvidia.com/linux-tegra-r215 based on the Quick Start Guide.

What am I missing? Why is the window empty?

How can I install any toolkit manually on the TK1 without using the JetPack component manager?
Like where can I find the CUDA 6.5 (6.5.53) Toolkit for L4T r21.5 .deb file?

The JetPack has several functions, including flash and some package management. In all cases of flashing the Jetson must be in recovery mode with the micro-B USB cable connected…since your flash is completed to R21.5, this does not apply, and recovery mode should not be used. In cases where packages are being managed, then the ethernet needs to be connected/configured for both host and Jetson; if JetPack was used for a flash, then network is probably “mostly” already set up. I do not use JetPack because my host is Fedora, but it sounds like perhaps there is a network configuration needed.

From the Jetson, can you ping any outside network address?

I flashed the Jetson manually, from host through micro-B USB connection based on the Quick Start Guide document and also as explained here: https://gist.github.com/jetsonhacks/2717a41f7e60a3405b34. I didn’t used the JetPack for flashing, so tomorrow I’ll try to set up the network connection with the host.

I was able to brows online from the Jetson but the host was on a different network connected toa rooter while the Jetson to the main server.

Where can I find the repository of the toolkits for R21.5?

I do the manual flash as well since my host does not support Ubuntu packages. This does mean though that networking must be set up manually. If you know the address of the Jetson (such as via “ifconfig”), then the router should allow access from your host via the dotted-decimal format address, e.g., something like “192.168.1.3” or “10.0.0.3” (whatever the router assigned. On your host, assuming the router assigns the same address each time, you could put an entry in the host’s “hosts” file (of “/etc”) to instead refer to the Jetson as something like “tegra-ubuntu”, e.g., a line similar to this appended:

10.0.0.3    tegra-ubuntu

Your router may have some sort of function as well which can be set up to label the Jetson “tegra-ubuntu” for anyone on the local network.

The R21.5 URL is:
https://developer.nvidia.com/linux-tegra-r215

The list of some legacy packages would be here (you’ll be interested in the CUDA 6.5 package, 32-bit ARMv7, Ubuntu 14.04):
https://developer.nvidia.com/cuda-toolkit-archive
https://developer.nvidia.com/cuda-toolkit-65

Now the host and Jetson are connected to the same rooter, each can ping the other one.
Still the JetPack does not recognize the board and the packages.
In the users guide http://developer.download.nvidia.com/embedded/jetson/TK1/docs/2_GetStart/Jeston_TK1_User_Guide.pdf enumerates the between he requirements that the host and Jetson should be connected vie ethernet, mini-B USB, and serial port.

I doesn’t connect through the serial port (due to lack of cable). Is UART needed for the JetPack or it is only used to access the debug console?

I’m going try to install manually the toolkits.

Micro-B USB is used for flash only, no packages are added this way. Recognition of a Jetson through micro-B and recovery mode does not apply to stages where normal package management occurs. If not flashing, you can ignore micro-B USB.

Package management uses the ethernet port. Ethernet is not used for flash, but is set up and used in all of the other cases outside of flash. Typically JetPack would flash and ignore ethernet, but then set up ssh keys or other networking after flash completes and Jetson reboots. Any package management issues may be a result of JetPack not having ssh keys and router setup as expected (you can ping, so flash and DHCP were successful…all that is left is for ssh setup…typically meaning keys).

Serial port is useful for monitoring what’s going on. This is not actually required for flash, nor for package management. I do not know if JetPack makes use of serial port once Jetson is rebooted, but it seems unlikely that this would matter to JetPack. I can’t be certain because I do not have an Ubuntu host to try JetPack with. Someone may be able to comment on how ssh keys are set up under JetPack, e.g., if passwordless logins should be set up via ssh keys.