2,054
edits
Changes
Jump to navigation
Jump to search
Line 24:
Line 24: + + + + + + + + + + + + + + + + + + + + + + − We take MV-MIPI-IMX178M as an example to introduce the hardware installation method.+ + + + + + + + + − + − The two are connected using 0.5 mm pitch*30P FFC cable with opposite direction. The cable must be inserted with the silver contacts facing outside.[[File:ADP-MV1-MV-MIPI-X 01.jpg|center|thumb|800x800px|ADP-MV1 to MV-MIPI-X|link=http://wiki.veye.cc/index.php/File:ADP-MV1-MV-MIPI-X_01.jpg]] − ==== Connection of ADP-MV1 to Raspberry Pi ==== − ===== Power supply ===== + + + + + + + + − + − + + + + + + + + + + + Line 55:
Line 100: − + − 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 75:
Line 126: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + − + − 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 93:
Line 210: + + + + + + + + Line 117:
Line 242: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Line 156:
Line 320: − + − − <small><code> Size: Discrete 3088x2064</code></small> − − Note: UYVY data format is for debugging use only. − + − + − + − + − + − + − + Line 184:
Line 344: + + + + + Line 190:
Line 355: − ======horizontal and <small>vertical</small> flip====== − − *horizontal flip − − <code>v4l2-ctl --set-ctrl horizontal_flip=1</code> − − *<small>vertical flip</small> − − <code>v4l2-ctl --set-ctrl <small>vertical_flip</small>=1</code> Line 224:
Line 380: − For example： − + + + + + − <code>v4l2-ctl --set-selection=target=crop,top=32,left=64,width=2592,height=1944</code>+ − + − + − The maximum frame rate will be adjusted automatically after setting ROI.+ + − Take MV-MIPI-IMX178M, 3088*2064 as an example.+ − + + + + + + − + − + + + + + − + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + − Since the memory requested by Raspberry Pi for the image, the width is 32-align and the height is 16-align, the 3088*2064 image will be saved as 3104*2064 size.+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + − ===== Set ROI =====+ − Take MV-MIPI-IMX178M, 3088*2064 as an example. − + + Line 300:
Line 634: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Line 408:
Line 786: − + Line 417:
Line 795: − + + + + + + + + + + + − ==== Raw data picture format ====+ + − + Line 428:
Line 817: + + Line 453:
Line 844: + + Line 461:
Line 854: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
→i2c script for parameter configuration
|MV series
|MV series
|MV-MIPI-IMX296M
|MV-MIPI-IMX296M
|Done
|-
|MV series
|MV-MIPI-IMX287M
|Done
|Done
|-
|-
|MV series
|MV series
|MV-MIPI-IMX265M
|MV-MIPI-IMX265M
|Done
|-
|MV series
|MV-MIPI-IMX264M
|Done
|-
|RAW series
|RAW-MIPI-SC132M
|Done
|-
|RAW series
|RAW-MIPI-IMX462M
|Done
|-
|RAW series
|RAW-MIPI-AR0234M
|Done
|Done
|}
|}
=== Hardware Setup ===
=== Hardware Setup ===
==== MV series cameras use the ADP-MV1 connection ====
MV series cameras need to use ADP-MV1 adapter board in order to connect to Raspberry Pi.
MV series cameras need to use ADP-MV1 adapter board in order to connect to Raspberry Pi.
===== Connection of MV series camera and ADP-MV1 =====
The two are connected using 0.5 mm pitch*30P FFC cable with opposite-side contacts. The cable must be inserted with the silver contacts facing outside.
{| class="wikitable"
!TOP
!BOTTOM
|-
|[[File:ADP-MV1-MV-MIPI-X 01.jpg|center|thumb|600x600px|ADP-MV1 to MV-MIPI-X|alt=]]
|[[File:ADP-MV1-MV-MIPI-X 02.jpg|alt=|center|thumb|600x600px|ADP-MV1 to MV-MIPI-X]]
|}
==== Connection of MV-MIPI-IMX178M and ADP-MV1 ====
===== Power supply =====
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.
{| class="wikitable"
|-
|[[File:ADP-MV1 to RPI5.jpg|link=http://wiki.veye.cc/index.php/File:ADP-MV1%20to%20RPI5.jpg|center|thumb|600x600px|ADP-MV1 to RPI5]]
|[[File:ADP-MV1 to RPI5 2.jpg|link=http://wiki.veye.cc/index.php/File:ADP-MV1%20to%20RPI5%202.jpg|alt=|center|thumb|600x600px|ADP-MV1 to RPI5_2]]
|}
===== 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 direction. 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]]
===== Raspberry Pi Zero, Zero W and Computer Module =====
===== Raspberry Pi Zero, Zero W and Computer Module =====
The two are connected using 15Pto22P FFC cable with same direction. Pay attention to the silver contacts facing side.[[File:MV-MIPI-X-RPI Z 01.jpg|center|thumb|800x800px|MV camera and Raspberry Pi zero connection|link=http://wiki.veye.cc/index.php/File:MV-MIPI-X-RPI_Z_01.jpg]]
The two are connected using 15Pto22P FFC cable with Same-side contacts. Pay attention to the silver contacts facing side.[[File:MV-MIPI-X-RPI Z 01.jpg|center|thumb|800x800px|MV camera and Raspberry Pi zero connection|link=http://wiki.veye.cc/index.php/File:MV-MIPI-X-RPI_Z_01.jpg]]<br />
====RAW series cameras directly connected to Raspberrypi====
===== Raspberry Pi 5 =====
The RAW-MIPI-SC132M use a 15-to-22-pin same-side FFC cable, while other RAW series cameras use a 22-pin opposite-side FFC cable.
[[File:RAW CAM to RPI5.jpg|link=http://wiki.veye.cc/index.php/File:RAW%20CAM%20to%20RPI5.jpg|center|thumb|800x800px|RAW CAM to RPI5]]
=====Raspberry Pi Model B and B+=====
The RAW-MIPI-SC132M use a 15-pin opposite-side FFC cable, while other RAW series cameras use a 15-to-22-pin same-side FFC cable.[[File:RAW-MIPI-AR0234-RPI4.jpg|center|thumb|800x800px|RAW series camera and RPI connection|link=http://wiki.veye.cc/index.php/File:RAW-MIPI-AR0234-RPI4.jpg]]
=====Raspberry Pi Zero, Zero W and Computer Module=====
The RAW-MIPI-SC132M use a 15-to-22-pin same-side FFC cable, while other RAW series cameras use a 22-pin opposite-side FFC cable.[[File:RAW-MIPI-AR0234-RPI ZERO.jpg|center|thumb|800x800px|RAW-MIPI-AR0234-RPI ZERO|link=http://wiki.veye.cc/index.php/File:RAW-MIPI-AR0234-RPI_ZERO.jpg]]
=== piOS Configuration ===
=== piOS Configuration ===
For details on how to install the Raspberry Pi system, please refer to the official documentation at [https://www.raspberrypi.org/documentation/installation/ Install raspberry pi guide].
For details on how to install the Raspberry Pi system, please refer to the official documentation at [https://www.raspberrypi.org/documentation/installation/ Install raspberry pi guide].
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===
For the convenience of later descriptions, global variables are configured here according to the sensor size.
*MV-MIPI-IMX178M
<code>export WIDTH=3088</code>
<code>export HEIGHT=2064</code>
<code>export FPS=22</code>
*MV-MIPI-SC130M
<code>export WIDTH=1280</code>
<code>export HEIGHT=1024</code>
<code>export FPS=108</code>
* MV-MIPI-IMX296M
<code>export WIDTH=1440</code>
<code>export HEIGHT=1088</code>
<code>export FPS=60</code>
*MV-MIPI-IMX287M
<code>export WIDTH=704</code>
<code>export HEIGHT=544</code>
<code>export FPS=319</code>
*MV-MIPI-IMX265M
<code>export WIDTH=2048</code>
<code>export HEIGHT=1544</code>
<code>export FPS=45</code>
*MV-MIPI-IMX264M
<code>export WIDTH=2432</code>
<code>export HEIGHT=2056</code>
<code>export FPS=28</code>
*RAW-MIPI-SC132M
<code>export WIDTH=1024</code>
<code>export HEIGHT=1280</code>
<code>export FPS=120</code>
*RAW-MIPI-IMX462M
<code>export WIDTH=1920</code>
<code>export HEIGHT=1088</code>
==== libcamera and V4L2 mode ====
* <code>export FPS=60</code>
*RAW-MIPI-AR0234M
<code>export WIDTH=1920</code>
<code>export HEIGHT=1200</code>
<code>export FPS=60</code>
===V4L2 mode manual===
===V4L2 mode manual===
We have saved the code for v4l2 mode in this [https://github.com/veyeimaging/raspberrypi_v4l2 github repository].
We have saved the code for v4l2 mode in this [https://github.com/veyeimaging/raspberrypi_v4l2 github repository].
<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.
* ./find_entity.sh
<code>$ ./find_entity.sh</code>
<code>Found mvcam @ i2c-4 entity on /dev/media3</code>
<code>Plese get frame from /dev/video0 and use /dev/v4l-subdev2 for camera setting.</code>
<code>Found mvcam @ i2c-6 entity on /dev/media0</code>
<code>Plese get frame from /dev/video8 and use /dev/v4l-subdev5 for camera setting.</code><br />After a reboot of Raspberry Pi 5, the media node and video node of the camera may change. Therefore, it is recommended to execute <code>./find_entity.sh</code> before performing subsequent operations to identify the device nodes.
The above prompt shows that the system has detected two cameras and their corresponding device nodes.
<code>i2c-4</code> corresponds to the CAM1 port on the board, and <code>i2c-6</code> corresponds to the CAM0 port on the board.
* media_setting_rpi5.sh
<code>./media_setting_rpi5.sh</code>
<code>Usage: ./media_setting_rpi5.sh veyecam2m/csimx307/cssc132/mvcam -fmt [UYVY/RAW8/RAW10/RAW12] -w [width] -h [height]</code>
<code>This shell script is designed to detect the connection of a camera on Raspberry Pi 5.</code>
<code> It utilizes media-ctl and v4l2-ctl commands to configure the linking relationships and data formats of the media pad.</code>
<code> Once completed, you can directly use /dev/video0 or /dev/video8 to obtain image data</code>
Before proceeding with further operations, it is '''necessary''' to execute this script to complete the configuration of parameters.
For instance，RAW-MIPI-AR0234M:
<code>./media_setting_rpi5.sh mvcam -fmt RAW8 -w 1920 -h 1200</code>
==== v4l2-ctl application examples ====
==== v4l2-ctl application examples ====
<small><code> Size: Discrete 3088x2064</code></small>
<small><code> Size: Discrete 3088x2064</code></small>
<small><code> [5]: 'UYVY' (UYVY 4:2:2)</code></small>
<br />On Raspberry Pi 5, the actual supported image formats depend on the capabilities of the camera, not the list provided here.
====== List the configurable parameters of the camera implemented in the driver ======
====== List the configurable parameters of the camera implemented in the driver ======
<code>v4l2-ctl -L</code>
<code>v4l2-ctl -L</code>
<code><small>User Controls</small></code>
<code>User Controls</code>
<code><small> horizontal_flip 0x00980914 (bool) : default=0 value=0</small></code>
<code> trigger_mode 0x00981901 (int) : min=0 max=2 step=1 default=0 value=0 flags=volatile, execute-on-write</code>
<code><small> vertical_flip 0x00980915 (bool) : default=0 value=0</small></code>
<code> trigger_src 0x00981902 (int) : min=0 max=1 step=1 default=1 value=1 flags=volatile, execute-on-write</code>
<code><small> trigger_mode 0x00981901 (int) : min=0 max=2 step=1 default=0 value=0 flags=volatile</small></code>
<code> soft_trgone 0x00981903 (button) : flags=write-only, execute-on-write</code>
<code><small> trigger_src 0x00981902 (int) : min=0 max=1 step=1 default=1 value=1 flags=volatile</small></code>
<code> frame_rate 0x00981904 (int) : min=1 max=60 step=1 default=30 value=30 flags=volatile, execute-on-write</code>
<code><small> soft_trgone 0x00981903 (button) : flags=write-only, execute-on-write</small></code>
<code> roi_x 0x00981905 (int) : min=0 max=1376 step=8 default=0 value=0</code>
<code><small> frame_rate 0x00981904 (int) : min=0 max=22 step=1 default=22 value=22 flags=volatile</small></code>
<code> roi_y 0x00981906 (int) : min=0 max=1024 step=4 default=0 value=0</code>
Parameters can be set and get using the following methods.
Parameters can be set and get using the following methods.
<code>v4l2-ctl --get-ctrl [ctrl_type]</code>
<code>v4l2-ctl --get-ctrl [ctrl_type]</code>
Note: For Raspberry Pi 5, the -d parameter needs to be added to all commands in this section to specify the subdev used for configuring parameters.
For example, if executing ./media_setting_rpi5.sh or ./find_entity.sh prompts the use of /dev/v4l-subdev2 for parameter configuration, then <code>v4l2-ctl -L</code> should be changed to <code>v4l2-ctl -L -d /dev/v4l-subdev2</code>.
All the above functions can be implemented using [[Mv mipi i2c.sh user guide|mv_mipi_i2c.sh]].
All the above functions can be implemented using [[Mv mipi i2c.sh user guide|mv_mipi_i2c.sh]].
Each of them is described below:
Each of them is described below:
======Trigger Mode======
======Trigger Mode======
<code>v4l2-ctl --set-ctrl <small>trigger_mode=[0-2]</small></code>
<code>v4l2-ctl --set-ctrl <small>trigger_mode=[0-2]</small></code>
====== Set ROI ======
====== Set ROI ======
* MV-MIPI-IMX178M
*method 1，use selection
<code>v4l2-ctl --set-selection=target=crop,top=0,left=0,width=$WIDTH,height=$HEIGHT</code>
Note: This method is not applicable to Raspberry Pi 5.
The maximum frame rate will be adjusted automatically after setting ROI.
* MV-MIPI-SC130M
*method 2，use user definedroi_x，roi_y and <code>--set-fmt-video</code>
<code>v4l2-ctl --set-selection=target=crop,top=32,left=64,width=640,height=640</code>
<code>v4l2-ctl --set-ctrl roi_x=0</code>
<code>v4l2-ctl --set-ctrl roi_y=0</code>
<code>v4l2-ctl --set-fmt-video=width=$WIDTH,height=$HEIGHT</code>
==== Video Streaming mode ====
==== Video Streaming mode ====
===== Set ROI =====
===== Set ROI =====
<code>v4l2-ctl --set-ctrl roi_x=0</code>
<code>v4l2-ctl --set-selection=target=crop,top=0,left=0,width=3088,height=2064</code>
<code>v4l2-ctl --set-ctrl roi_y=0</code>
<code>v4l2-ctl --set-fmt-video=width=$WIDTH,height=$HEIGHT</code>
===== Set Framerate =====
<code>v4l2-ctl --set-ctrl frame_rate=$FPS</code>
===== Frame rate statistics =====
===== Frame rate statistics =====
In streaming mode, the following commands can be used for frame rate statistics.
In streaming mode, the following commands can be used for frame rate statistics.
<code>v4l2-ctl --set-fmt-video=width=3088,height=2064,pixelformat=GREY --stream-mmap --stream-count=-1 --stream-to=/dev/null</code>
<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=GREY --stream-mmap --stream-count=-1 --stream-to=/dev/null</code>
===== Save image to file =====
===== Save image to file =====
<code>v4l2-ctl --set-fmt-video=width=3088,height=2064,pixelformat=GREY --stream-mmap --stream-count=1 --stream-to=y8-3104x2064.yuv</code>
======MV-MIPI-IMX178M======
*raw8
<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=3088,height=2064,pixelformat=GREY --stream-mmap --stream-count=1 --stream-to=y8-3104x2064.raw</code>
Or
Or
<code>./yavta -c1 -Fy8-3104x2064.yuv --skip 0 -f Y8 -s 3088x2064 /dev/video0</code>
<code>./yavta -c1 -Fy8-3104x2064.raw --skip 0 -f Y8 -s 3088x2064 /dev/video0</code>
Since the memory requested by Raspberry Pi for the image, the width is 32-align and the height is 16-align, the 3088*2064 image will be saved as 3104*2064 size.
*raw10
<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=3088,height=2064,pixelformat='Y10 ' --stream-mmap --stream-count=1 --stream-to=y10-3088x2064.raw</code>
*raw12
<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=3088,height=2064,pixelformat='Y12 ' --stream-mmap --stream-count=1 --stream-to=y12-3088x2064.raw</code>
======MV-MIPI-SC130M======
*raw8
<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=1280,height=1024,pixelformat=GREY --stream-mmap --stream-count=1 --stream-to=y8-1280x1024.raw</code>
*raw10
<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=1280,height=1024,pixelformat='Y10 ' --stream-mmap --stream-count=1 --stream-to=y10-1280x1024.raw</code>
====== MV-MIPI-IMX296M======
* raw8
<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=1440,height=1088,pixelformat=GREY --stream-mmap --stream-count=1 --stream-to=y8-1440x1088.raw</code>
*raw10
<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=1440,height=1088,pixelformat='Y10 ' --stream-mmap --stream-count=1 --stream-to=y10-1440x1088.raw</code>
======MV-MIPI-IMX265M======
* raw8
<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=2048,height=1544,pixelformat=GREY --stream-mmap --stream-count=1 --stream-to=y8-2048x1544.raw</code>
*raw10
<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=2048,height=1544,pixelformat='Y10 ' --stream-mmap --stream-count=1 --stream-to=y10-2048x1544.raw</code>
*raw12
<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=2048,height=1544,pixelformat='Y12 ' --stream-mmap --stream-count=1 --stream-to=y12-2048x1544.raw</code>
======MV-MIPI-IMX264M======
*raw8
<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=2432,height=2056,pixelformat=GREY --stream-mmap --stream-count=1 --stream-to=y8-2432x2056.raw</code>
*raw10
<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=2432,height=2056,pixelformat='Y10 ' --stream-mmap --stream-count=1 --stream-to=y10-2432x2056.raw</code>
* raw12
<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=2432,height=2056,pixelformat='Y12 ' --stream-mmap --stream-count=1 --stream-to=y12-2432x2056.raw</code>
======RAW-MIPI-SC132M======
* raw8
<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=1024,height=1280,pixelformat=GREY --stream-mmap --stream-count=1 --stream-to=y8-1024x1280.raw</code>
*raw10
<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=1024,height=1280,pixelformat='Y10 ' --stream-mmap --stream-count=1 --stream-to=y10-1024x1280.raw</code>
======MV-MIPI-IMX287M======
*raw8
<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=704,height=544,pixelformat=GREY --stream-mmap --stream-count=1 --stream-to=y8-704x544.raw</code>
* raw10
<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=704,height=544,pixelformat='Y10 ' --stream-mmap --stream-count=1 --stream-to=y10-704x544.raw</code>
*raw12
<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=704,height=544,pixelformat='Y12 ' --stream-mmap --stream-count=1 --stream-to=y12-704x544.raw</code>
====== RAW-MIPI-IMX462M======
*raw10
<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=1920,height=1088,pixelformat='Y10 ' --stream-mmap --stream-count=1 --stream-to=y10-1920x1088.raw</code>
*raw12
<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=1920,height=1088,pixelformat='Y12 ' --stream-mmap --stream-count=1 --stream-to=y12-1920x1088.raw</code>
====== RAW-MIPI-AR0234M======
*raw8格式
<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=1920,height=1200,pixelformat=GREY --stream-mmap --stream-count=1 --stream-to=y8-1920x1200.raw</code>
*raw10格式
<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=1920,height=1200,pixelformat='Y10 ' --stream-mmap --stream-count=1 --stream-to=y10-1920x1200.raw</code>
PS. This y8 file can be used with this player: [https://yuv-player-deluxe.software.informer.com/2.6/ YUV Displayer Deluxe].
PS. This y8 file can be used with this player: [https://yuv-player-deluxe.software.informer.com/2.6/ YUV Displayer Deluxe].
=====Preview=====
On a raspberry pi 5, VLC for preview is now having problems and not working.
======Preview using VLC======
1. Open VLC with command line <code>vlc</code> , or click the icon to launch.
2. Hit the <code>▶</code>(Play) button to call the open media window.
3. In <code>Capture Device</code> >> <code>Device Selection</code> >> <code>Video device name</code>, select the camera video node.
4. Hit <code>Advanced Options...</code> button
5. Type in the <code>width</code> and <code>height</code>, for example, 1280 and 1024.
6. Hit <code>OK</code> to save the settings and see the video feed.
<br />[[File:Mvcam via VLC.png|center|thumb|800x800px|Play mv camera using VLC on RPI|link=http://wiki.veye.cc/index.php/File:Mvcam_via_VLC.png]]<br />
======Preview using qv4l2======
Install qv4l2，
<code>sudo apt install qv4l2</code>
1. Open VLC with command line <code>vlc</code> to launch.
2. Hit the <code>▶</code>(Play) button to call the open media window.[[File:Mvcam via qv4l2.png|center|thumb|800x800px|Play mv camera using qv4l2 on RPI|link=http://wiki.veye.cc/index.php/File:Mvcam_via_qv4l2.png]]
====== Preview UYVY format images using gstreamer ======
<code>export DISPLAY=:0</code>
For easy installation, the MV series cameras provide UYVY mode. The maximum width supported by UYVY mode is 2880, and real-time preview can be performed using the following command.
'''Note:''' To increase the maximum frame rate and bandwidth, some modules no longer support the UYVY format. Please use the "fmtcap" command in the script to read the registers to confirm the specific configuration.
* install gstreamer
<code>sudo apt-get install gstreamer1.0-tools</code>
<code>sudo apt-get install libx264-dev libjpeg-dev</code>
<code>sudo apt-get install libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev libgstreamer-plugins-bad1.0-dev gstreamer1.0-plugins-ugly gstreamer1.0-tools gstreamer1.0-gl gstreamer1.0-gtk3</code>
* MV-MIPI-IMX178M
<code>v4l2-ctl --set-selection=target=crop,top=0,left=0,width=2816,height=2064</code>
<code>gst-launch-1.0 v4l2src device=/dev/video0 ! "video/x-raw,format=(string)UYVY, width=(int)2816, height=(int)2064, framerate=(fraction)22/1" ! v4l2convert ! "video/x-raw,format=(string)NV12" ! autovideosink sync=false -v</code>
* MV-MIPI-SC130M, MV-MIPI-IMX296M, MV-MIPI-IMX265M，MV-MIPI-IMX264M，MV-MIPI-IMX287M
<code>v4l2-ctl --set-selection=target=crop,top=0,left=0,width=$WIDTH,height=$HEIGHT</code>
<code>v4l2-ctl --set-ctrl frame_rate=$FPS</code>
<code>gst-launch-1.0 v4l2src device=/dev/video0 ! "video/x-raw,format=(string)UYVY, width=(int)$WIDTH, height=(int)$HEIGHT,framerate=(fraction)$FPS/1" ! v4l2convert ! "video/x-raw,format=(string)NV12" ! autovideosink sync=false -v</code>
Or just simply：
<code>gst-launch-1.0 v4l2src device=/dev/video0 ! videoconvert ! autovideosink</code>
====== Preview GREY format images using opencv ======
* install opencv
<code>pip uninstall opencv-python</code>
<code>sudo apt install python3-opencv</code>
* Preview using this [https://github.com/veyeimaging/raspberrypi_v4l2/tree/main/samples/opencv/raw_camera sample]:
<code>python ./v4l2dev_2_opencv_show_grey.py --width 640 --height 480 --fps 30</code>
On Raspberry Pi 5, you need to add a <code>--ctldev /dev/v4l-subdev*</code> parameter to specify the subdev for configuring parameters.
==== Trigger mode ====
==== Trigger mode ====
This section takes IMX178 as an example to show the configuration and use of trigger mode. For other cameras, just refer to the width and height of the stream mode.
===== Set ROI and Framerate =====
<code>v4l2-ctl --set-ctrl roi_x=0</code>
<code>v4l2-ctl --set-ctrl roi_y=0</code>
<code>v4l2-ctl --set-selection=target=crop,top=0,left=0,width=3088,height=2064</code>
<code>v4l2-ctl --set-fmt-video=width=$WIDTH,height=$HEIGHT</code>
<code>v4l2-ctl --set-ctrl frame_rate=$FPS</code>
===== Software trigger mode =====
===== Software trigger mode =====
Note: script [https://github.com/veyeimaging/mvcam_raspberrypi/tree/main/mv_tools_rpi link].
Note: script [https://github.com/veyeimaging/mvcam_raspberrypi/tree/main/mv_tools_rpi link].
====Notes for CM4 ====
Cm4 supports the use of two cameras at the same time. Following above steps will only be able to use CAM1. To use two cameras, follow the following steps:
===== Hardware Connection =====
Refer to [https://www.raspberrypi.com/documentation/computers/compute-module.html this Raspberry Pi instruction] ， add jumper to J6.
===== Upgrade dt-blob.bin=====
<code>sudo wget <nowiki>https://datasheets.raspberrypi.com/cmio/dt-blob-dualcam.bin</nowiki> -O /boot/dt-blob.bin</code>
=====For Buster OS（kernel5.10）=====
Upgrade dual camera version dtbo file, use mvcam as an example：
<code>sudo cp raspberrypi_v4l2/release/driver_bin/$(uname -r)/veye_mvcam-cm4.dtbo /boot/overlays/veye_mvcam.dtbo</code>
<code>sudo reboot</code>
=====For Bullseye OS（kernel5.15） =====
Edit file<code>/boot/config.txt</code>，Add one line<code>dtoverlay=[camera],cam0</code>.
Take veye_mvcam as an example.
<code>[all]</code>
<code>dtparam=i2c_vc=on</code>
<code>dtoverlay=veye_mvcam</code>
<code>dtoverlay=veye_mvcam,cam0</code>
===== Device node description=====
The CM4 module uses two I2C channels to communicate with the two cameras respectively.
{| class="wikitable"
!description
!i2c bus num
!lane num
!video node
|-
|CAM0
|0
|2lane
|video0
|-
|CAM1
|10
|2lane or 4lane
|video2（Buster），video1（Bullseye）
|}Note: If there is only one camera, video node is always video0.
====Compiling drivers from source code====
====Compiling drivers from source code====
Please refer to: [http://wiki.veye.cc/index.php/Build_drivers_from_source_for_rpi Build drivers from source for rpi].
Please refer to: [http://wiki.veye.cc/index.php/Build_drivers_from_source_for_rpi Build drivers from source for rpi].
Set rising edge trigger
Set rising edge trigger
<code>./mv_mipi_i2c.sh -w -f trgedge -p1</code>
<code>./mv_mipi_i2c.sh -w -f trgedge -p1 0</code>
In addition, rich trigger attributes can be set for hard triggering, such as trigger delay, signal filtering, etc.
In addition, rich trigger attributes can be set for hard triggering, such as trigger delay, signal filtering, etc.
<code>python gpio_trigger.py</code>
<code>python gpio_trigger.py</code>
Note: script [https://github.com/veyeimaging/mvcam_raspberrypi/tree/main/mv_tools_rpi link].
Note: script [https://github.com/veyeimaging/mvcam_raspberrypi/tree/main/mv_tools_rpi link].<br />
====Notes for CM4====
Regarding the descriptions of hardware connections, dtbo, and i2cbus, please refer to the previous sections.
As for accessing two cameras separately using 'mv_raspicam,' the methods are as follows:
* Preview CAM0
<code>./mv_raspicam -t -1 -c 0 -y 0</code>
* Preview CAM1
<code>./mv_raspicam -t -1 -c 1 -y 10</code>
=== Raw data format ===
==== Unpacked image format(padded) ====
==== Unpacked image format(padded) ====
For 10bit depth and 12bit depth pixel data, two bytes are always used to store one pixel. The V4L2 standard 'Y10 ', 'Y12 ' formats are stored in this way.
For 10bit depth and 12bit depth pixel data, two bytes are always used to store one pixel. The V4L2 standard 'Y10 ' (10-bit Greyscale),'Y12 ' (12-bit Greyscale)formats are stored in this way.
This storage method is convenient for software processing, but has the disadvantage of taking up more space.
This storage method is convenient for software processing, but has the disadvantage of taking up more space.
==== Packed image format ====
==== Packed image format ====
The data format saved by mv_raspicam is the data format on the MIPS bus, with no empty bit padding between pixels.
The data format saved by mv_raspicam is the data format on the MIPS bus, with no empty bit padding between pixels.
The V4L2 standard'Y10P' (10-bit Greyscale (MIPI Packed)),'Y12P' (12-bit Greyscale (MIPI Packed))formats are stored in this way.
[[File:Packed raw data layer.png|center|thumb|1200x1200px|Packed raw data layer]]
[[File:Packed raw data layer.png|center|thumb|1200x1200px|Packed raw data layer]]
<br />
<br />
===i2c script for parameter configuration===
===i2c script for parameter configuration===
We provide shell scripts to configure the parameters.
We provide shell scripts to configure the parameters.
https://github.com/veyeimaging/raspberrypi_v4l2/tree/main/mv_tools_rpi
[http://wiki.veye.cc/index.php/Mv_mipi_i2c.sh_user_guide mv_mipi_i2c.sh user guide]
[http://wiki.veye.cc/index.php/Mv_mipi_i2c.sh_user_guide mv_mipi_i2c.sh user guide]
=== Document History ===
=== Document History ===
* 2024-01-01
Add support for Raspberrypi 5.
*2023-08-16
Add support for RAW-MIPI-IMX462M and RAW-MIPI-AR0234M.
* 2023-06-07
Add preview method using qv4l2 and VLC.
* 2023-04-14
With the new version of the driver, the flip operation has been removed, and a new ROI configuration method has been added.
* 2023-03-29
Add opencv samples.
*2023-03-26
Add support for MV-MIPI-IMX287M.
*2023-03-04
Add the instructions related to CM4 in Bullseye system.
* 2023-02-10
Add note for CM4.
* 2022-12-08
Add support for the new MV-MIPI-IMX264M camera model.
* 2022-11-02
Add support for the new IMX265 and SC132 models.
* 2022-05-16
* 2022-05-16