Navigation

    VEYE IMAGING Forum

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Recent
    • Popular
    • Users
    • WIKI
    • veye.cc
    1. Home
    2. Popular
    Log in to post
    • All categories
    • Announcements
    • General Discussion
    • Machine Vision camera
    • VEYE MIPI camera
    • CS MIPI camera
    • FPD LINK III Camera
    • USB camera
    • Raspberry Pi App Software
    • Jetson App Software
    • NXP i.MX App Software
    • Rockchip App camera
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics
    • All Time
    • Day
    • Week
    • Month
    • M

      UNSOLVED OrangePi cm5-tablet RAW-MIPI-SC132M
      Rockchip App camera • • mparem

      7
      0
      Votes
      7
      Posts
      305
      Views

      veye_xumm

      @mparem
      Please post dmesg | grep mvcam output here.

    • G

      SOLVED mv-mipi-imx264m 移植到3588出现错误ERROR: csi size err
      VEYE MIPI camera • • goooofy

      4
      0
      Votes
      4
      Posts
      511
      Views

      veye_xumm

      @goooofy 好的。

    • J

      UNSOLVED VEYE-MIPI-IMX462 on Seeed J401 Carrier Board + Orin Nano 4GB (JetPack 6.2 / L4T 36.4.3) – No /dev/video Device Detected
      VEYE MIPI camera • • joe

      2
      0
      Votes
      2
      Posts
      275
      Views

      veye_xumm

      @joe

      @joe said in VEYE-MIPI-IMX462 on Seeed J401 Carrier Board + Orin Nano 4GB (JetPack 6.2 / L4T 36.4.3) – No /dev/video Device Detected:

      Questions:
      What could be preventing /dev/video0 from being created, even though the sensor is detected by the kernel?

      Under normal circumstances, as long as the I2C communication is working, the /dev/video0 node should be generated properly. Based on my initial assessment, your issue likely stems from differences in the usage of MIPI CSI pins between the J401 carrier board and NVIDIA's official developer kit when paired with the Orin Nano core module. Since our DTBO is based on the device tree of NVIDIA's official developer board, it may not be fully compatible with the J401 out of the box. You can try analyzing the full dmesg output to identify any errors. I suggest reaching out to Seeed for further assistance on this issue.