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 I can workaround this? What is the most efficient way to debug FVP with RME support. Any help is welcome here.
Thank you very much for the quick response! I followed the steps you proposed: running the model from consol IRIS server activated, and connecting it with new custom model setup. But unfortunately it produced the same problem. Rerun the same setup without RME feature activated was everything ok!
But what I realized after several times: If I run the proposed setup (RME activated), but I am using CADI server instead of IRIS it looks like I can join with the ARM debugger seamlessly. So my problem is resolved in this way!
Hi again Adam,
Are you using the Gold or Platinum edition of Arm Development Studio?RME functionality is only supported in Platinum edition (2022.b), not Gold (2022.1), which I believe is causing the issue.
I am using the Gold edition (2022.1)Thank you again for the information.