• Locked Locked
  • Replies 3 replies
  • Subscribers 120 subscribers
  • Views 2670 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

Model Debugger will exit when the plugin Tarmac is added

Heron Zhang
Note: This was originally posted on 19th October 2012 at http://forums.arm.com

Hi,
I want trace the instructions the CPU(Cortex-A9) executed, then I found the ARM Fast Models. After using Model debuggers of  Fast Models with plugin Tarmac several times normally,and get some trace files, the model debugger now  will exit every time when the plugin Tarmac is added, but  it will run normally when the Tarmac not started together. When the Tarmac plugin not started, the model debugger will run rightly.
When start the Model Debugger with the plugin Tarmac, it will exit automaticly after running for a while,and the error information is as follow:

[root@hw022 bin]# ./modeldebugger
terminal_0: Listening for serial connection on port 5000
terminal_3: Listening for serial connection on port 5001
terminal_1: Listening for serial connection on port 5002
terminal_2: Listening for serial connection on port 5003

FlashLoader: Loaded 41MB
ALSA lib confmisc.c:768:(parse_card) cannot find card '0'
ALSA lib conf.c:3513:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:3513:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1251:(snd_func_refer) error evaluating name
ALSA lib conf.c:3513:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:3985:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2184:(snd_pcm_open_noupdate) Unknown PCM default
Attaching the Tarmac trace to component RTSM_EB_Cortex_A9.coretile.core.cpu0.
Illegal instruction



I had reinstalled the Fast models several times  in different servers, disappointedly....How can I sovlve this problem? THANKS  A  LOT!
Parents
  • Note: This was originally posted on 22nd October 2012 at http://forums.arm.com

    Thanks very much,I tryed it anain as you suggested.The error infomation is :Information (Debugging Terminated) Debugging of target 'coretile.core.cpu0' is terminated. Reason: Simulation has sent kill interface

    signal
    Does this mean there is something wrong with my simulatin? Why I can run this simulation without trace.

    I've not had this problem myself, but a couple of thoughts....
    I am guessing that you are building the model as a library (.so or .dll), then loading that through MD.  Try loading the library with the command line tool Model Shell instead, passing -S (note the s is upper case).  This will start the model with debug enabled. Launch MD, the try connecting (not loading) to a simulation.  This should tell you whether it's MD that has a problem or the model/plugin.
    Assuming its the plugin, check you host OS and build tool chain.  Are they what the Fast Models tool chain call for?  The Tarmac plugin is shipped pre-built, but you have to build the models yourself.  The crash might be down to you using a slightly different version of GCC to the plugin, causing weird runtime problems.








Reply
  • Note: This was originally posted on 22nd October 2012 at http://forums.arm.com

    Thanks very much,I tryed it anain as you suggested.The error infomation is :Information (Debugging Terminated) Debugging of target 'coretile.core.cpu0' is terminated. Reason: Simulation has sent kill interface

    signal
    Does this mean there is something wrong with my simulatin? Why I can run this simulation without trace.

    I've not had this problem myself, but a couple of thoughts....
    I am guessing that you are building the model as a library (.so or .dll), then loading that through MD.  Try loading the library with the command line tool Model Shell instead, passing -S (note the s is upper case).  This will start the model with debug enabled. Launch MD, the try connecting (not loading) to a simulation.  This should tell you whether it's MD that has a problem or the model/plugin.
    Assuming its the plugin, check you host OS and build tool chain.  Are they what the Fast Models tool chain call for?  The Tarmac plugin is shipped pre-built, but you have to build the models yourself.  The crash might be down to you using a slightly different version of GCC to the plugin, causing weird runtime problems.








Children
No data