Difference between revisions of "Rockchip platform Application Note Index"

Latest revision as of 15:09, 24 April 2024

1 Main App Note

1.1 VEYE and CS series camera

1.2 MV and RAW series camera

2 I2C user guide

For the parameter configuration aspect of the camera module, we use the DRA (Direct Register Access) approach instead of encapsulating the interface in the v4l2 driver in order to achieve better flexibility and a more direct parameter configuration function.

The following shell scripts can be used directly or embedded into your programs. Of course, by reading their source codes, you will be able to see the registers and access methods corresponding to each function.

2.1 veye_mipi_i2c.sh

Applicable models: VEYE-MIPI-290/327,VEYE-MIPI-IMX327S,VEYE-MIPI-IMX462,VEYE-MIPI-IMX385.

VEYE-MIPI-290/327 I2C.sh user guide

2.2 cs_mipi_i2c.sh

Applicable models: CS-MIPI-IMX307,CS-MIPI-SC132.

CS-MIPI-IMX307 I2C.sh user guide

2.3 veye5_mipi_i2c.sh

Applicable models:VEYE-MIPI-IMX335.

VEYE-MIPI-IMX335 i2c script user guide

2.4 mv_mipi_i2c.sh

Applicable models:MV-MIPI-XXX,RAW-MIPI-XXX.

mv_mipi_i2c.sh user guide

@@ Line 1: / Line 1: @@
-[http://wiki.veye.cc/index.php/NXP_i.MX_Application_Note_Index/zh 查看中文]
+[[Rockchip platform Application Note Index/zh|查看中文]]
 ===Main App Note===
-*[http://wiki.veye.cc/index.php/VEYE_CS_Camera_on_AVNET_Maaxboard How to use VEYE and CS series camera module on AVNET Maaxboard(mini) board]
+==== VEYE and CS series camera ====
-===I2C user guide===
+*[[VEYE CS Camera on Firfly Boards|How to use VEYE series camera module on Firefly RK35xx boards]]
+*[[VEYE CS Camera on Radxa Boards|How to use VEYE series camera module on Radxa RK35xx boards]]
+==== MV and RAW series camera ====
+* [[MV Camera on Firfly Boards|How to use MV and RAW series camera module on Firefly RK35xx boards]]
+*[[MV Camera on Radxa Boards|How to use MV and RAW series camera module on Radxa RK35xx boards]]
+=== I2C user guide ===
+For the parameter configuration aspect of the camera module, we use the DRA (Direct Register Access) approach instead of encapsulating the interface in the v4l2 driver in order to achieve better flexibility and a more direct parameter configuration function.
+The following shell scripts can be used directly or embedded into your programs. Of course, by reading their source codes, you will be able to see the registers and access methods corresponding to each function.
+====veye_mipi_i2c.sh====
+Applicable models: VEYE-MIPI-290/327,VEYE-MIPI-IMX327S,VEYE-MIPI-IMX462,VEYE-MIPI-IMX385.
 *[[VEYE-MIPI-290/327 i2c/|VEYE-MIPI-290/327 I2C.sh user guide]]
+====cs_mipi_i2c.sh====
+Applicable models: CS-MIPI-IMX307,CS-MIPI-SC132.
 *[[CS-MIPI-X i2c|CS-MIPI-IMX307 I2C.sh user guide]]
+====veye5_mipi_i2c.sh====
+Applicable models:VEYE-MIPI-IMX335.
+*[[5m mipi i2c user guide|VEYE-MIPI-IMX335 i2c script user guide]]
+====mv_mipi_i2c.sh====
+Applicable models:MV-MIPI-XXX,RAW-MIPI-XXX.
+*[[mv_mipi_i2c.sh user guide]]