how to install cgt 7.4.x to CCS 3.3

Hi Ki-Soo,

Below is the updated compiler.reg in red but I still don't see this compiler from the component manager.

I wonder what is CGT_C:|compiler\bin| because when I check my current compiler 7.0.4, this part is CGT_C:|Program Files (x86)|Texas Instruments|C6000 Code Generation Tools 7.0.4|bin|

Do you think I need to replace "CGT_C:|compiler\bin|" with "CGT_C:|Program Files (x86)|Texas Instruments|C6000 Code Generation Tools 7.0.4|bin|"?

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Texas Instruments\CGT_C:|compiler|bin|]
"ProductName"="Texas Instruments C6000 Code Generation Tools"
"VendorName"="Texas Instruments"
"Version"="7.4.13"

[HKEY_LOCAL_MACHINE\SOFTWARE\Texas Instruments\CGT_C:|compiler|bin|\TMS320C62XX\Build Tools\Assembler\SearchPath_1]
"bActive"=dword:00000001
"Order"=dword:00000000
"Path"="C:\\Program Files (x86)\\Texas Instruments\\C6000 Code Generation Tools 7.4.13\\include\\"

[HKEY_LOCAL_MACHINE\SOFTWARE\Texas Instruments\CGT_C:|compiler|bin|\TMS320C62XX\Build Tools\Compiler\SearchPath_1]
"bActive"=dword:00000001
"Order"=dword:00000000
"Path"="C:\\Program Files (x86)\\Texas Instruments\\C6000 Code Generation Tools 7.4.13\\include\\"

[HKEY_LOCAL_MACHINE\SOFTWARE\Texas Instruments\CGT_C:|compiler|bin|\TMS320C62XX\Build Tools\Linker\SearchPath_1]
"bActive"=dword:00000001
"Order"=dword:00000000
"Path"="C:\\Program Files (x86)\\Texas Instruments\\C6000 Code Generation Tools 7.4.13\\lib\\"

[HKEY_LOCAL_MACHINE\SOFTWARE\Texas Instruments\CGT_C:|compiler|bin|\TMS320C64XX\Build Tools\Assembler\SearchPath_1]
"bActive"=dword:00000001
"Order"=dword:00000000
"Path"="C:\\Program Files (x86)\\Texas Instruments\\C6000 Code Generation Tools 7.4.13\\include\\"

[HKEY_LOCAL_MACHINE\SOFTWARE\Texas Instruments\CGT_C:|compiler|bin|\TMS320C64XX\Build Tools\Compiler\SearchPath_1]
"bActive"=dword:00000001
"Order"=dword:00000000
"Path"="C:\\Program Files (x86)\\Texas Instruments\\C6000 Code Generation Tools 7.4.13\\include\\"

[HKEY_LOCAL_MACHINE\SOFTWARE\Texas Instruments\CGT_C:|compiler|bin|\TMS320C64XX\Build Tools\Linker\SearchPath_1]
"bActive"=dword:00000001
"Order"=dword:00000000
"Path"="C:\\Program Files (x86)\\Texas Instruments\\C6000 Code Generation Tools 7.4.13\\lib\\"

[HKEY_LOCAL_MACHINE\SOFTWARE\Texas Instruments\CGT_C:|compiler|bin|\TMS320C67XX\Build Tools\Assembler\SearchPath_1]
"bActive"=dword:00000001
"Order"=dword:00000000
"Path"="C:\\Program Files (x86)\\Texas Instruments\\C6000 Code Generation Tools 7.4.13\\include\\"

[HKEY_LOCAL_MACHINE\SOFTWARE\Texas Instruments\CGT_C:|compiler|bin|\TMS320C67XX\Build Tools\Compiler\SearchPath_1]
"bActive"=dword:00000001
"Order"=dword:00000000
"Path"="C:\\Program Files (x86)\\Texas Instruments\\C6000 Code Generation Tools 7.4.13\\include\\"

[HKEY_LOCAL_MACHINE\SOFTWARE\Texas Instruments\CGT_C:|compiler|bin|\TMS320C67XX\Build Tools\Linker\SearchPath_1]
"bActive"=dword:00000001
"Order"=dword:00000000
"Path"="C:\\Program Files (x86)\\Texas Instruments\\C6000 Code Generation Tools 7.4.13\\lib\\"

 

Thanks,

Dongho

Thank you KiSoo ;) Now I can see the new compiler from the component manager!

Hi KiSoo

Thanks for your help but I have another question with this 7.4.13 compiler.
Once I select this ver, I can't build the existing project.
What I've found is, after this compiler selection, when i check the Build Options, I don't see the Compiler, Linker, Link Order tap.
I see only General and DspBiosBuilder tap.
And I don't see the included .h, .lib, and .c from the navigation explorer anymore.
Let me know if you have any idea.

Thanks,
Dongho

Dongho - what device are you working with? And is it a BIOS project?

KiSoo, below is the .pjt file I'm working on now. Let me know if you need more information.
Also if possible, i want to have a help session to resolve this issue asap.

-Dongho



; Code Composer Project File, Version 2.0 (do not modify or remove this line)

[Project Settings]
ProjectDir="T:\ssp_dsp_core\source\Algorithm\block_encoder\c64x\unit_test\"
ProjectType=Executable
CPUFamily=TMS320C64XX
Tool="Compiler"
Tool="CustomBuilder"
Tool="DspBiosBuilder"
Tool="Linker"
Config="Debug"
Config="Release"

[Source Files]
Source="..\..\..\..\..\..\ssp_tools\ti_compiler_c6000_code_generation_tools_7.0.1\lib\rts64plus.lib"
Source="..\ssp_block_encoder.c"
Source="main.c"
Source="test.cmd"

["Compiler" Settings: "Debug"]
Options=-k -pm -pdsw225 -o3 -fr"$(Proj_dir)\Debug" -i"..\" -i"..\..\" -i"..\..\..\" -d"_DEBUG" -mi100 -mv6400+

["Compiler" Settings: "Release"]
Options=-o3 -fr"$(Proj_dir)\Release" -mv6400

["Linker" Settings: "Debug"]
Options=-c -m".\unit_test.map" -o".\unit_test.out" -w -x

["Linker" Settings: "Release"]
Options=-c -m".\Release\unit_test.map" -o".\Release\unit_test.out" -w -x

["main.c" Settings: "Debug"]
Options="Compiler" +{-g} -{-o3}

["test.cmd" Settings: "Debug"]
LinkOrder=1

["test.cmd" Settings: "Release"]
LinkOrder=1

Hi KiSoo,

Also when I open an existing project in CCS V3.3, I could see that all source files are moved under douments folder. I am unable to build the project. Also I am unable to add any C files to the project. 

And I found one of your answer to somebody had similar issue as me. Your recommendation was below but it is not good for me. After running these two .dll, I still sees all the sources under documents folder... so can't build.

I've seen that issue with CCSv3 occur when either the project manager component or the build tools have been disabled.

Could you try the below:

re-register the project management component:

> regsvr32 C:\CCStudio_v3.3\cc\bin\projsvr.dll

re-register the build tools:

> regsvr32 C:\CCStudio_v3.3\tms470\cgtools\bin\btiarm.dll

yes it could be possible that the dlls are not registered. Likely the bti one since that would come with the new CGT.

Note that the instructions there work for a 32-bit windows system. Since you are on a 64-bit OS, those would not work. You need to make sure you call the 32-bit version of regsvr32 and not the the 64-bit version of regsvr32.

support.microsoft.com/.../282747

Try that and see if that helps any.

I followed below steps.

cd \windows\syswow64
C:\Windows\SysWOW64>regsvr32 C:\CCStudio_v3.3\cc\bin\projsvr.dll
C:\Windows\SysWOW64>regsvr32 C:\Program Files (x86)\Texas Instruments\C6000 Code Generation Tools 7.4.13\bin\bti6000.dll

when i register bti6000.dll, I got below error because of the spaces "Program Files (x86)"

The module "C:\Program" failed to load. ......The specified module could not be found.

I can successfully registerbti6000.dll by using " " as below. But still I have the issue. All the source files are under documents folder and can't build.
C:\Windows\SysWOW64>regsvr32 "C:\Program Files (x86)\Texas Instruments\C6000 Code Generation Tools 7.4.13\bin\bti6000.dll"

I can successfully registerbti6000.dll by using " " as below. But still I have the issue. All the source files are under documents folder and can't build.
C:\Windows\SysWOW64>regsvr32 "C:\Program Files (x86)\Texas Instruments\C6000 Code Generation Tools 7.4.13\bin\bti6000.dll"

I tried this out and I am also able to reproduce this. Looking at the registry, I think there are some entries missing (BT_CSLID). I'll need to get some assistance from some other experts. This may take time since CCSv3 integration with the newer compiler versions is completely unsupported.

In the meantime, I suppose you can try the original workaround you asked about - manually copy the cgt to the existing compiler folder. It is basically copying all the content inside the new compiler into C:\CCStudio_v3.3\C6000\cgtools (backup cgtools first and then erase everything in there before copying the new stuff in). This is an ugly hack that I don't recommend but I suppose it doesn't hurt to try.

Also note that CCSv3.3 is unsupported and it is strongly recommended to update your CCS version if you want to use the newer compiler. It is likely even if you get CCSV3 to recognize the newer compilers, that you will run into other various issues down the road and we will not be able to provide much support on this.

thanks
ki