I’ve been trying out a few different USB (UVC) cameras on Jetson TX1. And I can reproduce the problem with all of them. For example, when I plugged a Logitech C920 into the USB 3.0 port of Jetson TX1 and ran the OpenCV “hog” sample (samples/gpu/hog) with live camera feed, the TX1 system would usually hard hang within 2~3 hours. If I ran the same OpenCV “hog” sample with a video file input, the TX1 system could work overnight without problem.
I’m using JetPack 2.0 on Jetson TX1. Has anyone experienced a similar problem?
Thanks for reporting the issue, we are currently investigating the case and we’ll let you know when we have an update.
Because the Jetson is mostly designed to be an embedded device, it tries to conserve power by automatically suspending inactive USB ports to save power. Not sure if the hang was caused by “temporarily” disabling USB.
You may need to disable USB auto suspend mode, this is a link to being sure lower power is not entered:
We are working on reproducing the issue. In the meantime, I would request you to send us the sample along with the steps followed for running it, which could help us in replicating the scenario at our end.
I did more testing and found the problem only occurred when I used the UVC camera and the GPU (for computer vision tasks) simultaneously. I’m now trying to find an easy and deterministic way to reproduce the problem. I think I’ll post the repro steps in 1~2 days.
(Since the OpenCV4Tegra which comes with JetPack-2.1 does not support live camera input, I have to compile OpenCV from source to be able to repro the problem.)
Here’s some additional validation work I’ve tried on Jetson TX1:
Environment: Jetson TX1 with fresh Jetpack-2.1, with a Logitech C920r camera plugged into the USB 3.0 port
If I only exercise the camera, I cannot repro the problem. The following works fine overnight.
I have 2 Jetson TX1 boards on hand. I can now conclude that the USB hard-hanging problem is more easily reproduced on the older board (bought around Dec. 2015), but it’s very difficult to repro the problem on the newer board. I’ll post more information, such as S/N, about the boards later.
When running the gpu hog program with UVC camera source, I can see xhci related messages in dmesg. And the older TX1 board usually hard-hangs within 2~3 hours. (Note the same test runs OK on Jetson TK1.)
The issue you met is the same USB3.0 camera + OpenCV4Tegra hang issue as below?
“USB 3.0 port of Jetson TX1 and ran the OpenCV “hog” sample (samples/gpu/hog) with live camera feed, the TX1 system would usually hard hang within 2~3 hours. If I ran the same OpenCV “hog” sample with a video file input, the TX1 system could work overnight without problem.”
Or it’s other symptom?
If it’s OpenCV related, then we will have a new version updated within JetPack2.2 release, please stay tuned.
hi, im on a usb webcam, i run the videoCapture code, but it always give me -216 error, could not get any frame, i test the webcam with luvcview, it is working. im on Jetpack 2.1 with opencv4tegra. is there anything i could do to solve the problem? or is there any “for sure” c++ code that can run on Jetpack 2.1?
I am new to Tegra and OpenCV4Tegra. I am having a lot of problems trying to get OpenCV4Tegra to work with the nvidia camera and logitech camera on the TX1.
This command, from the console will display video from the USB camera on the monitor…
$ gst-launch-1.0 v4l2src device=“/dev/video0” ! xvimagesink -e
How can I use the gst pipeline from OpenCV4Tegra to access the camera? If I do the following:
VideoCapture cap (“v4l2src device=‘/dev/video0’ ! xvimagesink -e”)
and then open the cap stream… I get no output. The program does not generate errors, but also does not open any frames from the camera. I have looked at the threads in this forum and it appears that the problem is OpenCV4Tegra on Jetpack 2.1 is not compiled to allow gst usage. Can somebody confirm this?
If this is true, then what good is OpenCV4tegra if I can’t open a video stream from a USB camera or the TX1 provided camera?
Regarding your OpenCV 3.1.0 install issue, that might be the known issue, OpenCV compiling frequently crash in R24.1 64-bit environment. Please repeat compiling till it’s done, or to wait for next release.
You’ll also want to post the camera model/info and lsusb -vvv for that camera (plus lsusb -t). The command producing the OOPS would be useful. Actual L4T version can be posted via “head -n 1 /etc/nv_tegra_release”.