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.

Configuring CC v4 for User permissions.

Other Parts Discussed in Thread: LM3S3748

I´m sorry if this is a simple question,  but after an hour of searching I have not found a solution,

My PC is configured with both Administrator and User accounts.

The Users have no write access to the D: System drive, which contains the "Windows" and "Program Files" directories.  They do however have full access to their part of the C: Documents and Settings directory. 

As configured normally, CC has been installed under D:\Program Files.  However it will not run in "User" mode as it requires write access to this directory in order to write mew files into \ccsv4\DebugServer\ etc.

Is there a solution to this?

 

Many thanks

 

Nicholas Lusty

 

 

 

  • Nicholas,

    What Windows is this (XP?)? In any case, whatever account used to run CCS needs write access to that directory. If it is not an admin account, the user account must be modified to have write access.

    ki

  • Hi Ki,

    Thanks for your answer.

    Yes, I use Windows XP. I tend to try to keep my executables and data separate for security reasons.  No "exe" files on my DATA drive (which also has "Documents and Settings"), and no user write access to my SYSTEM drive, and try to limit Administrator access to short periods of installing trusted software.

    This is the first professional Windows application I have had in a long time which doesn't choose to use either
    - a configurable area, or
    - the %TEMP%  or %TMP% folder or
    - something under Documents and Settings
    for its data files.

    Of course I can (and will) give my usual userid access to the necessary folders.

    A quick build of a new project (The LM3S3748 oscilloscope example) showed the following files were changed:

    %ProgramFiles%\Texas Instruments\ccsv4\emulation\analysis\bin\db
    __catalog
    log.0000000001
    topics

    %ProgramFiles%\Texas Instruments\ccsv4\eclipse\configuration\org.eclipse.update
    bookmarks.xml

    %ProgramFiles%\Texas Instruments\ccsv4\DebugServer\license
       licenselocation.txt

    %ProgramFiles%\Texas Instruments\ccsv4\DebugServer\bin\win32\BrdDat
       ccBoard0.dat

    %ProgramFiles%\Texas Instruments\ccsv4\eclipse\configuration\org.eclipse.osgi\bundles\222\1\.cp\os\win32\x86
       win32refresh.dll

    %ProgramFiles%\Texas Instruments\ccsv4\eclipse\configuration\org.eclipse.core.runtime
       .contributions.3
       .contributors.3
       .extraData.3
       .mainData.3
       .namespaces.3
       .orphans.3
       .table.3

    %ProgramFiles%\Texas Instruments\ccsv4\eclipse\configuration\org.eclipse.core.runtime\.manager
       .fileTable.10

     Perhaps something to change in future versions, or is this problem fundamentally related to Eclipse? 

    This is my private computer, but I have worked for at least rwo companies where write access is not allowed to the "Program Files"  folder, and where this could be a problem.

    Many thanks

     

    Nick

     

    p.s. modifying the access rights to the following folders (and their progeny) seemed to work:
    %ProgramFiles%\Texas Instruments\ccsv4\emulation\analysis\bin\db
    %ProgramFiles%\Texas Instruments\ccsv4\eclipse\configuration\
    %ProgramFiles%\Texas Instruments\ccsv4\DebugServer\license
    %ProgramFiles%\Texas Instruments\ccsv4\DebugServer\bin\win32\BrdDat

     

     

  • Hello Nicholas, 

    eclipse\configuration directory is a location where eclipse stores its current ... configuration. Something like most windows apps writing to windows registry. Eclipse already supports being able to specify where this should be re-directed. In newer versions of eclipse it is supposed to happen automatically, but I have not tried it on windows. You can start eclipse from command line with "eclipse -configuration AbsolutePathToUserSpecificDir". You could adjust the shortcut that you use to start CCS. However, this will only get you partially there as those other files still go to locations that you listed. 

    CCSv5 is targeted to have this support where install location can be read only and other data will be written to user specific location. Unfortunately, general availability of CCSv5 with full support for Stellaris devices is targeted for 3Q next year. 

     

    martin

     

  • Excellent news for an excellent product!