• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 810 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.

CCS 5.5 + Window 7 64 bit: Simulator failure: Cannot connect to target CPU.

SThakkar
Intellectual 470 points

Other Parts Discussed in Thread: CCSTUDIO

ccs.zip

 

I get an error for the cycle accurate simulator or functional simulator ccxml. And I get the error in all my workspaces even if I restart CCS and my PC.

 

Looking into the CCS forums, I see that a lot of people have complained about similar issues, not just with CCS debug session with emulator but also the simulator. The simulator does not have anything to do with JTAG issues. It has to be something in software.

 

After going through many post, I tried the following but nothing helped:

  1. Increase the xmx memory in the eclipse.ini and ccstudio.ini.

  2. Create a new the debug session target ccxml

  3. Check the jre environment.

  4. Create a new workspace

 

I remember I had to install JDK and possibly related version of JRE on my PC for some other apps running on my PC.

I found that the JRE environment in control panel was updated to only have version 1.8. I found that JRE that came with eclipse was lost. So, I searched and added JRE that came with CCS 5.5, and add and enabled just that JRE. Now, CCS point to correct JRE:

java.home=C:\ti\ccsv5\eclipse\jre

 

I restarted the PC and launched CCS 5.5 again. Still, the simulator keeps giving me the same error.  I have attached logs when I tried the simulator in a clean environment (new CCS 5.5 workspace and new ccxml for debug session) 

  • 0
    TI__Guru**** 171729 points
    Hi,

    That is certainly a very unusual message to be thrown when using a Simulator. I don't recall seeing this before and couldn't find any posts that show this specific error message when the debugger is configured to use the simulator. If I understood your post correctly it seems you found some threads - would you mind sharing the links?

    Also, which simulator are you trying to use? I have been using simulators for many years in CCSv5.5 + Windows 7/64 and haven't seen many issues. Perhaps this is tied to a specific simulator.

    At last, how are you launching the simulator? Directly from the project or from the Target Configurations view?

    Regards,
    Rafael
  • 0 in reply to desouza
    Intellectual 470 points

    C6678SimulatorFunctional.zipTechnically, the exact message is: Can't Initialize Target CPU

    I could not figure out what leads to this from the log file I attached in the previous post.

    !ENTRY com.ti.ccstudio.debug 1 0 2016-10-04 09:36:25.047

    !MESSAGE DS_ERROR: Can't Initialize Target CPU

    I use the C6678 big endian function or cycle accurate simulator. I have attached ccxml. I am launching the simulator from that Target Configurations tab.

    Issues that show up when I search for "Can't Initialize Target CPU" on the forum:

    Not everything applies in my case, but I tried some things anyways as I mentioned in the previous post.

    thanks

  • 0 in reply to SThakkar
    TI__Guru**** 171729 points

    Hi,

    Thanks for sending the configuration file. It seems the errors are coming from your CCSv5.5 install, as I am able to run it here without a problem:

    In my setup I have not only CCSv5.5 but several others (6.1.3, 6.2.0, etc.) and several Java installs as well, both 32 and 64-bit. There were some issues repored in the past regarding Windows environment variables influencing the functionality of CCS - something mentioned in this thread.

    The last piece of information log that you can send is the Debug Server log. Check this wiki topic to learn how to obtain it.

    If this log does not reveal anything specific, unfortunately I would strongly suggest you to reinstall your copy of CCSv5.

    Regards,

    Rafael

  • 0 in reply to desouza
    Intellectual 470 points

    Reinstalling CCS resolved the problem.

    Thanks