Please note: We are aware of an issue affecting replies on the Arm Community forums, which may not be loading as expected.
We apologize for any inconvenience and appreciate your patience while we investigate and work to resolve the issue.
Thank you for your understanding.
Hello
on the same Linux RH7 machine, it happens that the performances of ARM DS when connecting the debugger to a waiting Virtual Platform Fast Model (using CADI) are very random, and often, it takes 3-4 mns to
establish the connection. Sometimes, it takes only a few seconds.But most of the time, it's too slow.
I don't understand why there can be so much difference in performances of connection to a virtual platform. What can I do when ARM DS takes too much time to connect to a Virtual Platform ?
Best regards
Frederic Huguet
Hello Stephen,
many thanks for your question. Could you please tell me how to configure the ^ports used for the debugger connection to the VP ? That is, where in the ARM DS is located the option to be used ?
This is not very clear on my side ....
Best Regards
Frederic
Hi again,Is there a particular reason why you are using CADI? "Iris" supersedes CADI, and is now the default in Arm DS Debugger.You can launch a model with, for example: ./FVP_Base_Cortex-A53x1 --iris-server --print-port-number"--print-port-number" reports the port number that the Iris server is listening to, for example:Iris server started listening to port 7100If that port is already in use, the next port is selected, for example, 7101.Make a note of that port number.Then, in the debug launch dialog, you can specify the same port number:The FVP models also support:--iris-port-range MIN:MAXSet the range of ports to scan when starting an Iris server. The first available port found will be used.and--iris-port PORTSet a specific port to use for the Iris server.
Stephen