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

  39
  Topics
  254
  Posts

  

  @lozinski Sorry, we currently do not have products that meet your requirements. The VEYE-LVDS-327 has been discontinued for a long time.

• Machine Vision camera
  26
  Topics
  271
  Posts

  

  @stiwana
  https://wiki.veye.cc/index.php/Mv_series_camera_appnotes_4_jetson

  For specific information, please refer to the link above. We provide a veye_viewer client for customers to initially get started and verify usage.

  We haven't done extensive debugging on GStreamer yet. As for OpenCV, there are examples provided in the article above. Regarding the latency issue: although the camera itself has negligible delay, each image entering the Jetson system will experience some latency due to the V4L2 buffer, format conversion, and preview processes—all of which involve memory buffering queues.

  The most fundamental solution is to develop your own program tailored to your product's specific needs, allowing flexible management of buffers. Additionally, note that the V4L2 buffer containing the camera images after they enter the Jetson system includes timestamps. It is recommended that you use these timestamps.

  Regarding the supply of this product, we will maintain long-term availability unless the chip is discontinued. We will keep a regular inventory sufficient to meet retail demand. For bulk orders of several hundred units or more, the production cycle is typically within one month.

• VEYE MIPI camera

  VEYE series MIPI CSI-2 camera modules

  297
  Topics
  2159
  Posts

  F

  @veye_xumm 好的 一定

• CS MIPI camera

  CS series MIPI CSI-2 camera modules

  141
  Topics
  1003
  Posts

  

  @fumyang 请问您用的是哪个相机模组？

• 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
  47
  Topics
  370
  Posts

  

  @nian 不客气

• 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
  15
  Topics
  118
  Posts

  N

  Hi,

  I'm trying to follow this instruction to compile veye imx287m for yocto linux 6.13, but it seems it's not fully compatible with this kernel version

  https://github.com/veyeimaging/rk35xx_radxa/tree/main/linux/drivers

  | SYNC include/config/auto.conf | GEN Makefile | DTC arch/arm64/boot/dts/rockchip/rk3566-radxa-zero-3e.dtb | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:7.1-12 Label or path csi2_dphy0 not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:37.1-12 Label or path csi2_dphy1 not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:41.1-12 Label or path csi2_dphy2 not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:45.1-14 Label or path csi2_dphy_hw not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:85.1-11 Label or path mipi_csi2 not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:116.1-7 Label or path rkcif not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:120.1-17 Label or path rkcif_mipi_lvds not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:129.1-23 Label or path rkcif_mipi_lvds_sditf not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:133.1-11 Label or path rkcif_mmu not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:136.1-7 Label or path rkisp not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:140.1-12 Label or path rkisp_vir0 not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:144.1-12 Label or path rkisp_vir1 not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero-3e.dts:19.1-12 Label or path rgmii_phy1 not found | FATAL ERROR: Syntax error parsing input tree

  and I cannot find things like mipi_csi2 in these files:

  rk3566-radxa-zero-3.dtsi.txt

  rk3566-base.dtsi.txt

  rk356x-base.dtsi.txt

  commit in yocto layer meta-rockchip says that radxa 3e requires the latest kernel:

  https://github.com/radxa/meta-rockchip

  git show e0b13fe8 ... NOTE: currently support for this board requires a U-Boot fork for the bootloader, and linux-next for the kernel. Support will probably come in linux kernel 6.11-ish, at which point U-Boot will then use that kernel's device tree which means U-Boot support will come after the release of whichever kernel includes support for this board.

  this email also says that kernel versions below 6.9 do not support radxa zero 3 devices, so I'm wondering how it is possible to use 5.10 which is mentioned in your instructions

  https://lists.yoctoproject.org/g/yocto-patches/topic/kernel_and_u_boot_version/111621524

  could please anyone tell if there is an easy way to adopt dtsi for 6.13 kernel version?

  thanks