Hi Adam,

The RME support in Arm DS was introduced this year. Could you ensure that you are using the latest version of Arm DS ? It seems Arm DS is not able to connect to the model when RME is enabled. You may have to import a new model connection to Arm DS to be able to debug. For this , start the model with Debug Server (-S or -I depending on whether using CADI or IRIS Debug interface) , then in Arm DS, go to File -> New Model Connection and complete the new model connection wizard.

 

If you still run into issues, you could try contacting the Arm DS support team.

 

Best Regards

Soby Mathew

 

From: Ádám Tóth via TF-A <tf-a@lists.trustedfirmware.org>
Sent: 13 October 2022 12:38
To: tf-a@lists.trustedfirmware.org
Subject: [TF-A] Debug RME feature on FVP_Base_RevC-2xAEMvA_11.19_14

 

Hello,

I am about to debug RME feature with ARM DS on FVP_Base_RevC-2xAEMvA_11.19_14  platform. I am using the Trusted Firmware with RME extension based on this description https://trustedfirmware-a.readthedocs.io/en/latest/components/realm-management-extension.html My observation is running plainly the model, everything looks ok, the VFP can run the SW without any problem. (I can see the consol windows with normal booting procedure)

In case I would like to set up the ARM debugger in ARM DS, the simulation immediately stops after start with a popup window: "Unable to connect to device ARMAEM-a_MP_0 Error opening connection to device 16 Socket is closed(E_io_error) Socket is closed"

Apparently my Debug settings are good: With the same settings I can run/debug the complete ARM Reference Solution (Linux, u-boot, TrustedFirmware) based on this description: https://gitlab.arm.com/arm-reference-solutions/arm-reference-solutions-docs/-/tree/master/docs/aemfvp-a but if I add additional flags for FVP: (-C cluster0.rme_support_level=2 -C cluster1.rme_support_level=2) I still can run the model, but cannot debug so when I activate the RME feature the ARM debugger do the previously mentioned behavior (stops right after start)

How can I workaround this? What is the most efficient way to debug FVP with RME support. Any help is welcome here.

Bye,
Adam