• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 524 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.

-nosplash stopped working

Bill Etcheverry
Intellectual 345 points
Other Parts Discussed in Thread: CCSTUDIO

I have been using command line builds for months and suddenly they have stopped working.

c:\ti\ccsv5\eclipse\eclipsec.exe -nosplash com.ti.ccstudio.apps.projectBuild -data C:\Users\x0183614\workspace_v5_prime_int_u -ccs.projects PLC_AppBoot -ccs.configuration Debug_F28335_120

The CCS v5.1 gui pops open and the build script stalls.

We are getting ready to do a release and I really need this to be working.

  • 0
    TI__Guru**** 465671 points

    Hi Bill,

    Bill Etcheverry said:
    The CCS v5.1 gui pops open and the build script stalls.

    This usually happens when the command is called incorrectly.

    Bill Etcheverry said:
    c:\ti\ccsv5\eclipse\eclipsec.exe -nosplash com.ti.ccstudio.apps.projectBuild -data C:\Users\x0183614\workspace_v5_prime_int_u -ccs.projects PLC_AppBoot -ccs.configuration Debug_F28335_120

    You seem to be missing '-application' in front of the project build command. You need:

    c:\ti\ccsv5\eclipse\eclipsec.exe -nosplash -application com.ti.ccstudio.apps.projectBuild -data C:\Users\x0183614\workspace_v5_prime_int_u -ccs.projects PLC_AppBoot -ccs.configuration Debug_F28335_120

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 345 points

    Thanks for the quick response!

  • 0 in reply to Bill Etcheverry
    TI__Guru**** 465671 points

    Glad to help.

    One thing I do to avoid typing in that whole string every time (and to avoid typos and such) is I created a batch file that wraps the command so that I only need to pass in the workspace folder, project and configuration. It really saves time and avoids potential errors.

    I've attached the example here (renamed as a *.txt)

    Usage would be:

    > timake_ccsv5.bat <workspace folder> <project> <configuration>

    ex:

    > timake_ccsv5.bat C:\Users\x0183614\workspace_v5_prime_int_u PLC_AppBoot Debug_F28335_120

    Of course you can tweak the bat file to change things the way you wish (add more parameters, etc)

    Note in line 4 I set the path to the CCSv5 installation. This would need to be updated to whereever you have v5 installed on your local machine (looks like you have it in the default 'C:\ti' folder)

    ki

    Fullscreen 6710.timake_ccsv5.txt Download 
    @echo off

REM CCSv5 installation to use for command-line builds
set INSTALL_DIR=C:\TI\CCSv5.2.1.00018

REM Set parameters to be passed to the command.
SET WORKSPACE=%1
SET PROJECT=%2
SET CONFIG=%3

@echo on

cmd /c %INSTALL_DIR%\ccsv5\eclipse\eclipsec.exe -noSplash -data %WORKSPACE% -application com.ti.ccstudio.apps.projectBuild -ccs.projects %PROJECT% -ccs.configuration %CONFIG%