• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 448 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.

C6414T Code Composer Version and Code Generation Tools

gbrillo
Prodigy 30 points

Hi all,

we are working on an update of an existing project, and so decided to move from a C6414 DSP to the newest C6414T. I looked for details and read the related documentation, included the provided migrating guide. 

My question is related to the Code composer IDE version to use within the new C6414T. I have read that the code is fully portable (600 MHz version) and I suppose that we can use the same tools too.

I must be sure about that, and so I'm asking if we could use the Code Composer version that we are using at the moment within the new C6414T based board.

With the old project we were using a CCS 2.21.00, and probably we will be asked to obtain a binary identical to the latest we have released. Can we use that CCS revision within the new C6414T?

If not, we are using a Code Composer 3.3 in other projiects, is this revision (ad related code generation tools) usable with the C6414T?

best regards.

  • 0
    TI__Expert 8055 points

    gbrillo,

    You should be ok in either case.  As far as target connectivity, the connection is the same between the 6414 and 6414T.  The same driver is used.  So if 6414 works with CCS 2.21, 6414T will also.  CCS 3.3 will also work with both.

    As far as the creation of identical binaries goes, this is not dependent on the version of CCS, but on the version of Code Generation  Tools.  You can download whatever version of tools you are using in CCS 2.21 and use it with CCS 3.3. In order to switch between tools in CCSv3.3, you need to select Help->About->Component Manager, select the appropriate compiler version, and then restart CCS.

    If you move to CCSv5, you are able to tie specific versions of Code Generation Tools to specific projects.  So there would be need to go back and forth.  When you build project A, it'll pick one set of tools, when you build project B, it'll pick another, if that's what it's configured for.

    Regards,

    Dan