MV Camera on Firfly Boards - Revision history

Bluewhale: /* Document History */

2025-12-26T07:21:06Z

Document History

Bluewhale: /* Upgrade Firefly Ubuntu system */

2025-12-26T07:11:01Z

Upgrade Firefly Ubuntu system

Bluewhale: /* Introduction to github repositories */

2025-12-26T07:09:18Z

Introduction to github repositories

Show changes

Xumm: /* Application examples */

2025-07-10T06:23:45Z

Application examples

Xumm at 09:17, 14 April 2025

2025-04-14T09:17:13Z

Xumm: /* Example of import image to OpenCV */

2025-04-14T07:03:45Z

Example of import image to OpenCV

Xumm: /* State Detection and Environment Variable Configuration */

2025-03-23T07:52:29Z

State Detection and Environment Variable Configuration

Xumm: /* Document History */

2025-03-23T07:46:27Z

Document History

Xumm: /* State Detection and Environment Variable Configuration */

2025-03-23T07:45:09Z

State Detection and Environment Variable Configuration

Xumm: /* Configuring global variables */

2025-03-23T07:44:49Z

Configuring global variables

@@ Line 171: / Line 171: @@
 https://wiki.t-firefly.com/en/Firefly-Linux-Guide/index.html
 ===Document History===
 *2025-04-14

@@ Line 150: / Line 150: @@
 After successfully identifying the camera, the camera will be recognized as /dev/video0.
-=== Camera Application Development Guide ===
+===Camera Application Development Guide===
 [[MV Camera Application Development Guide on Rochchip|Application Development Guide]]
 ===References===

@@ Line 403: / Line 403: @@
 *raw12
-<code>v4l2-ctl -d /dev/video0 --set-fmt-video=$WIDTH,height=$HEIGHT,pixelformat='Y12 ' --stream-mmap --stream-count=1 --stream-to=y12-${WIDTH}x${HEIGHT}.raw</code>
+<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat='Y12 ' --stream-mmap --stream-count=1 --stream-to=y12-${WIDTH}x${HEIGHT}.raw</code>
 Please refer to the description in the previous section for the image format.

@@ Line 4: / Line 4: @@
 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 and ROC-RK3588S-PC board as an example to introduce how to connect MV and RAW series cameras to the RK3566/3K3568 and RK3588S/RK3588 system.
+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).
@@ Line 36: / Line 36: @@
 |MV series
 |MV-MIPI-IMX264M
 |Done
 |-
@@ Line 110: / Line 114: @@
 === Upgrade Firefly Ubuntu system ===
-For the ROC-RK3566-PC and ROC-RK3588S-PC, we have provided an image of the release 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]to burn in a standard system.
+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===
@@ Line 134: / Line 138: @@
 On the ROC-RK3588S-PC, the camera is mounted on i2c-7, with an i2c address of 0x3b.
-On the ROC-RK3566-PC, the camera is mounted on i2c-4.
+On the ROC-RK3566-PC and ROC-RK3576-PC, the camera is mounted on i2c-4.
 * Check the video0 device node:
@@ Line 193: / Line 197: @@
 <code>export I2C_BUS=7</code>
-* ROC-RK3566-PC
+* ROC-RK3566-PC and ROC-RK3576-PC
 <code>export I2C_BUS=4</code>
@@ Line 481: / Line 485: @@
 https://wiki.t-firefly.com/en/ROC-RK3588S-PC/
 *Firefly Linux User Guide
@@ Line 486: / Line 494: @@
 https://wiki.t-firefly.com/en/Firefly-Linux-Guide/index.html
 ===Document History===
 * 2025-03-23

@@ Line 418: / Line 418: @@
 <code>sudo apt install python3-opencv</code>
-See the [https://github.com/veyeimaging/rk356x_firefly/tree/main/linux/samples samples] directory on github for details.
+See the [https://github.com/veyeimaging/rk35xx_veye_bsp/tree/main/samples samples] directory on github for details.
 <code>python ./v4l2dev_2_opencv_show_grey.py --width 1456 --height 1088 --fps 60 --i2c 7</code>

@@ Line 145: / Line 145: @@
 After successfully identifying the camera, the camera will be recognized as /dev/video0.
 ==== Using media-ctl to view topology ====
 Using the media-ctl command can clearly display the current topography structure.
@@ Line 248: / Line 298: @@
 === Application examples ===
 ==== Configure parameters using v4l2-ctl ====
 <code>$ v4l2-ctl -d /dev/v4l-subdev2 -L</code>

@@ Line 249: / Line 249: @@
 === Application examples ===
 ===='''State Detection and Environment Variable Configuration'''====
-[https://github.com/veyeimaging/nvidia_jetson_veye_bsp/tree/master/mv_tools_jetson/i2c_tools Here], we provide an <code>mv_probe.sh</code> script that automatically detects the connected camera and configures environment variables with its default model, width, height, frame rate, and other information.
+[https://github.com/veyeimaging/rk35xx_veye_bsp/tree/main/mv_tools_rockchip/i2c_tools Here], we provide an <code>mv_probe.sh</code> script that automatically detects the connected camera and configures environment variables with its default model, width, height, frame rate, and other information.
 Usage:

@@ Line 248: / Line 248: @@
 === Application examples ===
-====Configuring  global variables====
+Usage:
-<code>export WIDTH=1280</code>
+<code>source ./mv_probe.sh</code>
-<code>export HEIGHT=1024</code>
+A typical output:
-<code>export FPS=108</code>
+<code>$ source ./mv_probe.sh</code>
-*MV-MIPI-IMX296M
+<code>The mvcam driver is loaded on i2c-10, but the camera is not detected!</code>
-<code>export WIDTH=1456</code>
+<code>Found veye_mvcam camera on i2c-11.</code>
-<code>export HEIGHT=1088</code>
+<code>Setenv CAMERAMODEL = RAW-MIPI-SC535M</code>
-<code>export FPS=60</code>
+<code>Setenv FPS = 49</code>
-*MV-MIPI-IMX287M
+<code>Setenv HEIGHT = 2048</code>
-<code>export WIDTH=704</code>
+<code>Setenv WIDTH = 2432</code>
-<code>export HEIGHT=544</code>
+You can verify the environment variable output using:
-<code>export FPS=319</code>
+<code>echo $CAMERAMODEL</code>
-*MV-MIPI-IMX265M
+Note that these environment variables are only valid for the current session.
-<code>export WIDTH=2048</code>
+'''Important Notes:'''
-<code>export HEIGHT=1544</code>
+*This script requires the <code>mvcam</code> driver version '''1.1.06 or later'''.
-<code>export FPS=45</code>
+Example:
 <code>export WIDTH=2432</code>
-<code>export HEIGHT=2056</code>
+<code>export HEIGHT=2048</code>
-<code>export FPS=28</code>
+<code>export FPS=50</code>
-*RAW-MIPI-SC132M
+* ROC-RK3588S-PC
-<code>export WIDTH=1024</code>
+<code>export I2C_BUS=7</code>
-<code>export HEIGHT=1280</code>
+* ROC-RK3566-PC
-<code>export FPS=120</code>
+<code>export I2C_BUS=4</code>
 ==== Configure parameters using v4l2-ctl ====
 <code>$ v4l2-ctl -d /dev/v4l-subdev2 -L</code>