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

@sheko It looks like nothing is abnormal. You haven’t installed a lens, right?

@sheko

 cd veye_viewer
    chmod +x ./*
	chmod 755 ./config/*.sh
    ./start_veye_viewer.sh

@sheko
Hi,
It looks like you downloaded the source code, but didn’t compile it. You can download the precompiled binary from the link below and run it directly.
https://github.com/veyeimaging/veye_viewer/releases/download/v1.1.4_rpi/veye_viewer_RaspberryPi_bin.zip

@sheko

You have successfully loaded the driver and detected the camera. Please refer to the instructions for the veye_viewer client software in the previous link to directly preview the images:
https://wiki.veye.cc/index.php/Mv_series_camera_appnotes_4_rpi#veye_viewer

@sheko
https://wiki.veye.cc/index.php/Raspberry_Pi_Application_Note_Index

part1.2

@sheko
The RAW-MIPI-SC132M module requires the mvcam driver, not cssc132.

@xlwvu7mx You are welcome.

@xlwvu7mx
The driver has been uploaded to GitHub, please check.

@d_101 Sorry for the late reply. Based on the current situation, I can only suspect a hardware issue that is causing the I2C path to be unavailable. This could be a problem with your mainboard or with the camera itself. Please return the camera to us, and we will perform testing and inspection.

@ffgemanof
The veye_viewer client currently does not support the mono10 and mono12 formats. If you need to use these formats, please configure the data format using mv_mipi_i2c_new.sh, and then acquire the data using v4l2-ctl or the V4L2 API.