• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 97 subscribers
  • Views 1341 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.

find something to load cfg files on command line(e.g. DOS console) same like loading cfg files on CCS

Hyungtae Kim
Prodigy 100 points
Other Parts Discussed in Thread: CCSTUDIO

Hi,

I am looking for something to load cfg files on command line(e.g. DOS console) same like loading cfg files on CCS.

I am making something to build the C667x DSP project on command line.

(I refer to http://processors.wiki.ti.com/index.php/Projects_-_Command_Line_Build/Create)

I made like below some scripts to build our project.

eclipsec -noSplash -data "%SOURCE_ROOT%" -application com.ti.ccstudio.apps.projectBuild -ccs.workspace -ccs.clean
eclipsec -noSplash -data "%SOURCE_ROOT%" -application com.ti.ccstudio.apps.projectBuild -ccs.workspace -ccs.autoImport

However, I realized I need one more thing before build on command line.

It's cfg file loading on CCS.

When I usually build on CCS, I have to double-clicking cfg file(Configuro Script File)

before clean/build.

So, I refer to http://rtsc.eclipse.org/cdoc-tip/index.html#xdc/tools/configuro/package.html

However, I don't know how exactly to do on CCS inside.

Could you tell me how exactly works loading(double-clicking) cfg file on CCS?

and

What scripts can I use to do same like  loading(double-clicking) cfg file on CCS?

Please help me.

thanks for reading.

BR,

Hyungtae.

  • 0
    TI__Mastermind 37985 points

    Hyungtae,
    just to make things easier to understand I want to explain the difference between two tools that you are referring to. The first tool is XGCONF, the graphical environment that lets you edit the config script file. The only output from XGCONF is that config script file.
    The second tool is xdc.tools.configuro. Configuro accepts the config script file as an input, and then it generates various C source files and linker command scripts that are used in the build.
    XGCONF is optional, you can make changes to the config script file in any editor. Configuro on the other hand must process the config script file in order to build an app.

    Now, I am not sure if you are trying to open XGCONF outside of the CCS and edit the configuration, or you just want to run xdc.tools.configuro to process the config script file. XGCONF as of now is available only within CCS, so you can't start it from the command line. I am not very familiar with using CCS on the command line, but if you are just trying to build your app, you are basically running gmake on an existing gmakefile. Your project's gmakefile should invoke configuro without any extra steps.

    What's the output when you run the eclipsec command lines you copied above?

  • 0 in reply to Sasha Slijepcevic
    Prodigy 100 points

    Dear. Sasha

     

    Thanks for your explanation.

     

    The answers what you wanted to know.

    1. I just want to run xdc.tools.configuro to process the config script file, not edit it.

    2. The output when you run the eclipsec command lines you copied above

        is .map file and .out file

     

    I really want to know when I do double-clicking .cfg file before build,

    what exactly happens inside CCS.

    is it possible to describe it by XGCONF script such as  xdc.tools.configuro?

     

  • 0 in reply to Hyungtae Kim
    TI__Mastermind 37985 points

    I asked about the output of eclipsec because I wanted to see what was being displayed in your command window. One of the things that should happen is that you see the command line that runs xdc.tools.configuro. Also, if you are seeing any errors it would be helpful to see those errors.

    When you double-click on a CFG file, CCS starts XGCONF. You can't really replicate XGCONF using xdc.tools.configuro because they are different tools that do different things. XGCONF is just a fancy replacement for a text editor, while xdc.tools.configuro is a tool that generates C sources, as I described in my previous email. The development flow looks like this:
    XGCONF (or any text editor) -> CFG script -> xdc.tools.configuro -> C sources

    When you build a project, all that is required is that a CFG script already exists. Once you create a CFG script, you can build and clean as many times as you want without ever changing that script. That should be true for eclipsec too. BTW, is there any reason you need to use eclipsec if you already decided to build on the command line. You can just use a makefile as described here: http://rtsc.eclipse.org/docs-tip/Consuming_Configurable_Content/makefiles#Integrating_with_TI_Code_Gen_Tools

  • 0 in reply to Sasha Slijepcevic
    Prodigy 100 points
    OK, Sasha.

    I understand what you said.

    As you said 'When you double-click on a CFG file, CCS starts XGCONF',
    Can you describe what XGCONF do?
    When I double-click cfg files on CCS, It makes some files and folders for compile.
    Can you translate 'Double-Clicking cfg file' to some script to run on command line?
  • 0 in reply to Hyungtae Kim
    TI__Mastermind 37985 points

    XGCONF reads in your existing CFG script, accepts your changes, and saves a new version of your CFG script. In the background, it also creates some temporary files whose purpose is to help with checking validity of the new values added in the GUI. However, these files are not used for anything else, and when you build the project, xdc.tools.configuro does not read those files.

    XGCONF can't run outside of CCS. The most similar tool that can run outside of CCS would be any text editor in which you can edit your CFG script and then save it. A text editor does not offer the same user experience as XGCONF, but they both are used for the same purpose - editing of CFG scripts.