@lin 你使用的源码版本有可能给我们的版本不同。 我觉得需要首先判断一下你的系统最终生效的dtb的名字是什么。 firefly的sdk的不同的版本，可能对应不同的dtb名字。 系统起来之后，运行这个命令有可能能有提示。 dmesg | dts

@joe yes

@peter 你好，中括号[]不需要输入。比如-p1 NTSC,这样即可。

@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. [image: 1702970334043-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.

@etale_cohomology [image: 1702967744898-080d6fcb-12e7-4338-800a-b7ef90734db4-image.png] I think the FFC cable direction is wrong here.

@veye_xumm said in Driver Problem for Jetson Nano 4GB Developer Kit and VEYE-MIPI-327-fpdlink Camera Module: @samet_moveon [image: 1702432469399-3a1f99aa-daca-4ba5-991b-0cfd6294253c-image.png] According to your previous hints, it seems that your FPD-Link channel has been successfully established, and Jetson can access the camera through I2C. However, there are several errors in your driver that need to be addressed. We use the camera I mentioned above in our products and I need to solve this problem so that we can proceed to the production phase, can you please help me how to solve this problem? Also my version is Jetpack4.5, L4T r32.5 and I have to use this version.

@veye_xumm [image: 1702446803775-1fc9cba1-4600-4a24-abb6-e2b025bbd568.jpeg] 格式是nv12了。但分辨率对不上。（将lvds_sditf disabled 以后）

@veye_xumm 使用vooya打开了图像 [image: 1702361336825-364335c7-cb24-4c35-be07-4752de0a4ad6-image.png]