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

@alex_ai I used firmware version 1.14 for comparison and did not observe any significant noise changes in gamma mode 1 compared to other modes. Could you provide your specific usage parameters and environment?

@alex_ai Thank you for your feedback; we will look into this issue.

@ouyangxin 你好，你理解的没错，但是我们现在已经取消了对sda模式的支持，所以这上面的讨论已经没有意义了。

@zoldaten looking forward to your good news.

@zoldaten
In the source code of veyecam2m.c, please comment out this function.

Additionally, since you are using the RAW-MIPI-SC132M camera, you only need the mvcam driver and its corresponding dtb.

@alex_ai OK, the GX series and the VEYE series use completely different ISP solutions, so their parameters do not correspond one-to-one. I look forward to your test results.

@zoldaten
As long as you follow the steps and place our driver and DTS files into the Orange Pi source tree, then compile the image according to the official Orange Pi instructions and flash this image onto the board, the VEYE camera driver should appear correctly.

Essentially, this operation just adds the driver to the original standard Orange Pi system. No additional steps are required after flashing the image. I suspect that you may not have fully applied the modifications in all the necessary parts of the source code.

@zoldaten

@zoldaten said in OrangePi cm5-tablet RAW-MIPI-SC132M:

i burned SD with your image provided and there veye presented. what`s the difference ?

Sorry, I misunderstood you earlier. I thought you meant that following the steps to compile wasn't working at all. So, now that you've successfully compiled it, the veyecamera has appeared, correct?

What you should do now is modify the source code of the DTS. For different MIPI interfaces, use different dtsi configurations to set it up for the specific camera or sensor model you want.

@sheko Sorry, I just got back from the Chinese New Year holiday. Regarding using the RAW-MIPI-SC132M on the Raspberry Pi 5, I suggest you primarily refer to this document. It covers driver installation, how to use the V4L2 mode, and methods for previewing using OpenCV.
https://wiki.veye.cc/index.php/Mv_series_camera_appnotes_4_rpi

@zoldaten I noticed you placed the compiled image onto the SD card. This is likely incorrect. You should refer to the official Orange Pi documentation and flash the compiled image to the eMMC storage that comes with the Orange Pi CM5 core board.

Additionally, you might wonder why we compile the camera's dtsi directly into the main dtb instead of building it separately as an overlay. This approach follows the practice recommended by the Orange Pi manufacturer.