• State Suggested Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 120 subscribers
  • Views 1583 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ARM DS slow connection to Fast Model

FredericH

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 

Parents
  • 0 Arm Employee Badge in reply to FredericH

    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 7100

    If 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:MAX
    Set the range of ports to scan when starting an Iris server. The first available port found will be used.
    and
    --iris-port PORT
    Set a specific port to use for the Iris server.

    Stephen

Reply
  • 0 Arm Employee Badge in reply to FredericH

    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 7100

    If 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:MAX
    Set the range of ports to scan when starting an Iris server. The first available port found will be used.
    and
    --iris-port PORT
    Set a specific port to use for the Iris server.

    Stephen

Children
No data