• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 1536 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.0 gets stuck after repeated command line (headless) builds

gbl
Intellectual 400 points
Other Parts Discussed in Thread: CCSTUDIO

Hi,

with CCS 5.0 (all variants so far) I have the following problem (which occurs also with totally new workspaces, OS used is Windows XP):

Headless builds like

eclipsec -nosplash -data %WSP_DIR% -application com.ti.ccstudio.apps.projectBuild -ccs.projects Twin_dspDI Twin_dspDT Twin_dspEI Twin_dspET -ccs.configuration %CCS_CONFIG% -ccs.clean 1>"%WORKSPACE%\..\builds\%BUILD_ID%"\cleanTwin.stdout.log 2>"%WORKSPACE%\..\builds\%BUILD_ID%"\cleanTwin.stderr.log

eclipsec -nosplash -data %WSP_DIR% -application com.ti.ccstudio.apps.projectBuild -ccs.projects Twin_dspDI Twin_dspDT Twin_dspEI Twin_dspET -ccs.configuration %CCS_CONFIG%

run fine the first time. The 2nd time (sometimes also later) they get stuck forever either during the clean or build process. On a multi-core PC this can be recognized by one core showing a permanent maximum load (which suddenly decreases when the process eclipsec.exe is stopped).

The only way to correct this behaviour is to do a 'clean' in the GUI. In rare cases only deleting and re-importing all projects helps.

First tests with CCS 5.1 indicate that this problem does not exist there (although this may also be accident).

Are any bugs of Eclipse 3.6 (soved in 3.7) known that could cause this behavior? Or in TI plugins which have been modified from 5.0 to 5.1?

Use of CCS 5.0 is the preferred solution as 5.1 is still in development and we need the tools for product design.

 

 

  • 0
    TI__Genius 15190 points

    Hi, 
    I have a difficult time reproducing this issue. I have used a patched version of CCS v5.0.2 with 6 projects in workspace, most of them are relatively small, but one is relatively large. I have rebuilt these projects using commands from above (making adjustments for workspace paths and project names).  In my case there are no dependencies between projects. I have attempted to run the build 5 times in succession without a hang. Do you have dependencies between your projects? Is there anything else that you can think that might help in reproducing these issues? 

     

    Thanks,
    Martin

     

  • 0 in reply to MartinS
    Intellectual 400 points

    Hi,

    there are dependencies between the projects. The strucure is something like

    Proj1 = ProjC + ProjD + ProjF

    Proj2 = ProjC + ProjD + ProjG

    Proj3 = ProjC + ProjE + ProjH

    Proj4 = ProjC + ProjE + ProjI

    Proj1-4 are built with two commands (first clean all projects, then build them all).

    eclipsec -nosplash -data %WSP_DIR% -application com.ti.ccstudio.apps.projectBuild -ccs.projects Proj1 Proj2 Proj3 Proj4 -ccs.configuration %CCS_CONFIG% -ccs.clean 1>"%WORKSPACE%\..\builds\%BUILD_ID%"\clean.stdout.log 2>"%WORKSPACE%\..\builds\%BUILD_ID%"\clean.stderr.log

    eclipsec -nosplash -data %WSP_DIR% -application com.ti.ccstudio.apps.projectBuild -ccs.projects Proj1 Proj2 Proj3 Proj4 -ccs.configuration %CCS_CONFIG%

    All I know is that the problem is somewhere in the clean process. I tried to compare the workspace files for good and bad cases but did not that easily find a difference.