cz@tegra-ubuntu:~$ v4l2-ctl -d /dev/video0 --set-fmt-video=width=1280,height=2050,pixelformat=YUYV --stream-mmap --stream-count=1 --stream-to=frame_mipi.yuv
VIDIOC_S_FMT: failed: Invalid argument
<
frame_mipi.zip (831.4 KB)
cz@tegra-ubuntu:~$ v4l2-ctl -d /dev/video0 --set-fmt-video=width=1280,height=2050,pixelformat=YUYV --stream-mmap --stream-count=1 --stream-to=frame_mipi.yuv
VIDIOC_S_FMT: failed: Invalid argument
<
frame_mipi.zip (831.4 KB)
please dig into driver side to resolve this error report.
Hello JerryChang,
this problem is ok,I want to solve the problem that data comes out and YUYV and uyuv are opposite
hello Towe_Roll,
how you determine that, could you please analysis with 3rdparty tool, such as 7yuv for confirmation.
Hello JerryChang,
i used 7yuv for confirmation, now i change here is ok , but i think is not a good job.
Hi,
It is more like the camera source does not output data correctly. We would suggest check the camera sensor or device tree again. Swapping the formats in VI driver is more like a workaround.
Hello JerryChang,
Now I am still stuck on this problem, sometimes the camera starts to get camera data will fail especially the first time, but when I power the camera back on or the kernel prints the following log it will work properly, my camera is continuously clock I don’t know if there is any impact, is there any good solution?
Hello DaneLLL,
thank you replay, My driver and device tree refer to imx219, and I can’t find the problem there at present. I can only modify vi driver to avoid this problem temporarily.
hello Towe_Roll,
as you can see… it has reach 2500ms capture timeout.
it’s VI error recover to reset the capture channel to make it works.
is your camera sending stream as soon as system power-on?
please try adding a reset to the camera driver when your user-space app being called.
Hello JerryChang,
It will be added in the next version of my hardware, but it is not debugged at present, and the continuous clock of my sensor cannot be turned on during startup. Is there an interface on nx to turn on this reset?
hello Towe_Roll,
there’s already reset mechanism, tegra_channel_error_recover()
.
thank you, i will try
I don’t understand, it looks you’re try to compile the code? please dig into the error report to debug the issue.
Hello JerryChang,
tegra_channel_error_recover()
, i cant find it, i use r32.7.2
hello Towe_Roll,
we don’t support back-porting the changes, please consider moving L4T release version forward.
Hello JerryChang,
ok !
I want to know mipi video dev name whether changes are supported , whether specific device names can be implemented by udev as with usb dev ?
just like this photo
hello Towe_Roll,
I don’t understand, could you please give an example of your expectation.
Hello JerryChang,
That is, I want the video name generated by my camera to be fixed, and the video name will not change due to the sequence of access to other cameras