This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCD 3.3: CGT missing and sources listed in Documents folder

Other Parts Discussed in Thread: CCSTUDIO

BS

Yes, I know CCS v3.3 is not officially supported on Windows 7. Yes, I know x64 is additional pain.

Hello,

I'd like to ask community for hints. Here is my situation. I am using CCS v3.3 on Windows 7 x64. I set it use XP SP3 compatibility mode and run as administrator. It was fine. Until I tried to install fresh release of CGT. Some time ago using some unreproducible magic I got my setup working with CGT 6.0.29. But today I tried 6.0.31 and did not succeed. I know I have to use modern tools, but there still some issues to be resolved.

Here what I do. I installed CGT v6.0.31. After some previous trials I found I have to install at same level, as original CGT. In my case it is

C:\TI\CCStudio_v3.3\C6000>dir /ad /b
cgtools
cgt_6_0_28
cgt_6_0_29
cgt_6_0_31
cgt_6_1_20
csl
DSK6X11
xdais

Then I run Component manager standalone. If I go to build tools, in C64xx node there are all installed tools listed, but unchecked. I tick 6.0.31, save, exit. But changes don't get saved. If I rerun component manager, there will be no selection in C64xx. I've tried to launch Component manager from CCS Help/About menu - same result.

One of consequences of observed problem is that all my sources in project explorer disappeared in Sources folder, but appeared in Documents folder instead. Build fails with "Error, Don't know how to build file". If I open Project, build options, then I see that there is no build tools tab present, only General, DspBiosBuilder and XDC. At present I can select only original 6.0.8 CGT, then I see Compiler, Linker and Link order tabs.

I found similar issue on this forum. Tried to re-register bti6000.dll from cgt_6_0_31/bin folder. It did not help.

I've tried to setup registry values both running compiler.reg and SetupInCCSnRegistry.exe 6.0.31. It did not help.

This way I get my environment broken. CGT 6.0.8 is recognized by CCS, but useless because of bug, which leads to crash. That bug is fixed in following releases of CGT, but I cannot use them in my setup. CCS 5.1 does not work for me yet.

So I'd like to ask for some deeper troubleshooting hints. As I mentioned, it seems, that build tools are not recognized by CCS. I don't mind to manually check ini files and registry for proper values. Please advise.

  • Hello,

    Did you get your standalone CGT installation from: https://www-a.ti.com/downloads/sds_support/CodeGenerationTools.htm#C6000? Sounds like you did but I just want to confirm it.

    rrlagic said:

    One of consequences of observed problem is that all my sources in project explorer disappeared in Sources folder, but appeared in Documents folder instead. Build fails with "Error, Don't know how to build file". If I open Project, build options, then I see that there is no build tools tab present, only General, DspBiosBuilder and XDC. At present I can select only original 6.0.8 CGT, then I see Compiler, Linker and Link order tabs.

    I found similar issue on this forum. Tried to re-register bti6000.dll from cgt_6_0_31/bin folder. It did not help.

    Did you also re-register projsvr.dll? Also check in the component manager if the Project Manager component is enabled (has checkbox enabled). If that doesn't help, it may be an issue with the registry or your component ini file. The ini file, on win7-64, is probably in C:\Program Files (x86)\Common Files\Texas Instruments. Attach the ccs_Compdb.ini file here and i can take a look and see if it looks fishy.

    Thanks

    ki

  • BS

    God bless the people who fixed e2e form for me, now I can post!

    Hello Ki-Soo,

    Thank you for response.

    Yes, I have downloaded CGT from the page you mentioned. To be 100% sure downloaded one more time using provided link.

    I have tried to register both projsvr.dll and bti6000.dll, both before CGT installation and after. I checked Project Manager component - it is selected. However, Build Tools selection is not saved. Under TMS320C64XX node I see all CGT installations, but they all are unchecked, see attachment. Then I select CGT, save exit. On the next run of either Component manager or CCS, this selection is not remembered, again I see all boxes unchecked. The only selection which can persist is v6.0.8.

    I attach ccs_Compdb.ini file as well. Please advise where to look. I don't mind ini files or registry manipulations.

    Thanks in advance.

    ccs_files.zip
  • Hello,

    Is there any hope to revive my setup?

  • Sorry for the delay, I was out for a few days last week and missed this.

    Thanks for the zip. the ini files looks fine, the project manager plugins are there and getting picked up. I'm not sure what other suggestions I can offer. Maybe set the component manager executable (.\cc\bin\comp_mgr.exe) in XP compatibility mode and administrator. It does look like some permissions issue. Did you try logging in with the administrator account (not your account with admin rights but the actual administrator account)? Also turn off UAC and see if this helps.

    ki

  • Hello,

    Thanks for suggestion. Setting XP SP3 compatibility mode and run as administrator were the first thing to enable CCS 3.3 on Win7. These settings did not change, when odd behaviour happened. Moreover, I have similar system, notebook with Win7 x64. I've just tried to install CGT 6.0.31, works fine there. Antivirus, UAC, and compatibility settings are exactly same. Sure, I will try other recipes just to make sure. Still I want to trace the root cause of the issue. So far I see only one: on my working machine there is CCS v5.1 as well, on notebook I have installed, but then removed it.

    Just in case, could you please suggest how to combat another issue. I have uninstalled  CCS v5.1 on the notebook, but reference to its CGT 7.3.1 still present in component manager. How can I remove it?

    Thanks.

  • Tried reinstalling CCS3.3, still no luck...

  • rrlagic said:
    Just in case, could you please suggest how to combat another issue. I have uninstalled  CCS v5.1 on the notebook, but reference to its CGT 7.3.1 still present in component manager. How can I remove it?

    If the CGT still remains on the system, you can uninstall it or remove the registry keys. There should be a little exe called 'RemoveRegistryKeys.exe' in the CGT directory that will do this. Otherwise you will have to delete entries from the Windows registry (not recommended).

    Sorry to hear that the original issue still exists. CCSv3.3 support on Windows 7 seems to be a crapshoot. Some people have really good luck where everything works while others can't get it to work at all. Those people run CCSv3.3 in a XP virtual machine to avoid the problems.

    ki

  • Hello Ki-Soo,

    Thank you for taking time on this issue. I know about XP Mode and used it for a while to run CCS 3.1. My overall experience with that setup is quite unsatisfactory. Honestly, I have forced my team to switch to 3.3 as it was working on Windows 7 natively.

    I know, that 3.3 is too old, but fifth generation is not full feature replacement for it. That's why I keep trying. Is it possible to get information, how CCS recognises, which CGT set is active? I mean what does configuration manager change (registry key, ini file, whatever), so CCS knows it? I don't mind to do some registry edition.

    Thanks in advance.

  • Hello,

    Sorry for the delay. I have not played around with the CCSv3 registry in some time and looks like the location of the entries that v3 uses in Windows 7 is different than XP so I had to do some digging. Anyway:

    rrlagic said:
    I know, that 3.3 is too old, but fifth generation is not full feature replacement for it. That's why I keep trying. Is it possible to get information, how CCS recognises, which CGT set is active? I mean what does configuration manager change (registry key, ini file, whatever), so CCS knows it? I don't mind to do some registry edition.

    If the component manager GUI is not working for you, you can try doing what the Component Manager basically does: modify the registry to point the CCSv3 version to the version of CGT that you wish to use. On my windows 7-64 machine, I can browse to:

    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Texas Instruments\CCS_C:|CCStudio_v3.3

    Then select the device family that is applicable for the device you are using (ex: TMS320C64XX). Then under the subnode 'Build Tools', you can see there is a  path to the compiler bin directory for the active compiler. Try manually changing the path. Also check the paths under 'Assembler' and 'Compiler' if you are using CSL and XDAIS.

    Hope this helps.

    ki

  • Hello Ki-Soo,

    Thank you for keeping help me.

    I checked registry location you hinted. Its fine. When I modify CGT settings in Component Manager, registry updates correctly. But if I restart Component Manager or simply make refresh from View menu - selection is not remembered. I mean although correct setting is written in registry, Component Manager displays all CGT unchecked.

    But then I was pressing all available menu options without any certain purpose - and you would not believe - the miracle happen. Seems after selecting Advanced and All CCS Installations from the View menu, CGT settings were saved.

    At this point I don't have clear recipe, but somehow it works for me now.

    Thank you for your time and efforts.