mirror of
https://github.com/ARM-software/arm-trusted-firmware.git
synced 2025-04-17 18:14:24 +00:00
rpi3: update documentation for OP-TEE support
Describe how to use BL32 build variable to load OP-TEE into FIP. Signed-off-by: Ying-Chun Liu (PaulLiu) <paulliu@debian.org>
This commit is contained in:
parent
7812abac86
commit
3d4642343f
1 changed files with 7 additions and 1 deletions
|
@ -122,7 +122,7 @@ secure platform!
|
|||
0x10000000 +-----------------+
|
||||
| Secure SRAM | BL2, BL31
|
||||
0x10100000 +-----------------+
|
||||
| Secure DRAM |
|
||||
| Secure DRAM | BL32 (Secure payload)
|
||||
0x10300000 +-----------------+
|
||||
| Non-secure DRAM | BL33
|
||||
0x11000000 +-----------------+
|
||||
|
@ -237,6 +237,12 @@ The following build options are supported:
|
|||
in AArch64 mode. If set to 1, it will jump to BL33 in Hypervisor in AArch32
|
||||
mode.
|
||||
|
||||
- ``BL32``: This port can load and run OP-TEE. The OP-TEE image is optional.
|
||||
Please use the code from `here <https://github.com/OP-TEE/optee_os>`__.
|
||||
Build the Trusted Firmware with option ``BL32=tee-header_v2.bin
|
||||
BL32_EXTRA1=tee-pager_v2.bin BL32_EXTRA2=tee-pageable_v2.bin``
|
||||
to put the binaries into the FIP.
|
||||
|
||||
The following is not currently supported:
|
||||
|
||||
- AArch32 for TF-A itself.
|
||||
|
|
Loading…
Add table
Reference in a new issue