@m4416202
你可以参考这个帖子，跟你的问题类似。https://forum.veye.cc/topic/501/sc130m搭配rk3588不出图/16

@geniusdo 一般来说，每一个mipi口都会有一个单独的i2c总线与之对应。

@vaa

@vaa said in imx462 on RockChip 3399 (OP1) Asus Tinker Board 2:

Do you have imx462 camera with USB3.0 interface (UVC driver) then?

No

@hchorsi
The following link has a 50cm FFC cable. However, please note that when using such an extra-long FFC cable, you need to provide separate power to the camera.
https://de.aliexpress.com/item/4001257031331.html

@veye_xumm 好的谢谢您

@zzz 平台接入问题，已联系线下解决。

@esjeeybi

The driver code for RK358x and RK3566 is almost identical. You can check the "veyecam2m.c" file in both directories to confirm this.
What I mean is that you can leverage the driver code provided for RK358x kernel version 5.10 and port it to Orange Pi.

@vladimi-zheng 他这个跟你的问题应该不是一回事。你这个我首先怀疑fpc叠放，引起了信号串扰。

@jdx-jdx 3b2b4efe-374b-4427-a793-4d689364d5f5-image.png
这种排线的堆叠摆放会产生很强的信号串扰。
你这种情况需要改一下排线摆放，或者更换为带有屏蔽层的FFC cable。

@harryxiong
你好，已经增加了wdrsharppen的设置功能。请参考：
https://wiki.veye.cc/index.php/VEYE-MIPI-290/327_i2c/#wdrsharppen

@veye_xumm Thank you very much!

@stevenyang
如果是电磁辐射，必须改为屏蔽线。
你也可以尝试一下下图这种铝膜覆盖和导电布覆盖的ffc线。
f1d27e41-18cf-43b4-a98f-ba6e88d6f02e-f8bd68b76bc00b00f7e9a62f402b0ab.png

@cheesefish 不客气。

@lucas
https://wiki.veye.cc/index.php/VEYE-MIPI-290/327_i2c/#hdver

./veye_mipi_i2c.sh -r -f hdver -b [i2cbus]

You can use this command to identify the hdver of your camera.

@veye_xumm

At mgain=10 we don't see anything, neither hot pixels nor stars.
We see other people using the cam with mgain = 25 and no hot pixels at all.
And we had one set of parameters, where we didn't have hot pixels at mgain = 25 either.
It only lasted 5 minutes though.

@veye_xumm 好的，非常感谢！

@nvidia-0 said in raw-mipi-sc132驱动问题:

tegra194-camera-rbpcv2-veye_mvcam.dts

与dts中这个地方对应的，是代码中的
e21c4c8b-41d1-46b4-83b1-dd9d0a0acccb-image.png

@nvidia-0 是的