OP-TEE OTP overview

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]

The two OP-TEE trusted applications (TA), STM32MP BSEC and STM32MP NVMEM, provide a generic interface for the device non-volatile OTP (one-time programmable) fuses.

These two TAs offer interfaces to read and/or write OTP data and status at other TAs in secure world and at non-secure applications.

2 System overview[edit]


2.1 Component description[edit]

  • Non secure world (Linux):
    • 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 Core API Lib (User Space): Library called by the client application to access to the kernel space.
    • 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 driver (Kernel Space): Generic driver that sends messages to the OP-TEE OS.

2.2 API description[edit]

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

3 Configuration[edit]

3.1 OP-TEE_OS configuration[edit]

Activate STM32MP BSEC PTA in OP-TEE configuration core/arch/arm/plat-stm32mp1/conf.mk :


Activate BSEC driver write support in OP-TEE configuration core/arch/arm/plat-stm32mp1/conf.mk :


In ecosystem release ≤ v4.1.0 More info.png , this configuration is activated on OP-TEE debug release with:


Activate STM32MP NVMEM TA in OP-TEE configuration core/arch/arm/plat-stm32mp1/conf.mk :

Warning white.png Warning
It is strongly recommended to deactivated the TA STM32MP NVMEM in final product

3.2 Device tree configuration[edit]

Detailed DT configuration for STM32 internal peripherals:

4 How to use the OP-TEE OTP interfaces[edit]

The access to Trusted application (TA) is done with TEE client API architecture/globalplatform_api.html#tee-client-api.

4.1 STM32MP BSEC PTA[edit]

The STM32MP BSEC PTA interface runs at TEE kernel level and provides access to OTP data and status: lock and error. (core/pta/stm32mp/bsec_pta.c )

This interface is used by Trusted Application in secure world to access all available OTP, not masked by hardware.

See example in the STM32MP NVMEM TA: ta/stm32mp_nvmem/ta_stm32mp_nvmem.c , this access is only allowed for open device (checked during open session) but no access restriction for other TA.

This interface is also used by non-secure world BSEC driver to access to unsecured OTP:

Only the lower OTPs words are default accessible by non-secure world (TEE_LOGIN_REE_KERNEL), the software needs to manage exceptions to allow some upper OTPs to be accessed by the non-secure world as described in BSEC_device_tree_configuration, when an OTP is not accessible, the returned value is 0x0.

4.2 STM32MP NVMEM TA[edit]

The STM32MP NVMEM early TA interface runs in at secure user space level and allows access to secure not volatile memory (NVMEM), by exchanging buffer with provisioning application and with STM32CubeProgrammer tools (ta/stm32mp_nvmem/ta_stm32mp_nvmem.c ).

Warning white.png Warning
Session to the STM32MP NVMEM TA failed on closed device, because open session to STM32MP BSEC PTA is refused

See example in U-Boot: arch/arm/mach-stm32mp/cmd_stm32prog/stm32prog.c .

Warning white.png Warning
This interface is a potential security breach, it should be used only in development phases or for provisioning software, it is recommended to deactivate this TA in a final product

5 References[edit]

Please refer to the following links for additional information: