blob: 66eb76d1dec473cc1aa9e2bd80ff50d58bca5096 [file] [log] [blame]
Balint Dobszay1bf41f52022-05-30 12:56:38 +02001FVP_USE_BASE_PLAT ?= y
2FVP_VIRTFS_ENABLE ?= y
3FVP_VIRTFS_AUTOMOUNT ?= y
4MEASURED_BOOT ?= y
5MEASURED_BOOT_FTPM ?= n
6TS_SMM_GATEWAY ?= y
Balint Dobszayc3d34122022-05-30 13:28:06 +02007TS_UEFI_TESTS ?= y
Balint Dobszay1bf41f52022-05-30 12:56:38 +02008
9TF_A_FLAGS ?= \
10 BL32=$(OPTEE_OS_PAGER_V2_BIN) \
11 BL33=$(EDK2_BIN) \
12 PLAT=fvp \
13 SPD=spmd \
14 SPMD_SPM_AT_SEL2=0 \
15 ARM_SPMC_MANIFEST_DTS=$(ROOT)/build/fvp/spmc_manifest.dts
16
17include fvp.mk
18include trusted-services.mk
19
20OPTEE_OS_COMMON_EXTRA_FLAGS += \
21 CFG_SECURE_PARTITION=y \
22 CFG_CORE_SEL1_SPMC=y \
23 CFG_CORE_HEAP_SIZE=131072 \
24 CFG_DT=y \
25 CFG_MAP_EXT_DT_SECURE=y
26
27# The boot order of the SPs is determined by the order of calls here. This is
28# due to the SPMC not (yet) supporting the boot order field of the SP manifest.
29$(eval $(call build-sp,internal-trusted-storage,dc1eef48-b17a-4ccf-ac8b-dfcff7711b14,$(SP_PSA_ITS_EXTRA_FLAGS)))
30$(eval $(call build-sp,protected-storage,751bf801-3dde-4768-a514-0f10aeed1790,$(SP_PSA_PS_EXTRA_FLAGS)))
31$(eval $(call build-sp,crypto,d9df52d5-16a2-4bb2-9aa4-d26d3b84e8c0,$(SP_PSA_CRYPTO_EXTRA_FLAGS)))
32ifeq ($(MEASURED_BOOT),y)
33$(eval $(call build-sp,attestation,a1baf155-8876-4695-8f7c-54955e8db974,$(SP_PSA_ATTESTATION_EXTRA_FLAGS)))
34endif
35ifeq ($(TS_SMM_GATEWAY),y)
36$(eval $(call build-sp,smm-gateway,ed32d533-99e6-4209-9cc0-2d72cdd998a7,$(SP_SMM_GATEWAY_EXTRA_FLAGS)))
37endif
Balint Dobszayc0b8fdf2022-06-02 14:41:54 +020038
39$(eval $(call build-ts-app,libts))
40$(eval $(call build-ts-app,ts-service-test))
41$(eval $(call build-ts-app,psa-api-test/internal_trusted_storage))
42$(eval $(call build-ts-app,psa-api-test/protected_storage))
43$(eval $(call build-ts-app,psa-api-test/crypto))
44ifeq ($(MEASURED_BOOT),y)
45$(eval $(call build-ts-app,psa-api-test/initial_attestation))
46endif
47ifeq ($(TS_UEFI_TESTS),y)
48$(eval $(call build-ts-app,uefi-test))
49endif