Version of Code Generation tools

Hi Ki-Soo, 

I am having the same problem. I am using ccs4.2.4 and although i did try to import the project, it stills tells me to use 6.1.2 (C6000). The project is already imported. How to proceed from here ??

Thanks, 

AQ

AQ - the quick answer is to install CGT version 6.1.2 and point you 4.2.4 installation to it. Did you try that?

ki

Ki-Soo, 

I was reluctant to install more softwares on my PC then the need be. So, anyways i created a new project and started importing files to it. This proved to be a pain but i had no other choice. Why is it, that a project is imported and still they generate a complaint on CGT versions. While importing, it should sort out all these differences, right ??

Thanks for the help,

AQ

1898541 said:

Why is it, that a project is imported and still they generate a complaint on CGT versions. While importing, it should sort out all these differences, right ??

The complaint/warning is for your (the user's) benefit. In older version of CCS (CCSv3 and earlier), the CGT version used to last build the project was not stored in the project settings. The project just used whatever CCS was currently configured for. So no warnings because it didn't know / didn't care. But changing a CGT version is a big big deal since many people WANT TO KNOW if there is a mismatch between what was used in the past (and deemed working) and what CGT version CCS will use in the present (many customers spend a lot of time and resources verifying a specific version of the CGT and do not ever want to move in the middle of a project) So since starting with v4 we stored the CGT version info with the project, we can warn the user.

That said, there have been some complaint in regards to usability about the in-your-face warnings and the imports failing. We changed it in v5 to be less noisy and try to find an appropriate CGT version if the exact match is not found. It will tell you what the project originally used and the best match found that it is using.

Thanks

ki

Thanks for the reply Ki-Soo, 

So finally you are doing in v5 what you should have done in v4 :)

CCS keeps on growing at a rapid pace and it's difficult for us, new user's to get accustomed to it. A lot of documentation we find on the newer version is written with a implied understanding that the user already is familiar with old versions of CCS, which may not always be a case.

Would you be able to provide me with links from where i can start fresh to learn the developing environment etc. We are using CCS 4.2.2. 

Thanks,

AQ

1898541 said:

So finally you are doing in v5 what you should have done in v4 :)

Help me tell that to the people who complained that they want the "in-your-face" v4 behavior back :)

Can't please everyone - learned that one long ago.

1898541 said:

CCS keeps on growing at a rapid pace and it's difficult for us, new user's to get accustomed to it. A lot of documentation we find on the newer version is written with a implied understanding that the user already is familiar with old versions of CCS, which may not always be a case.

Would you be able to provide me with links from where i can start fresh to learn the developing environment etc. We are using CCS 4.2.2. 

The documentation is a bit fragmented for v4 and marginally better for v5. We are putting together more material and pulling together existing material here:

http://processors.wiki.ti.com/index.php/Category:CCS_Training

But the focus is CCSv5. We are actually deprecating v4 support and won't be putting together any new material for it. Any reason why you want to stick to v4?

Agreed. 

Thanks a lot for the quick replies and the help provided. You rock :)