VEYE IMAGING Forum
    • Categories
    • Tags
    • Recent
    • Popular
    • Users
    • WIKI
    • veye.cc
    • Register
    • Login
    1. Home
    2. desperex
    3. Topics
    D
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 16
    • Groups 0

    Topics

    • D

      RAW-MIPI-SC132M on 1.8V I2C bus

      Watching Ignoring Scheduled Pinned Locked Moved VEYE MIPI camera
      10
      0 Votes
      10 Posts
      3k Views
      veye_xummV
      @desperex The linux of this board is open source. firefly has contact information on the wiki page, and you can get a download link to the material after you purchase it and consult it.
    • D

      RAW-MIPI-SC132M on VisionFive 2

      Watching Ignoring Scheduled Pinned Locked Moved General Discussion
      3
      0 Votes
      3 Posts
      2k Views
      D
      @veye_xumm said in RAW-MIPI-SC132M on VisionFive 2: We suggest you find a dts of mipi sensor that has been running successfully on Vision Five for reference, or seek help from the board manufacturer. Current device tree for VF2 includes working example of imx219 sensor, which is used as a base for your own driver - https://github.com/starfive-tech/linux/blob/JH7110_VisionFive2_devel/arch/riscv/boot/dts/starfive/jh7110-visionfive-v2.dtsi I just don't see big difference. Pins J1-11 need to be pulled high. http://wiki.veye.cc/index.php/RAW-MIPI-SC132M_Data_Sheet#Interface_.26_Pin_list I don't think you can put the Raspberry Pi dts directly onto Vision Five. This dts corresponds to two parts of the driver. The part of the camera driver named veyemvcam, and the other part corresponds to the mipi reception and processing driver of the main chip (for your board it is the Vision Five main chip). Thanks, I'd probably need to study specs & docs for the sensor and SBC more deeply.
    • D

      Please advise compatible mono camera

      Watching Ignoring Scheduled Pinned Locked Moved General Discussion
      15
      0 Votes
      15 Posts
      7k Views
      D
      @veye_xumm Thanks!