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

@robot 我们就是用的nvidia orin nano的官方开发板，跟你图中差不多。
不过我们没有发不过【原厂系统】。 对于jetpack6.2.2，我们有发布dtbo和一套ko文件。只要把这些替换到nvidia原系统即可。
对应步骤是这个文章的：
7.4.3和7.5.3两步，然后按照8.1和8.2进行检测一下。
https://wiki.veye.cc/index.php?title=How_to_upgrade_the_Jetson_system_to_support_VEYE_cameras/zh

完成之后重新上电，可以执行 sudo dmesg |grep sc132，把输出结果给我看看。

@robot 确实是CS-MIPI-SC32，这个型号挺老的了。你回头就按照这个步骤搞一下看看先。

@robot 我有点怀疑你使用的相机型号是不是对应cssc132的驱动。可否拍个照片我看一下？

@golden0514 好的，2464分辨率应该是内存对齐的问题。并不是传输错误的问题。树莓派5新版本的piOS好像是修改了内存对齐的逻辑：

紧密排列图片大小
Buffersize= ALIGN_UP（width*bit_depth/8,32）*ALIGN_UP(height,16)

行buffersize需要是32字节的整数倍；列buffersize是16字节的整数倍。

举例来说，3088*2064@8bit的图像大小是6406656; 3088*2064@10bit的图像大小是7991808；3088*2064@12bit 的图像大小是9576960。

可能修改一下pixel_layer_convert 工具就可以了。

暂时的话，建议你使用width是32的整数倍的roi分辨率试一下。

@golden0514

不好意思，隔了这么久才给您回复。这几天咱们尽快解决。
我这边使用如下手段进行抓图，并且测试，没有能重现您的问题。请您在您的树莓派上重复测试一下试试。

1. 配置分辨率并抓图100帧：

$ ./media_setting_rpi5.sh mvcam -fmt RAW12 -x 0 -y 0 -w 2432 -h 2056 -c 0
$ v4l2-ctl -d /dev/video0 --set-fmt-video=width=2432,height=2056,pixelformat='Y12P' --stream-mmap --stream-count=100 --stream-to="y12-2432x2056.raw" 

2. 从Y12P转为y12

./pixel_layer_convert  -I Y12P -i y12-2432x2056.raw -o y12-2432x2056_0001_new.raw -w 2432

然后使用YUV Player Deluxe进行播放，是正常显示的。
上面使用的脚本和转换工具都在这个文章里面：
https://wiki.veye.cc/index.php?title=Mv_series_camera_appnotes_4_rpi/zh

@golden0514 不好意思，再多问一句，你用的roi参数以及fps参数是多少？

@golden0514 另外，请问你使用的ffc cable长度？能否拍一个硬件连接图的照片我看看。

raw8格式，使用我们veye_viewer客户端，是否有图像错误的问题？

@golden0514 said:

用QT V4L2也可以看到这种跳动，只不过是近似2×2排布。

我这边可以用这种方式来预览，尝试重现？

@habreu Sorry for the late reply. This issue is usually caused by the FFC cable being inserted in the wrong direction. Please simply make sure that the contact surface of the FFC cable aligns correctly with the contact surface of the connector.

@golden0514
不好意思，看到有点晚了。
请确认一下相机的版本号，可以通过mv_mipi_i2c_new.sh进行读取。

@123456123 said:

X Developer Kit 上用 VEYE MV-MIPI-IMX264M。系统是 R35.5，内核 5.10.192-tegra。把 FDT 切到 VEYE 的 dtb，并替换成 VEYE patched Image 后，重启就会黑屏，但 SSH 还能连上。想请教一下怎么解决。

Jetpack5.1.3,L4T版本r35.5

说实话这个版本的jetpack有点老了。但是我们应该是做过验证的。

请将你的extlinux.conf文件的内容贴出来。
另外：
https://wiki.veye.cc/index.php?title=How_to_upgrade_the_Jetson_system_to_support_VEYE_cameras/zh#Image和DTB更新成功了吗？
第8节的内容，执行一下，把结果发出来，我看看。