1. Article purpose[edit source]
The purpose of this article is to:
- briefly introduce the CEC peripheral and its main features
- indicate the level of security supported by this hardware block
- explain how each instance can be allocated to the runtime contexts and linked to the corresponding software components
- explain, when necessary, how to configure the CEC peripheral.
2. Peripheral overview[edit source]
The CEC (consumer electronics control) or HDMI-CEC is an STM32 internal peripheral that allows to receive/send messages from/to devices, such as TV or tuner, through a HDMI cable.
2.1. Features[edit source]
Refer to the STM32MP15 reference manuals for the complete list of features, and to the software components, introduced below, to see which features are implemented.
Refer to the STM32 CEC presentation [1] for an overview of the CEC hardware block capabilities.
2.2. Security support[edit source]
The CEC is a non-secure peripheral.
3. Peripheral usage and associated software[edit source]
3.1. Boot time[edit source]
The CEC is not used at boot time.
3.2. Runtime[edit source]
3.2.1. Overview[edit source]
The CEC internal peripheral can be allocated to:
- the Arm® Cortex®-A7 non-secure core to be controlled in Linux® by the CEC framework
or
- the Arm® Cortex®-M4 to be controlled in STM32Cube MPU Package by STM32Cube CEC driver
Chapter Peripheral assignment describes which peripheral instance can be assigned to which context.
3.2.2. Software frameworks[edit source]
| Domain | Peripheral | Software components | Comment | ||
|---|---|---|---|---|---|
| OP-TEE | Linux | STM32Cube | |||
| Low-speed interface | CEC | CEC framework | CEC HAL driver | ||
3.2.3. Peripheral configuration[edit source]
The configuration is applied by the firmware running in the context to which the peripheral is assigned. The configuration can be done alone via the STM32CubeMX tool for all internal peripherals, and then manually completed (particularly for external peripherals), according to the information given in the corresponding software framework article or for Linux® in the CEC device tree configuration article.
3.2.4. Peripheral assignment[edit source]
Click on the right to expand 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 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 statically connected in the device.
Refer to How to assign an internal peripheral to a runtime context for more information on how to assign peripherals manually or via STM32CubeMX.
The present chapter describes STMicroelectronics recommendations or choice of implementation. Additional possiblities might be described in STM32MP15 reference manuals.
| Domain | Peripheral | Runtime allocation | Comment | |||
|---|---|---|---|---|---|---|
| Instance | Cortex-A7 secure (OP-TEE) |
Cortex-A7 non-secure (Linux) |
Cortex-M4 (STM32Cube) | |||
| Visual | CEC | CEC | ☐ | ☐ | Assignment (single choice) | |
4. How to go further[edit source]
Refer to the STM32 CEC application note (AN4066) [2] for a detailed description of the CEC peripheral and applicable use-cases.
Even if this application note is related to STM32 microcontrollers, it also applies to STM32 MPUs.
5. References[edit source]
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.