• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 52 subscribers
  • Views 2217 views
  • Users 0 members are here
Support feedback
Options
Options

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 to existing Eclipse fails (error: No CCS installation foud)

Manuel Kracht
Prodigy 100 points
Other Parts Discussed in Thread: CODECOMPOSER

 

I'm trying to install CCS 5.0.9 and 5.1.1 to my existing eclipse Indigo to develop C2000 software.

After intstalling CCS to this existing exlipse I always get the following errors in eclipse:

 

DLL file could not be found.  Expecting an absolute path of the library: .TraceJNI.dll

and

No CCS installation found!


Codecomposer preferences are not visible in Eclipse->Window->Preferences

 

Does anyone knows how to solve my problems

  • 0
    TI__Guru*** 130875 points

    Hi Manuel,

    what version is your existing eclipse?

    CCSv5 should be installed over the latest C/C++ Indigo version ... link below.

    http://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/indigo/SR1/eclipse-cpp-indigo-SR1-incubation-win32.zip

    Please keep us informed.

    Best Regards,

    Lisa

  • 0 in reply to Lisa TI
    Prodigy 100 points

    Hi Lisa,

    I was using eclipse 3.7.0, now with 3.7.1 ist works.

    But there is one more problem now. When trying to debug I always get the following error message:

     

    Regards

    Manuel

  • 0 in reply to Manuel Kracht
    Prodigy 100 points

    Installed plugins and error log:

    !ENTRY org.eclipse.core.jobs 4 2 2012-02-20 09:03:17.375
!MESSAGE An internal error occurred during: "Launching New_configuration".
!STACK 0
java.lang.NullPointerException
	at com.ti.common.project.core.internal.CommonProjectCorePlugin.getDelegateFactory(CommonProjectCorePlugin.java:491)
	at com.ti.common.project.core.internal.CommonProjectCorePlugin.getToolChainPropertyProvider(CommonProjectCorePlugin.java:478)
	at com.ti.common.project.core.util.CTIProjectCoreUtils.getToolChainPropertyProvider(CTIProjectCoreUtils.java:415)
	at com.ti.common.project.core.util.CTIProjectCoreUtils.getConfigurationSettings(CTIProjectCoreUtils.java:975)
	at com.ti.common.project.core.util.CTIProjectCoreUtils.getDependencies(CTIProjectCoreUtils.java:1070)
	at com.ti.common.project.core.util.CTIProjectCoreUtils.getDependencies(CTIProjectCoreUtils.java:1085)
	at com.ti.ccstudio.debug.launch.CCSLaunchDelegate.addReferencedProjects(CCSLaunchDelegate.java:497)
	at com.ti.ccstudio.debug.launch.CCSLaunchDelegate.getAllProjects(CCSLaunchDelegate.java:290)
	at com.ti.ccstudio.debug.launch.CCSLaunchDelegate.getProjectsForProblemSearch(CCSLaunchDelegate.java:281)
	at com.ti.ccstudio.debug.launch.CCSLaunchDelegate.getBuildOrder(CCSLaunchDelegate.java:439)
	at org.eclipse.debug.core.model.LaunchConfigurationDelegate.saveBeforeLaunch(LaunchConfigurationDelegate.java:255)
	at com.ti.ccstudio.debug.launch.CCSLaunchDelegate.preLaunchCheck(CCSLaunchDelegate.java:213)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:809)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
	at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:928)
	at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1132)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
  • 0 in reply to Manuel Kracht
    TI__Guru*** 130875 points

    Hi Manuel,

    do you also get this if you manually try to launch a debug session? Ie if you launch the target configuration or start from the debug perspective?   Did you create a CCS project?

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Prodigy 100 points

    Dear Lisa,

    I'm not using a CCS project, its a makefile projekt. I started the debug session via "Debug Configuration" window with a "Code Composer Studio - Device Debugging" target configuration.  

    After installing CCS 5.0.9 instead of 5.1.1, everything works fine!

    Do I need 5.1.1 bugfixes for C2000 MUCs?

     

    Regards

    Manuel

  • 0 in reply to Manuel Kracht
    TI__Guru*** 130875 points

    Hi Manuel,

    no, you do not specifically need 5.1.1 for C2000 coding.  Of course we always recommend being up to date but if 5.1.1 is problematic for you, then I would suggest skipping this update for now and grabbing a later release.  The code generation tools are installed alongside CCS and are actually separate entities you can update yourself so you should be fine to use 5.0.9.


    I am glad to hear you have a working environment and hope the above helps clarify for you.

    All the best with development.

    Best Regards

    Lisa