1. Article purpose[edit | edit source]
The purpose of this article is to:
- briefly introduce the CSI peripheral and its main features,
- indicate the peripheral instances assignment at boot time, and their assignment at runtime (including whether instances can be allocated to secure contexts),
- list the software frameworks and drivers managing the peripheral, and to
- explain how to configure the peripheral.
2. Peripheral overview[edit | edit source]
The CSI2-Host (camera serial interface) internal peripheral is used to receive video data from an external MIPI® CSI camera sensor device, or from any other digital video equipment supporting a CSI interface. Received data are internally transferred to the DCMIPP[1] internal peripheral for further processing.
The MIPI® CSI is part of a group of communication protocols defined by the MIPI® Alliance [2]. The CSI2-Host peripheral supports MIPI® CSI2 v1.3 standard, and can receive various frame data formats using two data lanes @ 2.5 Gbps/lane.
For information on the complete list of features, refer to the STM32 MPU reference manuals. For further information on the implemented features, refer to the introduction of software frameworks and drivers below.
3. Peripheral usage[edit | edit source]
This chapter is applicable within the scope of the OpenSTLinux BSP running on the Arm® Cortex®-A processor(s), and the STM32CubeMPU Package running on the Arm® Cortex®-M processor.
3.1. Boot time assignment[edit | edit source]
The CSI internal peripheral is not used at boot time.
3.1.1. On STM32MP2 series[edit | edit source]
STM32MP2 internal peripherals assignment table template
| rowspan="1" | Visual | rowspan="1" | CSI | CSI | | | ⬚ | |-
|}
3.2. Runtime assignment[edit | edit source]
3.2.1. On STM32MP25x lines 
[edit | edit source]
STM32MP2 internal peripherals assignment table template
| rowspan="1" | Visual | rowspan="1" | CSI | CSI | ⬚OP-TEE | ☑ | ⬚ | ☐ | | |-
|}
4. Software frameworks and drivers[edit | edit source]
Below are listed the software frameworks and drivers managing the CSI peripheral for the embedded software components listed in the above tables.
- Linux®: V4L2 framework
- STM32Cube: CSI HAL driver
5. How to assign and configure the peripheral[edit | edit source]
The peripheral assignment can be done via the STM32CubeMX graphical tool (and manually completed if needed).
This tool also helps to configure the peripheral by generating:
- partial device trees (pin control and clock tree) for the OpenSTLinux software components, and
- HAL initialization code for the STM32CubeMPU Package.
The configuration is applied by the firmware running in the context in which the peripheral is assigned.
For additional information, refer to the CSI device tree configuration article for Linux®.
6. How to go further[edit | edit source]
|
Coming soon |
7. References[edit | edit source]
- ↑ DCMIPP internal peripheral
- ↑ https://www.mipi.org MIPI® Alliance
Arm® is a registered trademark of Arm Limited (or its subsidiaries) in the US and/or elsewhere. 
Arm® is a registered trademark of Arm Limited (or its subsidiaries) in the US and/or elsewhere.