• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 53 subscribers
  • Views 741 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.

A question about CCS4.2.4.00033 and SD-XDS560v2 STM

Z-SEED
Intellectual 660 points

Hi,

I met a question about CCS4.2.4.00033.
 
I used sdxds560v2 to emulate DM6437 with CCS4.2.4.00033. After I connected the target board, then I pointed "Terminate All", then a dialog popuped and said " Java(TM) 2 Platform Standard Edition binary has stopped working", then CCS was closed.
 
However, if I just launched the debugger, and not connected the target board, then I pointed "Terminate All", then everything was ok.
 
The CCS version is CCS4.2.4.00033.
The emulator is SD XDS560v2 STM.
The OS is Windows 7 64bit.
The CPU of PC is AMD Athlon(tm) II X4 640 Processor.
  • 0
    Intellectual 660 points

    Is anybody answer the question?

    My target board with DM6437 used well in win7 32bit OS. So I think maybe it is the problem of CCS4.2.4.00033 in 64bit operation system.

  • 0 in reply to Z-SEED
    TI__Guru* 84110 points

    Z,

    Since this is a CCSv4 software question, the right people to address it are in the Code Composer Forum. This thread will be moved there from the C64x Single Core Forum, which is for hardware questions. We have a lot of forums, so we understand the difficulty with figuring out where to go. But answers are faster in the right forum, and better.

    To start, though, please look at the TI Wiki Pages for FAQ - CCSv4. The Wiki is a great place to find information like this. It may mean that you search TI.com and the forums and the Wiki, until you start to find which tends to have which type of information that you are looking for.

    Regards,
    RandyP

     

    If you need more help, please reply back. If this answers the question, please click  Verify Answer  , below.

  • 0
    TI__Guru**** 173310 points

    Z-SEED said:
    After I connected the target board, then I pointed "Terminate All", then a dialog popuped and said " Java(TM) 2 Platform Standard Edition binary has stopped working", then CCS was closed.

    We've had a few reports in the past of CCS crashing when terminating debug session but we added fixes in some of the early 4.2.x versions as well. Please take a look at this related thread: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/36438.aspx

    Since you're still experiencing this issue with the latest 4.2.4, could you please generate the diagnostic logs as described in this page and attach it here as a zip file?
    http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#CCS_Diagnostic_Logs
    That should help our engineering team look into it again and see if there are lingering problems that still need addressed.

    Also, as suggested in this post, could you try renaming the ctools.dll file found in  /ccsv4/emulation/analysis/bin/ to something else and see if that makes the crash go away?

  • 0 in reply to RandyP
    Intellectual 660 points

    RandyP:

    I posted the file in CCS Forum, your people moved it to the C64x Single Core Forum. Now it is TI don't want to ansker my question, just move my posted form here to there, and then moved from there to here again!!!

  • 0 in reply to AartiG
    Intellectual 660 points

    AartiG:

    Thanks for your support. The crash went away after I renamed the ctools.dll.

  • 0 in reply to Z-SEED
    TI__Guru**** 173310 points

    Z-SEED said:

    Thanks for your support. The crash went away after I renamed the ctools.dll.



    I am glad to hear that renaming the ctools.dll no longer crashes CCS. However, if you have the time we would still appreciate if you could generate and provide us with the diagnostic logs as described in this page http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#CCS_Diagnostic_Logs
    This would require that you rename ctools.dll back to its original, and reproduce the crash again. Make sure to enable debug server logging and ctools/trace logging as described in that wiki page before reproducing the problem.

    Even though renaming that dll file is a workaround, we do want to get to the root cause of the problem and the logs should help with that.