I am a software engineer of the VEYE team and will try my best to help you.
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 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.
- 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.
- 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
@zjutony
http://wiki.veye.cc/index.php/CS-MIPI-SC132_Data_Sheet/zh
只有这几种模式。
试试这个
gst-launch-1.0 nvv4l2camerasrc ! "video/x-raw(memory:NVMM),format=(string)UYVY, width=(int)1280, height=(int)1080, framerate=(fraction)45/1" ! nvvidconv ! "video/x-raw(memory:NVMM),format=(string)I420" ! nvoverlaysink sync=false
@年华灬
这个模组启动比较慢，大约7-8秒，你进行sysreset之后需要等会儿才能正确读到。
会不会是i2c通信有问题，你检查检查排线插接情况，是否有接触不良？
可以循环使用
i2cdetect -y 10
查看是否有0x3b,有的话，说明摄像头的i2c还活着，在响应。
如果detect一会儿有，一会儿没有，一种可能，摄像头在不停重启。
可以尝试在detect到的时候发送sysreset
@年华灬
你的意思是，可以配置为1080p模式，无法配置为640*480是吗？
请读一下你的模组版本号我看看
@年华灬
CS-MIPI-IMX307并不是任意尺寸可设的，它只提供了三种分辨率模式。
http://wiki.veye.cc/index.php/CS-MIPI-IMX307_STARVIS_Module/zh
@dan_lionking
Can you provide me with your complete command? That way I can easily try to reproduce the problem on my end.
@年华灬
解决的方案：
读一下两个程序的代码，建议参考veye_raspivid的，它有一个spiltter，现在有没有用到的。
这个spiltter相当于是一个数据的分发器，用其空闲的port，去做拍照功能。
@年华灬
肯定会这样。
硬件只有一个摄像头，只有一个数据通道，两个进程不能同时去占据同一个资源。
@年华灬
因为bmp拍照是取得第一张，所以是0字节。
临时得一个方法是你连续拍两张取第二张。
我们会尽快解决此bug。