- 1 Camera interfaces on Jetson TK1
- 2 Interface details
- 2.1 USB 2.0
- 2.2 USB 3.0
- 2.3 Gigabit Ethernet
- 2.4 Firewire
- 2.5 CSI MIPI
- 3 Multiple Cameras
- 4 Stereo Cameras
- 5 Specialized camera sensors
- 6 Camera access
Camera interfaces on Jetson TK1
The Jetson TK1 board provides several different interfaces that allow camera input:
- USB 3.0 port (supports many USB 2.0 or USB 3.0 webcams). Additional USB 3.0 ports can be added through mini-PCIe, eg: mini-PCIe (untested).
- USB 2.0 port (through a micro-B to female USB-A adapter, that is sometimes included with Jetson TK1).
- Gigabit Ethernet port. Additional Gigabit or Dual-Gigabit Ethernet ports can be added through mini-PCIE, eg: mini-PCIe (untested).
- CSI-2 MIPI dual camera ports (one 4-lane camera port and one 1-lane camera port) through the GPIO expansion port.
- Firewire (available through mini-PCIe), eg: mini-PCIe (untested).
- Analog video capture cards, available through mini-PCIe (eg: mini-PCIe (untested)), USB 3.0 (eg: USB 3.0 (untested)), or USB 2.0 (eg: USB 2.0 (untested)).
USB 2.0 (480 Mbps) is the most common & cheapest method for camera input, since USB 2.0 webcams range from $5 - $200. However, USB 2.0 is the slowest of the possible camera interfaces, so it usually only supports upto 720p 30fps (eg: Logitech C310 $45 (untested)), (except for the few USB 2.0 cameras supporting 1080p video compression, such as Logitech C910 (untested)). Logitech C910 is known to work on Jetson TK1 in uncompressed modes but has not been tested in 1080p compressed mode.
Typically, webcams are successfully giving the same frame-rates & resolutions on Jetson TK1 as on an x86 desktop running Linux (eg: 640x480 @ 30 FPS, 960x720 @ 15 FPS, and 1920x1080 @ 15 FPS). Note that many webcams will run slower if there is low lighting, so for example, it might be 30 FPS when pointed at a bright light but only 10 FPS when pointed at a shadow.
Disabling USB auto-suspend
Some USB devices & cameras have problems on Jetson TK1 due to automatic suspending of inactive USB ports in L4T 19.2 OS to save power. So you might need to disable USB auto-suspend mode. This will disable it temporarily until you reboot:
sudo bash -c 'echo -1 > /sys/module/usbcore/parameters/autosuspend'
To automatically disable USB auto-suspend on bootup, follow the instructions to Run a command automatically on bootup.
USB 2.0 webcams known to be working
- Rocksoul WC-102 5MP
- Gearhead WC4500AFW
- Logitech C210
- Logitech C615
- Logitech C920
- Rocketfish HD Webcam Pro
- Creative Live! Cam Chat VF0700
- Generic "Full HD 1080p" webcams using the Realtek chipset
- Microsoft LifeCam HD-3000
- Microsoft LifeCam Studio
- Sony PlayStation Eye (PS3 Eye) (can give very fast framerates, but some extra steps are required).
USB 2.0 webcams with known problems
- Microsoft LifeCam HD-5000 does not work. Please use a different model such as LifeCam HD-3000 instead.
Note: If a webcam or video capture card is supported by UVC or Video4Linux (see examples) then it will probably work the same on Jetson TK1 as on a desktop, but there is a possibility that it requires the firmware to be copied to your "/lib/firmware" folder or potentially even compiling & flashing your own custom Linux kernel with appropriate drivers enabled.
USB 3.0 (5 Gbps "SuperSpeed") on the full-sized USB port (J1C2 connector) has enough bandwidth to allow sending uncompressed 1080p video streams. But USB 3.0 hasn't reached the mass consumer market like USB 2.0 has, so USB 3.0 cameras are mostly still limited to expensive professional-grade cameras. eg: PointGrey Flea3 1080p @ 60 FPS (working!) or e-Con See3CAM_80 1080p @ 30 FPS (working!).
Enabling support for USB 3.0 on the full-sized USB port
Note that early versions of Linux4Tegra didn't come with USB 3.0 support enabled, and thus you might need to enable USB 3.0 support and re-flash your whole L4T system. According to the L4T R19.2 Release Notes, you should modify the odmdata settings (in "pm375_release_armhf/Linux_for_Tegra/jetson-tk1.conf") to enable USB 3.0:
# Use ODMDATA=0x6009C000 for USB 2.0 operation or for use as a root device. # Use ODMDATA=0x6209C000 for USB 3.0 operation. Requires firmware loaded from userspace or initial ramdisk. ODMDATA=0x6209C000;
Then flash your L4T system and reboot.
Enabling USB 3.0 support on L4T 21.2 is easier. You only have to change one parameter in:
USB 3.0 webcams known to be working
e-con Systems have tested many of their USB 3.0 cameras with Jetson TK1. They require flashing a custom Linux kernel that has the CONFIG_HIDRAW setting enabled, by following their tutorial, or using the The Grinch kernel by Korneliusz Jarzębski.
- e-Con See3CAM_80 (~$90) was tested on Jetson TK1 with 1920x1080 @ 30 FPS (uncompressed) (see video) as well as other settings. This camera board has good Linux support and contains an 8 Mega-Pixel MIPI camera with auto-focus ability and an onboard ISP including 10 GPIOs that can potentially be used for other purposes besides flash & camera activation.
- e-Con See3CAMCU50 was tested on Jetson TK1 with 1920x1080 @ 30 FPS (uncompressed), 2592x1944 @ 15 FPS (MJPG compressed), 1280x720 @ 60 FPS (MJPG compressed), as well as other settings.
- e-Con See3CAM_12CUNIR (low-light & near-Infrared camera) was tested on Jetson TK1 with 1280x720 @ 55 FPS (uncompressed 16-bit grayscale), as well as other settings.
- e-Con See3CAM_11CUG was tested on Jetson TK1 with 1280x720 @ 30 FPS (uncompressed 16-bit grayscale), 2592x1944 @ 15 FPS (MJPG compressed), as well as other settings.
- e-Con See3CAM_10CUG_C was tested on Jetson TK1 with 640x480 @ 45 FPS (uncompressed RAW Bayer color), as well as other settings.
- e-Con See3CAM_10CUG_M (global shutter camera) was tested on Jetson TK1 with 1280x720 @ 60 FPS (uncompressed grayscale), as well as other settings.
- e-Con See3CAM_10CUG_M was tested on Jetson TK1 with 1280x960 @ 45 FPS (uncompressed), as well as other settings.
PointGrey Flea3 model FL3-U3-13E4C-C with 1280x1024 @ 60 FPS has been tested and works with L4T 21.2. Setup steps for this camera to work:
- Install FlyCapture SDK for ARM Hard Float
- USB 3.0 support
- Disable USB auto suspend
- You need to configure USBFS so that all pixel formats of the camera can be used. Configure USBFS describes how to do it for Grub. The same can be done on Jetson TK1 by adding:
"IP Cameras" are fairly easy to find and are a good option for single or multiple cameras. Gigabit Ethernet (1 Gbps) has enough bandwidth for uncompressed 1080p video streams. eg: GigE cameras (untested) or regular IP network cameras. Nico notes that older GigE cameras typically do not apply any compression, since compression is a feature of the newer GigE Vision 2 standard, and thus most industrial GigE cameras for computer vision don't have compression and send Bayer images instead. IP cameras typically have M-JPEG compression as well as a video streaming server such as by providing a URL where M-JPEG or JPEG frames are available.
Firewire has been used for professional video capture for a long time, since Firewire cameras do a lot of both the compression and the data transmission in hardware and thus don't put nearly as much stress on the host CPU compared to USB.
CSI-2 MIPI is the most efficient method for camera input, since the cameras are tiny and the images can be processed directly by the ISP rather than needing to be stored into the computer's DRAM first before processing. However using a CSI MIPI camera directly requires much more work than using a USB, Ethernet or Firewire camera.
Licensing costs of the ISP has been reported as the constraint as it is only generally viable for millions of units.
An untested example is 720p 60fps. However there isn't a single standard for CSI cameras, thus each customer typically designs their own connector that is specific to a camera module and a computer or ISP.
MIPI-CSI2 sensors known to be working
There are several ways to handle multiple cameras on Jetson TK1 at the same time:
- Ethernet: multiple IP cameras on a network (eg: several TRENDnet Internet Cameras (untested) at $118 each). Theoretically you could have 6 x FullHD 1080p 30fps cameras using 3 x Gigabit Ethernet ports on Jetson TK1 (discussed on the forum)!
- CSI MIPI: 2 cameras (eg: a front camera and a rear camera (untested)).
- Code Laboratories: (DUO MLX) (Working/Manufacturer Supported - DUO3D on Jetson).
- IDS: (N10) (untested).
- Leopard Imaging: (LI-USB30) (untested).
- Point Grey: (Bumblebee XB3)(untested).
Specialized camera sensors
- Time-Of-Flight 3D depth "RGBD" cameras (eg: Microsoft Kinect is known to work, see details below).
- Night-vision or Thermal-imaging Infrared cameras, typically with interfaces similar to standard cameras.
Microsoft Kinect Structured-Light 3D Depth camera
Then you need to follow the Kinect Manual Installation Guide rather than the many x86 based guides, since the Tegra CPU uses ARM architecture.
Asus XTion Pro Live RGB-D Sensor using OpenNI2 library
Asus XTion Pro Live is a RGB-D sensor based on the Primesense's patent (Primesense has been acquired and deleted by Apple in the end of 2013) that drives the first Microsoft Kinect. Asus Xtion sensor, differently from Microsoft Kinect, can be powered directly by USB cable not requiring an external power source.
You can find a guide to compile OpenNI2 library for Jetson TK1 and use it to interface Asus XTion Pro Live on the blog of the robotic project MyzharBot.
To see which video capture devices you have available:
To see the supported video formats of your webcam:
sudo apt-get install luvcview luvcview -d /dev/video0 -L
You can also use luvcview to record video from your webcam to a video file. It will open a GUI window showing the camera preview. Then along the middle of the bottom row there are 4 rectangle buttons, click the bottom-left of the 4 buttons to start/stop video recording, and the bottom-right button to quit. To record video using the default settings of your webcam:
luvcview -o out.avi
To record video using a custom resolution (of those shown when running luvcview -L above):
luvcview -o out.avi -s 640x480
Normally, guvcview can be used to adjust default camera settings, but it seems that the default guvcview is not working correctly on ARM due to a kernel change.