@canglin 默认是discontinues模式。

@veye_xumm 谢谢，原来它只能写成/dev/v4l-subdev2

@vaa said in New Raspberry pi 5 support:

@veye_xumm
In case I try to set pixel_format to any other value is cause VIDIOC_STREAMON fail. I suppose this is a bug in the driver.
Some other applications like gstreamer only set pixel_format if you directly point to do this, this is why it works, but many others (e.g. trying to set default pixel_format) are not.

Will you going to fix the issue?

@veye_xumm 好的，谢谢

@natzguk pls try this:
https://github.com/veyeimaging/rk35xx_firefly/blob/main/linux/samples/gstreamer/veye camera/preview.sh

@liliant 一般来说，能出图，i2c是通的；那么摄像头应该没有坏，控制参数也应该生效才对。

@lll 是的。本质上是修改对应的寄存器即可。

@newleaf You are welcome.

@veye_xumm For anyone else. This works perfectly. Note that when recompiling on 64-bit Pi, the following warning is produced. It still builds. Just copy the outputs to bin and the scripts work fine.

./make.sh i2c_read.c: In function ‘main’: i2c_read.c:112:35: warning: passing argument 4 of ‘i2c_rd’ from incompatible pointer type [-Wincompatible-pointer-types] 112 | i2c_rd(fd, device_addr,reg_addr, &value, num); | ^~~~~~ | | | unsigned char (*)[512] i2c_read.c:20:68: note: expected ‘unsigned char *’ but argument is of type ‘unsigned char (*)[512]’ 20 | static int i2c_rd(int fd, uint8_t i2c_addr, uint16_t reg, uint8_t *values, uint32_t n)

@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名字。
系统起来之后，运行这个命令有可能能有提示。

dmesg | dts

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