OP-TEE OTP overview

This message will disappear after all relevant tasks have been resolved.

Semantic MediaWiki

There are 1 incomplete or pending task to finish installation of Semantic MediaWiki. An administrator or user with sufficient rights can complete it. This should be done before adding new data to avoid inconsistencies.

Applicable for

STM32MP13x lines, STM32MP15x lines

This article gives information about the OTP framework in OP-TEE and the associated interfaces.

1 Framework purpose[edit source]

The OP-TEE OTP PTA provides a generic interface for the device non-volatile OTP (one-time programmable) fuses.

It offers interfaces to read and/or write OTP data and status at Trusted Applications (TA) in secure world and at non-secure applications.

2 System overview[edit source]

Coming soon

2.1 Component description[edit source]

NVMEM framework (kernel space)

The NVMEM framework in Linux^® kernel provides sysfs interface and NVMEM API.

NVMEM drivers (kernel space)

Provider drivers such as BSEC Linux^® driver that exposes OTP data to the core.

TEE framework (kernel space)

The TEE framework provides TEE client API to communicate with secure services, as the services provided by the OP-TEE Linux^® driver.

OP-TEE (Secure)

The OP-TEE secure OS is running on the Cortex-A in secure mode and exposes secure service with Trusted Applications (TA), as BSEC PTA and NVMEM PTA.

Hardware
- BSEC internal peripheral

Coming soon

2.2 API description[edit source]

The OTP interface is provided by two trusted applications (TA) in OP-TEE, accessible from the normal world with the GlobalPlatform API:

BSEC PTA: used to export OTP to other TA or to normal world (individual access)
- lib/libutee/include/pta_bsec.h

NVMEM TA: used to export OTP to STM32cubeProgrammer (global access)
- ta/stm32mp_nvmem/include/ta_stm32mp_nvmem.h

3 References[edit source]

Please refer to the following links for additional information: