To get started, download JetPack to an x86_64 Linux machine used for flashing and select ‘Jetson TK1’ after starting JetPack.
This release includes an updated CPU clock maximum frequency to meet 5-year lifetime guarantees.
Depending on operating use-case, please refer to the Release Notes above or the Tegra K1 Datasheet for more information.
Does the version of OpenCV4Tegra included in this release of JetPack fix all the compatibility issues with ROS that existed in previous versions? I was able to install ros-indigo-desktop correctly and use rqt_logger_level (which did not work on OpenCV4Tegra 2.4.10 which I previously had installed) but I’m wondering if the problems mentioned on [url]http://wiki.ros.org/NvidiaJetsonTK1[/url] such as the cv_bridge linking problem have been resolved (or if the “hack” mentioned on that page still needs to be performed).
UPDATE: For anyone interested, I did some testing of my own and the linking problems with cv_bridge and image_geometry are still present, but the fix available at [url]http://myzharbot.robot-home.it/blog/software/ros-nvidia-jetson-tx1-jetson-tk1-opencv-ultimate-guide/[/url] took care of it for me. I’m happy to finally be at a point where I can use OpenCV in ROS on the Jetson TK1 without any problems (at least, problems that I know about!).
Doing an upgrade killed my working nVIDIA TK1. I tried from Jet PACK 1 to 3 and nothing seems to work. It falshes and then when we reboot the system, LED is on for few seconds (fan running) and then goes OFF making system presumably shutdown.
Basically you’d need to attach a serial console to see what’s going on (settings 115200 8N1, CTS/DTS flow control or software flow control).
One hardware check is to see if it can be put in recovery mode. If so, then the host will see the Jetson via “lsusb -d 0955:772”. If this works, and if it can remain on, then chances are it is not a hardware problem. If this can’t succeed, then it is a hardware issue.
If it turns out lsusb succeeds and the unit can remain on, then you could clone the eMMC to extend the hardware testing. Being able to clone would almost certainly mean hardware is fully functional. If lsusb works, then clone information is here:
[url]http://elinux.org/Jetson/Cloning[/url]