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

  40
  Topics
  256
  Posts

  

  @lpcq2000 抱歉现在MCU bypass模式已经不再被支持了。我们的资料有一些迟滞，回头会更新到上面。

• Machine Vision camera
  28
  Topics
  289
  Posts

  D

  @veye_xumm Hi,
  Firmware update does not solve the problem, after software reset auto exposure mode works normal

• VEYE MIPI camera

  VEYE series MIPI CSI-2 camera modules

  304
  Topics
  2201
  Posts

  

  @d_101 Sorry for the late reply. Based on the current situation, I can only suspect a hardware issue that is causing the I2C path to be unavailable. This could be a problem with your mainboard or with the camera itself. Please return the camera to us, and we will perform testing and inspection.

• CS MIPI camera

  CS series MIPI CSI-2 camera modules

  142
  Topics
  1017
  Posts

  S

  @veye_xumm

  That's right. It worked with the lens. Thank you very much for your technical support.

• 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
  48
  Topics
  399
  Posts

  J

  @veye_xumm it is resolved now, the image is shown. Before with the steps on the forum the .dtbo file was also missing, I copied it from another folder and it didn't work. The right and supported way of installing drivers is very confusing, I tried installing by wiki guide and then compiling locally (github), since it didn't work. Thank you for your patience.

• Jetson App Software
  27
  Topics
  249
  Posts

  

  @dragos You are welcome.

• 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
  18
  Topics
  139
  Posts

  X

  @veye_xumm
  Thank you for your reply. The lenghts were:

  20 cm from camera to adapter using stock white 22-pin FFC cable 10 cm from the adapter to the board itself using 31-pin cable.

  I've done some experiments today with different cable length combinations and various results.

  CSI0:

  22-pin 20 cm + 31 pin 15 cm. 0 fps, ecc2, fs/fe, f_seq errors. 22-pin 10 cm + 31 pin 10 cm. 14-38 fps, very unstable with dropped buffers, ecc2, fs/fe, f_seq errors. 22-pin 20 cm + 31 pin 10 cm. 0 fps, ecc2, fs/fe, f_seq errors. 22-pin 10 cm + 31 pin 15 cm. 0 fps, ecc2, fs/fe, f_seq errors.

  CSI1:

  22-pin 20 cm + 31 pin 15 cm. 60 fps, no errors. 22-pin 10 cm + 31 pin 10 cm. 60 fps, crc, err_data errors. 22-pin 20 cm + 31 pin 10 cm. 60 fps, crc, err_data errors. 22-pin 10 cm + 31 pin 15 cm. 60 fps, no errors.

  So, the new information is that CSI0 managed to receive at least some data and there are combinations of cable length (that are suprisingly longer) that make errors disappear completely on CSI1. As far as I can judge, this indicates hardware problems rather than issues with, for example, dt overlays.

  Regarding your question about adapter board. Differential pairs are length matched. I will request information about impedance matching from the developer of that board. The adapter only contains voltage stab and I2C level adapter - MIPI lanes are connected directly.