Using CCS with Windows Vista and 7

Support information

Code Composer Studio 4 (CCSv4) and newer are fully supported in Windows Vista and 7 (both 32 and 64 bit versions).

Code Composer Studio 3.x (CCSv3) has limited support for Windows Vista and is not supported in Windows 7 (both 32 and 64 bit versions)

Installation

CCSv3

See Code Composer Studio v3.3: Windows Vista Known Issues posted on Update Advisor

It is recommended to install somewhere other than the program files directory. Vista protects files in this directory which can cause problems for CCS.

If you are getting Error: 2738 or Error: 2739 at the beginning of the installation, chances are the <vbscript.dll> or <jscript.dll> are not properly registered.

To correct this follow the procedure below:

• Go to Start Menu --> All Programs --> Accessories
• Right-click on Command Prompt and select Run as administrator
• If you are using 32-bit version of Windows type the following commands in the prompt:

cd %windir%\system32
reg delete "HKCU\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f
reg delete "HKCU\SOFTWARE\Classes\CLSID\{F414C260-6AC0-11CF-B6D1-00AA00BBBB58}" /f
regsvr32 vbscript.dll
regsvr32 jscript.dll

• If you are using 64-bit version of Windows type the following commands in the prompt:

cd %windir%\syswow64 followed by Enter key.
reg delete "HKCU\SOFTWARE\Classes\CLSID\{B54F3741-5B07-11CF-A4B0-00AA004A55E8}" /f
reg delete "HKCU\SOFTWARE\Classes\CLSID\{F414C260-6AC0-11CF-B6D1-00AA00BBBB58}" /f
regsvr32 vbscript.dll
regsvr32 jscript.dll

Source: http://blogs.msdn.com/heaths/archive/2007/05/31/windows-installer-errors-2738-and-2739-with-script-custom-actions.aspx

Also it is recommended to set both 'cc_app.exe' and 'cc_setup.exe' in '<CCSv3 INSTALL DIR>\cc\bin' to run as administrator and in XP3 compatibility mode.

CCSv4 (and greater)

By default, Microsoft Windows Vista and Windows 7 do not allow user level accounts to write files in the "Program Files" directory. This can prevent CCS from starting when installed in the "Program Files" or "Program Files (x86)" directory, because CCS stores configuration data by default in its install directory. Either of the following workarounds can be used to avoid this problem:

• Install CCS outside the "Program Files" or "Program Files (x86)" directory
• Instruct CCS to store configuration data outside the "Program Files" or "Program Files (x86)" directory using the -configuration command line argument. The problem will not occur when running CCS as the Administrator user, but this is not recommended because it compromises the Windows Vista security model

Note: Unlike CCSv4, the default installation directory for CCSv5 (and greater) is outside the "Program Files" directory (C:\ti).

FAQ

Q: I am installing CCS3.3 under Vista 64. Even with administrator privileges and UAC turned off I see some errors. Will they cause any issues?

If the errors you see are:

Error 1920: Service "drpkiant" (drpkiant) failed to start. Verify that you have sufficient privileges to start system service.

Error 1920: Service “XDSFast1_ISA_Bus_Drivers” (xdsfast1) failed to start. Verify that you have sufficient privileges to start system service.

Just ignore the service errors then install CCSv3.3.

Q: Is there emulation support for 64bit Windows?

If you want to use emulation on 64bit Windows you will need to use an emulator for which there are 64bit drivers available.

Q: Does the cc_setup tool work on Vista?

Yes it works but you want to make sure not to run CCS from setup. i.e. when you save your target configuration and it asks you if you want to start or restart CCS say no. Always run CCS from a desktop shortcut and not from setup on Vista. If I run from setup I will frequently get an error after a while telling me that windows needs to reboot.