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.

using v3.3 and v4.0 simultaneously and licensing questions

 

I have several EVMs and a couple of EZDSPs for the C5505.  I only want to develop code for the C5505.  I don't understand what CCS licenses pertain to me.

We have been using v3.3 and we are restructuring a lot of code right now and so if we should switch to CCS v4.0, then now is the time to do it.

1. Is there a big advantage to using CCS v4 over v3.3?    CCS v3.3 seems to be getting the job done okay.

2. Am I already licensed to use v4.0 based on my purchases of the EVMs this past 9 months?  Or do I have to pay something more in order to develop and produce code for production?

3. Can some of our developers use v3.3 and others use v4.0 in the same folder?  Or will the source code differ between the CCS versions or the studios step on one another when used simultaneously on the same code?

Thanks,

David 

 

  • Hi David,

    david beccue said:
    1. Is there a big advantage to using CCS v4 over v3.3?    CCS v3.3 seems to be getting the job done okay.

    This presentation explains the benefits of migrating to CCSv4.

    david beccue said:
    2. Am I already licensed to use v4.0 based on my purchases of the EVMs this past 9 months?  Or do I have to pay something more in order to develop and produce code for production?

    If you purchased a full CCS 3.3 license in the last 9 months, you are eligible for a free upgrade to a full v4 license. If the CCS 3.3 version is some limited DSK/EVM version (basically limited to use only with that DSK/EVM), then you are not eligible for a full v4 license. But you can still use a free bundled license which allows use to DSK/EVMs.

    david beccue said:
    3. Can some of our developers use v3.3 and others use v4.0 in the same folder?  Or will the source code differ between the CCS versions or the studios step on one another when used simultaneously on the same code?

    I'm not sure what you mean by "same folder". v3 and v4 installations can safely co-exist on the same machine but they much be installed in different locations. v4 has a completely new project format than v3. So if you are using both 3.3 and v4 for development on the same code base, note that you will have to maintain different project files for v3 and v4.

    Thanks

    ki

  •  

    Thanks for the help.  

    I love the presentation for CCS v4.

    I guess the thing that most confuses me is the "free bundled license".  I don't understand how this product differs from the "full" version.  It seems that with the "free bundled" CCS, I can compile for the EVM right now.  And then I can use the "free bundled" CCS with my production product via the JTAG debugger (XDS100).   I just can't think of what else anyone would use the CCS for except these two scenarios.  So the "full" version doesn't make sense for anyone to buy, since it comes free with a $50 ezdsp kit.  So therefore I must be missing something.  What is it?

    By "same folder" I meant that the source files would be in a folder that both ccs v3.3 and v4 both can compile and use.  I understand that CCS would each be installed in their own "Program Files" folder, AND that they would have different project files.  But could those project files be in the same folder as the source files and everything play nicely together?

     

     

     

  • David,

    The difference between the free bundled version and the full version is that you can use any external emulator (XDS510, XDS560) with the full version while the free version only supports XDS100 for external emulators. The XDS100 is pretty slow in terms of performance but since it is very cheap, people are willing to put up with this... even past the evaluation phase. If you are fine with the slow performance, then yes, you can use CCS all the way to the finish.

    Regarding question #2, yes v3 and v4 project files can safely co-exist in the same source tree. Because the project management system is totally different between the two, the associated project files are not shared between the two (with the exception of output from the compiler like object files, generated pp files, etc)

    Thanks

    ki

  •  

    That's very clear now.  Thanks!

    David