mirror of
https://github.com/ARM-software/arm-trusted-firmware.git
synced 2025-04-16 09:34:18 +00:00
09ac1ca27c
Update Versal platform to enable runtime detection of variants instead of relying on the build argument VERSAL_PLATFORM. Integrate functionality for identifying the board variant during runtime, allowing dynamic adjustment of CPU and UART clock values accordingly. Print the runtime board information during boot. This advancement streamlines the build process by eliminating dependencies on variant-specific builds, enabling the use of a single binary for multiple variants. Removing all the platform related constants for versal_virt,SPP,EMU as they are not used. Change-Id: I8c1a1d391bd1a8971addc1f56f8309a3fb75aa6d Signed-off-by: Amey Avinash Raghatate <AmeyAvinash.Raghatate@amd.com> Signed-off-by: Maheedhar Bollapalli <MaheedharSai.Bollapalli@amd.com>
111 lines
4.4 KiB
ReStructuredText
111 lines
4.4 KiB
ReStructuredText
Xilinx Versal
|
||
=============
|
||
|
||
Trusted Firmware-A implements the EL3 firmware layer for Xilinx Versal.
|
||
The platform only uses the runtime part of TF-A as Xilinx Versal already has a
|
||
BootROM (BL1) and PMC FW (BL2).
|
||
|
||
BL31 is TF-A.
|
||
BL32 is an optional Secure Payload.
|
||
BL33 is the non-secure world software (U-Boot, Linux etc).
|
||
|
||
To build:
|
||
```bash
|
||
make RESET_TO_BL31=1 CROSS_COMPILE=aarch64-none-elf- PLAT=versal bl31
|
||
```
|
||
|
||
To build bl32 TSP you have to rebuild bl31 too
|
||
```bash
|
||
make CROSS_COMPILE=aarch64-none-elf- PLAT=versal SPD=tspd RESET_TO_BL31=1 bl31 bl32
|
||
```
|
||
|
||
To build TF-A for JTAG DCC console
|
||
```bash
|
||
make RESET_TO_BL31=1 CROSS_COMPILE=aarch64-none-elf- PLAT=versal bl31 VERSAL_CONSOLE=dcc
|
||
```
|
||
|
||
To build TF-A with Errata management interface
|
||
```bash
|
||
make RESET_TO_BL31=1 CROSS_COMPILE=aarch64-none-elf- PLAT=versal bl31 ERRATA_ABI_SUPPORT=1
|
||
```
|
||
|
||
To build TF-A with Straight-Line Speculation(SLS)
|
||
```bash
|
||
make RESET_TO_BL31=1 CROSS_COMPILE=aarch64-none-elf- PLAT=versal bl31 HARDEN_SLS_ALL=1
|
||
```
|
||
|
||
Xilinx Versal platform specific build options
|
||
---------------------------------------------
|
||
|
||
* `VERSAL_ATF_MEM_BASE`: Specifies the base address of the bl31 binary.
|
||
* `VERSAL_ATF_MEM_SIZE`: Specifies the size of the memory region of the bl31 binary.
|
||
* `VERSAL_BL32_MEM_BASE`: Specifies the base address of the bl32 binary.
|
||
* `VERSAL_BL32_MEM_SIZE`: Specifies the size of the memory region of the bl32 binary.
|
||
|
||
* `VERSAL_CONSOLE`: Select the console driver. Options:
|
||
- `pl011`, `pl011_0`: ARM pl011 UART 0
|
||
- `pl011_1` : ARM pl011 UART 1
|
||
|
||
* `CPU_PWRDWN_SGI`: Select the SGI for triggering CPU power down request to
|
||
secondary cores on receiving power down callback from
|
||
firmware. Options:
|
||
|
||
- `0` : SGI 0
|
||
- `1` : SGI 1
|
||
- `2` : SGI 2
|
||
- `3` : SGI 3
|
||
- `4` : SGI 4
|
||
- `5` : SGI 5
|
||
- `6` : SGI 6 (Default)
|
||
- `7` : SGI 7
|
||
|
||
# PLM->TF-A Parameter Passing
|
||
------------------------------
|
||
The PLM populates a data structure with image information for the TF-A. The TF-A
|
||
uses that data to hand off to the loaded images. The address of the handoff
|
||
data structure is passed in the ```PMC_GLOBAL_GLOB_GEN_STORAGE4``` register.
|
||
The register is free to be used by other software once the TF-A is bringing up
|
||
further firmware images.
|
||
|
||
Reference DEN0028E SMC calling convention
|
||
------------------------------------------
|
||
|
||
Allocated subranges of Function Identifier to SIP services
|
||
----------------------------------------------------------
|
||
|
||
+-----------------------+-------------------------------------------------------+
|
||
| SMC Function | Identifier Service type |
|
||
+-----------------------+-------------------------------------------------------+
|
||
| 0xC2000000-0xC200FFFF | Fast SMC64 SiP Service Calls as per SMCCC Section 6.1 |
|
||
+-----------------------+-------------------------------------------------------+
|
||
|
||
IPI SMC call ranges
|
||
-------------------
|
||
|
||
+---------------------------+-----------------------------------------------------------+
|
||
| SMC Function Identifier | Service type |
|
||
+---------------------------+-----------------------------------------------------------+
|
||
| 0xc2001000-0xc2001FFF | Fast SMC64 SiP Service call range used for AMD-Xilinx IPI |
|
||
+---------------------------+-----------------------------------------------------------+
|
||
|
||
PM SMC call ranges
|
||
------------------
|
||
|
||
+---------------------------+---------------------------------------------------------------------------+
|
||
| SMC Function Identifier | Service type |
|
||
+---------------------------+---------------------------------------------------------------------------+
|
||
| 0xc2000000-0xc2000FFF | Fast SMC64 SiP Service call range used for AMD-Xilinx Platform Management |
|
||
+---------------------------+---------------------------------------------------------------------------+
|
||
|
||
SMC function IDs for SiP Service queries
|
||
----------------------------------------
|
||
|
||
+--------------+--------------+--------------+
|
||
| Service | Call UID | Revision |
|
||
+--------------+--------------+--------------+
|
||
| SiP Service | 0x8200_FF01 | 0x8200_FF03 |
|
||
+--------------+--------------+--------------+
|
||
|
||
Call UID Query – Returns a unique identifier of the service provider.
|
||
|
||
Revision Query – Returns revision details of the service implementor.
|