- Last edited one week ago ago
BSEC internal peripheral
1 Article purpose
The purpose of this article is to
- briefly introduce the BSEC peripheral and its main features
- indicate the level of security supported by this hardware block
- explain how each instance can be allocated to the three runtime contexts and linked to the corresponding software components
- explain, when necessary, how to configure the BSEC peripheral.
2 Peripheral overview
The BSEC peripheral is used to control an OTP (one time programmable) fuse box, used for on-chip non-volatile storage for device configuration and security parameters.
Refer to STM32MP15 reference manuals for the complete list of features, and to the software components, introduced below, to see which features are implemented.
2.2 Security support
The BSEC is a secure peripheral.
3 Peripheral usage and associated software
3.1 Boot time
The BSEC is configured at boot time to set up platform security.
The BSEC instance is a system peripheral and is controlled by the Arm® Cortex®-A7 secure:
3.2.2 Software frameworks
| Security | BSEC | OP-TEE BSEC driver | Linux NVMEM framework | | |- |}
3.2.3 Peripheral configuration
The configuration is based on Device tree, please refer to BSEC device tree configuration article.
It can be applied by the firmware running in a secure context, done in TF-A or in OP-TEE.
It can also be configured by Linux® kernel, please refer to NVMEM overview article.
3.2.4 Peripheral assignment
| rowspan="1" | Security | rowspan="1" | BSEC | BSEC | ✓ | ✓ | | |-