I am trying to flash my Jetson TX1 using JetPack 3.0, but I am having issues. Here is a list of everything I’ve done and the problems I’ve run into:
Run JetPack normally (after running chmod +x)
There was not enough memory on the host computer.
Run JetPack from a 64GB flashdrive (granted only about 25GB are free)
This involved remounting the usb port on the host computer, but once I got that working, JetPack ran. I got to the point where the XTerm pops up and tells you to put the Jetson TX1 in force recovery mode, which I did (yes, lsusb does indicated that the board is connected). There is an error because the command to run sudo_daemon tried to use the flag -installer=fake_installer_pid. The program crashed, directing me to check the flash log file. This log file indicates that jetpackfifo could not be opened because it didn’t exist.
When the XTerm asks for my sudo password, copy the file jetpackfifo_req and rename the copy to jetpackfifo (clearing out the contents of the file as well)
This got to roughly the same spot as my last attempt, but the XTerm was just stuck trying to run a cp command. Using ps -a multiple times, I was able to determine that it was trying (and failing) to run the same command over and over, as the process for that command had a different time for each call of ps -a.
At this point I dug around some of the log files. In */_installer/tmp/log I found several lines indicating that various fifos could not be created (“operation not permitted”). I figured this was the source of my problems.
Give every file related to JetPack all possible permissions (-rwxrwxrwx)
Nothing changed from my last attempt. After some research I determined that the issue might have to due with the fact that the original call to ./JetPack-…run was not run with sudo.
Use the command “sudo ./JetPack-…run” (I didn’t actually use …s)
Very quickly the terminal read “Uncompressing JetPack 100% Extraction Failed”. This seems very odd since it worked just fine without the “sudo” part. One thread on this forum indicated that space may be an issue, but this all happens before I even reach the Components Manager, and I’m running on a flashdrive with about 25GB of free space.
This is as far as I’ve gotten. In case you were wondering, the host is running Ubuntu 14.04. I would be happy to give you any other specifications, outputs, or log files. Just let me know what you need. For now, I’m going to continue rooting around in the log files and .sh files (don’t worry, I won’t change anything) to see if I can figure anything else out. Any help is greatly appreciated.