I’m facing issue with capturing raw image with v4l2-ctl. Let me explain the issue. I’m observing this issue only in 6.2.0 torizon version and not in 5.7.0
Im trying to take a raw image for 2592 X 1944 resolution with v4l2-ctl and I can observed the size of image is equal that of 1080p image, and if I view it im not getting the complete image.
whereas if I try to capture raw with gst-launch , Iam able to do it without any issue.
I am able to observe that the resolution set by gstreamer is overriding the v4l2 resolution
please refer below image
As first step im switching resolution using gstreamer . then as next step im saving the image using v4l2 of different resolution.
the 3rd column is the image size i’m getting and 4th column is the actual image size that I should be getting.
v4l2-ctl --device /dev/video2 --set-fmt-video=width=2592,height=1944,pixelformat=UYVY --stream-mmap --stream-to=frame.raw --stream-count=1
I tried testing it with USB camera. There is no issue with USB CAM.
yes the gstreamer and v4l2 don’t interfere with each other
Just to confirm your findings, I too didn’t notice any issues with my USB camera as well. I guess somehow the issue is specific to your camera, or maybe CSI cameras in general. Though I don’t have a CSI type camera around to confirm. As Kevin said we may need more information about the specific camera you are using.
Certificate verification failed: The certificate is NOT trusted. The certifica te chain uses expired certificate. Could not handshake: Error in the certificat e verification. [IP: 188.8.131.52 443]* Get:7 Index of /debian buster/main arm64 Packages [7737 kB] Get:8 Index of /debian buster-updates/main arm64 Packages [8780 B] Reading package lists… E: The repository ‘https://feeds.toradex.com/debian/testing buster Release’ does not have a Release file.
Im facing issue while docker build. This is due to issue in certificate verification. Do you have any idea to bypass this certificate verification. tried few methods but failed to do so.
What is your Dockerfile here used for this build? It looks like you’re fetching things for Debian Buster. But our supported Debian containers are for Debian Bullseye and Bookworm only. That’s probably why it fails trying trying to access our feeds for Debian Buster.