@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 You are welcome.

@alex_ai

1. Roll back yesterday's driver update. For Raspberry Pi, keep using the MIPI clock discontinuous mode.
2. Upgrade the camera firmware. Please refer to this link: https://wiki.veye.cc/index.php/GX_camera_firmware_update_manual and update the camera to version GXC-MIPI-IMX662_C1.34_L2.19_20261014_upgrade.bin.

This should resolve your issue.

It appears that the piOS update changed the MIPI signal timing requirements on the Raspberry Pi 5 (which uses the RP1 chip to receive the MIPI signal).

@alex_ai
Register 0x44c should indeed be configured to 1.
This is quite strange, as the image preview works perfectly on our end with the exact same configuration.

1. Are you viewing the image via remote desktop?
2. Under the same conditions, does setting register 0x44c to 0 produce an image (with jitter), while setting it to 1 results in no image at all?

@alex_ai
No need to set it up manually anymore! We've updated the driver, so just grab the latest code, compile it, and install it.
https://github.com/veyeimaging/raspberrypi_v4l2

@alex_ai

@alex_ai said:

./gx_mipi_i2c.sh -r nondiscontinuousmode -b 6

use -w, not -r.
-w means write.

@alex_ai
Good news — I've found a solution to the issue. The camera's MIPI signal needs to be switched to continuous clock (non-discontinuous) mode. You can do this by running the following command: https://wiki.veye.cc/index.php/Gx_mipi_i2c.sh_user_guide#nondiscontinuousmode — or alternatively by setting register 0x44c in veye_viewer.
After making the change, please use the paramsave command to save the settings to the camera.

@alex_ai Sorry, I misunderstood your setup. I've verified this on other boards, including Jetson, and it works fine. I now believe the issue is caused by image scaling in the veye_viewer client software on the latest Raspberry Pi OS. We'll fix this as soon as possible — please bear with us.

@alex_ai

I believe the issue does not lie with the camera output, but rather with the compression process after you receive the data. Please verify this using the client software available at the link below. The veye_viewer client is designed to preview raw grey format data directly, without applying any compression.

https://github.com/veyeimaging/veye_viewer

@alex_ai Apologies for the delayed response. I would like to know if there is any vibration or shake in your actual application scenario. Could you please try turning off the 3D Noise Reduction (3DNR) to see if there is any improvement?

@habreu
If you are using the RAW-MIPI-IMX462M camera module, the corresponding script is mv_mipi_i2c_new.sh. Please note that many parameters can only be modified when frame capture is stopped. For details, please refer to the following link:
https://wiki.veye.cc/index.php/Mv_mipi_i2c.sh_user_guide