• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 545 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

xs.exe has stopped working

Usman Majid
Intellectual 620 points
Other Parts Discussed in Thread: SYSBIOS

Hi, I'm trying to use xdctools 3.24.3.33 with ipc 1.25.1.09, sysbios 6.34.3.19, and syslink 2.21.03.11. This is the combination of files I have found that works for my syslink program. I have no problem compiling the code in linux using g++/gcc, but I am having some problems debugging the dsp without being able to printf from the dsp side. So I decided I would load the dsp program into code composer so I would be able to use the jtag to see what is going on.

The error I am getting is that when I click build, after 1-2 seconds there is a popup stating "xs.exe has stopped working", and then the build window closes and nothing happens. I can switch the xdc version to a version 3.31+ and this doesn't happen, but my program will not work with a higher version of xdctools.

Is there an alternative way to debug the dsp or be able to see printf from the dsp side? Because my program runs without crashing on the board itself and I can interact with the arm side through putty. I build my program off the syslink sharedregion example, so I am passing things back to the arm and printing them out using variables in the shared region.

  • 0
    TI__Mastermind 35645 points

    Hi,

    Thanks for your post.

    This error often causes due to the incomplete xdc tools installation. More specifically, check if there is a directory 'jre/bin/client' in your installation, and check if there is a file jvm.dll in there.

    May be, if you could reinstall CCS, this wouldn't exhibit this issue else, would recommend you to replace the entire "jre" folder with a copy from working xdc tools version installation directory which is usually  "C:\ti\xdctools_3_2x_xx_xx". I guess, the above issue could happen when you upgrade the xdc tools version in which the installation was incomplete.

    The above recommendation should make you work again.

    Thanks & regards,

    Sivaraj K

    ------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question

    -------------------------------------------------------------------------------------------------------

  • 0 in reply to Sivaraj Kuppuraj
    Intellectual 620 points
    Thanks, I tried reinstalling before but that didn't help. When I manually deleted the old folder of the installation then reinstalled it worked.
    Is there a way to debug the dsp without having to load the program through code composer? I can load the dsp program from the arm using syslink.
  • 0 in reply to Usman Majid
    TI__Mastermind 35645 points
    Hi,

    Thanks for your update.

    It is not possible to debug the dsp app. without loading the image to the target through CCS debugger and before loading the image, target needs to be connected through appropriate emulator.

    Thanks & regards,
    Sivaraj K