@sophiajackson22 Thank you for the information, I will keep an eye on it.

@ess You are welcome.

@kuo 祝贺！

@bouncy 打印出来的帧率从30.26缓慢下降到30.00 这个是正常的。因为这个程序统计帧率是每秒钟统计一次，第一次统计会有1帧的误差，后面会逐渐逼近到最准确的数。 画面依然出现卡顿现象，请问这个原因可能是由什么引起的。 这个比较奇怪，在我这运行完全没问题。这里面用到的nvidconv是使用了硬件资源的。而且agx xavier性能干这点活，完全没有问题。 不知你的机器有没有同时干其他工作？ 可以用jtop分析一下。

@veye_xumm 要不你把整套板子寄过来我们来检查一下吧

@simonpi 不明白你的意思，wiki上都有啊~

@panguin @panguin said in jetson-Nano emmc版本载板的veye驱动文件: 您所说的extlinux.conf文件指的是主机还是开发板上的目录，应该是开发板吧？ 是的

@wackyrabbits 我私信你

@veye_xumm ok,寄到哪

@veye_xumm 好的，非常感谢！

@robot 有一种可能，你的i2c和mipi是错配的。

@newleaf You are welcome.

@veye_xumm 好的，谢谢

@lin 参考一下part7.3

客户已解决。是kernel配置中关于rkcif的配置原因。

线下沟通，已解决。 解决方案是，在取图之前，通过system函数直接调用如下脚本： export I2C_BUS=7 export WIDTH=2432 export HEIGHT=500 export FPS=50 v4l2-ctl -d /dev/v4l-subdev2 --set-ctrl roi_x=0 v4l2-ctl -d /dev/v4l-subdev2 --set-ctrl roi_y=548 media-ctl -d /dev/media0 --set-v4l2 '"m00_b_mvcam '"$I2C_BUS"'-003b":0[fmt:Y8_1X8/'"$WIDTH"'x'"$HEIGHT"'@1/'"$FPS"']' 然后再取图。 如果直接用mv_mipi_i2c,sh配置roi，那么相机内的参数直接被修改，这个数值无法实时反映到v4l2驱动层中。造成参数的错乱。

@golden0514 你好。 我们相机有一个底层逻辑，fps参数会优先于曝光时间设置。 如果你想要1秒的曝光时间，需要先将帧率设置为1帧/秒，然后再设置曝光时间即可。

@nkos Sorry, regarding the attempt to port the camera to the Radxa Zero 3 + 6.x, we tried to set up the standard build environment but were unable to compile successfully. I posted a question on the Radxa forum, but have not yet received a follow-up response. As for the method you mentioned to configure our registers, we recommend that you do not use the driver. Instead, please use our mv_mipi_i2c.sh script. https://wiki.veye.cc/index.php/Mv_mipi_i2c.sh_user_guide

Sorry for bumping an old thread but I would like to provide an update that might be relevant. Since the last post I've transitioned to custom designed FPC with length matching and impedance made correctly. With the same software stack, csi0 showed no progress (still getting those ecc errors), the csi1 worked perfectly. I have also tried the recent fix to rk35xx_veye_bsp (13684db), and to my surprise, the situation is now different. The camera on csi0 now shows 60 fps picture, but with colors distorted (heavy red, green, blue splashes over the objects) and the dmesg shows the following: [ 110.638757] (0xfdd30000)MIPI_CSI2 ERR1:0x1000000 (crc,vc: 0) [ 110.638772] (0xfdd30000)MIPI_CSI2 ERR1:0x1000000 (crc,vc: 0) [ 110.638786] (0xfdd30000)MIPI_CSI2 ERR1:0x1000000 (crc,vc: 0) [ 110.638800] (0xfdd30000)MIPI_CSI2 ERR1:0x1000000 (crc,vc: 0) [ 110.638814] (0xfdd30000)MIPI_CSI2 ERR1:0x1000000 (crc,vc: 0) [ 110.638828] (0xfdd30000)MIPI_CSI2 ERR1:0x1000000 (crc,vc: 0) [ 110.638842] (0xfdd30000)MIPI_CSI2 ERR1:0x1000000 (crc,vc: 0) [ 110.638856] (0xfdd30000)MIPI_CSI2 ERR1:0x1000000 (crc,vc: 0) [ 110.638871] (0xfdd30000)MIPI_CSI2 ERR1:0x1000000 (crc,vc: 0) [ 110.638891] (0xfdd30000)MIPI_CSI2 ERR1:0x1000 (err_data,vc: 0) [ 110.638925] rockchip-mipi-csi2 mipi2-csi2: stream off, src_sd: 00000000ae59244c, sd_name:rockchip-csi2-dphy0 [ 110.638935] rockchip-mipi-csi2 mipi2-csi2: stream OFF When connected to csi1, the picture is as good as always. I hope that my update will help you with your debugging effort. Feel free to ask me to do some additional testing. @veye_xumm

@esjeeybi I have compiled the version you need, please check GitHub.