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.

Re: Code Generation Tools version

I am working with a co-developer. We are attempting to share
our source files through a central repository (Subversion).
We both use CCS v4.2.4, and our compilers are both v6.0.1.

However, today, when I tried to build one of his projects,
using source files from the repository, I got a diagnostic:

   "This project was created using a version of Code
    Generation tools that is not currently installed:
    5.2.1 [C2000]. Please install the Code Generation
    tools of this version, or migrate the project to one
    of the supported versions."

Chris Maxwell83026 asked about this same issue on 31 Aug
2011, and got the following response:
>
> You can either choose to use the version of the compiler
> that comes with your CCS install or download and install the
> version originally used by the project.
>
I do not wish to downgrade my compiler to some older
version. I prefer the latter.

What does it mean "to use the version of the compiler that
comes with your CCS install"?  If I am not using the version
of the compiler that came with my install, what the heck am
I using?

  • HI Gary,

    you can find out what you have installed by going to Window->Preferences->Code Composer Studio->Build->Code Generation tools

    They are also available to download and install in that same location from here

    http://processors.wiki.ti.com/index.php/Compiler_Releases

    Please keep us informed how it goes.

    Best Regards,

    Lisa

  • <sigh>

    Why am I unable to explain what I want?

    1.  I have Compiler v6.0.1
    2.  Code Composer tells me this source file was once built
        with v5.2.1.  It has somehow invisibly 'branded' my
        source file such that no one may ever build it with any
        version of the compiler other than 5.2.1, and orders me
        to downgrade. (I used to think I understood ASCII.)
    3.  I refuse to downgrade. I refuse to believe that one
        compilation of a source file links it in perpetuity to
        a specific compiler version. I want it to build now with
        what I already have installed.

    Am I missing something or is Code Composer that massively
    broken?

  • Hi Gary,

    when you import the project CCS should ask you if you want to build with the newer compiler version.  You can simply select yes.  Alternatively you can select which from your installed compiler versions to use under

    Project->Properties->CCS General.  You have to have the advanced settings expanded.  You will see "compiler version"

    Does this answer things then?

    Best Regards,

    Lisa

  • I had no recollection of Code Composer asking me whether I
    wanted to build with the new version, so I deleted the
    project and imported it again.  The complete wizard cycle is
    illustrated herewith:

    I still don't see anything about changing versions.

  • Hi Gary,

    I am wondering if you only have one compiler version installed so it did not ask and is perhaps doing everything automatically.

    Please check the following two things

    Window->Preferences->CCS->BUild->COde Generation TOols ... what compiler versions do you have installed?

    Did you try setting a specific version in the project properties as per my last post?

    Project->Properties->CCS Build (corrected for v4.2.4 ... sorry I am too used to v5 now).  Once again compiler version can be set here.

    Please keep us informed.

    Best Regards,
    Lisa

  • On Wednesday, April 11, 2012 4:30 PM; Lisa TI wrote:
    >
    > Please check the following two things
    > Window->Preferences->CCS->BUild->COde Generation TOols ...
    > what compiler versions do you have installed?

     

    It would appear I have 3 (I only ordered C2000).

    >
    > Did you try setting a specific version in the project
    > properties as per my last post?
    >
    That would be the following directive?
    >
    > Alternatively you can select which from your installed
    > compiler versions to use under Project->Properties->CCS
    > General. You have to have the advanced settings expanded.
    > You will see "compiler version"
    >
    I can find no "CCS General" but I do find the following:

    If I read that correctly, I only have 1 version.

  • Hello,

    yes you only have v6.0.1 for the C2000 compiler so your projects will use this version as you can see. 

    Does this help clarify things for you then?

    Best Regards,
    Lisa

  • Just to add to Lisa's comments.

    When a project is created it stores the compiler version in the project.  This is so that you can have a project that is set to use a specific version of the compiler and another project that uses a different one.  This is very typical when you have a project where all the testing and validation has been done with a specific version and you don't want to change that.  However your new project is starting off and you want to use the latest tools.

    In your case your project is set to use a version that you do not have installed so CCS lets you know this when you try to build.   If your team is all aligned on a newer version then you can checkout the project, switch the compiler version in the project to the newer one you have and then check it back in.  

    In CCSv5 the project properties are more descriptive and show you both the version the project is set to use and the one it is actually using.

    Regards,

    John

  • I should explain that I have been so silent because of a
    much needed vacation.  I returned yesterday and resumed work
    on this project.

    On Wednesday, April 11, 2012 6:45 PM; Lisa TI wrote:
    >
    > Does this help clarify things for you then?
    >
    No, I still don't know why I could not build my project with
    the version I had installed.

    Then on Wednesday, April 11, 2012 6:57 PM; JohnS wrote:
    >
    > When a project is created it stores the compiler version in
    > the project. This is so that you can have a project that is
    > set to use a specific version of the compiler and another
    > project that uses a different one. This is very typical when
    > you have a project where all the testing and validation has
    > been done with a specific version and you don't want to
    > change that. However your new project is starting off and
    > you want to use the latest tools.
    >
    This make sense.  But only if I can override it.

    >
    > In your case your project is set to use a version that you
    > do not have installed so CCS lets you know this when you try
    > to build. If your team is all aligned on a newer version
    > then you can checkout the project, switch the compiler
    > version in the project to the newer one you have and then
    > check it back in.
    >
    As I wrote in the original post, I never changed compilers.
    I acquired this code from a co-worker who may have built it
    with an earlier version before he checked it in, but we have
    upgraded in sync.

    I still don't know how to switch the project to my version
    of CCS, if it is earmarked for an older one.

    You will recall, when someone said the import wizard should
    ask me during the import process whether I want to switch
    versions of the compiler, I deleted the project that was
    causing me pain, and re-imported the project, capturing
    every screen of the process in an image that I posted on
    this forum. I was trying to document that it never asked me
    whether I wanted to switch versions, and I didn't see it the
    second time.

    At about this point I left town for 5 days. I don't remember
    whether I re-built the project after the new import, but
    this week the error message no longer appears and I can no
    longer replicate the problem. I have too many other
    challenges to devote much time trying to bring it back.

    I notice someone has marked my question as answered. If Code
    Composer does wierd things when the moon is waning gibbous,
    then yes, that explains everything. Otherwise, if it comes
    back again, I will have no more idea what to do about it
    than I did this time.