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
@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.
@ess
Our company discussed and decided to bring this forward. It is expected that the version will be available to you within 10 days.
@lingchuang
fpdlink现在提供的是legacy mode的应用。
参考这个说明，了解legacy mode。
http://wiki.veye.cc/index.php/Raspberry_Pi_Application_Note_Index/zh
参考这个文章前半部分，先配置一下pios。
http://wiki.veye.cc/index.php/Raspberry_Pi_Application_Note_Index/zh
@lingchuang
0/1的意思是输入0，或者1，根据你的fpdlink线接到哪个端口来确定。
另外，现在树莓派的i2c bus一般情况是10，你可能需要额外加一个-b 10参数。
@pimat
In fact isp has a much greater impact on image quality than is generally believed.But I'm not familiar with libcamera, so I can't give you an in-depth explanation.
The imx462 has better NIR band sensitivity than the imx327, and the price is about the same as the imx327, so I recommend the imx462.
Newly purchased products will be the latest version.
@mk
Hi，
Sorry, but the usb series has very few configurable options. To the point that it is basically unconfigurable, except for resolution and frame rate.
@suchb b 你好，我们的确在进行这样一项计划。 使用cs系列方案，做imx662，目标室做到50-60fps帧率，优秀的dol宽动态。
@rob77
I see no problem with your operation.
The dtb defines the peripherals of the core and base boards and needs to be consistent with the actual core and base boards.
Is it possible that your jetson nano is not the standard Nvidia b01 version of the dev kit?
@rob77
I think you should use JetPack_4.6.1_Linux_JETSON_NANO_TARGETS dts,instead of 4.6 version.
I'm not sure that's the root cause, but that's all I can think of right now.
