Difference between revisions of "Raspberry Pi Application Note Index"
(整理了appnote的逻辑结构，增加引导说明.) |
|||
| Line 14: | Line 14: | ||
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. | 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. | 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. | ||
| Line 35: | Line 37: | ||
*[[CS-MIPI-X i2c|CS-MIPI-IMX307 I2C.sh user guide]] | *[[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]] | ||
=== Others === | === Others === | ||
*[[RaspberryPI I2C confilct problem|Raspberry Pi I2C bus conflict problem]] | *[[RaspberryPI I2C confilct problem|Raspberry Pi I2C bus conflict problem]] | ||
Revision as of 10:00, 27 February 2022
1 Main AppNotes
The latest 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 following articles address the use of different models of camera modules in lagacy mode.
- How to use VEYE-MIPI-290/327 camera module on Raspberry Pi
- How to use CS-FPD-CAM series camera module on Raspberry Pi
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.
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.