@魏魏飞
本身触发应该是不会丢失帧的，当然你可以用示波器来验证一下触发信号。就是你说的那个周期性的下降沿，这个是周期性的，规律的，不是不定期的。
我感觉问题出在录像上，你的pipeline可能有丢帧。
可以试试lagecy mode。

@veye_xumm Perfect, thank you very much for your support. It is now working.

已在其他帖子解决。

@lym123

@lym123 said in 在树莓派平台 cs132 丢帧:

出现了这个情况

这个是因为你保存数据到sd卡或者emmc存储空间中。这个是由于文件系统缓存的问题。 可以改为直接到/dev/null,能准确捕捉和判断帧率。

@salva OK

@octa_yk No, this is just a suggestion for you.

@xzh said in raw-mipi-sc132相关开发例程:

这个引脚悬空是可以的。摄像机板子上自带一个弱上拉。

@veye_xumm Glad to hear that! I would like to test it as soon as possible.

@lin 你的图片我看不到。但是根据你的描述，似乎没有更新dtb。
另外我们提供了一个现成的镜像，在这个链接：
https://github.com/veyeimaging/rk35xx_firefly/releases

@desperex The linux of this board is open source. firefly has contact information on the wiki page, and you can get a download link to the material after you purchase it and consult it.

@mjyc
./media_setting_rpi5.sh XXX只有这个是必须要执行的。
上电之后，执行一次。

@veye_xumm 好的，已解决

@john
We compared the baseboards of the J401 and J401B and found no differences. Regarding the earlier issue with the J401, we suspect that the USB hub chip, which is mounted on the same I2C bus as the camera, was intercepting responses for the I2C address 0x3b. This aligns with your hypothesis.

Could you visually inspect the J401B and check if there are any version or sub-model changes in the USB hub chip compared to the J401?

Regarding your intention to test the response issue at address 0x22, you do not need to recompile the device tree blob (dtb). You can directly use the command i2cdetect -y -r i2cnum to perform the test.

@antony
You've made a very accurate analysis and testing, which is admirable.
For this camera model, to save space, we use a double-sided contact connector, which indeed has caused some issues. We are planning to improve this module by replacing it with a 22-pin single-sided contact connector.

I, together with our hardware colleagues, conducted an analysis, and the results align with your test findings.
After reconnecting the FFC cable correctly following a reversal, the sensor's registers and error codes did not indicate a damaged state for the camera.

0cc7b86d-d1f6-4833-b373-dc0dc445c5ed-f5b019a3f2a6617992ded7348331e2b.png
In the case of reversed power connection, the pins that are actually damaged are CON_CS_D1P and CON_CSI_CLKP. Unfortunately, this issue cannot be detected through software.

@veye_xumm

I understood that the synchronization signal is very accurate in an environment close to hardware.

We will check the details from time to time.

@veye_xumm
As the time is too long and there is no further feedback from the customer, I will mark this post as resolved.

@mk No such plan, this cannot be supported. Sorry.

@wqeeqweqwwccsd
当然是支持的。你可以看这篇文章 6.3 6.4两个部分。
http://wiki.veye.cc/index.php/FPD_LINK_III_for_Jetson/zh
其中，6.4 xavier的典型案例就有实现了同一颗954连接的两路视频的同步。

Why not use Again 27,and Dgain 5?

Thanks I will try and let you know.

@eledog
我们装了一个你用的lite版本，运行是没有问题的。
9ecdb20e-ebc2-49f8-8719-e16be7cff655-image.png
你用的硬件是4GB版本，我们的是2GB版本。

我这没法重现的情况下，你可以尝试103-123行进行逐行注释来找一下原因。
bb570ba3-c8aa-4d0a-828b-a582d8b0222e-image.png