Adding the command line to run the FVP:

<path-to-model>/FVP_Base_RevC-2xAEMvA -C pctl.startup=0.0.0.0 -C cluster0.NUM_CORES=4 -C cluster1.NUM_CORES=4 -C bp.secure_memory=1 -C bp.secureflashloader.fname=trusted-firmware-a/build/fvp/debug/bl1.bin -C bp.flashloader0.fname=trusted-firmware-a/build/fvp/debug/fip.bin -C bp.pl011_uart0.out_file=fvp-uart0.log -C bp.pl011_uart1.out_file=fvp-uart1.log -C bp.pl011_uart2.out_file=fvp-uart2.log -C bp.vis.disable_visualisation=1 -C cluster0.has_arm_v8-5=1 -C cluster1.has_arm_v8-5=1 -C cluster0.has_branch_target_exception=1 -C cluster1.has_branch_target_exception=1 -C cluster0.has_pointer_authentication=2 -C cluster1.has_pointer_authentication=2 -C cluster0.restriction_on_speculative_execution=2 -C cluster1.restriction_on_speculative_execution=2 -C cluster0.restriction_on_speculative_execution_aarch32=2 -C cluster1.restriction_on_speculative_execution_aarch32=2 -C pci.pci_smmuv3.mmu.SMMU_AIDR=2 -C pci.pci_smmuv3.mmu.SMMU_IDR0=0x0046123B -C pci.pci_smmuv3.mmu.SMMU_IDR1=0x00600002 -C pci.pci_smmuv3.mmu.SMMU_IDR3=0x1714 -C pci.pci_smmuv3.mmu.SMMU_IDR5=0xFFFF0472 -C pci.pci_smmuv3.mmu.SMMU_S_IDR1=0xA0000002 -C pci.pci_smmuv3.mmu.SMMU_S_IDR2=0 -C pci.pci_smmuv3.mmu.SMMU_S_IDR3=0

________________________________________ From: Olivier Deprez via Hafnium hafnium@lists.trustedfirmware.org Sent: 21 February 2022 09:08 To: Hafnium@lists.trustedfirmware.org; Friedrich Subject: [Hafnium] Re: S-EL1

Hi,

See build options here: https://trustedfirmware-a.readthedocs.io/en/latest/components/secure-partiti...

I'd suggest starting from the reference proposed by TF-A/TF-A-tests.

Build Hafnium: make PROJECT=reference

Build TF-A-tests: make CROSS_COMPILE=aarch64-none-elf- PLAT=fvp DEBUG=1 TESTS=spm -j8

Build TF-A: make CROSS_COMPILE=aarch64-none-elf- SPD=spmd CTX_INCLUDE_EL2_REGS=1 ARM_ARCH_MINOR=5 BRANCH_PROTECTION=1 CTX_INCLUDE_PAUTH_REGS=1 PLAT=fvp DEBUG=1 BL33=../tf-a-tests/build/fvp/debug/tftf.bin BL32=../hafnium/out/reference/secure_aem_v8a_fvp_clang/hafnium.bin SP_LAYOUT_FILE=../tf-a-tests/build/fvp/debug/sp_layout.json all fip

BL33 points to the nwd payload (here TFTF, but can be UEFI or uboot) BL32 points to hafnium binary (built for SPMC) SP_LAYOUT_FILE describes the partitions (path to image payload and manifest). Update the first entry to your own kernel and rebuild TF-A.

"cactus-primary" : { "image": "kernel.bin", "pm": "kernel.dts", "owner": "SiP" },

Regards, Olivier.

________________________________________ From: Friedrich via Hafnium hafnium@lists.trustedfirmware.org Sent: 18 February 2022 05:02 To: Hafnium@lists.trustedfirmware.org Subject: [Hafnium] S-EL1

How can I run my kernel in S-EL1 using hafnium?

Best, Friedrich -- Hafnium mailing list -- hafnium@lists.trustedfirmware.org To unsubscribe send an email to hafnium-leave@lists.trustedfirmware.org -- Hafnium mailing list -- hafnium@lists.trustedfirmware.org To unsubscribe send an email to hafnium-leave@lists.trustedfirmware.org