I have uploaded a zip archive, please download it, unzip it, and use it.

@veye_xumm
I think my connections are not as good as it should be.
I'll try in better condition if the problem persist, I'll make a new issue.
Thanks

@veye_xumm 你好，如果相机恢复出厂设置还是无法采集，有什么方案彻底重置相机吗？比如重装驱动？有操作说明吗？

@veye_xumm 好的，感谢，找到了，得用新的链接，我用的是之前旧的链接

@xmy
编译完之后，按照文档的part3部分，安装驱动就可以了。
https://wiki.veye.cc/index.php/Build_drivers_from_source_for_rpi/zh

@veye_xumm OK，明白，多谢！

@veye_xumm 感谢

@毛宪历
这个板子上，请使用如下命令进行测试先：

python3 ./v4l2dev_2_opencv_show_grey.py --width 2432 --height 2048 --fps 50 --i2c 7

@毛宪历 不好意思，现在我们还没有提供成型的SDK。
提供的资料是以标准v4l2接口实现的。
你可以参考下面这个链接的7.4.4 yavta应用范例。
https://wiki.veye.cc/index.php/MV_Camera_on_Firfly_Boards/zh#yavta.E5.BA.94.E7.94.A8.E8.8C.83.E4.BE.8B

@veye_xumm 好的，非常感谢

@skysplitter It is recommended that you turn off the 3D denoise and wdr features if you have a relatively fast moving vehicle in your usage scenario. This is because these two features essentially use two frames of data to calculate.
2d denoise can be turned on.

@vitob said in NVidia Jetson Jetpack 6 support?:

In the meantime, can you help explain this question on tegra-camera.ko and v4l2-core/*.ko? Why they needs to be updated and where can I find the source code of them? Once updating them using the veye release .ko, will that affect other cameras (for example, I want to port/develop driver for another sensor myself)? Thanks.

These driver changes add support for RAW8 RAW10 RAW12 data types on the one hand, and externally triggered modes on the other.
Their code reference:
https://github.com/veyeimaging/nvidia_jetson_veye_bsp/tree/master/kernel_patch_4_mv/l4t-r36.3

Compile step by step reference:：
https://wiki.veye.cc/index.php/VEYE_CS_Camera_source_for_Jetson

Did u solve it ???
Iam using jetson nano B01 Devkit
I have exact problem like u :
1b047cd6-2fcf-43d5-a62e-ded2c5ab38de-image.png

@lin 相机触发模式出图和流模式出图，对你的程序接收图像而言，没有区别啊！

@oleg
This link provides a reference for workarounds to this problem.
Camera menu appears on VEYE-MIPI-IMX327S

However, I'm curious why this issue occurs so frequently on your end. Could you please measure the SCL level using an oscilloscope? When the VEYE module is not configured, SCL should always remain high. If there are frequent and continuous level changes, it indicates that the system is operating on the I2C bus.

430b65cc-ea10-47f9-ae2a-42c02f3119eb-bddd9a7161c7e66c0648f1da3766162.png

@carrot said in Can't select 25Hz framerate on MIPI IMX462:

Please try this:

sudo ./veye_mipi_i2c.sh -w -f videoformat -p1 PAL -b 9 gst-launch-1.0 nvv4l2camerasrc device=/dev/video0 ! "video/x-raw(memory:NVMM),format=(string)UYVY,width=(int)1920,height=(int)1080" ! nvvidconv ! "video/x-raw(memory:NVMM),format=(string)I420" ! fpsdisplaysink video-sink=fakesink -v

@veye_xumm 请问FPGA和RK3588直连，没有I2C，怎么在设备树里添加相机？相机驱动又该怎样处理？