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

@Jiangzb said:

问有适配RK3588-Linux6.1的AR0234CS驱动（裸摄像头）？

不好意思，没有。

@lpcq2000 这个不支持输出lvds信号。J1作为我们模组内部的信号，不对外公布其信号定义。

@alex_ai Sure, I'll keep an eye on this issue going forward. Thanks for your feedback.

@alex_ai
For your use case, I'd suggest giving it a try — reduce the denoise2d and denoise3d values, or even set them to 0. At the same time, you can also try lowering the sharpen value.

@alex_ai

I'd like to first confirm your firmware version with you. As shown below, everything is working fine on my end.

pi@raspberrypi:~/gx_product_tool $ ./gx_mipi_i2c.sh -r snsreg 0x3070
Read Sensor Reg 0x3070, val=0x0 
pi@raspberrypi:~/gx_product_tool $ ./gx_mipi_i2c.sh -r snsreg 0x3071
Read Sensor Reg 0x3071, val=0x0 

pi@raspberrypi:~/gx_product_tool $ ./gx_mipi_i2c.sh -r version
Read version is C 01.32 and L 01.19

Regarding the image quality during IR-cut switching, may I ask whether you are using the same IR-cut filter for both the IMX662 and the IMX462? Also, could you share some sample images with me?

@alex_ai
I would recommend using the exptime and curgain functions first to check the current performance of the camera module. If you are familiar with the sensor registers, you can verify the sensor's working status by reading registers 0x3070 and 0x3071.

@robot 有这个可能，我们很久前有一个CS-MIPI-IMX307，在某些板子上有类似的问题。

@alex_ai

We recently updated the ISP tuning. Please give it a try.

https://wiki.veye.cc/index.php/GX-MIPI-IMX662_Version_Log

@robot 好的。

@robot
其实我比较建议你不用纠结cssc132这款，这个型号现在已经是按单生产状态，随时会停产。既然你们目标使用MV-MIPI-SCC130M，就应该直接用这款去调。
这两个型号的方案完全不同，从MIPI信号上来讲,到实际第三方板子的使用经验上来说,在orin平台上的连通表现也会不一样。