GitHub Community
Porting ov2740 camera sensor on imx93 #171047
Replies: 2 comments 9 replies
-
|
From your description, the hang at VIDIOC_STREAMON is usually caused by a mismatch between your MIPI CSI2/ISI configuration or incorrect PLL / clock settings for the camera. Things to check / try:
Also:
|
Beta Was this translation helpful? Give feedback.
-
|
Hi @Dee570
root@imx93frdm:~# v4l2-ctl -d /dev/video0 --set-fmt-video=width=1932,height=1092,pixelformat=BA10 --stream-mmap=4 --stream-count=1 --stream-to=ov2740_tp.raw --verbose Also, I checked with the scope: BR |
Beta Was this translation helpful? Give feedback.
-
|
This error usually means there’s an issue with your access or credentials. Try this: Make sure you have permission to push to that repo. Check if you’re signed in with the right account in Visual Studio. Verify the remote URL is correct. Sometimes signing out and back in or regenerating your token fixes it. |
Beta Was this translation helpful? Give feedback.
-
|
@Dee570 |
Beta Was this translation helpful? Give feedback.
-
|
Hi, did you manage to fix that issue? If possible, may I ask how you resolved the problem? |
Beta Was this translation helpful? Give feedback.
-
|
Hello, Today, I received EVK hardware board, then compared to my custom hardware and confirmed that there are no hardware issues. However, I’m currently facing a new problem: RAW10 image capture is producing incorrect byte data. Again, I really appreciate your support so far. |
Beta Was this translation helpful? Give feedback.
-
|
I am happy to know that I helped you. What does it mean by incorrect byte data? The RAW10 format can be one of the following: And the stream on the bus looks like the following image, 
If you are using the V4L2 to capture frames, V4L2 stores the 10-bit data in 16-bit, and you can use OpenCV to convert to RGB. v4l2-ctl -d /dev/video0 --verbose --set-fmt-video=width=2592,height=1944,pixelformat=BG10 --stream-mmap --stream-count=1 --stream-to=raw10_2592x1944.raw Set the width and height according to your frame size, and check which RAW format the V4L2 exposed to you. v4l2-ctl --device=/dev/video0 --list-formats Also, I suggest you use the NXP linux_imx 6.6.36 if you are using Yocto to build your image. You also need to patch the imx mipi driver to support raw data:
@@ -1138,6 +1156,8 @@ static int dwc_mipi_csi2_set_fmt(struct v4l2_subdev *sd,
@@ -1216,6 +1238,8 @@ static int dwc_mipi_csi2_s_stream(struct v4l2_subdev *sd, int enable)
diff --git a/drivers/staging/media/imx/imx8-isi-fmt.c b/drivers/staging/media/imx/imx8-isi-fmt.c struct mxc_isi_fmt mxc_isi_out_formats[] = {
If you want to see the RAW image, you can use the following link. It is helpful to see what you are getting from the camera sensor |
Beta Was this translation helpful? Give feedback.
-
|
Another point to check: You can determine the supported format from the camera registers according to the data sheet: 6.16 format control [0x4300 ~ 0x4302, 0x4316, 0x4320 ~ 0x4329] Also, check if one of the flip bits is on; this may affect your format 
I hope this information is helpful to you. Let me know once you manage to get the right frames from the camera BR |
Beta Was this translation helpful? Give feedback.
-
|
Hello Mr.Basel, After a few days, thanks to your guidance, I’ve completely fixed the bug.
That’s the key. I noticed this after you mentioned the 16-bit padding. I opened and compared the raw binary files of a color bar pattern captured from both IMX and Raspberry, and spotted the difference. That helped me realize I needed to modify the image parser we had built.
Finally, we were able to successfully capture a correct image — all thanks to your help. Sincerely appreciate it! |
Beta Was this translation helpful? Give feedback.
-
|
I am happy to hear that my help was worthwhile. BR |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Copilot Feature Area
General
Body
I am trying to operate an OV2740 camera module on the IMX93 FRDM board.
And when I am trying to capture a frame, the v4l2-ctl hangs :
root@imx93frdm:~# v4l2-ctl -d /dev/video0 --set-fmt-video=width=1932,height=1092,pixelformat=BA10 --stream-mmap=4 --stream-count=1 --stream-to=test_capture.raw --verbose
VIDIOC_QUERYCAP: ok
VIDIOC_G_FMT: ok
VIDIOC_S_FMT: ok
Format Video Capture Multiplanar:
Width/Height : 1932/1092
Pixel Format : 'BA10' (10-bit Bayer GRGR/BGBG)
Field : None
Number of planes : 1
Flags :
Colorspace : sRGB
Transfer Function : Default
YCbCr/HSV Encoding: ITU-R 601
Quantization : Full Range
Plane 0 :
Bytes per Line : 3864
Size Image : 4219488
VIDIOC_REQBUFS returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_QUERYBUF returned 0 (Success)
VIDIOC_G_FMT returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_QBUF returned 0 (Success)
VIDIOC_STREAMON returned 0 (Success)
The media graph looks to be ok :
root@imx93frdm:~# media-ctl -p
Media controller API version 6.6.36
Media device information
driver mxc-md
model FSL Capture Media Device
serial
bus info platform:42800000.bus:camera
hw revision 0x0
driver version 6.6.36
Device topology
entity 1: mxc_isi.0 (16 pads, 2 links, 0 routes)
type V4L2 subdev subtype Unknown flags 0
pad0: Sink
<- "mxc-mipi-csi2.0":4 [ENABLED]
pad1: Sink
pad2: Sink
pad3: Sink
pad4: Sink
pad5: Sink
pad6: Sink
pad7: Sink
pad8: Sink
pad9: Sink
pad10: Sink
pad11: Sink
pad12: Source
-> "mxc_isi.0.capture":0 [ENABLED]
pad13: Source
pad14: Source
pad15: Sink
entity 18: mxc_isi.0.capture (1 pad, 1 link)
type Node subtype V4L flags 0
device node name /dev/video0
pad0: Sink
<- "mxc_isi.0":12 [ENABLED]
entity 22: mxc-mipi-csi2.0 (8 pads, 2 links)
type Node subtype V4L flags 0
device node name /dev/v4l-subdev0
pad0: Sink
<- "ov2740 2-0036":0 [ENABLED,IMMUTABLE]
pad1: Sink
pad2: Sink
pad3: Sink
pad4: Source
-> "mxc_isi.0":0 [ENABLED]
pad5: Source
pad6: Source
pad7: Source
entity 31: ov2740 2-0036 (1 pad, 1 link, 0 routes)
type V4L2 subdev subtype Sensor flags 0
device node name /dev/v4l-subdev1
pad0: Source
[stream:0 fmt:SGRBG10_1X10/1932x1092 field:none
crop.bounds:(0,0)/1932x1092
crop:(0,0)/1932x1092]
-> "mxc-mipi-csi2.0":0 [ENABLED,IMMUTABLE]
My DTS :
&clk {
assigned-clocks = <&clk IMX93_CLK_CCM_CKO3>;
assigned-clock-parents = <&clk IMX93_CLK_24M>;
assigned-clock-rates = <24000000>;
};
ov2740_mipi: ov2740_mipi@36{
compatible = "ovti,ov2740";
reg = <0x36>;
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_cam_mclk>;
clocks = <&clk IMX93_CLK_CCM_CKO3>;
assigned-clocks = <&clk IMX93_CLK_CCM_CKO3>;
assigned-clock-rates = <24000000>;
clock-names = "xclk";
clock-frequency = <24000000>;
reset-gpios = <&pcal6524 22 GPIO_ACTIVE_LOW>;
csi_id = <0>;
mipi_csi;
rotation = <0>;
orientation = <2>;
status = "okay";
port {
ov2740_mipi_ep: endpoint {
remote-endpoint = <&mipi_csi_in_ep>;
bus-type = <4>;
data-lanes = <1 2>;
clock-noncontinuous;
link-frequencies = /bits/ 64 <360000000>;
};
};
&cameradev {
status = "okay";
};
&isi_0 {
status = "okay";
cap_device {
status = "okay";
};
};
&mipi_csi {
status = "okay";
fsl,rx-lanes = <2>;
csis-hs-settle = <16>;
/* Port 0: sink from the sensor */
port@0 {
reg = <0>;
mipi_csi_in_ep: endpoint {
remote-endpoint = <&ov2740_mipi_ep>;
data-lanes = <2>;
cfg-clk-range = <28>;
hs-clk-range = <0x16>;
bus-type = <4>;
clock-noncontinuous;
};
};
};
The driver is the ov2740 driver from the linux-imx scargapth. I modified it to match the DT, and I changed the PLL configuration to match a 24MHz clock :
Here is the camera data sheet:
www.elinfor.com/pdf/OmniVision/OV2740-OmniVision.pdf
Note that my module regulators are connected to the 3.3 volt; because of this, I didn't define regulators in the DTS
I based my changes on the driver from:
https://github.com/6by9/linux/tree/rpi-6.1.y-ov2740
Any advice
BR
Basel
Beta Was this translation helpful? Give feedback.
All reactions