Difference between revisions of "Raspberry Pi Application Note Index"

From wiki_veye
Jump to navigation Jump to search
 
(20 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
[[Raspberry Pi Application Note Index/zh|查看中文]]
 
[[Raspberry Pi Application Note Index/zh|查看中文]]
 +
 +
=== Main App Notes ===
 +
 +
==== VEYE and CS series App Notes ====
 +
{| class="wikitable"
 +
!Series
 +
!Model
 +
!Status
 +
|-
 +
|VEYE series
 +
|VEYE-MIPI-IMX327S
 +
|Done
 +
|-
 +
|VEYE series
 +
|VEYE-MIPI-IMX385
 +
|Done
 +
|-
 +
|VEYE series
 +
|VEYE-MIPI-IMX462
 +
|Done
 +
|-
 +
|CS series
 +
|CS-MIPI-IMX307
 +
|Done
 +
|-
 +
|CS series
 +
|CS-MIPI-SC132
 +
|Done
 +
|}
 +
===== V4l2 mode =====
 +
The v4l2 mode is the main application mode in the future, which supports 64-bit piOS.
 +
 +
Raspberry Pi decided to use libcamera to implement an isp solution that does not rely on Broadcom's gpu firmware as much as possible.
 +
 +
At the driver layer, the standard V4L2 sensor driver was used whenever possible, and a series of libcamera-apps were released at the application layer.
 +
 +
Our camera module is not dependent on libcamera because we have implemented isp functionality inside the camera.
 +
 +
In the following article, we provide the standard V4l2 mode driver and implement the application layer demo based on this driver: preview, video recording, network transmission, opencv application, etc.
 +
 +
*[[V4L2 mode for Raspberry Pi|How to use VEYE and CS series camera module on Raspberry Pi(V4L2 mode)]]
 +
 +
Of course, we have plans to provide application layer demos similar to libcamera-apps in the future.
 +
 +
===== Legacy mode =====
 +
The system of Raspberry Pi - '''bullseye''' has removed the support of '''raspicam''' by default，which depends on MMAL and Broadcom's GPUs firmware. Of course we can still use this so called '''legacy mode''', and it still has value.
 +
 +
The latest Raspberry Pi system, Bookworm, no longer supports the legacy mode.
 +
 +
The following articles address the use of different models of camera modules in lagacy mode.
 +
 +
* [[CS-MIPI-X for Raspberry Pi|How to use CS-MIPI-X camera module on Raspberry Pi]]
 +
 +
*[[VEYE-MIPI-290/327 for Raspberry Pi|How to use VEYE-MIPI-290/327 camera module on Raspberry Pi]]
 +
*[[CS-FPD-CAM for Raspberry Pi|How to use CS-FPD-CAM series camera module on Raspberry Pi]]
 +
 +
==== MV series App Notes ====
 +
{| 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
 +
|-
 +
|RAW series
 +
|RAW-MIPI-SC132M
 +
|Done
 +
|-
 +
|RAW series
 +
|RAW-MIPI-IMX462M
 +
|Done
 +
|-
 +
|RAW series
 +
|RAW-MIPI-AR0234M
 +
|Done
 +
|}
 +
 +
* [[Mv series camera appnotes 4 rpi|How to use MV series camera module on Raspberry Pi]]
 +
 +
===== V-by-One-HS KIT =====
 +
 +
* [[V-by-One-HS KIT appnotes 4 rpi|How to use V-by-One-HS KIT on Raspberry Pi]]
 +
 +
=== 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]]<br />
 +
=== Others ===
 +
 +
*[[RaspberryPI I2C confilct problem|Raspberry Pi I2C bus conflict problem]]

Latest revision as of 10:32, 18 October 2023

查看中文

1 Main App Notes

1.1 VEYE and CS series App Notes

Series Model Status
VEYE series VEYE-MIPI-IMX327S Done
VEYE series VEYE-MIPI-IMX385 Done
VEYE series VEYE-MIPI-IMX462 Done
CS series CS-MIPI-IMX307 Done
CS series CS-MIPI-SC132 Done
1.1.1 V4l2 mode

The v4l2 mode is the main application mode in the future, which supports 64-bit piOS.

Raspberry Pi decided to use libcamera to implement an isp solution that does not rely on Broadcom's gpu firmware as much as possible.

At the driver layer, the standard V4L2 sensor driver was used whenever possible, and a series of libcamera-apps were released at the application layer.

Our camera module is not dependent on libcamera because we have implemented isp functionality inside the camera.

In the following article, we provide the standard V4l2 mode driver and implement the application layer demo based on this driver: preview, video recording, network transmission, opencv application, etc.

Of course, we have plans to provide application layer demos similar to libcamera-apps in the future.

1.1.2 Legacy mode

The system of Raspberry Pi - bullseye has removed the support of raspicam by default，which depends on MMAL and Broadcom's GPUs firmware. Of course we can still use this so called legacy mode, and it still has value.

The latest Raspberry Pi system, Bookworm, no longer supports the legacy mode.

The following articles address the use of different models of camera modules in lagacy mode.

1.2 MV series App Notes

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
RAW series RAW-MIPI-SC132M Done
RAW series RAW-MIPI-IMX462M Done
RAW series RAW-MIPI-AR0234M Done
1.2.1 V-by-One-HS KIT

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.

2.2 cs_mipi_i2c.sh

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

2.3 veye5_mipi_i2c.sh

Applicable models:VEYE-MIPI-IMX335.

2.4 mv_mipi_i2c.sh

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

3 Others

Retrieved from "http://wiki.veye.cc/index.php?title=Raspberry_Pi_Application_Note_Index&oldid=7134"