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/CCSTUDIO: Using CCS from external drive

Part Number: CCSTUDIO
Other Parts Discussed in Thread: CONTROLSUITE

Tool/software: Code Composer Studio

Hello,

I have new windows installation, but i still have my prev hard drive with CCS installed on it.

Is there an option to work with CCS without re-install it? (like eclipse?) How?

When I'm running the 'ccstudio.exe' file i'm get an error message with reference to log file.

Thanks

  • Ron,

    What version of CCS are you using? I have done this with recent versions of CCS (v7 and later). Depending on which debug probe you are using you may need to install drivers. Are you able to attach the log file?

    Regards,
    John
  • Hi,

    I'm using CCS 6.

    Log file attached.

    Thanks

    1531143016088.log

  • Ron,

    I just gave this a try with CCSv6.0.0. I copied an existing installation to a usb stick. I then ran the installation from the stick. For me this was fine.

    I created a new workspace when I started CCS. By chance did you use an existing one? I tried using an existing workspace and that seemed to work fine as well.

    Was the entire installation folder copied over? When you installed CCS it would look something like this:
    <root install folder>
    ccsv6
    xdctools_3_30_01_25_core

    You need to copy that root folder. The log makes it seem like the eclipse plugins and features folders are missing.

    Regards,
    John

  • Hi John,
    Thanks.

    I think running CCS from external drive with computer that already have CCS installed on it might be a different case from running it on computer that doesn't have CCS installed on it.

    The CCS actually doesn't started so I can't choose new/existing workspace.

    On my hard drive (where the CCS was installed on the previous windows installation) the folders look like you described,
    I have:
    <root install folder>
    ccsv6
    controlSUITE
    xdctools_3_30_01_25_core

    The file that I tried to run is '<install root>/ccsv6/eclipse/ccstudio.exe'

    I thought it might be issue with paths or some configurations.

    Any suggestions?

    Thanks,
    Ron.

  • Ron,

    It really should work. We do this sometimes with workshops where we have CCS installed on USB sticks and then just get people to run from the stick. I am trying to find a clean machine around here that doesn't have a prior CCS on it.

    If you run eclipse.exe instead of Ccstudio.exe does that open?

    John
  • Thanks.

    No if I run eclipse.exe it shows same message box which says that error occurred and to see log file.

    same if I run eclipsec.exe

    I may reinstall it anyway, but still it is interest me if (and how) ccs may run at that way.

    Thanks,

    Ron.

  • I just noticed that you mentioned eclipsec.exe and not eclipse.exe. They are actually different. Is eclipse.exe there for you?
  • JohnS said:
    I just noticed that you mentioned eclipsec.exe and not eclipse.exe.  They are actually different.  Is eclipse.exe there for you?

    Yes, I have both eclipse.exe and  eclipsec.exe in addition to ccstudio.exe.

    All these exe (even if they are different), show me the same error msg box.

    Thanks

  • CCS has dependencies on some Microsoft visual C runtimes being present but I would not expect that for eclipse/eclipsec. But maybe even when using those launchers our components are getting loaded which then have the dependency on those libraries.

    CCSv8.1 is dependent on MSVC9,MSVC110,MSVC141. The numbering is odd, MSVC9 is the 2008 VC libraries, MSVC110 is 2012 and MSVC141 is 2015
    They are available here:
    support.microsoft.com/.../the-latest-supported-visual-c-downloads

    I am not sure which ones CCSv6 was dependent on but I can see if I can find out.

    John
  • Ron if you give this a try again in the future check the MSVC installations on the machine. That could very well be what is preventing it from running. I will close off this thread but we can pick it up again if you give it a try down the road.

    Regards,
    John