• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 392 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS: CCS V9 crashes on newly created workspace due to execution restriction rights

Clément Letonnelier
Expert 2816 points
Other Parts Discussed in Thread: CCSTUDIO

Tool/software: Code Composer Studio

Hi,

We were using CCS V8 so far and decided to switch to CCS V9 (9.3.0) as we intend to use the newly added processor from the C2000 delfino family.

After the install, I have created a new workspace. However, when I restart the software it crashes (see log).

It seems the software is trying to run an executable from a folder inside my user folder.

The problem is that our IT is using AppLocker and restrict execution to a set of directories (such as C:\ProgramData for example) and the user folder is obviously not an allowed one.

What is also odd is that if I uses the workspace I used to have for the V8 with the V9, it doesn't crash.

This is really problematic for us.

Thanks in advance,

Clément

5633.log.txt

  • 0
    TI__Guru**** 466711 points

    Hello,

    I believe the issue is that starting with v9, we put the jxbrowser cache in the eclipse configuration folder instead of the workspace folder. I assume your workspace folders are in a parent folder that has write/run permissions. Typically the eclipse config folder is typically inside the eclipse install dir. But if CCS is installed in a location without write/run access, then it will place this eclipse config folder in the user home directory (which typically has write/run access). But in your case, you don't have full permissions in your user directory. Hence the issue.

    You will need to either install CCS in a writable location or allow the .eclipse folder inside you user home folder to have write/run access. Otherwise you cannot use any of the browser based views in CCSv9+. If you wish to go with the latter, then I can provide a workaround to disable the Getting Started view that is causing the CCS crash on startup.

    Thanks

    ki

  • 0 in reply to Ki
    Expert 2816 points

    Hi,

    Yeah basically:

    • Where the css install is: I have execute rights but not write rights
    • Where the workspace is: I have write rights but not execute rights

    I can install CCS in a writable location, this is totally forbidden by my company IT rules.

    Wrt. the home folder having write/run access, this can also be an issue, I don't think my company IT will allow execution without knowing what's executed.

    It's really problematic this changed starting from the V9, it was perfectly fitting our strong IT security policy.

    I would be interested in the workaround. What would I miss apart from the getting started view (which I don't necessarily have a need for) ?

    Best regards,

    Clément

  • 0 in reply to Clément Letonnelier
    TI__Guru**** 466711 points

    Clément Letonnelier said:
    Wrt. the home folder having write/run access, this can also be an issue, I don't think my company IT will allow execution without knowing what's executed.

    All you need is for is just the .eclipse subfolder (and things underneath) in your user folder to have execute access. Would this be possible?

    Clément Letonnelier said:
    I would be interested in the workaround. What would I miss apart from the getting started view (which I don't necessarily have a need for) ?

    Besides the Getting Started View, you would lose any view that is JxBrowser based (App Center, Resource Explorer, etc).

    The workaround is:

    open the below file for editing:

    <CCS INSTALL DIR>\ccs\eclipse\plugins\com.ti.ccstudio.branding_<ID>\plugin_customization.ini

    change org.eclipse.ui/showIntro to "false" (it should be on line 2)

    Thanks

    ki

  • 0 in reply to Ki
    Expert 2816 points

    Hi,

    I had the change made by the IT to that file as it was protected against me writing to that location.

    It didn't change anything as you can see from the attached log.

    Clément

    6237..log.txt

  • 0 in reply to Clément Letonnelier
    TI__Guru**** 466711 points

    According to your log, the Getting Started view is still attempting to open. After you made the edit to the ini file, can you try using a clean new workspace folder?

  • 0 in reply to Ki
    Expert 2816 points

    This did the trick thanks