I am looking for a trial version of Code Composer version 3.3. Unfortunately, version 4 will not for my current project needs. Please let me know if there is any way that I could get a trial 3.3.
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.
I am looking for a trial version of Code Composer version 3.3. Unfortunately, version 4 will not for my current project needs. Please let me know if there is any way that I could get a trial 3.3.
Hi Dustin,
CCS V3.x is discontinued, so you need to use CCS 4.2 instead.
Why will V4.x not fit your needs? You can import your existing projects to CCS 4.x and start working on them with ease (http://processors.wiki.ti.com/index.php/Importing_CCSv3_Projects_into_CCSv4).
Download the DVD image from here http://processors.wiki.ti.com/index.php/Download_CCS and register for a 30-days evaluation license for free.
Refer to GSG:CCSv4 installation for details on installing CCS and to GSG:CCSv4 Running for the first time for details on how to get a license.
You can extend your 30-days trial by another 90-days by following this link: https://focus-webapps.ti.com/licreg/productactivation.tsp?toPerform=firstTimeActivation&orderablePartNumber=TMDFCCS-ALLT90A&FNOPartNumber=TMDFCCS-ALLT90A-v4.0
Rgds
aBUGSworstnightmare
Thank you for the detailed reply. The latest version will not run our black label code, we have to use the 3.3 version that it was developed with as the object code cannot be changed. It is ok if 3.3 is discontinued, I only need the installer file.
Dustin,
If you want to keep object code consistency, you can install CCSv4 and download the tools used to build the original project (Code Generation Tools and DSP/BIOS). The links are:
Code Generation Tools:
http://processors.wiki.ti.com/index.php/Compiler_Releases
Target Content:
http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/index.html
Please note that debugging capability may be impacted in CCSv4 when using the older tools, especially if using an older version of DSP/BIOS.
Hope this helps,
Rafael
In CCSv4, you can use the same version of the compiler/BIOS version in 3.3 as Rafael suggested to keep object code consistency and then use v4 for full debug support.
My project was built in 3.3 but after converting to 4 and compiling, the bebugger does not work. The debugger gets hung up in the code and I manually have to use step into and step over to get through the code. Any ideas why this would be happening?
Kelly,
Without a fully reproducible test case, it is very difficult to try to figure out why this is happening.If you can provide one, that would be great. Also provide the full CCS version number, emulator used, target being used and what compiler version you used in 3.3 and in v4.
Thanks
ki