Posts made by veye_xumm

@stiwana

1. The MV-MIPI-GMAX4002M model was missing on this page and has now been added. Both Jetpack 5.1 and 6.2 are supported. However, we currently only provide the 4-lane mode DTB for Orin NX and Orin Nano under JP6.2 mode, as only these two boards have official baseboards that expose the 4-lane interface.
3. You're right. Just place the order using that link. We will ship ADP-MV1-V2.
4. For Jetson Xavier NX, since the official baseboard only exposes 2 lanes, the DTB in our provided driver remains configured for 2-lane mode, which limits the maximum frame rate.
   As for Orin NX, there is no such restriction. You can refer to the 4 How to Use 4-Lane Modesection to enable 4-lane mode.
5. yes.
6. The MV series products feature ISP (Image Signal Processor) capabilities, including typical functions such as auto-exposure, LUT (Look-Up Table), and more.

@israel_bolo Actually, for the development of new projects, I would recommend using the V4L2 mode, which is the material from the link below.
https://wiki.veye.cc/index.php/V4L2_mode_for_Raspberry_Pi

@israel_bolo

May I ask which version of piOS you are currently using? The libdmipicam mode is only suitable for the 32-bit legacy mode of piOS.

@dragos You are welcome.

@dragos
I think the MIPI CSI interface on this board only exposes 2 lanes and uses a 15-pin connector.
Could you check your board to see if that's the case?

@dragos May I ask if the board you're using is an official NVIDIA development board or a compatible third-party board?

@linoooooo 你好，我们的相机内部isp流程是没有整帧缓存的，相机本身引入的delay是毫秒之内。
我觉得你这个延时主要是v4l2取图缓存和显示缓存的缘故。不过说实话SDL库我们不太懂，怎样优化需要您自己研究一下。
至于相机采集后，您这边程序直接导入算法的话，延迟肯定要比这种测量方法小的多。

@israel_bolo
I see some warnings, but no errors. could you please continue and see if it compiles?

@otca
The camera is now successfully probed, which confirms that both the I2C and the enable pin are functioning correctly.
The current issue indicates that the I2C control channel is working, but the MIPI CSI data channel is not. Please verify whether the MIPI CSI interface pin assignment on this carrier board matches that of the official Orin NX development board.
The Device Tree Source (DTS) should be adjusted accordingly to match the carrier board.

@stiwana Sorry, we do have this in mind, but no actual plans or projected time of completion at this time.

@阿坎德 你好，有进一步的结果吗？

@nkos
Please enter this directory and run ./make.sh.
mv_tools_rpi/sources

@阿坎德 看现象感觉是内存泄漏。这个demo现在基本用途上是客户做一下出图验证和聚焦。所以只是个简单的例子。回头我们会安排时间跟进一下。

@阿坎德 相机本身支持最大的分辨率是2464（H）× 2056（V），所以你需要修改一下你命令行中width这个参数为2464.

@阿坎德
预览的话，我们验证过的是这个脚本：
https://github.com/veyeimaging/rk35xx_veye_bsp/tree/main/samples/opencv/mv camera
v4l2dev_2_opencv_show_grey.py

@阿坎德 模糊的原因是镜头聚焦不清晰，应该拧动镜头进行聚焦。
软件方面已经正常了。

@阿坎德
看起来是内存行对齐的问题。
图像宽 2464，向上以256字节进行对齐，是2560.
你可以按照2560*2056这个分辨率打开文件，试一下。

@megan
First of all, please go to the following link to update the driver of mvcam. The latest driver will set the lane number in the camera according to the configuration of the DTS.

https://github.com/veyeimaging/rk35xx_veye_bsp/tree/main/linux/drivers/kernel_v5.10

Secondly, the DTS needs to be configured according to your RK3588 board, and I can't do it directly for you. You can make analogies and modifications by referring to the DTS of the camera originally supported by your board.

@megan

I see that you have ported the driver to the Radxa CM5 board. Your I2C is already working, otherwise the camera wouldn't be recognized correctly. Another thing to check is that the MIPI DPHY and CSI interfaces are properly configured in the DTS.

With the correct DTS configuration, typically on the RK3588 platform, a script for capturing images would look something like this:

export I2C_BUS=7
export WIDTH=1920

export HEIGHT=1200

export FPS=50

v4l2-ctl -d /dev/v4l-subdev2 --set-ctrl roi_x=0

v4l2-ctl -d /dev/v4l-subdev2 --set-ctrl roi_y=0

media-ctl -d /dev/media0 --set-v4l2 '"m00_b_mvcam '"$I2C_BUS"'-003b":0[fmt:Y8_1X8/'"$WIDTH"'x'"$HEIGHT"'@1/'"$FPS"']'

v4l2-ctl --set-ctrl frame_rate=$FPS  -d /dev/v4l-subdev2

v4l2-ctl -d /dev/video0 --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=GREY --stream-mmap --stream-count=-1 --stream-to=/dev/null