@macdaddyfpv

I was thinking that since you took it from a dual board down to a single board that you may be able to reduce the board size and break it out into 2 again to fit everything.

Yes, we have the ability. However, the decision to make a new version of model is more of a commercial consideration. We are now more focused on developing new sensor and new products.
I will seriously discuss your suggestion with my colleagues in the company.
Thank you for your approval and feedback.

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

@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

@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

@jdx-jdx
是的。probe成功才会生成video节点。

@tuzi said in veye imx327:

nvoverlaysink

可以给nvoverlaysink加个参数，控制一下显示区域。或者换一个其他sink试一下。

我暂时不能直接提供答案，你可以参考英伟达这个部分的文档略作研究。
https://docs.nvidia.com/jetson/archives/l4t-archived/l4t-325/#page/Tegra Linux Driver Package Development Guide/multimedia.html#

@jdx-jdx
错了。FDT一行要指明到文件名，不是到目录。

@jdx-jdx
请确认你用了正确的dtb文件，再确认FDT那一行正确指明了对应文件路径。

@g-towboat
Our solutions are 953 and 954 and the source code of the driver is provided. You can refer to this source code to support 964.
Now fpdlink products have been suspended due to chip out of stock, sorry.

@stiwana

@stiwana said in Low light MIPI camera supporting 720p60:

Is it possible to output HDR imagery over the MIPI interface (IMX327S/IMX385/IMX462) or do we need to do it inside our own fpga?

These 2 modules support DOL HDR inside. You can enable this function via shell script.

Is the I2C command set open, such that we could do the camera module configuration from our baremetal application?

Yes, the I2C toolkit is open source.

Can you confirm my understanding that in this case our FPGA will be talking to the onboard ISP chip on your camera board over I2C, and not directly to the camera.

YES. Directly to ISP and my FPGA, not to sensor.

Roughly how much is the added latency due to your onboard ISP on the boards?

60-80ms I think. Because DOL WDR and 3D denoise functions.

The auto exposure and white balance will be handled by the onboard ISP, and will not need to be handled by our FPGA, correct?

Yes.

@stiwana
Hi，Thank you for your recognition, VEYE series does not support 720p@60fps, sorry.

@dan_lionking

@dan_lionking said in Camera menu appears on VEYE-MIPI-IMX327S:

./i2c_write $I2C_DEV $I2C_ADDR 0x07 0xFF
Camera OSD will be removed?

This command will disable the access function to the isp module. This step can be executed after the veye_mipi_i2c.sh operation. It should then solve your problem.

Will camera control by i2c be restored after turning the camera power on and off?

Yes

@tuzi

1. 请检查一下排线有没有插歪了？

2. 运行dmesg命令，看一下最下面一部分，报什么错误？

@dan_lionking
Hi,
The data on the I2C bus causes a false trigger.
I guess you use Raspberry Pi and an MIPI DSI-2 screen， right？

http://wiki.veye.cc/index.php/RaspberryPI_I2C_confilct_problem

Please refer to this.