mirror of
https://github.com/ARM-software/arm-trusted-firmware.git
synced 2025-04-16 09:34:18 +00:00
24dba2b39f
The platform port documents are not very standardised right now and they don't integrate properly into the document tree so: 1) Make sure each port has a proper name and title (incl. owner) 2) Correct use of headings, subheadings, etc in each port 3) Resolve any naming conflicts between documents Change-Id: I4c2da6f57172b7f2af3512e766ae9ce3b840b50f Signed-off-by: Paul Beesley <paul.beesley@arm.com>
35 lines
1.2 KiB
ReStructuredText
35 lines
1.2 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 ATF for different platform (for now its just versal virtual "versal_virt")
|
|
```bash
|
|
make RESET_TO_BL31=1 CROSS_COMPILE=aarch64-none-elf- PLAT=versal VERSAL_PLATFORM=versal_virt bl31
|
|
```
|
|
|
|
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
|
|
|
|
* `VERSAL_PLATFORM`: Select the platform. Options:
|
|
- `versal_virt` : Versal Virtual platform
|