Hi,
I am useing custom board based on i.Mx6Q the problem is that when i try running the camera useing the test application i get the Error.
mxc_v4l2_s_param: vidioc_int_s_parm returned an error -1
The camera which i use is OV7725 in CSI interface.Just wanted to know what is the reason for this error to occur.Is it because camera not detected or any i2c registration problem or Master Clock is not present.
Please Reply as soon as possible .
Thank you,
Deepanraj.A
Solved! Go to Solution.
Hi
Thank you Everyone the problem was in my camera .
Deepanraj.A
This error means that setting of capturemode and frame rate of your OV7725 are incorrect or you are not configuring correctly your camera, you can start reviewing if the I2C is getting out correctly. And then check your driver of your camera.
Have a great day,
Jaime
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hi,
I have remove the Ov5642 camera from the IPU1. And also remove the entry for same(camera) from .dtsi file. I have added my new sensor, having parallel interface with IPU2. Now I have only one node entry (/dev/video0). So it should be node for my sensor module.
Now when I run the gstreamer from command line I am getting the below errors:
root@imx6qsabresd:~# gst-launch mfw_v4lsrc device=/dev/video0 ! autovideosink
MAX resolution 1024x768
MFW_GST_V4LSRC_PLUGIN 3.0.11 build on Sep 27 2014 22:08:22.
Setting pipeline to PAUSED ...
MFW_GST_V4LSINK_PLUGIN 3.0
mxc_v4l2_s_param: vidioc_int_s_parm returned an error -22
ERROR: Pipeline doesn't want to pause.
Setting pipeline to NULL ...
Total rendered:0
[--->FINALIZE v4l_sink
Freeing pipeline ...
Hi,
Vinod
Just check your module is loaded or not..
It may possible that your module is not loaded and your are trying to access the device.
Thanks
Saurabh
Hi Saurabh,
My module is successfully loaded and it only support the Bayer RGB format. But I am still facing this error. Should I have to enable the clock for IPU2 in kernel level?@