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.

Code Composer Studio reg..,

Hi,

I am using Code Composer Studio V3.3 for my project application. Its work fine at the time of installation. Some fue days before due to some security reason Administrator rights have taken back in my company. From the date onwards I am facing some problem in CCS (Ex: .pjt file is not generating, some utility like DSP/BIOS configuration is not available and so on).

My question is Administrator rights is necessary to successful execution of CCS ?
Note : I have installed CCS in my PC with Admin rights.

  • saravana Muthu said:
    My question is Administrator rights is necessary to successful execution of CCS ?

    Yes, CCS ends up making dynamic accesses to various system registry entries during run time so to ensure proper operation you should have administrator privelages on the PC that is running CCS (not just the initial install).

    In theory you could have certain registry entries opened to the user to allow CCS to function without administrative privelages but this is not officially supported so there may still be problems. You may be able to get it to work without administrative privelages by adding the given user full control permissions to the registry entries: HKEY_LOCAL_MACHINE->SOFTWARE->GODSP, HKEY_LOCAL_MACHINE->SOFTWARE->Texas Instruments, and HKEY_CLASSES_ROOT. This can be done using start->run->regedit, just navigate to the registry entry in question and right click on it to open the permissions menu and make the change. Note that you would need administrator privelages to edit the permissions on these registry entries and that editing the Windows registry is not something you want to do unless you know exactly what you are doing, it is possible to break your Windows install if you edit the wrong registry entries, any registry changes you make are at your own risk.