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

@yd 已添加，请通过。

@hxm fcf1a632-3381-4084-817b-f27489ad76ae-image.png

@veye_xumm 我换块板子试试吧

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

@hxm https://github.com/veyeimaging/nvidia_jetson_veye_bsp/tree/master/mv_tools_jetson

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

@joe yes

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

@乔康 感谢你的分享。
这个问题应该还是跟kernel版本有关系。我们开始调的3588的kernel版本不需要veyecam2m_g_bus_config功能。
总是，驱动调试你们很棒了~👍

@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.

@etale_cohomology
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
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 1FC9CBA1-4600-4A24-ABB6-E2B025BBD568.jpeg 格式是nv12了。但分辨率对不上。（将lvds_sditf disabled 以后）

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

@dufuwei 不好意思，我们这个无法绕过ISP模块。也不能提供完整的原理图。

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

@kevin2008 生成video节点只能表明i2c通了。
看你的截图，像是mipi接收部分的配置不对。

@m4416202 请问取图的时候有什么报错吗？ dts是否已根据你的主板上的硬件做了调整？

@wackyrabbits said in MV-MIPI-IMX296M 修改ISP参数保存:

@veye_xumm
Thanks for answering the above question. Please also answer the following questions:

Are the Enable/Disable values ​​of the three parameters gammaenable, dpcenable, and lutenable such that enable is 1 and disable is 0? Is the value range of the gamma parameter (0, 4.0] ( Range (0,4.0], accurate is 0.01.), modify the gamma parameter value, but the screen does not respond. The current pixelformat is UYVY. If you want the gamma parameter to be effective, do you need to adjust the pixelformat to Mono8?
Certainly! Here are the responses:

Generally, in software or systems, the convention for enabling or disabling parameters often follows a pattern where 'enable' is represented by 1 and 'disable' is represented by 0. However, it's essential to refer to the specific documentation or guidelines for the software or system you're working with, as conventions can vary across different platforms or contexts.

The gamma parameter typically ranges from 0.01 to 4.0, inclusive. It seems that you're modifying the gamma parameter within the specified range, but the screen doesn't respond. Changing the pixel format to Mono8 might be necessary for the gamma parameter to take effect, especially if the current pixel format (UYVY) doesn't support gamma adjustments. Some pixel formats may not support certain image processing functionalities, so switching to a compatible format like Mono8 could enable the gamma parameter to function as intended. Always refer to the software or hardware documentation for specific details on parameter compatibility and functionality within different pixel formats to ensure the desired adjustments take effect.