Gitiles
Code Review Sign In
git01.mediatek.com / filogic / atf / 1b98861a780a43352f1ea8aaaa2ec06e89855e28 / . / docs / plat / xilinx-versal-net.rst
blob: acb67a68d9f54659ed3ff216d54ac927bd8d46c8 [file] [log] [blame]
Michal Simekb9ae59f2022-08-31 13:05:57 +0200[diff] [blame]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
Prasad Kummari1ad20162023-10-29 13:47:02 +0530[diff] [blame]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
Akshay Belsare50a29682023-01-18 15:54:12 +0530[diff] [blame]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
Amit Nagal18c475a2025-04-23 12:28:59 +0530[diff] [blame]27To build TF-A with SDEI_SUPPORT:
28```bash
29make RESET_TO_BL31=1 CROSS_COMPILE=aarch64-none-elf- PLAT=versal_net SDEI_SUPPORT=1 bl31
30```
31
Michal Simekb9ae59f2022-08-31 13:05:57 +0200[diff] [blame]32Xilinx Versal NET platform specific build options
33-------------------------------------------------
34
35* `VERSAL_NET_ATF_MEM_BASE`: Specifies the base address of the bl31 binary.
36* `VERSAL_NET_ATF_MEM_SIZE`: Specifies the size of the memory region of the bl31 binary.
37* `VERSAL_NET_BL32_MEM_BASE`: Specifies the base address of the bl32 binary.
38* `VERSAL_NET_BL32_MEM_SIZE`: Specifies the size of the memory region of the bl32 binary.
39
40* `VERSAL_NET_CONSOLE`: Select the console driver. Options:
Akshay Belsare50a29682023-01-18 15:54:12 +0530[diff] [blame]41 - `pl011`, `pl011_0`: ARM pl011 UART 0 (default)
Michal Simekb9ae59f2022-08-31 13:05:57 +0200[diff] [blame]42 - `pl011_1` : ARM pl011 UART 1
Akshay Belsare50a29682023-01-18 15:54:12 +0530[diff] [blame]43 - `dcc` : JTAG Debug Communication Channel(DCC)
Michal Simekb9ae59f2022-08-31 13:05:57 +0200[diff] [blame]44
45* `TFA_NO_PM` : Platform Management support.
46 - 0 : Enable Platform Management (Default)
47 - 1 : Disable Platform Management
Jay Buddhabhatti1dfe4972023-04-25 04:34:51 -0700[diff] [blame]48
49* `CPU_PWRDWN_SGI`: Select the SGI for triggering CPU power down request to
50 secondary cores on receiving power down callback from
51 firmware. Options:
52
53 - `0` : SGI 0
54 - `1` : SGI 1
55 - `2` : SGI 2
56 - `3` : SGI 3
57 - `4` : SGI 4
58 - `5` : SGI 5
59 - `6` : SGI 6 (Default)
60 - `7` : SGI 7
Prasad Kummari806a1b92024-02-08 17:30:51 +0530[diff] [blame]61
62Reference DEN0028E SMC calling convention
63------------------------------------------
64
65Allocated subranges of Function Identifier to SIP services
66-----------------------------------------------------------
67
68+-----------------------+-------------------------------------------------------+
69| SMC Function | Identifier Service type |
70+-----------------------+------------------------------+------------------------+
71| 0xC2000000-0xC200FFFF | Fast SMC64 SiP Service Calls as per SMCCC Section 6.1 |
72+-----------------------+-------------------------------------------------------+
73
74IPI SMC call ranges
75-------------------------------------------------------------
76
77+---------------------------+-----------------------------------------------------------+
78| SMC Function Identifier | Service type |
79+---------------------------+-----------------------------------------------------------+
80| 0xc2001000-0xc2001FFF | Fast SMC64 SiP Service call range used for AMD-Xilinx IPI |
81+---------------------------+-----------------------------------------------------------+
82
Jay Buddhabhatti852c74b2024-07-14 23:29:04 -0700[diff] [blame]83PM SMC call ranges for SiP SVC version 0.1
Prasad Kummari806a1b92024-02-08 17:30:51 +0530[diff] [blame]84--------------------------------------------------------
85
86+---------------------------+---------------------------------------------------------------------------+
87| SMC Function Identifier | Service type |
88+---------------------------+---------------------------------------------------------------------------+
89| 0xc2000000-0xc2000FFF | Fast SMC64 SiP Service call range used for AMD-Xilinx Platform Management |
90+---------------------------+---------------------------------------------------------------------------+
91
Jay Buddhabhatti852c74b2024-07-14 23:29:04 -0700[diff] [blame]92PM SMC call ranges for SiP SVC version 0.2
93--------------------------------------------------------
94
95+---------------------------+---------------------------------------------------------------------------+
96| SMC Function Identifier | Service type |
97+---------------------------+---------------------------------------------------------------------------+
98| 0xc2000FFF | Fast SMC64 SiP Service call used for pass-through of AMD-Xilinx Platform |
99| | Management APIs to firmware |
100+---------------------------+---------------------------------------------------------------------------+
101| 0xc2000A00-0xc2000AFF | Fast SMC64 SiP Service call range used for AMD-Xilinx Platform Management |
102| | specific TF-A APIs |
103+---------------------------+---------------------------------------------------------------------------+
104
Prasad Kummari806a1b92024-02-08 17:30:51 +0530[diff] [blame]105SMC function IDs for SiP Service queries
106----------------------------------------------
107
108+--------------+--------------+--------------+
109| Service | Call UID | Revision |
110+--------------+--------------+--------------+
111| SiP Service | 0x8200_FF01 | 0x8200_FF03 |
112+--------------+--------------+--------------+
113
114Call UID Query – Returns a unique identifier of the service provider.
115
116Revision Query – Returns revision details of the service implementor.