2,021
edits
Changes
Jump to navigation
Jump to search
Line 69:
Line 69: + + + + Line 87:
Line 91: − + − The difference between these two modes is described in detail on the [https://www.raspberrypi.com/documentation/accessories/camera.html#libcamera-and-the-legacy-raspicam-camera-stack Raspberry Pi website.] The libcamera-stack mode mentioned on the Raspberry Pi website is architecturally identical to the V4L2 mode we are talking about.+ + + + + + + Line 107:
Line 117: − − ==== libcamera and V4L2 mode ==== − Now piOS has switched to libcamera-stack mode. − − Libcamera is essentially centered on implementing isp functionality, something that is not needed for the MV series cameras. Therefore, we have adopted the V4L2 mode instead of using libcamera-stack. − − As with libcamera-stack, our V4L2 model implements the standard V4L2 driver for the linux driver layer too. Based on this driver, the application layer can directly develop programs to acquire images and perform further processing. Line 179:
Line 182: − + Line 198:
Line 201: + + + + + + + + Line 223:
Line 234: + + + + + Line 778:
Line 794: + + + +
→Document History
The ADP-MV1 requires a separate 5V power supply and can be powered directly from the Raspberry Pi motherboard using a Dupont cable.[[File:ADP-MV1-MV-MIPI-X 07.jpg|center|thumb|800x800px|ADP-MV1 power supply|link=http://wiki.veye.cc/index.php/File:ADP-MV1-MV-MIPI-X_07.jpg]]
The ADP-MV1 requires a separate 5V power supply and can be powered directly from the Raspberry Pi motherboard using a Dupont cable.[[File:ADP-MV1-MV-MIPI-X 07.jpg|center|thumb|800x800px|ADP-MV1 power supply|link=http://wiki.veye.cc/index.php/File:ADP-MV1-MV-MIPI-X_07.jpg]]
===== Raspberry Pi 5 =====
The two are connected using 15Pto22P FFC cable with Same-side contacts. Pay attention to the silver contacts facing side.
===== Raspberry Pi Model B and B+ =====
===== Raspberry Pi Model B and B+ =====
The two are connected using 1.0 mm pitch*15P FFC cable with opposite-side contacts. Pay attention to the silver contacts facing side.[[File:MV-MIPI-X-RPI B 01.jpg|alt=MV camera and RPI connection|center|thumb|800x800px|MV camera and RPI connection|link=http://wiki.veye.cc/index.php/File:MV-MIPI-X-RPI_B_01.jpg]]
The two are connected using 1.0 mm pitch*15P FFC cable with opposite-side contacts. Pay attention to the silver contacts facing side.[[File:MV-MIPI-X-RPI B 01.jpg|alt=MV camera and RPI connection|center|thumb|800x800px|MV camera and RPI connection|link=http://wiki.veye.cc/index.php/File:MV-MIPI-X-RPI_B_01.jpg]]
It is recommended to enable the ssh service and samba service of Raspberry Pi system, here we will not go into the details of how to enable ssh and samba service of Raspberry Pi system.
It is recommended to enable the ssh service and samba service of Raspberry Pi system, here we will not go into the details of how to enable ssh and samba service of Raspberry Pi system.
=== Legacy mode and V4L2 mode introduction ===
=== V4L2 mode and Legacy mode introduction ===
In the latest Raspberry Pi Bookworm system, support for Legacy mode has been removed. It is recommended for customers to use the V4L2 mode.
==== libcamera and V4L2 mode ====
Now piOS has switched to libcamera-stack mode.
Libcamera is essentially centered on implementing isp functionality, something that is not needed for the MV series cameras. Therefore, we have adopted the V4L2 mode instead of using libcamera-stack.
As with libcamera-stack, our V4L2 model implements the standard V4L2 driver for the linux driver layer too. Based on this driver, the application layer can directly develop programs to acquire images and perform further processing.
==== Legacy mode ====
==== Legacy mode ====
Traditional mode, relying on Broadcom's GPU for image processing. The traditional raspicam software set uses this model.
Traditional mode, relying on Broadcom's GPU for image processing. The traditional raspicam software set uses this model.
Since the two modes cannot co-exist, Legacy mode needs to be turned off when using V4L2 mode.
Since the two modes cannot co-exist, Legacy mode needs to be turned off when using V4L2 mode.
===Configuring global variables===
===Configuring global variables===
For the convenience of later descriptions, global variables are configured here according to the sensor size.
For the convenience of later descriptions, global variables are configured here according to the sensor size.
<code>export HEIGHT=1088</code>
<code>export HEIGHT=1088</code>
<code>export FPS=60</code>
* <code>export FPS=60</code>
*RAW-MIPI-AR0234M
*RAW-MIPI-AR0234M
<code>chmod +x *</code>
<code>chmod +x *</code>
* For Raspberry Pi 5
<code>sudo ./install_driver_rpi5.sh veye_mvcam</code>
It will install both CAM1 and CAM0 overlays in /boot/config.txt.
* For other Raspberry Pi
<code>sudo ./install_driver.sh veye_mvcam</code>
<code>sudo ./install_driver.sh veye_mvcam</code>
And the /dev/video0 node exists, which proves that the camera status is normal.
And the /dev/video0 node exists, which proves that the camera status is normal.
==== Raspberry Pi 5 Setting ====
On Raspberry Pi 5,the drivers now use the media controller API, and we must setup the media graph correctly first. This includes setting up the media pad formats correctly and correctly linking them together.
We provide a series of scripts to implement this functionality, saved in the rpi5_scripts directory.
<br />
==== v4l2-ctl application examples ====
==== v4l2-ctl application examples ====
=== Document History ===
=== Document History ===
* 2024-01-01
Add support for Raspberrypi 5.
*2023-08-16
*2023-08-16