• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 702 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/TMS320F28377D: CCS command line build causes workspace periodic save error

Tyler Tseng
Prodigy 110 points
Part Number: TMS320F28377D
Other Parts Discussed in Thread: CCSTUDIO

Tool/software: Code Composer Studio

Hi,

When we use CCS cmd line build instruction : 

eclipsec -noSplash -data "C:\myWorkspace" -application com.ti.ccstudio.apps.projectBuild -ccs.projects newProject -ccs.configuration Debug 

to build our project, we find CCS prompt below message sometimes

"Problem occured
Periodic workspace. has encountered a problem.
An internal error occured during: "Periodic workspace save."


we doubt this may causes the code HEX file inconsistent in each build even without editing any 
source code(it happens by chance), can we avoid this by changing any parameters of cmd line instruction?  
The CCS version is 6.1.1.00022, thanks.
  • 0
    TI__Guru**** 463941 points
    Hi Tyler,
    I see this message periodically, though I don't have a good answer why it happens. It will not impact the build of the image as you suspected - the error only refers to some issue with saving the workspace state (preferences, etc).

    Do you have CCS IDE up and running, and using the same workspace when you run the cmd build command?
    Thanks
    ki
  • 0 in reply to Ki
    Prodigy 110 points
    Hi Ki-Soo,
    Yes, CCS IDE is up and running for the same workspace during cmd line build process, we don't edit anything manaully at that time.
  • 0 in reply to Tyler Tseng
    TI__Guru**** 463941 points
    Likely the building of the projects in the workspace is touching some workspace metadata files which confuses the running CCS IDE instance since things were modified by a separate process. I've seen this happen to me also. It seems to be some kind of Eclipse limitation since I see it reported on other Eclipse based forums.