CCSv 4.1.3 - CGT declared as "not installed"

... re-installing CCS plus cleaning the registry and deleting the Texas Instruments folder completely and also deleting all the workspaces didn't help. The issue still exists on this single PC.

Kind regards,

one and zero

Hello,

I cannot see the full path in that screenshot. Could you tell me the full path?

Thanks

ki

Hi Ki,

the path doesn't really matter. It happens with any CGT version installed (also default directory).

Now after re-installing it also happens with the originally installed CGT's. No changes made to the slected CGTs version.

I know with this information it's impossible to re-produce the issue, but my question is what else can I do to clean the PC to be able to re-install CCS seeing the issue anymore.

Thanks,

one and zero

hmmm... looks related to:

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/61709.aspx

Could you provide the log file requested by Baltasar in that thread?

Thanks

ki

Thanks. I'll collect that .log file and provide it to you.

The other case doesn't explain how to get CCS working again. Do you have a generic solution for that or is this depending on the centent of the log file?

Kind regards,

one and zero

Usually we suggest trying a new clean workspace, but that doesn't seem to help for this issue. The .log file may provide some insight. Otherwise there isn't anything else I can think of.

ki

Juergen,

It could be a filesystem permission issue.  The user, which CCS runs under, must have 'execute' permission on all files in the CGT install directories.  Could you try looking into the set permissions?  Or try logging in as Administrator and running CCS?

- Baltasar

Juergen,

FYI - Jon, the other user who experienced the same problem, found that even though his tools are now discovered with my patch, project building still didn't work (see http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/61709/225748.aspx#225748).  This finally helped in figuring out what the root cause of the tool-discovery failure was. 

Your user would probably come back to you with the same problem, so please check if your user's PC has a file named "Program" in his D: drive.  If it does, rename that file, and restart CCS (you could even delete the patch that I sent you from the plugins/ directory), and tool-discovery and project-build should work from then on.

Also, could you take a look at the content of the "D:/Program" file?  It could give some clues into what created that file.  It's probably not a coincidence that more than one user ran into this problem.  If possible, please send that file to me as well.

Thanks,

- Baltasar