Categories

• Announcements

  Announcements and News

  13
  Topics
  20
  Posts

  

  @chjchoi
  We rarely maintain content in the news category anymore. The one you are referring to is here.

  http://wiki.veye.cc/index.php/VEYE_CS_Camera_for_Jetson_TX2#TX2_NX.28p3509-0000_carrier_board.29

• General Discussion

  General discussion about VEYE camera modules

  38
  Topics
  242
  Posts

  

  @izaak In fact, in the Video streaming mode, it is impossible to achieve an exposure time of 1 second. I conducted a test in the 2 - lane raw8 format, as follows:

  pi@raspberrypi:~/mvcamera/mv_tools_rpi $ ./mv_mipi_i2c_new.sh -w fps 0.01 w fps 0.01 pi@raspberrypi:~/mvcamera/mv_tools_rpi $ ./mv_mipi_i2c_new.sh -r fps r fps is 3.48 fps pi@raspberrypi:~/mvcamera/mv_tools_rpi $ ./mv_mipi_i2c_new.sh -w metime 1000000 w manual exp time is 1000000 us pi@raspberrypi:~/mvcamera/mv_tools_rpi $ ./mv_mipi_i2c_new.sh -r exptime r current exptime is 287129 us

  It can be achieved in Pulse Trigger Mode. However, due to the excessive accumulated dark current, the signal noise will be very high. I don't think it has practical value.

• Machine Vision camera
  24
  Topics
  256
  Posts

  

  @stiwana Sorry, we do have this in mind, but no actual plans or projected time of completion at this time.

• VEYE MIPI camera

  VEYE series MIPI CSI-2 camera modules

  290
  Topics
  2105
  Posts

  

  @linoooooo 你好，我们的相机内部isp流程是没有整帧缓存的，相机本身引入的delay是毫秒之内。
  我觉得你这个延时主要是v4l2取图缓存和显示缓存的缘故。不过说实话SDL库我们不太懂，怎样优化需要您自己研究一下。
  至于相机采集后，您这边程序直接导入算法的话，延迟肯定要比这种测量方法小的多。

• CS MIPI camera

  CS series MIPI CSI-2 camera modules

  140
  Topics
  1000
  Posts

  X

  @veye_xumm 是的 非阻塞缓存后写图，已经解决了。抓拍的图像基本模拟一次就有一张抓拍，因为闪一次时间是1ms 所以只抓到一张也是合理的。

• FPD LINK III Camera

  FPD LINK III Camera DevKit

  30
  Topics
  250
  Posts

  

  @kevin2008 生成video节点只能表明i2c通了。
  看你的截图，像是mipi接收部分的配置不对。

• USB camera

  CS series USB camera modules

  7
  Topics
  95
  Posts

  

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

• Raspberry Pi App Software
  46
  Topics
  361
  Posts

  

  @israel_bolo
  I see some warnings, but no errors. could you please continue and see if it compiles?

• Jetson App Software
  27
  Topics
  244
  Posts

  D

  Here are the dmesg logs from the 2-lane mode and 2-lane DTB, with the camera running in qv4l2:

  dragos@ubuntu:~$ sudo dmesg | tail -5 [ 845.656377] mvcam 10-003b: csi2_try format [ 845.656555] mvcam 10-003b: csi2_try format [ 845.656571] mvcam 10-003b: mvcam_csi2_get_fmt_idx_by_code success [ 845.740489] mvcam 10-003b: camera_common_mclk_enable: no device power rail [ 845.740746] mvcam 10-003b: camera_common_s_power: failed to enable mclk

  Here are the dmesg logs from the 4-lane mode and 2-lane DTB, with the camera running in qv4l2:

  dragos@ubuntu:~$ sudo dmesg | tail -30 [ 1140.858386] (NULL device *): vi_capture_control_message: NULL VI channel received [ 1140.858595] t194-nvcsi 13e10000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=2, csi_port=2 [ 1140.858815] (NULL device *): vi_capture_control_message: NULL VI channel received [ 1140.858988] t194-nvcsi 13e10000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 2 vc- 0 [ 1140.859692] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel [ 1143.417930] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms [ 1143.418162] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel [ 1143.418413] (NULL device *): vi_capture_control_message: NULL VI channel received [ 1143.418570] t194-nvcsi 13e10000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=2, csi_port=2 [ 1143.418788] (NULL device *): vi_capture_control_message: NULL VI channel received [ 1143.418967] t194-nvcsi 13e10000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 2 vc- 0 [ 1143.419528] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel [ 1143.449994] [RCE] ERROR: camera-ip/vi5/vi5.c:3893 [vi5_update_channel_match_data] "match configuration is already in use by by channel 34 cannot set channel match configuration" [ 1143.450010] [RCE] ERROR: services/capture/capture-scheduler.c:3024 [capture_scheduler_thread] "Error processing event 0x100003" [ 1145.977984] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms [ 1145.978230] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel [ 1145.978497] (NULL device *): vi_capture_control_message: NULL VI channel received [ 1145.978671] t194-nvcsi 13e10000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=2, csi_port=2 [ 1145.978889] (NULL device *): vi_capture_control_message: NULL VI channel received [ 1145.979052] t194-nvcsi 13e10000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 2 vc- 0 [ 1145.979836] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel [ 1148.538029] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms [ 1148.538287] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel [ 1148.538522] (NULL device *): vi_capture_control_message: NULL VI channel received [ 1148.538736] t194-nvcsi 13e10000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=2, csi_port=2 [ 1148.538965] (NULL device *): vi_capture_control_message: NULL VI channel received [ 1148.539135] t194-nvcsi 13e10000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 2 vc- 0 [ 1148.539784] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel [ 1148.550021] [RCE] ERROR: camera-ip/vi5/vi5.c:3893 [vi5_update_channel_match_data] "match configuration is already in use by by channel 34 cannot set channel match configuration" [ 1148.550033] [RCE] ERROR: services/capture/capture-scheduler.c:3024 [capture_scheduler_thread] "Error processing event 0x100003"

  Here are the dmesg logs from the 2-lane mode and 4-lane DTB, with the camera running in qv4l2:

  [ 363.310470] mvcam 10-003b: csi2_try format [ 363.310521] mvcam 10-003b: csi2_try format [ 363.310535] mvcam 10-003b: mvcam_csi2_get_fmt_idx_by_code success [ 363.398118] mvcam 10-003b: camera_common_mclk_enable: no device power rail [ 363.398335] mvcam 10-003b: camera_common_s_power: failed to enable mclk [ 366.485242] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms [ 366.485600] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel [ 366.485846] (NULL device *): vi_capture_control_message: NULL VI channel received [ 366.486023] t194-nvcsi 13e10000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=2, csi_port=2 [ 366.486291] (NULL device *): vi_capture_control_message: NULL VI channel received [ 366.486903] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel [ 366.537167] [RCE] ERROR: camera-ip/vi5/vi5.c:3893 [vi5_update_channel_match_data] "match configuration is already in use by by channel 35 cannot set channel match configuration" [ 366.537192] [RCE] ERROR: services/capture/capture-scheduler.c:3024 [capture_scheduler_thread] "Error processing event 0x100003" [ 369.044982] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms [ 369.045291] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel [ 369.045626] (NULL device *): vi_capture_control_message: NULL VI channel received [ 369.045805] t194-nvcsi 13e10000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=2, csi_port=2 [ 369.046046] (NULL device *): vi_capture_control_message: NULL VI channel received [ 369.046343] t194-nvcsi 13e10000.host1x:nvcsi@15a00000: csi5_stream_open: VI channel not found for stream- 2 vc- 0 [ 369.046928] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
• NXP i.MX App Software
  1
  Topics
  3
  Posts

  

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

• Rockchip App camera
  11
  Topics
  100
  Posts

  

  @jihua 我们在rk平台没有遇到过这个问题。看ecc2这个错误提示的话，像是mipi信号劣化了。