7.46.1.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

• CPU_PWRDWN_SGI: Select the SGI for triggering CPU power down request to

  secondary cores on receiving power down callback fromfirmware. Options:

  • 0 : SGI 0

  • 1 : SGI 1

  • 2 : SGI 2

  • 3 : SGI 3

  • 4 : SGI 4

  • 5 : SGI 5

  • 6 : SGI 6 (Default)

  • 7 : SGI 7

7.46.2.Configurable Stack Size

The stack size in TF-A for the Versal platform is configurable.The custom package can define the desired stack size as per the requirement inthe makefile as follows:

PLATFORM_STACK_SIZE:=<value>$(eval$(calladd_define,PLATFORM_STACK_SIZE))

7.46.3.CUSTOM SIP Service Support

• Dedicated SMC FIDVERSAL_SIP_SVC_CUSTOM(0x82002000) (32-bit) /(0xC2002000) (64-bit) is used by a custom package for providingCUSTOM SIP service.

• By default, the platform provides a bare minimum definition forcustom_smc_handler in this service.

• To use this service, the custom package should implement its own SMC handlernamedcustom_smc_handler. Once the custom package is included in theTF-A build, its definition ofcustom_smc_handler is enabled.

7.46.4.Custom Package Makefile Fragment Inclusion in TF-A Build

• Custom package is not directly part of the TF-A source.

• <CUSTOM_PKG_PATH> is the location where the user clones acustom package locally.

• The custom package must implement a makefile fragment namedcustom_pkg.mk so it can be included in the TF-A build.

• custom_pkg.mk should specify all the rules to include custom packagespecific header files, dependent libraries, and source files that arerequired to be part of the TF-A build.

• When<CUSTOM_PKG_PATH> is specified in the TF-A build command,custom_pkg.mk is included from<CUSTOM_PKG_PATH>.

• Example TF-A build command:

makeCROSS_COMPILE=aarch64-none-elf-PLAT=versalRESET_TO_BL31=1bl31CUSTOM_PKG_PATH=<...>

7.46.5.# PLM->TF-A Parameter Passing

The PLM populates a data structure with image information for the TF-A. The TF-Auses that data to hand off to the loaded images. The address of the handoffdata structure is passed in the`PMC_GLOBAL_GLOB_GEN_STORAGE4` register.The register is free to be used by other software once the TF-A is bringing upfurther firmware images.

7.46.6.Reference DEN0028E SMC calling convention

7.46.7.Allocated subranges of Function Identifier to SIP services

7.46.8.IPI SMC call ranges

7.46.9.PM SMC call ranges for SiP SVC version 0.1

7.46.10.PM SMC call ranges for SiP SVC version 0.2

7.46.11.SMC function IDs for SiP Service queries

Call UID Query – Returns a unique identifier of the service provider.

Revision Query – Returns revision details of the service implementor.