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.

Head less build in CCS4 crashes randomly a the beginning of the build

Other Parts Discussed in Thread: CCSTUDIO

Hi,

I'm trying to build a project in head less mode using CCS4 (Version 4.1.2.00027).

The import of the project works fine but the compilation is not always working.

When it doesn't work, I receive the error message below (coming few seconds after Building is printed, so really early in the process):

D:\share4linux\dsp\Application>"c:\Program Files\Texas Instruments\ccsv4\eclipse"\jre\bin\java -jar  "c:\Program Files\Texas Instruments\ccsv4\eclipse"\startup.jar -data d:\workspace -application com.ti.ccstudio.apps.projectBuild -ccs.projects XTRAN_DSP_Application

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
CCS headless build starting... [Thu Feb 23 17:42:47 CET 2012]
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

================================================================================
Pre processing...


================================================================================
Building...

--------------------------------------------------------------------------------
org.eclipse.core.internal.resources.ResourceException: Errors during build.
        at org.eclipse.core.internal.resources.Project.build(Project.java:91)
        at com.ti.ccstudio.apps.project.Build.buildProjects(Build.java:246)
        at com.ti.ccstudio.apps.project.Build.doRun(Build.java:104)
        at com.ti.ccstudio.apps.project.BaseHeadlessApp$1.run(BaseHeadlessApp.java:168)
        at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1737)
        at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1719)
        at com.ti.ccstudio.apps.project.BaseHeadlessApp.internalRun(BaseHeadlessApp.java:166)
        at com.ti.ccstudio.apps.project.BaseHeadlessApp.run(BaseHeadlessApp.java:136)
        at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
        at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
        at org.eclipse.core.launcher.Main.run(Main.java:996)
        at org.eclipse.core.launcher.Main.main(Main.java:971)

D:\share4linux\dsp\Application>

The compilation works from time to time, but not in a reliable way. This prevents me to get a working automatical build of the project.

Note: I never see the compilation of the same project fail when done using the GUI.

Is there a fix available of a way to get more debug info?

Hope somebody can help me on this one.

Daniel

  • Hi Daniel,

    You CCSv4 version is pretty old. Could you try updating your version of CCS? CCSv5.1 is the latest but if you would like to avoid the major revision change and stick to v4, version 4.2.5 is the latest update for v4. I don't know for sure if it has a fix for your issue but I do know that there have been various fixes and improvements in the headless project commands since your release. Hopefully it will have a fix for you issue.

    Thanks

    ki

  • Hi,

    Unfortunately, we cannot upgrade to the latest version due to certification problems.

    Following your advice, we tried to upgrade to version 4.1.3 and it seems to fix our problem so we will stay on this version.

    Thanks for your help!

    Daniel