Navigation

    VEYE IMAGING Forum
    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Recent
    • Popular
    • Users
    • WIKI
    • veye.cc

    UNSOLVED veye-mipi-IMX462 on rpi5 get video stream but cant controll via v4l2 or i2c

    VEYE MIPI camera
    2
    6
    497
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      brunosaisi last edited by

      I am trying to use the module for guiding in astrophotography (Astroarch system on an rpi5), and there is an indi-v4l2 driver that recognizes the camera but can only play the video stream, not take singe exposures or control exposure and gain via v4l2. Being able to use the standard v4l2 controls would be ideal.

      I managed to install the veyecam2m driver and get video on dev/video0, but when i try v4l2-ctl -d /dev/video0 -l I get nothing back, no controls available for this device.
      I also tried the i2c_cmd method, built the read and write from source, and when i call for camera_i2c_config i get

      ~/raspberrypi/i2c_cmd/bin (master*) » ./camera_i2c_config
      setting GPIO for board revsion: d04170
      Failed: don't know how to set GPIO for this board! Type is 17
      Use i2c-10 for the sensor (-y 10)

      when i try veye_mipi_i2c.sh commands the answers are all wrong:

      ~/raspberrypi/i2c_cmd/bin (master*) » ./veye_mipi_i2c.sh -r -f devid
      device id is 0xff

      ~/raspberrypi/i2c_cmd/bin (master*) » ./veye_mipi_i2c.sh -r -f boardmodel
      Board model is VEYE-MIPI-327

      ~/raspberrypi/i2c_cmd/bin (master*) » ./veye_mipi_i2c.sh -w -f cameramode -p1 0x1
      w cameramode is 0x 1

      here i thought i had set it to manual mode, but no:

      ~/raspberrypi/i2c_cmd/bin (master*) » ./veye_mipi_i2c.sh -y 10 -r -f cameramode
      r cameramode is 0xff

      Can u shed some light? Thank you!

      B 1 Reply Last reply Reply Quote 0
      • B
        brunosaisi @brunosaisi last edited by

        @brunosaisi said in veye-mipi-IMX462 on rpi5 get video stream but cant controll via v4l2 or i2c:
        I also tried v4l2-ctl -d /dev/v4l-subdev2 -l

        and get:

        ~ » v4l2-ctl -d /dev/v4l-subdev2 -l

        Image Processing Controls

        pixel_rate 0x009f0902 (int64) : min=74250000 max=74250000 step=1 default=74250000 value=74250000 flags=read-only

        veye_xumm 1 Reply Last reply Reply Quote 0
        • veye_xumm
          veye_xumm @brunosaisi last edited by

          @brunosaisi
          For configuring this camera via I2C, the process is not done through v4l2-ctl but directly using a script. Please note the following regarding this script:

          1. If you are using the v4l2 driver mode, camera_i2c_config is not required.
          2. When running ./veye_mipi_i2c.sh, make sure to specify the I2C bus you are using with the -b parameter.

          Below is an explanation regarding the I2C bus.
          https://wiki.veye.cc/index.php/I2c_bus_number_and_video_node
          For long exposure usage, you may need to configure the lowlight function or the new_mshutter function. Please refer to the corresponding section in the link below.
          https://wiki.veye.cc/index.php/VEYE-MIPI-290/327_i2c/#new_mshutter

          B 1 Reply Last reply Reply Quote 0
          • B
            brunosaisi @veye_xumm last edited by

            @veye_xumm the -b parameter makes no difference, i tried all the possible bus numbers and still get all the wrong answers. for example:

            ~/raspberrypi/i2c_cmd/bin (master*) » ./veye_mipi_i2c.sh -b 11 -r -f hdver
            hardware version is 0xff
            release date is 20ff-ff-ff

            I was able to set new expmode to manual:
            ~/raspberrypi/i2c_cmd/bin (master*) » ./veye_mipi_i2c.sh -r -f new_expmode
            r new expmode is manual, use new_mshutter and new_mgain

            But when i try to set the new_mshutter i get:
            ~/raspberrypi/i2c_cmd/bin (master*) » ./veye_mipi_i2c.sh -b 10 -w -f new_mshutter -p1 1000

            awk: cmd. line:1: (FILENAME=- FNR=1) fatal: division by zero attempted
            ./veye_mipi_i2c.sh: line 1290: [: -gt: unary operator expected
            ./veye_mipi_i2c.sh: line 1294: >>8: arithmetic syntax error: operand expected (error token is ">>8")

            veye_xumm 1 Reply Last reply Reply Quote 0
            • veye_xumm
              veye_xumm @brunosaisi last edited by

              @brunosaisi
              Please show me the result of this:

              dmesg | grep veye

              This can reveal which specific I2C bus your camera is on.

              B 1 Reply Last reply Reply Quote 0
              • B
                brunosaisi @veye_xumm last edited by

                @veye_xumm

                ~ » dmesg | grep veye 1 ↵ ```
                [ 0.029025] /axi/pcie@1000120000/rp1/i2c@80000/veyecam2m@3b: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/csi@128000
                [ 0.029038] /axi/pcie@1000120000/rp1/i2c@88000/veyecam2m@3b: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/csi@110000
                [ 0.029063] /axi/pcie@1000120000/rp1/csi@110000: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/i2c@88000/veyecam2m@3b
                [ 0.029073] /axi/pcie@1000120000/rp1/csi@128000: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/i2c@80000/veyecam2m@3b
                [ 0.029230] /axi/pcie@1000120000/rp1/i2c@80000/veyecam2m@3b: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/csi@128000
                [ 0.029243] /axi/pcie@1000120000/rp1/i2c@88000/veyecam2m@3b: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/csi@110000
                [ 0.029270] /axi/pcie@1000120000/rp1/csi@110000: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/i2c@88000/veyecam2m@3b
                [ 0.029280] /axi/pcie@1000120000/rp1/csi@128000: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/i2c@80000/veyecam2m@3b
                [ 1.119276] /axi/pcie@1000120000/rp1/i2c@80000/veyecam2m@3b: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/csi@128000
                [ 1.119698] /axi/pcie@1000120000/rp1/i2c@88000/veyecam2m@3b: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/csi@110000
                [ 1.120359] /axi/pcie@1000120000/rp1/i2c@88000/veyecam2m@3b: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/csi@110000
                [ 1.120705] /axi/pcie@1000120000/rp1/csi@110000: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/i2c@88000/veyecam2m@3b
                [ 1.121105] /axi/pcie@1000120000/rp1/i2c@80000/veyecam2m@3b: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/csi@128000
                [ 1.121461] /axi/pcie@1000120000/rp1/csi@128000: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/i2c@80000/veyecam2m@3b
                [ 4.419673] /axi/pcie@1000120000/rp1/csi@128000: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/i2c@80000/veyecam2m@3b
                [ 4.419961] /axi/pcie@1000120000/rp1/i2c@80000/veyecam2m@3b: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/csi@128000
                [ 4.446956] /axi/pcie@1000120000/rp1/csi@110000: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/i2c@88000/veyecam2m@3b
                [ 4.446999] /axi/pcie@1000120000/rp1/i2c@88000/veyecam2m@3b: Fixed dependency cycle(s) with /axi/pcie@1000120000/rp1/csi@110000
                [ 4.562519] rp1-cfe 1f00110000.csi: found subdevice /axi/pcie@1000120000/rp1/i2c@88000/veyecam2m@3b
                [ 4.600108] rp1-cfe 1f00128000.csi: found subdevice /axi/pcie@1000120000/rp1/i2c@80000/veyecam2m@3b
                [ 4.829476] veyecam2m: loading out-of-tree module taints kernel.
                [ 4.837008] veyecam2m 11-003b: Unable to load ds90ub954 driver,will go on
                [ 4.945847] veyecam2m 11-003b: probe failed
                [ 4.965628] veyecam2m 10-003b: Unable to load ds90ub954 driver,will go on
                [ 5.078216] veyecam2m 10-003b: camera id is veyecam2m
                [ 5.080221] veyecam2m 10-003b: sensor is IMX327
                [ 5.080580] veyecam2m 10-003b: board type is ONE board
                [ 5.081367] rp1-cfe 1f00110000.csi: Using sensor veyecam2m 10-003b for capture
                [ 5.108106] veyecam2m 10-003b: veyecam2m camera probed

                i already tried the ./veye_mipi_i2c.sh with the -b set to 10, 11, 6, 4 and 0. all give the same results.

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post