1Xilinx Versal 2============= 3 4Trusted Firmware-A implements the EL3 firmware layer for Xilinx Versal. 5The platform only uses the runtime part of TF-A as Xilinx Versal already has a 6BootROM (BL1) and PMC FW (BL2). 7 8BL31 is TF-A. 9BL32 is an optional Secure Payload. 10BL33 is the non-secure world software (U-Boot, Linux etc). 11 12To build: 13```bash 14make RESET_TO_BL31=1 CROSS_COMPILE=aarch64-none-elf- PLAT=versal bl31 15``` 16 17To build ATF for different platform (supported are "silicon"(default) and "versal_virt") 18```bash 19make RESET_TO_BL31=1 CROSS_COMPILE=aarch64-none-elf- PLAT=versal VERSAL_PLATFORM=versal_virt bl31 20``` 21 22Xilinx Versal platform specific build options 23--------------------------------------------- 24 25* `VERSAL_ATF_MEM_BASE`: Specifies the base address of the bl31 binary. 26* `VERSAL_ATF_MEM_SIZE`: Specifies the size of the memory region of the bl31 binary. 27* `VERSAL_BL32_MEM_BASE`: Specifies the base address of the bl32 binary. 28* `VERSAL_BL32_MEM_SIZE`: Specifies the size of the memory region of the bl32 binary. 29 30* `VERSAL_CONSOLE`: Select the console driver. Options: 31 - `pl011`, `pl011_0`: ARM pl011 UART 0 32 - `pl011_1` : ARM pl011 UART 1 33 34* `VERSAL_PLATFORM`: Select the platform. Options: 35 - `versal_virt` : Versal Virtual platform 36 37# PLM->TF-A Parameter Passing 38------------------------------ 39The PLM populates a data structure with image information for the TF-A. The TF-A 40uses that data to hand off to the loaded images. The address of the handoff 41data structure is passed in the ```PMC_GLOBAL_GLOB_GEN_STORAGE4``` register. 42The register is free to be used by other software once the TF-A is bringing up 43further firmware images. 44