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]
Click on 
to expand or collapse the legend...
- ☐ means that the peripheral can be assigned to the given boot time context.
- ☑ means that the peripheral is assigned by default to the given boot time context and that the peripheral is mandatory for the STM32 MPU Embedded Software distribution.
- ⬚ means that the peripheral can be assigned to the given boot time context, but this configuration is not supported in STM32 MPU Embedded Software distribution.
- ✓ is used for system peripherals that cannot be unchecked because they are hardware connected in the device.
The present chapter describes STMicroelectronics recommendations or choice of implementation. Additional possibilities might be described in STM32MP25 reference manuals.
| Domain | Peripheral | Boot time allocation | Comment
| |||
|---|---|---|---|---|---|---|
| Instance | Cortex-A35 secure (ROM code) |
Cortex-A35 secure (TF-A BL2) |
Cortex-A35 non-secure (U-Boot) | |||
| Visual | CSI | CSI | ⬚ | |||
3.2. Runtime assignment[edit | edit source]
3.2.1. On STM32MP25x lines 
[edit | edit source]
Click on to expand or collapse the legend...
Check boxes illustrate the possible peripheral allocations supported by STM32 MPU Embedded Software:
- ☐ means that the peripheral can be assigned to the given runtime context.
- ☑ means that the peripheral is assigned by default to the given runtime context and that the peripheral is mandatory for the STM32 MPU Embedded Software distribution.
- ⬚ means that the peripheral can be assigned to the given runtime context, but this configuration is not supported in STM32 MPU Embedded Software distribution.
- ✓ is used for system peripherals that cannot be unchecked because they are hardware connected in the device.
The present chapter describes STMicroelectronics recommendations or choice of implementation. Additional possibilities might be described in STM32MP25 reference manuals.
| Domain | Peripheral | Runtime allocation | Comment
| |||||
|---|---|---|---|---|---|---|---|---|
| Instance | Cortex-A35 secure (OP-TEE / TF-A BL31) |
Cortex-A35 non-secure (Linux) |
Cortex-M33 secure (TF-M) |
Cortex-M33 non-secure (STM32Cube) |
Cortex-M0+ (STM32Cube) | |||
| Visual | 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 and header file of CSI HAL module
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.