1Xilinx Versal NET 2================= 3 4Trusted Firmware-A implements the EL3 firmware layer for Xilinx Versal NET. 5The platform only uses the runtime part of TF-A as Xilinx Versal NET already 6has a BootROM (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_net bl31 15``` 16 17To build bl32 TSP you have to rebuild bl31 too 18```bash 19make CROSS_COMPILE=aarch64-none-elf- PLAT=versal_net SPD=tspd RESET_TO_BL31=1 bl31 bl32 20``` 21 22To build TF-A for JTAG DCC console: 23```bash 24make RESET_TO_BL31=1 CROSS_COMPILE=aarch64-none-elf- PLAT=versal_net VERSAL_NET_CONSOLE=dcc bl31 25``` 26 27Xilinx Versal NET platform specific build options 28------------------------------------------------- 29 30* `VERSAL_NET_ATF_MEM_BASE`: Specifies the base address of the bl31 binary. 31* `VERSAL_NET_ATF_MEM_SIZE`: Specifies the size of the memory region of the bl31 binary. 32* `VERSAL_NET_BL32_MEM_BASE`: Specifies the base address of the bl32 binary. 33* `VERSAL_NET_BL32_MEM_SIZE`: Specifies the size of the memory region of the bl32 binary. 34 35* `VERSAL_NET_CONSOLE`: Select the console driver. Options: 36 - `pl011`, `pl011_0`: ARM pl011 UART 0 (default) 37 - `pl011_1` : ARM pl011 UART 1 38 - `dcc` : JTAG Debug Communication Channel(DCC) 39 40* `TFA_NO_PM` : Platform Management support. 41 - 0 : Enable Platform Management (Default) 42 - 1 : Disable Platform Management 43 44* `CPU_PWRDWN_SGI`: Select the SGI for triggering CPU power down request to 45 secondary cores on receiving power down callback from 46 firmware. Options: 47 48 - `0` : SGI 0 49 - `1` : SGI 1 50 - `2` : SGI 2 51 - `3` : SGI 3 52 - `4` : SGI 4 53 - `5` : SGI 5 54 - `6` : SGI 6 (Default) 55 - `7` : SGI 7 56 57Reference DEN0028E SMC calling convention 58------------------------------------------ 59 60Allocated subranges of Function Identifier to SIP services 61----------------------------------------------------------- 62 63+-----------------------+-------------------------------------------------------+ 64| SMC Function | Identifier Service type | 65+-----------------------+------------------------------+------------------------+ 66| 0xC2000000-0xC200FFFF | Fast SMC64 SiP Service Calls as per SMCCC Section 6.1 | 67+-----------------------+-------------------------------------------------------+ 68 69IPI SMC call ranges 70------------------------------------------------------------- 71 72+---------------------------+-----------------------------------------------------------+ 73| SMC Function Identifier | Service type | 74+---------------------------+-----------------------------------------------------------+ 75| 0xc2001000-0xc2001FFF | Fast SMC64 SiP Service call range used for AMD-Xilinx IPI | 76+---------------------------+-----------------------------------------------------------+ 77 78PM SMC call ranges 79-------------------------------------------------------- 80 81+---------------------------+---------------------------------------------------------------------------+ 82| SMC Function Identifier | Service type | 83+---------------------------+---------------------------------------------------------------------------+ 84| 0xc2000000-0xc2000FFF | Fast SMC64 SiP Service call range used for AMD-Xilinx Platform Management | 85+---------------------------+---------------------------------------------------------------------------+ 86 87SMC function IDs for SiP Service queries 88---------------------------------------------- 89 90+--------------+--------------+--------------+ 91| Service | Call UID | Revision | 92+--------------+--------------+--------------+ 93| SiP Service | 0x8200_FF01 | 0x8200_FF03 | 94+--------------+--------------+--------------+ 95 96Call UID Query – Returns a unique identifier of the service provider. 97 98Revision Query – Returns revision details of the service implementor. 99