Hi Varun,

cactus.dts complies with section 3.1 "Partition manifest at virtual FF-A instance" of the spec.

plat_spm_core_manifest_load consumes plat/arm/board/fvp/fdts/fvp_spmc_manifest.dts

The fields you refer to are in the SPM Core manifest attributes node: https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/tree/plat/arm/bo...

In your case I guess you'd have to use a command line like this (not tested though):

make \ CROSS_COMPILE=aarch64-none-elf- \ SPD=spmd \ SPMD_SPM_AT_SEL2=0 \ BL32=<path-to-cactus-binary> \ BL33=<path-to-nwd-binary> \ PLAT=fvp \ all fip

See also SPM documentation: https://trustedfirmware-a.readthedocs.io/en/latest/components/secure-partiti... https://trustedfirmware-a.readthedocs.io/en/latest/components/secure-partiti... https://trustedfirmware-a.readthedocs.io/en/latest/components/secure-partiti...

Regards, Olivier.

________________________________________ From: Varun Wadekar vwadekar@nvidia.com Sent: 07 August 2020 21:41 To: Olivier Deprez Cc: tf-a@lists.trustedfirmware.org Subject: Missing properties from cactus dts

Hello Olivier,

Hope you are doing well. As you already know, we are trying to test FF-A, using Cactus, on pre-8.4 Tegra platforms. While doing so, we saw that cactus.dts was missing the following properties

1. maj_ver 2. min_ver 3. spmc_id

plat_spm_core_manifest_load() expects these values in the core manifest file. i.e. cactus.dts.

What would be the right path forward? Do we add these fields to the dts file? Or modify plat_spmd_manifest.c file?

-Varun