About USB UVC issue

Hi Sir,

Did you ever see this error problem in the kernel log(dmesg)?

uvcvideo: Non-zero status (-75) in video completion handler.

Do you have any suggestion for us?

Thanks.

Hi,

The suggestion is please share your full dmesg and full usecase. What camera and which software release are you using?

Hi Wayne,

[ 427.401875] usb 1-3.2: new high-speed USB device number 6 using xhci-tegra
[ 427.424716] usb 1-3.2: New USB device found, idVendor=05e3, idProduct=0608
[ 427.431765] usb 1-3.2: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 427.439138] usb 1-3.2: Product: USB2.0 Hub
[ 427.445462] hub 1-3.2:1.0: USB hub found
[ 427.449861] hub 1-3.2:1.0: 4 ports detected
[ 429.756025] r8152 2-1:1.0 eth0: carrier on
[ 429.898412] usb 1-3.2.1: new high-speed USB device number 7 using xhci-tegra
[ 429.928058] usb 1-3.2.1: New USB device found, idVendor=09cb, idProduct=4007
[ 429.935721] usb 1-3.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 429.943535] usb 1-3.2.1: Product: Boson
[ 429.950191] usb 1-3.2.1: Manufacturer: FLIR
[ 429.954765] usb 1-3.2.1: SerialNumber: 22560
[ 429.960996] uvcvideo: Unknown video format 3132564e-0000-0010-8000-00aa00389b71
[ 429.970411] uvcvideo: Found UVC 1.00 device Boson (09cb:4007)
[ 429.995710] cdc_acm 1-3.2.1:1.2: ttyACM0: USB ACM device
[ 510.558886] uvcvideo: Non-zero status (-75) in video completion handler.

Boson thermal camera with USB UVC interface) for the drone.
L4T: 28.2

Yours Sincerely,
S.K.

Please just share the full dmesg as text file. Do no parse or grep anything.

Hi Wayne,

Sorry about that. Please see the attached file. Thanks.
kern_log.txt (122.5 KB)

Hi,

Sorry for late reply.

  1. Could you move to latest r28 release and see if this issue is still?

  2. Will other usb cam hit this problem?

Error code 75 means EOVERFLOW → “Value too large for defined data type”

Hi Wayne,

It’s hard for us to change the version.

We got two kinds of error values.
-71 → Protocol Error.
-75 → Data overflow.

Our EE team improve the connection sequence for the devices.
It’s not bad for the current status. (Not 100% successful)
We still find the best solution.

Hi,

  1. Why does it hard for you to change?

  2. Is this issue reproducible with nvidia devkit?

Hi Wayne,

  1. Our application is the drone.
    It’s not easy to change the new version right now. It took a lot of testing time.
    Our customers has the schedule pressure.

  2. No, I can’t get a “complete” nvidia devkit from our EE team (and TX1 is EOL).

Hi,

  1. I didn’t ask to develop or move your whole project to latest release. This is just for debug your current problem.

  2. Do you have other information to share? For example, what kind of camera is that?

The error log from your dmesg gives Unknown pixelformat. What pixel format are you using?

Jan 8 17:33:37 tegra-ubuntu kernel: [ 87.766621] Unknown pixelformat 0x00000000

Hi Wayne,

  1. I know what you mean, but I have more than one project.
  2. Boson thermal camera.
  3. My co-worker tells me that it comes from Boson. (maybe not standard UVC)

Hi,
Please refer to steps in
Jetson Nano FAQ
Q: I have a USB camera. How can I launch it on Jetson Nano?

In general we support YUV422 formats such as YUYV or UYVY. If your sensor outputs in unique format, you may not be able to run gstreamer command. Only can do frame capture through v4l2-ctl.

Hi DaneLLL,

My co-worker says that the sensor outputs is not the unique format.

Is it helpful for these messages ?

name : Boson
class : Video/Source
caps : video/x-raw, format=(string)I420, width=(int)640, height=(int)512, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, framerate=(fraction){ 9/1, 15/2 };
video/x-raw, format=(string)I420, width=(int)320, height=(int)256, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, framerate=(fraction)[ 0/1, 2147483647/1 ];
video/x-raw, format=(string)NV12, width=(int)640, height=(int)512, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, framerate=(fraction){ 9/1, 15/2 };
video/x-raw, format=(string)YV12, width=(int)640, height=(int)512, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, framerate=(fraction){ 9/1, 15/2 };
video/x-raw, format=(string)YV12, width=(int)320, height=(int)256, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, framerate=(fraction)[ 0/1, 2147483647/1 ];
video/x-raw, format=(string)BGR, width=(int)640, height=(int)512, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, framerate=(fraction){ 9/1, 15/2 };
video/x-raw, format=(string)BGR, width=(int)320, height=(int)256, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, framerate=(fraction)[ 0/1, 2147483647/1 ];
video/x-raw, format=(string)RGB, width=(int)640, height=(int)512, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, framerate=(fraction){ 9/1, 15/2 };
video/x-raw, format=(string)RGB, width=(int)320, height=(int)256, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, framerate=(fraction)[ 0/1, 2147483647/1 ];
video/x-raw, format=(string)GRAY16_LE, width=(int)320, height=(int)256, pixel-aspect-ratio=(fraction)1/1, interlace-mode=(string)progressive, framerate=(fraction){ 9/1, 15/2 };
properties:
udev-probed = true
device.bus_path = platform-70090000.xusb-usb-0:3:1.0
sysfs.path = /sys/devices/70090000.xusb/usb1/1-3/1-3:1.0/video4linux/video1
device.bus = usb
device.subsystem = video4linux
device.vendor.id = 09cb
device.vendor.name = FLIR
device.product.id = 4007
device.product.name = Boson
device.serial = FLIR_Boson_53857
device.capabilities = :capture:
device.api = v4l2
device.path = /dev/video1
v4l2.device.driver = uvcvideo
v4l2.device.card = Boson
v4l2.device.bus_info = usb-70090000.xusb-3
v4l2.device.version = 263206 (0x00040426)
v4l2.device.capabilities = 2233466881 (0x85200001)
v4l2.device.device_caps = 85983233 (0x05200001)

Hi,
You may try either I420 or NV12. See if the format works. Other formats are not well supported on Jetson platforms.