• Locked Locked
  • Replies 2 replies
  • Subscribers 119 subscribers
  • Views 2254 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

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

Running Model Debugger for more than one core

Vitali Sokhin
Note: This was originally posted on 15th July 2013 at http://forums.arm.com

Hello,

I try to run Model Debugger for ARMv8 target. It works fine if I choose to work with a single core.
If change ARM.NUM_CORES to be, for example, 2, then a window for the cpu0 opens normally,
but a window for cpu1 enters endless refresh loop (see the attached screenshot).

The only way to get out of it is to "kill -9" the model debugger process.

Can anyone please help to figure out what is going wrong?

   Thank you,
     Vitali
Parents
  • Arm Employee Badge
    Note: This was originally posted on 15th July 2013 at http://forums.arm.com


    Hello,

    I try to run Model Debugger for ARMv8 target. It works fine if I choose to work with a single core.
    If change ARM.NUM_CORES to be, for example, 2, then a window for the cpu0 opens normally,
    but a window for cpu1 enters endless refresh loop (see the attached screenshot).

    The only way to get out of it is to "kill -9" the model debugger process.

    Can anyone please help to figure out what is going wrong?

       Thank you,
         Vitali


    Vitali,

    Can you tell me which version of ModelDebugger you are using and the file name of the ARMv8 target you are using?

    Chris

Reply
  • Arm Employee Badge
    Note: This was originally posted on 15th July 2013 at http://forums.arm.com


    Hello,

    I try to run Model Debugger for ARMv8 target. It works fine if I choose to work with a single core.
    If change ARM.NUM_CORES to be, for example, 2, then a window for the cpu0 opens normally,
    but a window for cpu1 enters endless refresh loop (see the attached screenshot).

    The only way to get out of it is to "kill -9" the model debugger process.

    Can anyone please help to figure out what is going wrong?

       Thank you,
         Vitali


    Vitali,

    Can you tell me which version of ModelDebugger you are using and the file name of the ARMv8 target you are using?

    Chris

Children
No data