I am a software engineer of the VEYE team and will try my best to help you.
I was thinking that since you took it from a dual board down to a single board that you may be able to reduce the board size and break it out into 2 again to fit everything.
Yes, we have the ability. However, the decision to make a new version of model is more of a commercial consideration. We are now more focused on developing new sensor and new products.
I will seriously discuss your suggestion with my colleagues in the company.
Thank you for your approval and feedback.
@radiohound As far as I know, sony's datasheet is only open to corporate customers who have signed an NDA.
@tokabe
Hi,
On i.MX8m Platform, our roadmap is based on SOM board. For now, we have finished MYIR i.MX8m board and AVNET Maaxboard(mini) board.
http://wiki.veye.cc/index.php/NXP_i.MX_Application_Note_Index
The coral.ai board from google is in progress.
So the linux version we use now depends on the system version that comes with the SOM board.
We have a V5.y version driver on raspiberry PI, maybe this will help you.
http://wiki.veye.cc/index.php/V4L2_mode_for_Raspberry_Pi
Of course, we will transplant all product drivers, including CS-MIP-IMX307, to i.MX8m. This work is also in progress.
@desperex said in Please advise compatible mono camera:
About two or three years ago, we tried to connect VEYE series products to rk3399, but at that time there were some problems with its BSP.
Recently we restarted the development plan for rockchip chips.
The first thing we are doing is to connect VEYE series to firefly's RK3566 board. Now the development has been completed and we have made http://wiki.veye.cc/index.php/ADP-Tfirefly. This board is already online for sale.
Next, we have to create the adapter board for MV series to ROC-RK3566/8-PC and develop it.
As for the two boards you mentioned, the rk3399 chip is too old and we have no plans for now.
Orange Pi 5, we have not studied it before. I will submit it to our R&D department.
@nimadibaj
0x3b
This camera has isp module, so you can't control the sensor directly. please refer to the following code.
http://wiki.veye.cc/index.php/VEYE-MIPI-290/327_i2c/
https://github.com/veyeimaging/raspberrypi/blob/master/i2c_cmd/bin/veye_mipi_i2c.sh
@otca
"You did the right thing.
The Jetpack 4.6.5 version of the kernel does not yet support the MV series cameras.
Please switch to Jetpack 4.6.4 for your operations.
@mca312 said in IMX287 FPS:
The FPS is listed at 319 but the sensor supports 523. Can I set the ADC bit to 8 to achieve this? 319 is for 12 bit.
We have achieved a frame rate of 720×544 @ 530fps RAW8 in our new firmware version.
https://wiki.veye.cc/index.php/MV-MIPI-IMX287M_Data_Sheet
@mca312 said in IMX287 FPS:
I would also like to mount a CS lens or an M12 lens. What is the dimension needed for the lens mount?
Feel free to provide a note when placing your order, and we'd be happy to gift you an M12 holder.
Regarding CS lenses, unfortunately, they are not supported at the moment. We have a C-MOUNT01 which is compatible with C-mount lenses. You will need to purchase it separately.
@nimadibaj said in VEYE-IMX462 Video Format:
1_What is the actual video format?
UYVY
@nimadibaj said in VEYE-IMX462 Video Format:
3_What is the Line Rate of camera?
594Mbps
@nimadibaj said in VEYE-IMX462 Video Format:
2_What is the pixel-per-clock rate?
Should be 594Mbps *2 , Because we have 2lans.
@nimadibaj said in VEYE-IMX462 Video Format:
4_Is there a sample code for XILINX FPGA to receive VEYE-MIPI-IMX462 video output?
Sorry, we don't have the corresponding demos right now.
@stiwana
https://wiki.veye.cc/index.php/Mv_series_camera_appnotes_4_jetson
For specific information, please refer to the link above. We provide a veye_viewer client for customers to initially get started and verify usage.
We haven't done extensive debugging on GStreamer yet. As for OpenCV, there are examples provided in the article above. Regarding the latency issue: although the camera itself has negligible delay, each image entering the Jetson system will experience some latency due to the V4L2 buffer, format conversion, and preview processes—all of which involve memory buffering queues.
The most fundamental solution is to develop your own program tailored to your product's specific needs, allowing flexible management of buffers. Additionally, note that the V4L2 buffer containing the camera images after they enter the Jetson system includes timestamps. It is recommended that you use these timestamps.
Regarding the supply of this product, we will maintain long-term availability unless the chip is discontinued. We will keep a regular inventory sufficient to meet retail demand. For bulk orders of several hundred units or more, the production cycle is typically within one month.
@stiwana
I think the post on the forum might have misled you. In fact, the latency of the VEYE series (models starting with VEYE-) is relatively high.
The latency of the MV series, for instance MV-MIPI-GAMX4002M, is very low (below 1ms) because our ISP pipeline does not use frame buffering and only has a small amount of line buffering.
@mparem
https://github.com/veyeimaging/rk35xx_orangepi/releases/tag/v1.2_mvcam_tablet_cm5
Please try this image file on cm5-tablet.
@barbanevosa
The issue occurs because the camera sensor outputs a resolution of 3088 × 2064, but the receiving side (V4L2 buffers) aligns each line to a stride of 3136 bytes for memory alignment. When OpenCV is used directly with cv2.CAP_V4L2, it applies the width setting (3088) both to the sensor and to the buffer interpretation. Since the actual buffer has padding (3136 vs. 3088), OpenCV misinterprets the data layout, which results in visible image artifacts (stripes).
We recommend using a GStreamer pipeline to handle the stride and alignment internally, so that OpenCV receives a clean image with the correct resolution.
@flaty
DMA BUFF模式的支持，并不是相机驱动所决定的，而是rockchip的rkcif这个驱动决定的。 数据的传递顺序是：camera-->mipi rx--->rkcif。
我查阅了一些资料，显示5.10版本的rk3588的驱动好像是比较明确不支持DMA BUFF模式的。这也就限制了你camera到其他外设驱动的buffer零拷贝传递的能力。 不过如果你只是想零拷贝从camera驱动中拿到数据，进入算法的话，V4L2_MEMORY_MMAP模式应该就可以支持。
rkcif驱动在kernel6以上版本是否支持了DMA buffer模式，没有确切的说法。
@flaty 我的理解中，相机驱动并不涉及到BUFF模式的限制。实际上数据的收取和防止到内存是rk的mipi接收单元的驱动所决定的。
下面是网上插到的信息，希望能有帮助。
从你贴的代码来看，报错 Failed to queue buffer: Invalid argument（EINVAL）通常意味着结构体成员设置有问题，或者驱动不支持 DMABUF 模式。结合你写的代码，我帮你逐条排查一下：
v4l2_buffer 初始化问题你这里写的是：
struct v4l2_buffer buf={0};
struct v4l2_plane planes[1]={0};
这是对的，但要注意 buf.length 必须和 planes 数组元素数量一致，并且 buf.m.planes 不能为空。
buf 关键字段设置你代码里：
buf.index = 0;
buf.type = V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE;
buf.memory = V4L2_MEMORY_DMABUF;
buf.length = 1;
buf.m.planes = planes;
buf.type 用 V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE 是对的（说明驱动是 multiplanar 类型）。 buf.memory 设置成 DMABUF 正确。
buf.index 不是 0 就行，它必须是你在 VIDIOC_REQBUFS 时分配的 buffer 数量里的一个合法索引。比如如果你 req.count = 4，那么只能用 0..3。planes[0].m.fd = frame_buffers[i].dmabuf_fd;
planes[0].length = buffer_size;
问题可能出在这里：
planes[0].m.fd：必须是 dma-buf 的有效 fd。planes[0].length：应该是该 plane 的大小，但 通常驱动并不依赖这个值。有些驱动要求设置 bytesused，即：planes[0].bytesused = buffer_size;
如果 bytesused 没设，驱动可能直接返回 EINVAL。
试着改成这样：
struct v4l2_buffer buf;
struct v4l2_plane planes[VIDEO_MAX_PLANES]; // 通常 >= 1
memset(&buf, 0, sizeof(buf));
memset(planes, 0, sizeof(planes));
buf.type = V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE;
buf.memory = V4L2_MEMORY_DMABUF;
buf.index = i; // 循环里的 buffer 索引
buf.length = 1; // plane 数量
buf.m.planes = planes;
planes[0].m.fd = frame_buffers[i].dmabuf_fd;
planes[0].length = buffer_size; // plane 总大小
planes[0].bytesused = buffer_size; // 必须加上
不是所有 V4L2 驱动都支持 V4L2_MEMORY_DMABUF。你可以用下面的方法确认：
v4l2-ctl -d /dev/video0 --querycap
如果 ioctl 里不支持 DMABUF，就算代码写对了也会 EINVAL。
有些驱动只支持 MMAP，那就得用 V4L2_MEMORY_MMAP。
建议：先在 QBUF 前打印出 buf 和 planes[0] 的值，确认 index、fd、bytesused 都合理。
@flaty 建议您参考一下yavta的源码。git clone https://github.com/veyeimaging/yavta.git
@jhaijun 不好意思我们这个论坛是只针对我们公司自己产品的。 sony 机芯的话确实没有搞过。
@joe Sorry for overlooking the information in the earliest post. I think the board in the link below is suitable, as it is compatible with the official nVidia development board.
https://www.alibaba.com/product-detail/Nvidia-jetson-orin-nano-development-board_1600993126148.html?spm=a2747.product_manager.0.0.61e871d2RIVAmD