• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 536 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.

CCS/CODECOMPOSER: Preserving CCS5.5 environment and upgrading to newer version

Stephen Phillips1
Expert 1250 points
Part Number: CODECOMPOSER

Tool/software: Code Composer Studio

We have a registered version of CCS5 and there is a concern to maintain the exact version of the build environment for future use.

At the same time there are some TI products we wish to use CCS to develop for for.

So if one uses the install for CCS5.5 does this have what upgrades patches fixes etc for 5.5 there existed prior to changing to CCS6?

In this case we used msp TI C compiler 4.2.7 so it is highly desirable to create in a Virtual Machine the exact build environment to preserve it.

For the license we used a network license manager, how long will that work? What do we do for a VM?

So then we migrate to say CCS 7 (latest) we have the network license manager for CCS5.X, does this work for CCS7? Do we need to procure a whole new license?

That's all.

Stephen

  • 0
    Guru 20045 points
    Hello Stephen,

    I believe TI has changed the licensing scheme for all Code Composer versions. You don't need a licence anymore.

    Also, I am assuming you have the hex file for all software. Why not just build the software in CCSv7 and check to see if the generated hex file matches the CCSv4 or CCSv5.5 hex file.

    Stephen
  • 0 in reply to stevenh
    TI__Guru**** 162305 points
    Stephen is correct. We no longer charge for CCS licenses. Thus you can download and install CCSv7 without worrying about a license. We also have a license file available on the CCS download page that can be used with CCSv4/5/6 if you wish to simplify your CCSv5 environment so that you don't have to run the license server.

    The link to the license file is available here:
    processors.wiki.ti.com/.../Download_CCS

    You can also have different projects setup to use different versions of the compiler. Thus in CCSv7 you could have "legacy" project that used the 4.x compiler and "new" project that used the latest compiler. That said creating an archive of the tools used for a particular product is a good idea.

    Regards,
    John