• Locked Locked
  • Replies 14 replies
  • Subscribers 53 subscribers
  • Views 2566 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.

Installing products into CCS from command line

Kaveh Vaghefi
Expert 1704 points

Is there a page that lists ALL available command line options somewhere?  I'd like to figure out if I can install tivaware products into CCS from the command line.

  • Guru 192875 points
    Hi,

    Here's the wiki article: processors.wiki.ti.com/.../Create

    Regards,
    Gautam
  • in reply to Gautam Iyer
    Expert 1704 points

    Gautam Iyer said:
    Hi,

    Here's the wiki article: processors.wiki.ti.com/.../Create

    Regards,
    Gautam

    This was the first page I found, but it doesn't list all the possible command line options.  Only a select few.  It also doesn't list how to install a product into CCS, only add a discovery path.

  • in reply to Kaveh Vaghefi
    TI__Mastermind 22060 points
    Hi Kaveh,
    Could you describe what you'd like to do? Which components would you like to install via the command line? Are they app center components or components from selected product families? I can help you with the command line options if I knew what you were looking to do.
    Danish
  • in reply to danishinnis
    Expert 1704 points
    Yes, they're app center components, basically the TI-RTOS for TivaC product. I'd appreciate the help, but I would appreciate a reference of some sort even more, preferably one that details all the options/possibilities available via command line.
  • in reply to Kaveh Vaghefi
    TI__Mastermind 22060 points
    Hi Kaveh,
    The advanced command line options are for internal testing and hence not documented. Unfortunately, the only way to install app center items via the command line will require you to install all components.

    You would have to run the command like this:
    <installer> --prefix <install directory> --mode unattended --apps-select-all true

    Please let me know if you need more help,

    Danish
  • in reply to danishinnis
    Expert 1704 points
    Hi Danish,

    This does not solve. I have a specific version of the TI-RTOS for TivaC that I need to install (locally hosted). We can't just blindly take the latest version every time. If I interpret your command properly, it would simply install everything and take the latest version on TI's site. Can you please provide more information?

    Kaveh
  • in reply to Kaveh Vaghefi
    TI__Mastermind 22060 points
    Yes, that's what it does.

    Kaveh, I don't see TI_RTOS in the app center list from the installer. I may have misunderstood your requirement. If you mean, download after you start CCS, there are no commandline install options for that.
    Danish
  • in reply to danishinnis
    Expert 1704 points

    It's pretty much the first thing in the app center.  At least it is when you have the program installed.  I'm looking for a way to install it from the command line, but install a specific version of it, not the latest version.

    I'm curious, how does TI expect customers to solve the problem of automated builds and using the TivaC RTOS in such a build system?  To do so, we need to be able to define the version of the RTOS we want to build against and invoke everything from the command line.

  • in reply to Kaveh Vaghefi
    TI__Guru**** 159725 points

    Kaveh,

    Automated builds don't typically involve installing software.  The expectation is that you have the necessary software installed and then you build.

    Your project will define the version of the compiler and TI-RTOS to use.  The screen capture below shows the TI-RTOS version selection.  When you build from the GUI or the command line that is the version of TI-RTOS that will be used.

    To install all the necessary software and then to build seems like a huge amount of overhead. You could do it by downloading the packages and keeping them on the machine or a network share and then invoke the command line installers for each.  

    Why wouldn't the build machines have the necessary software in place?  If you can help us understand what you are doing and why we may be able to help you.

    Regards,

    John

  • in reply to JohnS
    Expert 1704 points

    I agree, I don't want to install CCS as part of my automated build here.  I do want to provide the TI-RTOS for TivaC product that CCS uses to build.  Why?  Because we've had to make a couple of fixes to this library that TI hasn't made yet.

    I understand that if I want to provision a build machine, that I need to install CCS somewhere on that build machine.  I'm also happy to install the compilers and various tools to that machine, the problem comes when I need to make modifications or adjustments to the open source libraries (i.e. TI-RTOS) that are built and are typically "installed" into CCS.  I think what's getting in the way here is that I need to install TI-RTOS for TivaC into CCS to get my project to build, and that seems to be something CCS doesn't have command line support for.

  • in reply to Kaveh Vaghefi
    TI__Guru**** 159725 points
    So basically you want to make sure that it is always using your specific verison of TI-RTOS. That makes sense.

    Could you manually install TI-RTOS into a specific location and then as part of your build process copy in the modifications? The reason I am suggesting this is that in addition to installing TI-RTOS, CCS will also need to discover the installation so that it can use it. If we do it this way it has discovered the original installation so it is available for use in a build but then you copy in your content so that your modificaitons are used.

    John
  • in reply to JohnS
    Expert 1704 points
    That's a possibility, there's another issue here as well. I'd like to be able to install ccs in a spot that doesn't need write access in order to run its build. This would make it easier to roll out newer versions of the toolchain, as you wouldn't have to log into multiple build machines to update ccs manually on each. I can't find any "best practices" on TIs site when it comes to trying to incorporate CCS into an automated build system. Does one exist?

    In the past, we've simply ripped everything out of CCS and invoked it manually. This time around I'd like to try to keep the CCS projects in sync with the build.
  • in reply to Kaveh Vaghefi
    Expert 1704 points

    Any other ideas here?  I really would like to know how to explicitly install these tools into CCS, without having to rely on some "auto-discovery" method to do it.

  • in reply to Kaveh Vaghefi
    TI__Guru**** 159725 points

    Kaveh,

    Discovery of TI-RTOS is required.  CCS has to discover it, even copying it into the CCS installation folder requires it to be discovered there.

    My suggestion was to have the environment setup so that CCS has discovered TI-RTOS in a set location.  Then if needed as part of your flow you can copy in your changes to TI-RTOS.  CCS will be aware of and able to use TI-RTOS from the set location and will be then using your modified version.

    Regards,

    John