• State TI Thinks Resolved
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 54 subscribers
  • Views 431 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.

Original question:

CODECOMPOSER: Build project on the terminal - How to use eclipsec with CCS v12.6.0?

CODECOMPOSER: CCS with PowerShell: cannot create new project on Windows

Isaac Lucas de Lima Yuki
Intellectual 315 points
Part Number: CODECOMPOSER
Other Parts Discussed in Thread: CCSTUDIO

Hello, 

trying to follow the instructions of TI on building apps with Powershell: https://software-dl.ti.com/ccs/esd/documents/ccs_projects-command-line.html

Also tried using gmake, but I thought this might be more complicated as it seems that I have to write my own makefile? Could you confirm?

Unfortunatelly I'm getting these error(s):

Fullscreen
1
2
3
4
PS C:\Projekte\TQ_Ti\AM64x\TQMaX4XxL.MCU.bsp> eclipsec -noSplash -data "workspace_dir" -application com.ti.ccstudio.apps.projectCreate -ccs.projectSpec "TQMaX4XxL.MCU.BSP.projectspec" -ccs.name testing -ccs.device AM64x
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

also tried this:

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
PS C:\Projekte\TQ_Ti\AM64x\TQMaX4XxL.MCU.bsp> eclipsec -noSplash -data "workspace_dir" -application com.ti.ccstudio.apps.projectCreate (-ccs.projectSpec TQMaX4XxL.MCU.BSP.projectspec | -ccs.name testing -ccs.device AM64x)
#SOME ERROR MESSAGE ON GERMAN SAYING OH NO I DON'T KNOW WHAT .ccs is
-ccs : Die Benennung "-ccs" wurde nicht als Name eines Cmdlet, einer Funktion, einer Skriptdatei oder eines
ausführbaren Programms erkannt. Überprüfen Sie die Schreibweise des Namens, oder ob der Pfad korrekt ist (sofern
enthalten), und wiederholen Sie den Vorgang.
In Zeile:1 Zeichen:91
+ ... ce_dir" -application com.ti.ccstudio.apps.projectCreate (-ccs.project ...
+ ~~~~
+ CategoryInfo : ObjectNotFound: (-ccs:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Regards

Isaac

  • 0 in reply to Ki
    Intellectual 315 points

    Hello Ki,

    Either I didn't get what you want, or this doesn't work, because I'm using wrong commands:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    PS C:\Projekte\TQ_Ti\AM64x\TQMaX4XxL.MCU.bsp> cmd.exe /c eclipsec -noSplash -data "workspace_dir" -application com.ti.ccstudio.apps.projectCreate ( -ccs.projectSpec "./TQMaX4XxL.MCU.BSP.projectspec" | -ccs.name "testing" -ccs.device "AM64x" )
    -ccs : Die Benennung "-ccs" wurde nicht als Name eines Cmdlet, einer Funktion, einer Skriptdatei oder eines
    ausführbaren Programms erkannt. Überprüfen Sie die Schreibweise des Namens, oder ob der Pfad korrekt ist (sofern
    enthalten), und wiederholen Sie den Vorgang.
    In Zeile:1 Zeichen:103
    + ... e_dir" -application com.ti.ccstudio.apps.projectCreate ( -ccs.project ...
    + ~~~~
    + CategoryInfo : ObjectNotFound: (-ccs:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
    PS C:\Projekte\TQ_Ti\AM64x\TQMaX4XxL.MCU.bsp> eclipsec -noSplash -data "workspace_dir" -application com.ti.ccstudio.apps.projectCreate ( -ccs.projectSpec "./TQMaX4XxL.MCU.BSP.projectspec" | -ccs.name "testing" -ccs.device "AM64x" )
    -ccs : Die Benennung "-ccs" wurde nicht als Name eines Cmdlet, einer Funktion, einer Skriptdatei oder eines
    ausführbaren Programms erkannt. Überprüfen Sie die Schreibweise des Namens, oder ob der Pfad korrekt ist (sofern
    enthalten), und wiederholen Sie den Vorgang.
    In Zeile:1 Zeichen:92
    + ... e_dir" -application com.ti.ccstudio.apps.projectCreate ( -ccs.project ...
    + ~~~~
    + CategoryInfo : ObjectNotFound: (-ccs:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Note: Either way, it is for me very important to use the .projectspec file.

    Thanks for help!

    Regards,

    Isaac

  • 0 in reply to Isaac Lucas de Lima Yuki
    TI__Guru**** 450761 points

    Issac - my apologies, I missed some other details in your post. Besides the powershell considerations, there are two other issues:

    Isaac Lucas de Lima Yuki said:
    Note: Either way, it is for me very important to use the .projectspec file.

    The projectCreate command does not support the generation of a projectspec file. You must manually create a projectspec file.

    The second issue is that there is incorrect syntax in your command. Please note that for the usage specified in the document:

    eclipsec -noSplash -data "<workspace_dir>" -application com.ti.ccstudio.apps.projectCreate (-ccs.projectSpec <file> | -ccs.name <name> -ccs.device <id>) [<options>]

    The part in bold means that you either use -ccs.projectSpec to specify an existing projectspec file to create the project OR you use -ccs.name and -ccs.device to specify the name and device for the project to create).

    For example, it is either:

    cmd.exe /c eclipsec -noSplash -data "<workspace_dir>" -application com.ti.ccstudio.apps.projectCreate -ccs.projectSpec "./TQMaX4XxL.MCU.BSP.projectspec" 

    OR

    cmd.exe /c eclipsec -noSplash -data "<workspace_dir>" -application com.ti.ccstudio.apps.projectCreate -ccs.name "testing" -ccs.device "AM64x"

    Note that for the former, TQMaX4XxL.MCU.BSP.projectspec must already exist since the command will use that projectspec to create the project.

    Hope this clarifies things.

    ki

  • 0 in reply to Ki
    TI__Guru**** 450761 points

    Also please note that you need to pass in an actual workspace folder. "workspace_dir" is just a placeholder for an actual workspace directory.