-----Original Message----- From: Olivier Deprez [mailto:Olivier.Deprez@arm.com] Sent: 22 August 2022 13:50 To: Javier Almansa Sobrino Javier.AlmansaSobrino@arm.com; tf-a@lists.trustedfirmware.org; Shameerali Kolothum Thodi shameerali.kolothum.thodi@huawei.com Subject: Re: [TF-A] Re: TF-A RME support
Hi,
now you'd need -C cluster0.memory_tagging_support_level=2 -C cluster1.memory_tagging_support_level=2 -C bp.dram_metadata.is_enabled=1 (and CTX_INCLUDE_MTE_REGS=1 on TF-A command line).
Thanks. That did the trick.
I guess action is on TF-A team to update the doc. pages..
Yes. That would be very useful.
Thanks, Shameer
Regards, Olivier.
From: Shameerali Kolothum Thodi via TF-A tf-a@lists.trustedfirmware.org Sent: 22 August 2022 14:38 To: Javier Almansa Sobrino; tf-a@lists.trustedfirmware.org Subject: [TF-A] Re: TF-A RME support
-----Original Message----- From: Javier Almansa Sobrino [mailto:Javier.AlmansaSobrino@arm.com] Sent: 22 August 2022 13:28 To: Shameerali Kolothum Thodi
shameerali.kolothum.thodi@huawei.com;
tf-a@lists.trustedfirmware.org Subject: Re: [TF-A] TF-A RME support
Hi Shameer,
Can you try by setting rme_support_level to 2 for both clusters?
Ok. With rme_support_level=2, it make a bit of progress but still get stuck as below,
Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. NOTICE: Booting Trusted Firmware NOTICE: BL1: v2.7(debug):v2.7.0-235-g1631f9c75 NOTICE: BL1: Built : 11:44:37, Aug 22 2022 INFO: BL1: RAM 0x4035000 - 0x403c000 INFO: Loading image id=31 at address 0x4001010 INFO: Image id=31 loaded: 0x4001010 - 0x4001258 INFO: FCONF: Config file with image ID:31 loaded at address = 0x4001010 INFO: Loading image id=24 at address 0x4001300 INFO: Image id=24 loaded: 0x4001300 - 0x40015e4 INFO: FCONF: Config file with image ID:24 loaded at address = 0x4001300 INFO: BL1: Loading BL2 INFO: Loading image id=1 at address 0x4022000 INFO: Image id=1 loaded: 0x4022000 - 0x402cca1 NOTICE: BL1: Booting BL2 INFO: Entry point address = 0x4022000 INFO: SPSR = 0x3cd INFO: Configuring TrustZone Controller INFO: Total 6 regions set. INFO: [GPT] Boot Configuration INFO: PPS/T: 0x0/32 INFO: PGS/P: 0x0/12 INFO: L0GPTSZ/S: 0x0/30 INFO: PAS count: 0x5 INFO: L0 base: 0x4003000 INFO: [GPT] PAS[0]: base 0x80000000, size 0x7c000000, GPI 0x9, type 0x1 INFO: [GPT] PAS[1]: base 0xfc000000, size 0x1c00000, GPI 0x8, type 0x1 INFO: [GPT] PAS[2]: base 0xfdc00000, size 0x2000000, GPI 0xb, type 0x1 INFO: [GPT] PAS[3]: base 0xffc00000, size 0x300000, GPI 0xa, type 0x1 INFO: [GPT] PAS[4]: base 0xfff00000, size 0x100000, GPI 0xa, type 0x1 INFO: Enabling Granule Protection Checks INFO: FCONF: Reading FW_CONFIG firmware configuration file from: 0x4001010 INFO: FCONF: Reading firmware configuration information for: dyn_cfg INFO: FCONF: Reading TB_FW firmware configuration file from: 0x4001300 INFO: FCONF: Reading firmware configuration information for: arm_sp NOTICE: BL2: v2.7(debug):v2.7.0-235-g1631f9c75 NOTICE: BL2: Built : 11:44:42, Aug 22 2022 INFO: BL2: Doing platform setup INFO: BL2: Loading image id 3 INFO: Loading image id=3 at address 0x4004000 INFO: Image id=3 loaded: 0x4004000 - 0x401baf7 INFO: BL2: Loading image id 23 INFO: Loading image id=23 at address 0x7f00000 INFO: Image id=23 loaded: 0x7f00000 - 0x7f023b5 INFO: BL2: Loading image id 25 INFO: Loading image id=25 at address 0x4001300 INFO: Image id=25 loaded: 0x4001300 - 0x4001348 INFO: BL2: Loading image id 34 INFO: Loading image id=34 at address 0xfdc00000 INFO: Image id=34 loaded: 0xfdc00000 - 0xfdc018d1 INFO: BL2: Loading image id 4 INFO: Loading image id=4 at address 0x6000000 INFO: Image id=4 loaded: 0x6000000 - 0x6100000 INFO: BL2: Skip loading image id 21 INFO: BL2: Skip loading image id 22 INFO: BL2: Loading image id 26 INFO: Loading image id=26 at address 0x4001500 INFO: Image id=26 loaded: 0x4001500 - 0x4001b65 INFO: BL2: Loading image id 5 INFO: Loading image id=5 at address 0x88000000 INFO: Image id=5 loaded: 0x88000000 - 0x8802a3c0 INFO: BL2: Loading image id 27 INFO: Loading image id=27 at address 0x80000000 INFO: Image id=27 loaded: 0x80000000 - 0x80000048 INFO: BL2: Loading image id 40 INFO: Loading image id=40 at address 0x7000000 INFO: Image id=40 loaded: 0x7000000 - 0x700d7d0 INFO: BL2: Loading image id 41 INFO: Loading image id=41 at address 0x7100000 INFO: Image id=41 loaded: 0x7100000 - 0x710f7d0 INFO: BL2: Loading image id 42 INFO: Loading image id=42 at address 0x7200000 INFO: Image id=42 loaded: 0x7200000 - 0x720f7d0 INFO: BL2: Loading image id 43 INFO: Loading image id=43 at address 0x7600000 INFO: Image id=43 loaded: 0x7600000 - 0x7613620 NOTICE: BL2: Booting BL31 INFO: Entry point address = 0x4004000 INFO: SPSR = 0x3cd INFO: BL31 FCONF: FW_CONFIG address = 4001010 INFO: FCONF: Reading FW_CONFIG firmware configuration file from: 0x4001010 INFO: FCONF: Reading firmware configuration information for: dyn_cfg WARNING: Skip SMMU GPC configuration. INFO: FCONF: Reading HW_CONFIG firmware configuration file from: 0x7f00000 INFO: FCONF: Reading firmware configuration information for: cpu_timer INFO: FCONF: Reading firmware configuration information for: uart_config INFO: FCONF: Reading firmware configuration information for: topology INFO: FCONF: Reading firmware configuration information for: gicv3_config NOTICE: BL31: v2.7(debug):v2.7.0-235-g1631f9c75 NOTICE: BL31: Built : 11:44:52, Aug 22 2022 INFO: GICv3 with legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: Maximum SPI INTID supported: 255 INFO: BL31: Initializing runtime services INFO: SPM Core setup done. INFO: RMM setup done. INFO: BL31: Initializing BL32
Thanks, Shameer
On Mon, 2022-08-22 at 11:36 +0000, Shameerali Kolothum Thodi wrote:
Hi Javier,
-----Original Message----- From: Javier Almansa Sobrino
[mailto:Javier.AlmansaSobrino@arm.com]
Sent: 22 August 2022 12:12 To: Shameerali Kolothum Thodi
<shameerali.kolothum.thodi@huawei.com
;
tf-a@lists.trustedfirmware.org Subject: Re: [TF-A] TF-A RME support
Hi Shameer,
May I know the parameters you are using to boot up FVP as well as the version?
Please find below,
FVP_Base_RevC-2xAEMvA \ -C bp.flashloader0.fname=/home/sk/arm-TF-A- RME/build/fvp/debug/fip.bin \ -C bp.secureflashloader.fname=/home/sk/arm-TF-A- RME/build/fvp/debug/bl1.bin \ -C bp.refcounter.non_arch_start_at_default=1 \ -C bp.refcounter.use_real_time=0 \ -C bp.ve_sysregs.exit_on_shutdown=1 \ -C cache_state_modelled=1 \ -C cluster0.NUM_CORES=4 \ -C cluster0.PA_SIZE=48 \ -C cluster0.ecv_support_level=2 \ -C cluster0.gicv3.cpuintf-mmap-access-level=2 \ -C cluster0.gicv3.without-DS-support=1 \ -C cluster0.gicv4.mask-virtual-interrupt=1 \ -C cluster0.has_arm_v8-6=1 \ -C cluster0.has_branch_target_exception=1 \ -C cluster0.rme_support_level=1 \ -C cluster0.has_rndr=1 \ -C cluster0.has_amu=1 \ -C cluster0.has_v8_7_pmu_extension=2 \ -C cluster0.max_32bit_el=-1 \ -C cluster0.restriction_on_speculative_execution=2 \ -C cluster0.restriction_on_speculative_execution_aarch32=2 \ -C cluster1.NUM_CORES=4 \ -C cluster1.PA_SIZE=48 \ -C cluster1.ecv_support_level=2 \ -C cluster1.gicv3.cpuintf-mmap-access-level=2 \ -C cluster1.gicv3.without-DS-support=1 \ -C cluster1.gicv4.mask-virtual-interrupt=1 \ -C cluster1.has_arm_v8-6=1 \ -C cluster1.has_branch_target_exception=1 \ -C cluster1.rme_support_level=1 \ -C cluster1.has_rndr=1 \ -C cluster1.has_amu=1 \ -C cluster1.has_v8_7_pmu_extension=2 \ -C cluster1.max_32bit_el=-1 \ -C cluster1.restriction_on_speculative_execution=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=0xFFFF0475 \ -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
\ -C bp.pl011_uart0.out_file=uart0.log \ -C bp.pl011_uart1.out_file=uart1.log \ -C bp.pl011_uart2.out_file=uart2.log \ -C pctl.startup=0.0.0.0 \ -Q 1000 \ "$@"
And version of FVP used,
FVP_Base_RevC-2xAEMvA --version
Fast Models [11.18.16 (Jun 16 2022)]
Thanks, Shameer
Cheers, Javier
On Mon, 2022-08-22 at 11:06 +0000, Shameerali Kolothum Thodi via TF-A wrote:
Hi,
I am trying to setup and run the RME support in TF-A, using the steps described here,
https://trustedfirmware-a.readthedocs.io/en/latest/components/realm-
ma
nagement-extension.html#building-and-running-tf-a-with-rme
Build goes smoothly and when I launch FVP to run the RME tests using the command line mentioned in the link, the FVP terminal_0 seems to be get stuck at the below line,
Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. NOTICE: Booting Trusted Firmware NOTICE: BL1: v2.7(debug):v2.7.0-235-g1631f9c75 NOTICE: BL1: Built : 11:44:37, Aug 22 2022 INFO: BL1: RAM 0x4035000 - 0x403c000 INFO: Loading image id=31 at address 0x4001010 INFO: Image id=31 loaded: 0x4001010 - 0x4001258 INFO: FCONF: Config file with image ID:31 loaded at address = 0x4001010 INFO: Loading image id=24 at address 0x4001300 INFO: Image id=24 loaded: 0x4001300 - 0x40015e4 INFO: FCONF: Config file with image ID:24 loaded at address = 0x4001300 INFO: BL1: Loading BL2 INFO: Loading image id=1 at address 0x4022000 INFO: Image id=1 loaded: 0x4022000 - 0x402cca1 NOTICE: BL1: Booting BL2 INFO: Entry point address = 0x4022000 INFO: SPSR = 0x3cd INFO: Configuring TrustZone Controller INFO: Total 6 regions set.
Both the tf-a-tests.git and trusted-firmware-a.git are master branch and I am using the FVP_Base_RevC-2xAEMvA v11.18.16.
I am totally new to this setup and maybe I am missing something here.
Appreciate any help to get this resolved or tips to debug further.
Thanks, Shameer
-- TF-A mailing list -- tf-a@lists.trustedfirmware.org To unsubscribe send an email to tf-a-leave@lists.trustedfirmware.org