CCS 4.1.3 not recognising Compiler tools

Hi Jon,

Jon Nicoll said:

D:/Program Files/Texas Instruments/ccsv4/tools/compiler    # hmm - forward slashes in the pane, is this as expected?

Yes

Jon Nicoll said:

The lower pane has the green icons of tools discovered: ARM, C2000, C6000... etc. But there is no 'expand' box to allow me to see what the actual tools discovered are, and it does not appear that any tools actually have been discovered. So if I attempt to create an (ARM, for example) project, the CCS wizard tells me

"No Code Generation Tools have been installed... please install Code Generation Tools before creating a project of this type"

What kind of install did you do? Did you install from the full DVD (Platinum) image? And did you do a full install or a custom one?

Thanks

ki

Hi Ki-Soo, thanks for your reply:

Ki-Soo Lee said:

What kind of install did you do? Did you install from the full DVD (Platinum) image? And did you do a full install or a custom one?

I installed from an archive .zip file at our company, but I understand this is the full Platinum image: The file is  called

setup_CCS_4_Platinum.zip, and our installation procedures (which I understand I followed) call for setting the 'Platinum' option, and also 'install everything', which again I believe I did.

Thanks
Jon N

Hi Ki-Soo

A brief followup - I un-installed and re-installed CCS4 platinum, and continue to get the same problem.

I've attached a screenshot which shows the 'Code Generation Tools' part of 'Windows | properties' together with a dialog showing my directory structure.

As before, no CGTs appear to be being found, even if I try to add them manually.

BTW, I notice above the first panel it says 'Tool Discovery Path'. In the screenshot on the wiki page 'Compiler Installation and Selection' this says 'Extended Tool Discovery Path'. I assume this is djust slight differences between versions.

I perhaps ought to mention that others at my place of work have successfully installed CCS4 and the CGTools using the same .ZIP file I am working from ;-(.

Thanks in anticipation for your help.

Regards

Jon N

Hi Jon,

Could you locate the file <workspace>/.metadata/.log, and attach it to a post?

Thanks,

- Baltasar

Hi Baltasar

Baltasar Belyavsky said:

Could you locate the file <workspace>/.metadata/.log, and attach it to a post?

Interesting... My workspace doesn't have a .metadata/.log file!

I double-checked, by renaming my old workspace directory (whilst out of CCS), and restarting ,and creating a new workspace directory. Neither this or the old directory have a .log file.

They contain:

.plugins/    # directory

version.ini

.lock    # 0 bytes

(The .lock file seems to remain even when I exit CCS, which seems odd to me).

I do seem to have a .metadata/.log file from a previous attempted installation ... I'd be happy to attach that but it's probably a bit misleading bearing in mind the above (it just has a load of entries '.../blah/html cannot be opened', relating to the documentation).

Does this help any?

Thanks & Regards

Jon N

Jon,

This .log file would only be created when something actually gets logged, so it's not surprising that the file is missing initially.

Try launching CCS on a clean workspace again, and then navigate to the Preferences > CCS > Code Generation Tools page, and then see if the .log file is created at that point.

- Baltasar

Hi Baltasar

    I created a new workspace as you suggested, and also tried manually adding new CGT paths (to the 'correct' places AFAIK). A .log file was not created. In a separate run, I also tried adding a 'bad' CGT path, ie. a path in which I knew no CGT tools would be found. No .log file was created then either.

I realise this isn't the most helpful report to help narrow down the problem...

Best Regards

Jon N

Jon,

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

Hi Balthasar

Baltasar Belyavsky said:

Jon,

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

Not sure what you mean by 'execute' permission - I'm running under XP, not Linux. But I do seem to have permissions as expected; at least, the only attribute bits set are the 'A' (Archive) bit on a few files & directories, nothing related to CGT.

What you mean by the 'CGT Install directories' BTW? As mentioned, I can use the Arm compiler from the command line, so it's not a matter of permissions on those AFAICT.

I do have a fair level of Administrative permissions on this machine - I performed the installation myself. I can try to get someone will full Adminitrator permissions to run things - but surely me running at the same level that I installed CCS with makes sense?

Thanks for your continued assistance with this.

Regards

Jon N

Jon,

FYI - this problem has been reported in another post as well: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/62125/223165.aspx.

We're currently trying a few things, and I'll let you know once we find something.

- Baltasar

Hi Baltasar

Yes, that report looks like another occurrence of the same problem. I had previously tried adding the CGT path that way and got the error shown in the screenshot in that thread. I didn't report it as the canonical problem seemed to be that the tools weren't in the Window | Preferences | ... CGT panes.

At least it's not just me! I look forward to you finding out more about how to solve this...

Best Regards

Jon N

Jon,

Could you try the following steps:

1. Copy the attached file into your <CCS_install_dir>/ccsv4/eclipse/plugins/ directory.
2. Rename the file to change its extension to ".jar" from ".zip".
3. Restart CCS and check if your codegen tools get discovered or not.
   .

Thanks,

- Baltasar

Hi Baltasar

    Success! That seems to work ;-). The path to the tools comes up in the Window | properties | ... CGT tools dialog pane, and when I try to create a project (eg) "Ti v4.6.3" comes up in the 'Code Generation Tools' field.

Thank you very much. It would be interesting to know why this doesn't work for me when it seems to work for so many others.

Best Regards

Jon N

Hi Baltasar

    sorry for asking this followup question  - it may or may not be connected with the above issue.

Having got what I hope is a working CCS4 implementation, I have attempted to either create a CCS4 project, or import a legacy CCS3 project.

I can set either of these up fine (specifying ARM code generation, as it happens). But when I attepmt to build either these projects, I get the error:

Build error
(Exec error:%1 is not a valid Win32 application.
)

I would ask this as a new question, but it sorta-feels like it might be related to the CGT discovery. Am I doing something foolish?

Thanks again

Jon N

Jon,

Can you check if you have a file named "Program" in your D: drive?  (just "Program", without any file extension).  If you do, try renaming that file to something else, and restarting CCS.  And try to build a project then.

- Baltasar

Hi Baltasar

Hey, good catch!

I could probably have worked that one out, as well, with a little lateral thinking. I remember those sort of problems being around ... oh, 15 years ago or so? ;-/

Anyway, your help is much appreciated. I can now start to do some real work!

Thanks again

Jon N

OK, so this is the root cause of all the tool discovery problems on your PC.  You could now delete that plugin from the plugins/ directory, and the tool discovery should work without it.

It would be good go find out what created that "D:/Program" file on your PC.  Usually this happens when some script attempts to create a file, and whoever wrote the script forgot to enclose a "D:/Program Files/***" path in quotes.  You could try opening that file with Text Editor, and looking at the content...that might give you some clues into what created that file.  Let me know if you think CCS is responsible for creation of that file.

Thanks,

- Baltasar