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

    imx327 missing from raspberrypi_v4l2 ver 5.10.63-

    Scheduled Pinned Locked Moved VEYE MIPI camera
    6 Posts 2 Posters 2.0k Views 2 Watching
    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.
    • R Offline
      Roger
      last edited by

      The two 5.10.63 releases are missing the imx327 versions of the driver, would it be possible to release these files as well?

      1 Reply Last reply Reply Quote 0
      • R Offline
        Roger
        last edited by

        I emailed 'xumm' and was told
        "Please use veyecam2m.ko, this module support all 2M pixel VEYE-MIPI-* camera modules."
        So I believe the installation line:-
        sudo ./install_driver.sh [camera module]

        should use a [module name] of veyecam2m, which seems to install but as yet I don't have a fully working system motioneye or allsky system using it. I should find out soon...

        veye_xummV 1 Reply Last reply Reply Quote 0
        • veye_xummV Offline
          veye_xumm @Roger
          last edited by

          @roger
          Hi,
          Which rpi board do you use?

          Questions will be answered as soon as possible, please be patient.
          如果你使用中文，请直接用中文提问。
          May the force be with YOU. (This is the translation of the mysterious Chinese symbol above.)

          1 Reply Last reply Reply Quote 0
          • R Offline
            Roger
            last edited by

            I have the IMX327E boards. I am currently trying with bullseye 5.10.63.
            I installed the veyecam2m driver and updated the raspi-config to be able to select legacy support but I cannot get motioneye to work nor can I get the gstreamer tests on your readme on github for the v4l2. I see that the readme is out of date compared with the wiki but I still cannot get gstreamer to work.
            This all seems in order....

            pi@raspberrypi:~ $ dmesg |grep veye
            [ 11.775403] veyecam2m 10-003b: camera id is veyecam2m
            [ 11.778121] veyecam2m 10-003b: sensor is IMX327
            [ 11.778144] veyecam2m 10-003b: board type is TWO board
            [ 11.779786] veyecam2m 10-003b: veyecam2m camera probed

            @raspberrypi:~ $ ls /dev/video0
            /dev/video0

            pi@raspberrypi:~ $ v4l2-ctl --list-formats-ext
            ioctl: VIDIOC_ENUM_FMT
            Type: Video Capture

                [0]: 'UYVY' (UYVY 4:2:2)
            Size: Discrete 1920x1080

            But gstreamer gives:-

            pi@raspberrypi:~ $ gst-launch-1.0 v4l2src num-buffers=1 device=/dev/video0 ! 'video/x-raw, format=(string)UYVY, width=1920,height=1080' ! jpegenc ! filesink location=test_image.jpg
            Setting pipeline to PAUSED ...
            Pipeline is live and does not need PREROLL ...
            Pipeline is PREROLLED ...
            Setting Pipeline to PLAYING ...
            New clock: GstSystemClock
            ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Failed to allocate required memory.
            Additional debug info:
            ../sys/v4l2/gstv4l2src.c(659): gst_v4l2src_decide_allocation (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
            Buffer pool activation failed
            Execution ended after 0:00:00.004531494
            Setting pipeline to NULL ...
            ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Internal data stream error.
            Additional debug info:
            ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
            streaming stopped, reason not-negotiated (-4)
            Freeing pipeline ...

            veye_xummV 1 Reply Last reply Reply Quote 0
            • veye_xummV Offline
              veye_xumm @Roger
              last edited by

              @roger
              Hi，The bullseye version of the Raspberry Pi changed the camera driver architecture to support libcamera. I am still working on the v4l2 driver support on the bullseye system as well.
              I suggest you to use the older version of piOS first.

              Questions will be answered as soon as possible, please be patient.
              如果你使用中文，请直接用中文提问。
              May the force be with YOU. (This is the translation of the mysterious Chinese symbol above.)

              1 Reply Last reply Reply Quote 0
              • R Offline
                Roger
                last edited by

                Hi, I tried the V4L2 driver with Buster which worked OK on a Pi4 4 GB then I tested Bullseye with the legacy mode and the same V4L2 driver ( veyecam2m ver 5.10.63) and that worked OK too.
                I was previously testing with a Pi 3A which I would like to work but that does seem to have a problem with the v4L2 driver with both OS's.

                1 Reply Last reply Reply Quote 0

                Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                With your input, this post could be even better 💗

                Register Login
                • First post
                  Last post