@nkos Apologies for the delay. I've just returned from the National Day holiday and will follow up on this matter as soon as possible.

@lubertroft
hi,
http://wiki.veye.cc/index.php/CS-MIPI-SC132_version_log
yuyv is supported in this version .

Because it is CS series, of course cs_mipi_i2c.sh is the corresponding script.
http://wiki.veye.cc/index.php/VEYE-MIPI-290/327_i2c/#yuvseq

@fancong
请参考：
https://github.com/veyeimaging/nvidia_jetson_veye_bsp/releases/tag/v1.29

@etale_cohomology

1. If your IMX287 is running in stream mode, please use the upgrade package from the following link for the upgrade：
   https://www.mediafire.com/file/d4yjibcjp1hw8z8/MV-MIPI-IMX287M_C1.37_L2.04_20240306_beta_upgrade.bin/file
2. The camera will generate its own strobe synchronization signal. I suggest using this signal to drive your LED instead of using the Raspberry Pi's IO. For more details on the principle, please refer to the following link:
   https://wiki.veye.cc/index.php/Mv_mipi_camera_manual#Strobe
3. On the ADP-MV1 board, the J3-5 pin will output the strobe signal by default.
   https://wiki.veye.cc/index.php/ADP-MV1_Adapter_Board_Data_Sheet/zh

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

@esjeeybi
About how to compile our drivers on rpi:
http://wiki.veye.cc/index.php/V4L2_mode_for_Raspberry_Pi#Source_code_cross_compilation

You can get/set FPS, Gain, Brightness, Contrast via:
http://wiki.veye.cc/index.php/CS-MIPI-X_i2c

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

@etale_cohomology

@etale_cohomology said in IMX-287M: How to synchronize video frame capture with an LED?:

./mv_mipi_i2c.sh -r -f trgexp_delay -b 6
./mv_mipi_i2c.sh -r -f trginterval -b 6

In video streaming mode, these two parameters do not take effect. The camera will output the strobe control signal based on the actual exposure time, whether it is in manual exposure mode or automatic exposure mode.

@ess
Hi, thank you, it is indeed typo.
jetson supports trigger mode, which I have done research on and it has worked. The plan is to organize it and release it along with our new machine vision product line. Estimated 15 days or so.

@consti10

@consti10 said in Improve DE-coding on snapdragon devices:

turning off the HW decoder for h264 on android doesn't really make sense.
Maybe changing the poc type could fix this issue, too ?

I'm not sure about that.

1. When connected via USB (original cable) there can be artifacts (I suspect packet loss via usb or some driver bug)

You are right. This camera will have a probability of packet loss. The higher the cpu performance of the host, the less packet loss.
This problem is still being studied and solved.

2. POC type as described above.

@joe Of course.

@joe I noticed that JetPack 7.2 now supports the Orin series. We don't have immediate plans for this yet, but we will evaluate it and determine a timeline for development.

@lpcq2000
实在抱歉，最近网站升级，回复迟了。

$ ./mv_mipi_i2c_new.sh -w roi 0 0 720 240
w roi is 0,0,720,240 
$ ./mv_mipi_i2c_new.sh -r roi
r roi is 0,0,720,240 
$ ./mv_mipi_i2c_new.sh -r maxfps
r maxfps @ current setting is 1088.00 fps

设置720*240的话，帧率可以打到1088fps。

@xLWvU7mX As planned, the interface of our redesigned camera module will be fully compatible with our current MV series products. You can check its pinout from this link: https://wiki.veye.cc/index.php?title=MV-MIPI-GMAX4002M_Data_Sheet.
Based on this, our ADP-MV1-V2 adapter board will be fully compatible and will convert the signals of the new GX-MIPI-IMX662 to match the legacy version. You can refer to the interface definition of the ADP-MV1-V2 here: https://wiki.veye.cc/index.php?title=ADP-MV1-V2_Adapter_Board_Data_Sheet

@xLWvU7mX
Regarding your question, we have recently made some research progress that I'd like to share with you.

Concerning the signal robustness of MIPI CSI-2, we are planning a major board revision for the GX-MIPI-IMX662 in the near future. We will be adding a MIPI equalizer chip to it. We've already tested this addition, and it will significantly optimize and improve the transmission adaptability and robustness of the MIPI CSI-2 signals.

Additionally, during this board revision, we will also update the PCB dimensions to a 29x29mm two-board structure, which is identical to our MV series cameras. This redesign is expected to be completed within two months. Meanwhile, we will soon release a firmware update to optimize and upgrade the ISP image quality.

Additionally, during this board revision, we will also update the PCB dimensions to a 29x29mm two-board structure, which is identical to our MV series cameras. This redesign is expected to be completed within two months. Meanwhile, we will soon release a firmware update to optimize and upgrade the ISP image quality.

@jossen 不客气。

@jossen
这个版本，由于硬件设计的限制，下面是极限值。

另外，这个型号，需要用fps来进行配置，不要用fps_ex功能。
fps命令，支持到0.01的精度。
因此，你使用

sudo ./mv_mipi_i2c_new.sh -w fps 0.12 -b 2

进行参数配置。

@nian 不好意思，我们暂时没有计划做raw14bit输出的camera模组。

@sanlu

@zoldaten You can ignore the warning shown in your screenshot. However, your probe information is incomplete; it seems that the mvcam probe function has not been triggered.