CCS 5.3 "Import existing CCS ecplipse project"

Hi,

can you please explain in a little further detail what you mean/are experiencing?  When you select "copy projects into workspace" do you get any errors?  Is the project created?    I am thinking perhaps you may simply need to correct/check/update the include paths and variables as per this wiki.  This is typical when doing an import.

http://processors.wiki.ti.com/index.php/Include_paths_and_options

Please keep us informed.

Best Regards,

Lisa

Lisa TI said:

When you select "copy projects into workspace" do you get any errors?  Is the project created?

No errors. The project is created correctly, but no files are copied into project folder.

This is what you get after creating project (every file is unreachable):

Maybe because CCS 5.3 can't resolve files that are originally linked into the project.

Also, every linked resource (include files, libraries, etc...) is missing/wrong path:

Lisa TI said:

I am thinking perhaps you may simply need to correct/check/update the include paths and variables as per this wiki.  This is typical when doing an import.

http://processors.wiki.ti.com/index.php/Include_paths_and_options

I think that wasting hours for fixing invalid path is not acceptable.

SDK projects are close related each other, and it's quite impossible to detach just one, doinga working copy somewhere else and make modifications without affecting the original one. Codewarrio and Code composer, ten years ago, worked fine. Eclipse is a giant leap back...

Another environment variabile issue is coming out:

• I've installed SDK rev 1.0.0.7 and then SDK rev 1.0.0.4 (wrong order, I know)
• SDK rev 1.0.0.4 installer set environment variabile IA_SDK_HOME=C:\ti\am335x_sysbios_ind_sdk_1.0.0.4\sdk, overwriting the previous value (IA_SDK_HOME=X:\ti\am335x_sysbios_ind_sdk_1.0.0.7\sdk).
• I'm using two workspaces: one for SDK rev 4 and one for SDK7 rev.7.
• In the workspace related to SDK rev. 7 I've added in preference/general/workspace/Linked resourced the needed environment variaible:
• I've deleted the windows environment variable IA_SDK_HOME=c:\ti\am335x_sysbios_ind_sdk_1.0.0.4\sdk

Hi Eugenio,

a few comments.  It is an unfortunate but necessary evil to clean up include paths and variables when importing/migrating a project.   The trade of is newer version, newer features, bug fixes etc.

Having said that, one thing I wonder is if some of your problems are also being caused by the following.  It seems you are trying to set the bios tools versions in the include paths and variables. That is not where you set this.  The version of sys/bios etc a project uses is set in the project properties in the RTSC tab.  Project->Properties->General ... RTSC tab.

Best Regards,
Lisa

I've found this:

1)  installing a new SDK updates IA_SDK_HOME environment variable in Windows system:

2) CCS doesn't care about workspace's linked resource:

3) When you import a project into a workspace, some path are automatically updated with IA_SDK_HOME value as defined in Windows environment (not CCS linked resource value). Any further modification to IA_SDK_HOME value in Windows environment is not detected. So, you need to delete the project and import it again...

As result you get this: 

- you want CCS to have "IA_SDK_HOME" variable set within a particular workspace, and Linked resource property seems to be the thing you need to care about, BUT....

- CCS really doesn't care about that, and keeps reading IA_SDK_HOME variable value from Windows environment. If you delete IA_SDK_HOME definition in Windows environment, CCS5 doesn't report any error and leaves the field empty, with plenty of path errors...

- The smart guy, at this point, tries to update IA_SDK_HOME value in Windows environment, but CCS doesn't know that the variable has changed, and does nothing. Paths are still messed up.

- The desperate guy, at this point, delete the project and import it again. Wow: it's working!

As conclusion: why CCS (tested in v5.3 and v5.4) doesn't use Linked resource values?

Hi Eugenio,

I can pass along the feedback but one thing I wonder ... I notice both a C and an X drive in your images.  CCS does not typically like any junctions/mapped/virtual/server drives.  I wonder if this might be the issue.   Have you tried where both the path variable and system variable would be c:/ something.

Best Regards,

Lisa