UVC camera cant use in Jetson Nano offcial carrier board

[Arducam_Edward]

Hi all,
Thank you for your time.
Lastly, I bought a USB camera using on my Jetson nano 8 GB. However, when I use qv4l2 to previewe the camera, it shows black screen and output the error below:

libv4l2: error turning on stream: Protocol error VIDIOC_STREAMON: Protocol error
image
image
1177×838 86.5 KB

I also tried vlc, which had no luck too.
I connect this USB camera on my laptop and it is working on windows OS. I have been stuck by this problem for almost two day and really really want to figure it out. I will appriciate for any helpful advice.
Here is my jetson’s info:
Jetpack version:4.6.3
L4T: 32.7.3
If you have any other info, I will be pleasure share it. Thank you in advance.

[Arducam_Edward]

Here my picture:

[DaneLLL]

Hi,
Please refer to the steps in Jetson Nano FAQ

Q: I have a USB camera. How can I launch it on Jetson Nano?

and see if you can launch the camera in gstreamer.

[Arducam_Edward]

@DaneLLL

thank you for your reply

I try but no luck

gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-raw,format=YUY2,width=640,height=480,framerate=30/1 ! nvvidconv ! 'video/x-raw(memory:NVMM),format=NV12' ! nvoverlaysink
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Setting pipeline to PLAYING ...
New clock: GstSystemClock
ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Internal data stream error.
Additional debug info:
gstbasesrc.c(3055): gst_base_src_loop (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
streaming stopped, reason not-negotiated (-4)
Execution ended after 0:00:00.000450947
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...

[Arducam_Edward]

Update
After turning it on and off seven or eight times, the camera was finally ready to produce a picture. But after turning it off, there was a need to turn it on and off seven or eight times before it could produce a picture.

bandicam 2023-11-09 10-58-46-326.mp4

[DaneLLL]

Hi,
It may be an stability issue in the camera itself. Ideally it should be launched successfully each time.