@joe The RAW-MIPI-AR0234M is a MONO camera that has no color information and therefore does not support the UYVY data format. Please refer to this link below:
https://wiki.veye.cc/index.php/Mv_series_camera_appnotes_4_jetson#Configuring_global_variables

@aike 我们对接rk平台的经验中，只有一个厂家的板子遇到了给你这个完全一样的问题，就是用上次帖子中的方法解决的。该问题原因是此板厂提供的linux内核，调用veyecam2m_enum_frame_sizes时没有正确的传入fse->code参数，导致参数验证失败。

如果你这个方法解决不了问题，建议打开驱动中的DEBUG_PRINTK宏定义，查找一下哪个函数返回报错了。
如果只是打开这个宏定义不够，需要你手动在这些函数返回错误的地方增加打印信息，进行查找报错处。

@mv

For third-party carrier boards on the Orin Nano or Orin NX platform, we have indeed encountered issues with MIPI signal transmission quality. There isn't a good solution at the moment, so we recommend switching to an official NVIDIA board.

@paul-chang
这个只是一个提示信息，不影响驱动加载和后续测试的。
3f3fb167-a8b9-4a18-b05f-ced9201766d0-image.png
你可以看看有没有生成/dev/video0,如果没有，看看dtb是不是用对了。

@jgg You are welcome, will improve the wiki doc.

线下沟通，已解决。
解决方案是，在取图之前，通过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驱动层中。造成参数的错乱。

@veye_xumm Thank you for the quick assistance

@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