Difference between revisions of "GX Camera on Firfly Boards"

Latest revision as of 14:18, 30 December 2025

How to use the GX series cameras on the Firefly board

1 Overview

The GX series cameras are designed for embedded AI applications. They offer high-performance ISP capabilities, support multiple operating modes, provide a wide range of configurable features, and are built with a robust and reliable design. The cameras use the MIPI CSI-2 interface and are well suited for embedded computing platforms.

This article uses the Firefly ROC-RK3588S-PC, ROC-RK3576-PC, and ROC-RK3566-PC boards as examples to describe how to connect GX series cameras to RK3566/RK3568, RK3576, and RK3588S/RK3588-based systems.

Linux drivers are provided for the GX series cameras, with Ubuntu used as the reference operating system.

1.1 Camera Module List

Series	Model	Status
GX series	GX-MIPI-IMX662	Done

1.2 Supported boards

manufacturers	model	status
Firefly	ROC-RK3588S-PC	Done
Firefly	ROC-RK3576-PC	TBD
Firefly	ROC-RK3566-PC	TBD

2 Hardware Setup

Firefly boards use a 30-pin camera connector, while GX series cameras feature a 22-pin interface and require an independent 5 V power supply. Therefore, a dedicated FFC adapter cable and a separate power cable have been designed to support proper connection and power delivery.

2.1 Connection Diagram

GX Camera to Firfly

3 Introduction to the GitHub Repos

3.1 General part of the Rockchip platform

https://github.com/veyeimaging/rk35xx_veye_bsp

includes：

driver source code
i2c toolkits
application demo

3.2 Firefly Board–Related Resources

https://github.com/veyeimaging/rk35xx_firefly

This repository mainly includes the following contents:

Device Tree Source (DTS) files and compiled DTB files
Driver compilation and build instructions

3.3 Board Image Flashing

Precompiled Linux system images are provided in the GitHub Releases section.

4 Upgrade Firefly Ubuntu system

For the ROC-RK3566-PC, ROC-RK3576-PC, and ROC-RK3588S-PC boards, we provide release-version system images for flashing.

Please locate the system image corresponding to your specific board that includes support for GX series cameras from the previously mentioned download paths.

Refer to the official Firefly documentation (ROC-RK3588S-PC ROC-RK3566-PC ROC-RK3576-PC) for detailed instructions on flashing the system image.

5 Check system status

5.1 Camera Detection

After completing the system installation and connecting the camera hardware, power on the system. On the Firefly board, execute the following command to verify whether the camera has been detected correctly:

$ dmesg | grep gxcam

There should be similar prompts like the following:

[6.667547] gxcam 7-003b: veye gx series camera driver version: 01.00.01

[6.781681] gxcam 7-003b: camera is: GX-MIPI-IMX662

[6.820210] gxcam 7-003b: Success to get gxcam endpoint data lanes, dts uses 2 lanes,will set to camera

[6.834597] gxcam 7-003b: gxcam_enum_controls success

[6.891209] rockchip-csi2-dphy csi2-dphy0: dphy0 matches m00_b_gxcam 7-003b:bus type 5

From the log messages above, it can be confirmed that the detected camera model is GX-MIPI-IMX662.

The identifier 7-003b indicates that the camera is connected to I²C bus 7 with an I²C address of 0x3b.

On the ROC-RK3588S-PC, the camera is connected to i2c-7
On the ROC-RK3566-PC and ROC-RK3576-PC, the camera is connected to i2c-4

Next, execute the following command to check the video device node:

ls /dev/video0

If the output shows:

video0

this indicates that the camera has been successfully registered as /dev/video0.

At this point, both the camera hardware installation and driver setup are complete. For further application development, please refer to the following sections.

6 Camera Application Development Guide

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-20

The document format was adjusted, it was appropriately polished.

2025-11-28

The first version.

@@ Line 1: / Line 1: @@
-[https://wiki.veye.cc/index.php/GX_Camera_on_Firfly_Boards/zh 查看中文]
+[[GX Camera on Firfly Boards/zh|查看中文]]
 '''<big>How to use the GX series cameras on the Firefly board</big>'''
 ===Overview===
-The GX series cameras are designed for embedded AI applications. They feature outstanding ISP performance, multiple working modes, a wide range of functional options, and reliable stability design. They use the MIPI CSI-2 interface and are particularly suitable for use in embedded computing platforms.
+The GX series cameras are designed for embedded AI applications. They offer high-performance ISP capabilities, support multiple operating modes, provide a wide range of configurable features, and are built with a robust and reliable design. The cameras use the MIPI CSI-2 interface and are well suited for embedded computing platforms.
-This article takes the Firefly's ROC-RK3588S-PC, ROC-RK3576-PC and ROC-RK3566-PC motherboards as examples to introduce how to connect the GX series cameras to the RK3566/3K3568, RK3576 and RK3588S/RK3588 systems.
+This article uses the Firefly ROC-RK3588S-PC, ROC-RK3576-PC, and ROC-RK3566-PC boards as examples to describe how to connect GX series cameras to RK3566/RK3568, RK3576, and RK3588S/RK3588-based systems.
-We provide drivers for the Linux operating system (taking Ubuntu as an example).
+Linux drivers are provided for the GX series cameras, with Ubuntu used as the reference operating system.
 ====Camera Module List====
@@ Line 21: / Line 21: @@
 |}
-====Supported motherboards====
+====Supported boards====
 {| class="wikitable"
 !manufacturers
@@ Line 29: / Line 29: @@
 |Firefly
 |ROC-RK3588S-PC
-|accomplish
+|Done
 |-
 |Firefly
@@ Line 41: / Line 41: @@
 ===Hardware Setup===
-The motherboard of Firefly uses a 30-pin connector, while the GX series cameras have a 22-pin interface and require independent 5V power supply. Therefore, we have designed dedicated adapter cables (FFC cables) and power supply lines.
+Firefly boards use a 30-pin camera connector, while GX series cameras feature a 22-pin interface and require an independent 5 V power supply. Therefore, a dedicated FFC adapter cable and a separate power cable have been designed to support proper connection and power delivery.
-=====Connection of GX 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====
+=====Connection Diagram=====
-[[File:VBYONE connection with rk3588.jpg|center|thumb|800x800px|VBYONE connection with rk3588]]
+<br />[[File:Gx to firfly.png|alt=GX Camera to Firfly|center|thumb|800x800px|GX Camera to Firfly]]
+<br />
-===Introduction to the GitHub Library===
+===Introduction to the GitHub Repos===
 ====General part of the Rockchip platform====
 https://github.com/veyeimaging/rk35xx_veye_bsp
@@ Line 89: / Line 57: @@
 *application demo
-Domestic users can access the Gitee repository:
+====Firefly Board–Related Resources====
+https://github.com/veyeimaging/rk35xx_firefly
-https://gitee.com/veyeimaging/rk35xx_veye_bsp
-====Firefly motherboard-related sections====
-<nowiki>https://github.com/veyeimaging/rk35xx_firefly</nowiki>
-Including the following main contents:
-*DTS source code and DTB files
-*Driver compilation guidance document
-Domestic users can access the Gitee repository:
-<nowiki>https://gitee.com/veyeimaging/rk35xx_firefly</nowiki>
+This repository mainly includes the following contents:
-====Board firmware image writing====
+*Device Tree Source (DTS) files and compiled DTB files
-In the GitHub releases, a pre-compiled Linux system image is provided.
+*Driver compilation and build instructions
-Domestic users can download it through Baidu Cloud:https://pan.baidu.com/s/1LdK0n_uCx1yGej4PB8-bxg?pwd=yft9。
+====Board Image Flashing====
+Precompiled Linux system images are provided in the [https://github.com/veyeimaging/rk356x_firefly/releases GitHub ''Releases'' section].
 ===Upgrade Firefly Ubuntu system===
-For ROC-RK3566-PC, ROC-RK3576-PC and ROC-RK3588S-PC, we have provided the flashing images for the release system.
+For the ROC-RK3566-PC, ROC-RK3576-PC, and ROC-RK3588S-PC boards, we provide release-version system images for flashing.
-In the download path mentioned earlier, locate the corresponding image for the motherboard that supports the GX series camera products.
+Please locate the system image corresponding to your specific board that includes support for GX series cameras from the previously mentioned download paths.
-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/upgrade_bootmode.html ROC-RK3576-PC]） , and write the system.
+Refer to the official 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/upgrade_bootmode.html ROC-RK3576-PC]) for detailed instructions on flashing the system image.
 ===Check system status===
-====Whether the camera is correctly recognized====
+====Camera Detection====
-After completing the system installation and connecting the camera to the hardware, the system is powered on. Execute the following command on the Firefly board to check if the camera is connected correctly.
+After completing the system installation and connecting the camera hardware, power on the system. On the Firefly board, execute the following command to verify whether the camera has been detected correctly:
 <code>$ dmesg | grep gxcam</code>
@@ Line 136: / Line 94: @@
 <code>[6.891209] rockchip-csi2-dphy csi2-dphy0: dphy0 matches m00_b_gxcam 7-003b:bus type 5</code>
-By analyzing the above prompt information, it can be seen that the current camera model is GX-MIPI-IMX662.
+From the log messages above, it can be confirmed that the detected camera model is '''GX-MIPI-IMX662'''.
-From the 7-003b information, it can be seen that the current i2c bus number of the camera is 7 and the i2c address is 0x3b.
+The identifier <code>7-003b</code> indicates that the camera is connected to '''I²C bus 7''' with an '''I²C address of 0x3b'''.
-On ROC-RK3588S-PC, the camera is mounted on i2c-7; on ROC-RK3566-PC and ROC-RK3576-PC, the camera is mounted on i2c-4.
+*On the '''ROC-RK3588S-PC''', the camera is connected to '''i2c-7'''
+*On the '''ROC-RK3566-PC''' and '''ROC-RK3576-PC''', the camera is connected to '''i2c-4'''
-*Check the video0 device node:
+Next, execute the following command to check the video device node:
 <code>ls /dev/video0</code>
-You should see:
+If the output shows:
 <code>video0</code>
-After correctly identifying the camera, the camera is recognized as /dev/video0.
+this indicates that the camera has been successfully registered as <code>/dev/video0</code>.
-At this point, the hardware installation of the camera and the driver installation have been completed. For subsequent application development, please refer to the following article.
+At this point, both the camera hardware installation and driver setup are complete. For further application development, please refer to the following sections.
 ===Camera Application Development Guide===
-Application Development Guide
+[[GX Camera Application Development Guide|Application Development Guide]]
 ===References===
@@ Line 176: / Line 135: @@
 ===Document History===
-*2025-12-06
+*2025-12-20
-The document format was adjusted and it was appropriately revised.
+The document format was adjusted, it was appropriately polished.
 *2025-11-28