About

OP-TEE (Open Portable Trusted Execution Environment) is an open-source TEE designed for secure software execution implemented according to the GlobalPlatform TEE Client API and TEE Internal Core API. This project fosters collaboration among RISE members and individuals to develop OP-TEE for RISC-V.

Project Scope and Timelines

• PoC implementation of OP-TEE OS and OpenSBI 
• Run optee_test on QEMU virt (riscv64, dual-core)
• Run optee_test on Andes AE350 platform (QEMU and FPGA) 
• Leverage domain context switching and RPXY MPXY extension for OP-TEE SPD driver

• Add CI support for QEMU RV64 virt in OP-TEE OS 
• Integrate U-Boot
• Support dynamic shared memory

Components and Repos

• https://gitlab.com/riseproject/riscv-optee/buildroot.git
• https://gitlab.com/riseproject/riscv-optee/optee_os.git 
• https://gitlab.com/riseproject/riscv-optee/opensbi.git
• https://gitlab.com/riseproject/riscv-optee/u-boot.git
• https://gitlab.com/riseproject/riscv-optee/linux.git

QEMU Virt test environment

This implementation uses PMPs to isolate TEE and REE, no secure interrupt registered; software, timer and external interrupts will cause TEE managed exit to REE for interrupt handling.  

Boot process overview:

Memory Layout:

How to build and run optee_test:

git clone https://gitlab.com/riseproject/riscv-optee/buildroot.git -b dev-optee-mpxy
cd buildroot
make qemu_riscv64_virt_optee_defconfig
make
./output/images/start-qemu.sh 
# launch another terminal and connect to normal world
telnet localhost 64320
# run 'xtest' or 'optee_example*' in the shell

Stakeholders and Partners

• RISE
  • Andes Technology
    
    • Yu Chien Peter Lin <peterlin@andestech.com>
    • Alvin Che-Chia Chang <alvinga@andestech.com>
    • Tim Ouyang <tim609@andestech.com>

Dependencies

• MPXY/RPMI Specification
• SBI_00_04 - Domain Context Switch Support

Measure of Success

• Support QEMU virt (riscv64) in OP-TEE OS
• Support OP-TEE SPD in OpenSBI
• Support SMC-like RISC-V ABI in Linux and U-Boot OP-TEE drivers

Future Work

• IOPMP: To allow domains to request access ownership of devices
• AIA/APLIC: Secure/Non-secure interrupt handling
• FF-A like ABI: Unified protocol used among Secure/Non-secure images (need to be standardised for RISC-V)
• SmMTT: Additional secure features e.g. memory isolation, assigning interrupts to domains, etc. 

RISE Requirements

None

Status

Updates