• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 55 subscribers
  • Views 2045 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.

Looking for help using -ccs.projectSpec option for command line project creation

Anthony F. Seely
Guru 69050 points

Other Parts Discussed in Thread: CCSTUDIO, SYSBIOS

Hi, I'm looking for information about the format of a projectSpec file.

Have some need to create CCS projects through a script using a consistent template and this seems to be the way to go, but not finding

documentation on what can go into the file.  (unless it is just any other option that is output when you run the command line project create with --ccs.help?)

  • 0
    TI__Genius 9345 points

    Hi Anthony,

    I'm attaching the XML schema that defines the structure of the project-spec files.  The schema contains documentation on most of the attributes.  Let me know if you have any questions.

    Thanks,

    - Baltasar

  • 0 in reply to Baltasar Belyavsky
    TI__Guru 69050 points

    Hi Baltasar,

    I did a search for this file in the CCSv5 installation folder but didn't find it. 
    So, when creating an XML file that references this schema, what would be the best way to describe the schema location? In this case I'm planning to distribute the project generating script, and would like to reference the schema if possible rather than including a copy of it which may become out of date.

    I'll probably have more questions;  trying to understand the schema hierarchy now.  I notice most of the entries have annotations for documentation like you mention, so it looks like it'll be useful.   There's some near the end of the schema that don't include annotations and so I might have questions on these.

    Is there a way to generate a projectSpec file from an existing CCS Project?   That might be a good way to gain an understanding as well.

    Thanks and Best Regards,

    Anthony

  • 0 in reply to Anthony F. Seely
    TI__Genius 9345 points

    Anthony,

    Starting with CCS v5.3.0, the project-spec XML schema will be distributed with CCS in <ccs-install-root>/ccsvX/eclipse/plugins/com.ti.ccstudio.project.templates_X.X.X/schema/projectSpec.xsd.

    Currently, there is no capability allowing to generate a project-spec from an existing CCS project.

    If you have any questions on the project-spec usage, let me know, and i'll add the details into the schema file.

    Thanks,

    - Baltasar

  • 0 in reply to Baltasar Belyavsky
    TI__Prodigy 670 points

    Baltasar,

    I am trying to write a projectSpec using the schema you provided in the previous post with CCS v5.2. On running the following command

     ./eclipsec.exe -noSplash  -data "d:/workspace2" -application com.ti.ccstudio.apps.projectCreate -ccs.projectSpec tmp.projectspec -clean

    where tmp.projectspec looks like

    <projectSpec>
    <project name='temp2' device='TMS320C67XX.DA830/DA828.DSKDA830'>
    </project>
    </projectSpec>

    I get the following errors:

    !WARNING: Workspace autobuilding has been turned off!
    --------------------------------------------------------------------------------
    Creating project 'temp2'...
        NOTE: Output-type not specified - defaulting to 'executable'.
        NOTE: Device endianness not specified - defaulting to 'little'.
        NOTE: Compiler version not specified - defaulting to '7.3.4'.
        NOTE: Output-format not specified - defaulting to 'COFF'.
        NOTE: Runtime support library not specified - defaulting to 'libc.a'.
    java.lang.NullPointerException
            at org.eclipse.core.runtime.Path.<init>(Path.java:153)
            at org.eclipse.core.runtime.Path.fromOSString(Path.java:90)
            at com.ti.ccstudio.project.core.services.ProjectSpecParser$CreationCommand.validate(ProjectSpecParser.java:75)
            at com.ti.ccstudio.project.core.services.ProjectCreator.createCCSProject(ProjectCreator.java:660)
            at com.ti.ccstudio.project.core.services.ProjectCreator.createCCSProject(ProjectCreator.java:648)

            at com.ti.ccstudio.project.core.services.ProjectCreator.createCCSProject(ProjectCreator.java:617)
            at com.ti.ccstudio.apps.internal.project.Create.doRun(Create.java:335)
            at com.ti.ccstudio.apps.internal.BaseHeadlessApp$2.run(BaseHeadlessApp.java:240)
            at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
            at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2326)
            at com.ti.ccstudio.apps.internal.BaseHeadlessApp.internalRun(BaseHeadlessApp.java:238)
            at com.ti.ccstudio.apps.internal.BaseHeadlessApp.start(BaseHeadlessApp.java:187)
            at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
            at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
            at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
            at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
            at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
            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.equinox.launcher.Main.invokeFramework(Main.java:622)
            at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
            at org.eclipse.equinox.launcher.Main.run(Main.java:1410)

    ...

    What could be the problem ?

    Regards and Thanks,

    Maya Kamath

  • 0 in reply to Maya Kamath
    TI__Genius 9345 points

    Hi Maya,

    I will fix this problem for CCSv5.3.0.  For now, you can work around it by providing an absolute path to your projectspec.  And if the path contains spaces, enclose the path in double quotes.

    Thanks, and let me know if you run into any other problems.

    - Baltasar

  • 0 in reply to Baltasar Belyavsky
    TI__Prodigy 670 points

    Baltasar,

    Thanks - that works.

    Regards,

    Maya Kamath

  • 0 in reply to Maya Kamath
    TI__Prodigy 670 points

    Baltasar,

    One more question on the  -ccs.projectSpec usage. Is it not possible to specify an Rtsc configuration when using  -ccs.projectSpec ? I have tried the following command

    ./eclipsec.exe -noSplash  -data "d:/workspace2" -application com
    .ti.ccstudio.apps.projectCreate  -rtsc.platform "" -rtsc.enableRtsc -rtsc.xdcVersion 3.16
    .02.32 -rtsc.products "com.ti.rtsc.IPC:1.00.05.60;com.ti.rtsc.SYSBIOS:6.21.00.13;com.ti.r
    tsc.XDAIS:6.25.01.08" -rtsc.setConfiguroOptions "-o configPkg -t ti.targets.C674 -p ti.pl
    atforms.generic:plat -r whole_program -b \"t:/pa/f/s19/config.bld\" -c \"C:/Program Files
    /Texas Instruments/C6000 Code Generation Tools 6.1.3\" -DProjName=pa_i12_evmda830 -DENABL
    E_CPULOAD=true -DDSPLINK=true "  -ccs.projectSpec tmp.projectspec

    The CCS project is getting created as per tmp.projectspec but it does not have any of the RTSC properties. If I remove the -ccs.projectSpec option, I can create a project with the RTSC properites enabled. Is there any way I can specify the RTSC properties within the tmp.projectspec file ?

    I am using CCS v5.3

    Regards and Thanks,

    Maya Kamath