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

@jambojettt
Normally, the PiOS you installed comes with kernel-headers. Could you tell me which image link you used?
Can you help run this script and send me the results?

uname -a
ls /usr/lib/modules/
ls /usr/lib/modules/$(uname -r)

@jambojettt said in Can't get v4l2 to work, rasbperry pi 4b, rpi os x64, 6.12.57-v8+:

@veye_xumm yes, it updated to 6.12.57, but this problem also was in 6.12.47 that it was updated from.
How do I get the headers?

My Raspberry Pi comes with headers by default. You might want to reinstall piOS? We've already released the 6.12.47 ko file on GitHub.

@jambojettt

@jambojettt
Sorry for the slightly delayed reply. Normally, piOS comes with kernel-headers pre-installed. For example, here is a screenshot of my current system:

I suspect that you might have updated to a newer minor version of piOS, which caused this issue. The current major version of piOS should be 6.12.47.

@nkos Cheers!

@nkos
Below is a tutorial on using this camera module on Radxa boards.
https://wiki.veye.cc/index.php/MV_Camera_on_Radxa_Boards

Unlike the Raspberry Pi platform, on RK platforms, some preparatory work is required to use our module, which involves configuring the appropriate image parameters using media-ctl.
However, based on the information you provided, it seems you have already set it up correctly.

Once this preparation is complete, the process of capturing images is the same as on the Raspberry Pi.

If you encounter any issues, you can refer to the code example at:
https://wiki.veye.cc/index.php/MV_Camera_on_Radxa_Boards#Example_of_yavta

Additionally, we have an open-source client software available for your use and reference.

https://github.com/veyeimaging/veye_viewer

@jambojettt
Normally, after you install the kernel headers using the command sudo apt install raspberrypi-kernel-headers, you should be able to compile successfully.
May I ask — after performing this step, what error do you see during compilation?

@jambojettt According to the dmesg information, you have successfully installed the veyecam2m driver. However, the camera was not detected. What model of camera are you using?

@brunosaisi
For configuring this camera via I2C, the process is not done through v4l2-ctl but directly using a script. Please note the following regarding this script:

1. If you are using the v4l2 driver mode, camera_i2c_config is not required.
2. When running ./veye_mipi_i2c.sh, make sure to specify the I2C bus you are using with the -b parameter.

Below is an explanation regarding the I2C bus.
https://wiki.veye.cc/index.php/I2c_bus_number_and_video_node
For long exposure usage, you may need to configure the lowlight function or the new_mshutter function. Please refer to the corresponding section in the link below.
https://wiki.veye.cc/index.php/VEYE-MIPI-290/327_i2c/#new_mshutter

@john
We compared the baseboards of the J401 and J401B and found no differences. Regarding the earlier issue with the J401, we suspect that the USB hub chip, which is mounted on the same I2C bus as the camera, was intercepting responses for the I2C address 0x3b. This aligns with your hypothesis.

Could you visually inspect the J401B and check if there are any version or sub-model changes in the USB hub chip compared to the J401?

Regarding your intention to test the response issue at address 0x22, you do not need to recompile the device tree blob (dtb). You can directly use the command i2cdetect -y -r i2cnum to perform the test.