Difference between revisions of "MV Camera on Firfly Boards"
| (33 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[[MV Camera on Firfly Boards/zh|查看中文]] | [[MV Camera on Firfly Boards/zh|查看中文]] | ||
| + | |||
| + | ===Overview=== | ||
| + | The MV series and RAW series cameras are cameras designed for AI applications in the industrial field. They use the MIPI CSI-2 interface and are particularly suitable for use with embedded computing platforms. They have rich data formats and triggering features, extremely low latency, high bandwidth, and reliable stability. | ||
| + | |||
| + | This article takes Firefly's ROC-RK3566-PC,ROC-RK3576-PCand ROC-RK3588S-PC board as an example to introduce how to connect MV and RAW series cameras to the RK3566/3K3568 ,RK3576 and RK3588S/RK3588 system. | ||
| + | |||
| + | We provide drivers for the Linux operating system (using Ubuntu as an example). | ||
| + | |||
| + | ====Camera Module List==== | ||
| + | {| class="wikitable" | ||
| + | !Series | ||
| + | !Model | ||
| + | !Status | ||
| + | |- | ||
| + | |MV series | ||
| + | |MV-MIPI-IMX178M | ||
| + | |Done | ||
| + | |- | ||
| + | |MV series | ||
| + | |MV-MIPI-SC130M | ||
| + | |Done | ||
| + | |- | ||
| + | |MV series | ||
| + | |MV-MIPI-IMX296M | ||
| + | |Done | ||
| + | |- | ||
| + | |MV series | ||
| + | |MV-MIPI-IMX287M | ||
| + | |Done | ||
| + | |- | ||
| + | |MV series | ||
| + | |MV-MIPI-IMX265M | ||
| + | |Done | ||
| + | |- | ||
| + | |MV series | ||
| + | |MV-MIPI-IMX264M | ||
| + | |Done | ||
| + | |- | ||
| + | |MV series | ||
| + | |MV-MIPI-GMAX4002M | ||
| + | |Done | ||
| + | |- | ||
| + | |RAW series | ||
| + | |RAW-MIPI-SC132M | ||
| + | |Done | ||
| + | |- | ||
| + | |RAW series | ||
| + | |RAW-MIPI-IMX462M | ||
| + | |Done | ||
| + | |- | ||
| + | |RAW series | ||
| + | |RAW-MIPI-AR0234M | ||
| + | |Done | ||
| + | |- | ||
| + | |RAW series | ||
| + | |RAW-MIPI-SC535M | ||
| + | |Done | ||
| + | |} | ||
| + | In addition, the driver for the V-by-One HS connection mode has been finished on the Ubuntu system. | ||
| + | |||
| + | ===Hardware Setup=== | ||
| + | The MV series and RAW series cameras require an [[ADP-MV2 Adapter Board Data Sheet/zh|ADP-MV2]] adapter board to connect to the ROC-RK35xx-PC motherboard. | ||
| + | |||
| + | ====Connection of new ADP-MV2==== | ||
| + | |||
| + | =====Connection of MV series camera and ADP-MV2===== | ||
| + | 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-MV2-V2 to MV-MIPI-X.jpg|alt=|center|thumb|600x600px|ADP-MV2 to MV-MIPI-X|link=http://wiki.veye.cc/index.php/File:ADP-MV2-V2_to_MV-MIPI-X.jpg]] | ||
| + | |[[File:ADP-MV2-V2 to MV-MIPI-X No.2.jpg|alt=|center|thumb|600x600px|ADP-MV2 to MV-MIPI-X|link=http://wiki.veye.cc/index.php/File:ADP-MV2-V2_to_MV-MIPI-X_No.2.jpg]] | ||
| + | |} | ||
| + | |||
| + | =====Connection of RAW-MIPI-SC132M and ADP-MV2===== | ||
| + | The two are connected using 1.0 mm pitch*15P FFC cable with opposite-side contacts. The cable must be inserted with the silver contacts facing outside. | ||
| + | {| class="wikitable" | ||
| + | !TOP | ||
| + | !BOTTOM | ||
| + | |- | ||
| + | |[[File:ADP-MV2 to RAW-MIPI-SC132M.jpg|alt=|center|thumb|600x600px|ADP-MV2 to RAW-MIPI-SC132M|link=http://wiki.veye.cc/index.php/File:ADP-MV2_to_RAW-MIPI-SC132M.jpg]] | ||
| + | |[[File:ADP-MV2 to RAW-MIPI-SC132M No.2.jpg|alt=ADP-MV2 to RAW-MIPI-SC132M|center|thumb|600x600px|ADP-MV2 to RAW-MIPI-SC132M|link=http://wiki.veye.cc/index.php/File:ADP-MV2_to_RAW-MIPI-SC132M_No.2.jpg]] | ||
| + | |} | ||
| + | =====Connection of other RAW series camera and ADP-MV2===== | ||
| + | The two are connected using 0.5 mm pitch*pin FFC cable with opposite-side contacts. The cable must be inserted with the silver contacts facing outside. | ||
| + | {| class="wikitable" | ||
| + | !TOP | ||
| + | !BOTTOM | ||
| + | |- | ||
| + | |[[File:ADP-MV2 to RAW series camera.jpg|alt=|center|thumb|600x600px|ADP-MV2 to RAW series camera|link=http://wiki.veye.cc/index.php/File:ADP-MV2_to_RAW_series_camera.jpg]] | ||
| + | |[[File:ADP-MV2 to RAW series camera No.2.jpg|alt=ADP-MV2 to RAW series camera No.2|center|thumb|600x600px|ADP-MV2 to RAW series camera|link=http://wiki.veye.cc/index.php/File:ADP-MV2_to_RAW_series_camera_No.2.jpg]] | ||
| + | |} | ||
| + | =====Connection with Main board using ADP-MV2===== | ||
| + | The two are connected using 0.5mm pitch * 30P FFC coaxial wires, paying attention to the direction of the contact surfaces, silver contacts facing outside on the ADP-MV2 and facing inside on the RK board. | ||
| + | <br />[[File:RK-ADP-MV2-V2-RAW-MIPI 02.jpg|alt=|center|thumb|800x800px|RK to ADP-MV2 and MV cam|link=http://wiki.veye.cc/index.php/File:RK-ADP-MV2-V2-RAW-MIPI_02.jpg]] | ||
| + | |||
| + | ====V-by-One-HS-KIT Camera Connection Diagram==== | ||
| + | [[File:VBYONE connection with rk3588.jpg|center|thumb|800x800px|VBYONE connection with rk3588]] | ||
| + | <br /> | ||
| + | ===Introduction to github repositories=== | ||
| + | https://github.com/veyeimaging/rk35xx_veye_bsp | ||
| + | |||
| + | https://github.com/veyeimaging/rk35xx_firefly | ||
| + | |||
| + | includes: | ||
| + | |||
| + | *driver source code | ||
| + | *i2c toolkits | ||
| + | *application demo | ||
| + | |||
| + | In addition, a compiled linux kernel installation package and Android image is provided in the [https://github.com/veyeimaging/rk356x_firefly/releases releases]. | ||
| + | |||
| + | ===Upgrade Firefly Ubuntu system=== | ||
| + | For the ROC-RK3566-PC,ROC-RK3576-PC and ROC-RK3588S-PC, we have provided an image of the release system. | ||
| + | |||
| + | Download the latest Ubuntu imge from https://github.com/veyeimaging/rk35xx_firefly/releases/ . | ||
| + | |||
| + | Refer to the Firefly documentation [https://wiki.t-firefly.com/en/ROC-RK3588S-PC/upgrade_bootmode.html ROC-RK3588S-PC] [https://wiki.t-firefly.com/en/ROC-RK3566-PC/03-upgrade_firmware.html ROC-RK3566-PC] [https://wiki.t-firefly.com/en/ROC-RK3576-PC/03-upgrade_firmware.html ROC-RK3576-PC] to burn in a standard system. | ||
| + | ===Check system status=== | ||
| + | |||
| + | ====Whether the camera is correctly recognized==== | ||
| + | After system update, reboot the main board. | ||
| + | |||
| + | Execute the following command on the main board to check if the camera is properly connected. | ||
| + | |||
| + | <code>dmesg | grep mvcam</code> | ||
| + | |||
| + | You can see the camera model and the camera version number probed. | ||
| + | |||
| + | A prompt as below indicates that the MV-MIPI-IMX296M camera is detected on the i2c-7 bus. | ||
| + | |||
| + | <code>mvcam 7-003b: camera is:MV-MIPI-IMX296M</code> | ||
| + | |||
| + | <code>mvcam 7-003b: firmware version: 0x1290133</code> | ||
| + | |||
| + | On the ROC-RK3588S-PC, the camera is mounted on i2c-7, with an i2c address of 0x3b. | ||
| + | |||
| + | On the ROC-RK3566-PC and ROC-RK3576-PC, the camera is mounted on i2c-4. | ||
| + | |||
| + | *Check the video0 device node: | ||
| + | |||
| + | <code>ls /dev/video0</code> | ||
| + | |||
| + | You should see: | ||
| + | |||
| + | <code>video0</code> | ||
| + | |||
| + | After successfully identifying the camera, the camera will be recognized as /dev/video0. | ||
| + | |||
| + | ===Camera Application Development Guide=== | ||
| + | [[MV Camera Application Development Guide on Rochchip|Application Development Guide]] | ||
| + | |||
| + | ===References=== | ||
| + | |||
| + | *ROC-RK3566-PC Manual | ||
| + | |||
| + | https://wiki.t-firefly.com/en/ROC-RK3566-PC/ | ||
| + | |||
| + | *ROC-RK3588S-PC Manual | ||
| + | |||
| + | https://wiki.t-firefly.com/en/ROC-RK3588S-PC/ | ||
| + | |||
| + | *ROC-RK3576-PC Manual | ||
| + | |||
| + | https://wiki.t-firefly.com/en/ROC-RK3576-PC/ | ||
| + | |||
| + | *Firefly Linux User Guide | ||
| + | |||
| + | https://wiki.t-firefly.com/en/Firefly-Linux-Guide/index.html | ||
| + | ===Document History=== | ||
| + | |||
| + | * 2025-12-26 | ||
| + | |||
| + | Add a chapter on application development guidelines | ||
| + | |||
| + | *2025-04-14 | ||
| + | |||
| + | Add support for RK3576. | ||
| + | |||
| + | *2025-03-23 | ||
| + | |||
| + | Add description of mv_probe.sh. | ||
| + | |||
| + | *2024-07-09 | ||
| + | |||
| + | Add support for RAW-MIPI-SC535M. | ||
| + | |||
| + | *2024-04-17 | ||
| + | |||
| + | Support RK3566. | ||
| + | |||
| + | *2024-03-10 | ||
| + | |||
| + | Add pictures and descriptions of hardware connections for the new version of ADP-MV2. | ||
| + | |||
| + | *2023-08-30 | ||
| + | |||
| + | Add support for RAW-MIPI-IMX462M and RAW-MIPI-AR0234M. | ||
| + | |||
| + | *2023-07-31 | ||
| + | |||
| + | Support V-by-One on ubuntu system. | ||
| + | |||
| + | *2023-04-12 | ||
| + | |||
| + | Release 1st version.<br /> | ||
Latest revision as of 15:21, 26 December 2025
1 Overview
The MV series and RAW series cameras are cameras designed for AI applications in the industrial field. They use the MIPI CSI-2 interface and are particularly suitable for use with embedded computing platforms. They have rich data formats and triggering features, extremely low latency, high bandwidth, and reliable stability.
This article takes Firefly's ROC-RK3566-PC,ROC-RK3576-PCand ROC-RK3588S-PC board as an example to introduce how to connect MV and RAW series cameras to the RK3566/3K3568 ,RK3576 and RK3588S/RK3588 system.
We provide drivers for the Linux operating system (using Ubuntu as an example).
1.1 Camera Module List
| Series | Model | Status |
|---|---|---|
| MV series | MV-MIPI-IMX178M | Done |
| MV series | MV-MIPI-SC130M | Done |
| MV series | MV-MIPI-IMX296M | Done |
| MV series | MV-MIPI-IMX287M | Done |
| MV series | MV-MIPI-IMX265M | Done |
| MV series | MV-MIPI-IMX264M | Done |
| MV series | MV-MIPI-GMAX4002M | Done |
| RAW series | RAW-MIPI-SC132M | Done |
| RAW series | RAW-MIPI-IMX462M | Done |
| RAW series | RAW-MIPI-AR0234M | Done |
| RAW series | RAW-MIPI-SC535M | Done |
In addition, the driver for the V-by-One HS connection mode has been finished on the Ubuntu system.
2 Hardware Setup
The MV series and RAW series cameras require an ADP-MV2 adapter board to connect to the ROC-RK35xx-PC motherboard.
2.1 Connection of new ADP-MV2
2.1.1 Connection of MV series camera and ADP-MV2
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.
| TOP | BOTTOM |
|---|---|
2.1.2 Connection of RAW-MIPI-SC132M and ADP-MV2
The two are connected using 1.0 mm pitch*15P FFC cable with opposite-side contacts. The cable must be inserted with the silver contacts facing outside.
| TOP | BOTTOM |
|---|---|
2.1.3 Connection of other RAW series camera and ADP-MV2
The two are connected using 0.5 mm pitch*pin FFC cable with opposite-side contacts. The cable must be inserted with the silver contacts facing outside.
| TOP | BOTTOM |
|---|---|
2.1.4 Connection with Main board using ADP-MV2
The two are connected using 0.5mm pitch * 30P FFC coaxial wires, paying attention to the direction of the contact surfaces, silver contacts facing outside on the ADP-MV2 and facing inside on the RK board.
2.2 V-by-One-HS-KIT Camera Connection Diagram
3 Introduction to github repositories
https://github.com/veyeimaging/rk35xx_veye_bsp
https://github.com/veyeimaging/rk35xx_firefly
includes:
- driver source code
- i2c toolkits
- application demo
In addition, a compiled linux kernel installation package and Android image is provided in the releases.
4 Upgrade Firefly Ubuntu system
For the ROC-RK3566-PC,ROC-RK3576-PC and ROC-RK3588S-PC, we have provided an image of the release system.
Download the latest Ubuntu imge from https://github.com/veyeimaging/rk35xx_firefly/releases/ .
Refer to the Firefly documentation ROC-RK3588S-PC ROC-RK3566-PC ROC-RK3576-PC to burn in a standard system.
5 Check system status
5.1 Whether the camera is correctly recognized
After system update, reboot the main board.
Execute the following command on the main board to check if the camera is properly connected.
dmesg | grep mvcam
You can see the camera model and the camera version number probed.
A prompt as below indicates that the MV-MIPI-IMX296M camera is detected on the i2c-7 bus.
mvcam 7-003b: camera is:MV-MIPI-IMX296M
mvcam 7-003b: firmware version: 0x1290133
On the ROC-RK3588S-PC, the camera is mounted on i2c-7, with an i2c address of 0x3b.
On the ROC-RK3566-PC and ROC-RK3576-PC, the camera is mounted on i2c-4.
- Check the video0 device node:
ls /dev/video0
You should see:
video0
After successfully identifying the camera, the camera will be recognized as /dev/video0.
6 Camera Application Development Guide
7 References
- ROC-RK3566-PC Manual
https://wiki.t-firefly.com/en/ROC-RK3566-PC/
- ROC-RK3588S-PC Manual
https://wiki.t-firefly.com/en/ROC-RK3588S-PC/
- ROC-RK3576-PC Manual
https://wiki.t-firefly.com/en/ROC-RK3576-PC/
- Firefly Linux User Guide
https://wiki.t-firefly.com/en/Firefly-Linux-Guide/index.html
8 Document History
- 2025-12-26
Add a chapter on application development guidelines
- 2025-04-14
Add support for RK3576.
- 2025-03-23
Add description of mv_probe.sh.
- 2024-07-09
Add support for RAW-MIPI-SC535M.
- 2024-04-17
Support RK3566.
- 2024-03-10
Add pictures and descriptions of hardware connections for the new version of ADP-MV2.
- 2023-08-30
Add support for RAW-MIPI-IMX462M and RAW-MIPI-AR0234M.
- 2023-07-31
Support V-by-One on ubuntu system.
- 2023-04-12
Release 1st version.