CCS v 4.2.5.00005
Windows XP.
I have been using CCS 4.2.5 without issue on some C6000 based projects. I now want to do work on C5500 based projects. Apparently when I first installed CCS 4.1.2 on my machine I must have only selected the C6000 family. As a result the only two platforms or Project Types that show up (for example if creating a brand new project) are C6000 and ARM.
In comparing my ccs install to an existing install on a second PC, I see several files within PC #2 ccsv4\eclipse\plugins folder that are not in my machine. For example files like: "com.ti.ccstudio.buildDefinitions.C5500_legacy_4.1.2etc.jar. So it seems to me that I need to somehow install support for the C5500 device on my existing CCS 4.2 installation. I believe this is the core issue with another issue I posted on not being able to load an example project from the C55x CSL.
I have tried to use the "Help->software Updates->find and install" menu item, using the "Search for new features to install", selecting all Listed Sites, but nothing comes up other than C5500 code Gen tools, which I have installed but has not solved the problem.
How do I add support for the C5500 platform? Is there a specific "update Site" I should point to?
thanks
-S
----- Please click the Verify Answer button on this post if it answers your question --------
Hi Shawn,
is this a duplicate post? You can rerun the installer to the same directory to add further support. You should also upgrade to 4.2.5.
Another note, the CSL I believe was from CCSv3.3. This may also be an issue.
Please keep us informed how the above goes and also any further details on what exactly you are trying to do.
Best Regards,
Lisa
I should clarify, there is something you can do if you do not want to keep a v3 installation alongside v5, then you will need to install CSL separately and point v5 to it since v4 and v5 do not come with the CSL libraries. Have a look at this migration wiki.
http://processors.wiki.ti.com/index.php/Importing_CCSv3_Projects_into_CCSv4#CSL_and_XDAIS
This is where CSL can be downloaded from:
http://processors.wiki.ti.com/index.php/Chip_support_library
The above migration wiki should help get rid of most of the path/build warnings/problems. The remaining one should simply be to correct to the CCS installation root instead of CCSv3 installation rool. This wiki should help with that
http://processors.wiki.ti.com/index.php/Include_paths_and_options
Please keep us informed.
Sorry for the duplicate post. Once I had better isolated the root cause of the other issue I created a new post with a more specific question.
I am already running 4.2.5.
I tried installing to the same directory and got the following message. Is the issue now that the disk image with the setup exe I have is for an older version (4.1.2) of CCS than I am currently running (4.2.5)?
First I would try installing the CSL as stand alone, as I mentioned in my last post.
If you also wish to do the overinstallation, get 4.2.5 from here and don't bother with the old dvd.
http://processors.wiki.ti.com/index.php/Download_CCS
There is no dvd image for 4.2.5, but there is one for version 4.2.4, so I will try that and let you know what happens.
By the way, I don't think it has to do with the CSL installation, since the CSL CCSv4 example projects load just fine on my laptop which isn't missing the 5500 support in its CCS install.
Same result with the 4.2.4 DVD image when trying the re-install. Any new suggestions?
OK, I thought of something else to try. I just rolled back my CCS from v4.2.5 to 4.2.4 and the ran the 4.2.4 install to the same directory. It has now given me the option to "repair" the old install and I was able to select the C5500 components. It looks like that install is working. Once its done, I'll update to 4.2.5 again and see if all works.
ok, glad to hear you seem to have it sorted. Please let us know that it does indeed work.
Best Regards,Lisa
OK, so I was able to get an “overinstall” of CCS to work by rolling back my CCS from 4.2.5 to 4.2.4 and then running the 4.2.4 setup exe from the downloaded DVD image. So I guess the trick was to have the version of existing CCS match the version of the DVD install/setup exe.
happy to hear it is now working and all the best with development.
Thanks for the update.