Gitiles
Code Review Sign In
git01.mediatek.com / filogic / atf / c0a68d4a28ec1418b1ccfa54807da11704f7ac07 / . / docs / plat / xilinx-versal-net.rst
blob: d22a46d120c1a4925bb6b8831855408040de8c1f [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
Michal Simekb9ae59f2022-08-31 13:05:57 +0200[diff] [blame]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:
Akshay Belsare50a29682023-01-18 15:54:12 +0530[diff] [blame]36 - `pl011`, `pl011_0`: ARM pl011 UART 0 (default)
Michal Simekb9ae59f2022-08-31 13:05:57 +0200[diff] [blame]37 - `pl011_1` : ARM pl011 UART 1
Akshay Belsare50a29682023-01-18 15:54:12 +0530[diff] [blame]38 - `dcc` : JTAG Debug Communication Channel(DCC)
Michal Simekb9ae59f2022-08-31 13:05:57 +0200[diff] [blame]39
40* `TFA_NO_PM` : Platform Management support.
41 - 0 : Enable Platform Management (Default)
42 - 1 : Disable Platform Management
Jay Buddhabhatti1dfe4972023-04-25 04:34:51 -0700[diff] [blame]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
Prasad Kummari806a1b92024-02-08 17:30:51 +0530[diff] [blame]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
Jay Buddhabhatti852c74b2024-07-14 23:29:04 -0700[diff] [blame]78PM SMC call ranges for SiP SVC version 0.1
Prasad Kummari806a1b92024-02-08 17:30:51 +0530[diff] [blame]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
Jay Buddhabhatti852c74b2024-07-14 23:29:04 -0700[diff] [blame]87PM SMC call ranges for SiP SVC version 0.2
88--------------------------------------------------------
89
90+---------------------------+---------------------------------------------------------------------------+
91| SMC Function Identifier | Service type |
92+---------------------------+---------------------------------------------------------------------------+
93| 0xc2000FFF | Fast SMC64 SiP Service call used for pass-through of AMD-Xilinx Platform |
94| | Management APIs to firmware |
95+---------------------------+---------------------------------------------------------------------------+
96| 0xc2000A00-0xc2000AFF | Fast SMC64 SiP Service call range used for AMD-Xilinx Platform Management |
97| | specific TF-A APIs |
98+---------------------------+---------------------------------------------------------------------------+
99
Prasad Kummari806a1b92024-02-08 17:30:51 +0530[diff] [blame]100SMC function IDs for SiP Service queries
101----------------------------------------------
102
103+--------------+--------------+--------------+
104| Service | Call UID | Revision |
105+--------------+--------------+--------------+
106| SiP Service | 0x8200_FF01 | 0x8200_FF03 |
107+--------------+--------------+--------------+
108
109Call UID Query – Returns a unique identifier of the service provider.
110
111Revision Query – Returns revision details of the service implementor.