• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 1260 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 v3.3 Workspace Error

Gregory Havenga
Prodigy 60 points
Other Parts Discussed in Thread: OMAP-L137

I was happily developing along, trying different things to get my DSP only (C6747 on the OMAP-L137 EVM) to run out of flash.

I was making progress, but periodically I was getting out of code composer studio and back in after building the image and trying to flash it.

On loading CCS v3.3 and then trying to open my workspace, I now get a dialog box titled "Code Composer Studio" that says "Error Loading Workspace!".  I can't get rid of this, I can't open any projects, I'm dead in the water!

I've tried restoring my workspace from a zipped copy, removing all the intermediate files, etc., and nothing is helping.

Is there ANY WAY to tell what CCS3 doesn't like about this workspace (or whatever else it doesn't like)?

  • 0
    Prodigy 60 points

    It's worse than I described - I can't open projects, create a new workspace, nothing - does anyone know how to do a "do-over"?  

    I've cleaned out everything I can think of - but to no avail.

    Ideas?  TI Support?

  • 0 in reply to Gregory Havenga
    Prodigy 60 points

    I finally had to resort to repairing the CCS v3.3 installation.

    One thing - on  Win 7 CCS v3.3 crashes on exit nearly every time - I think this lead to corruption in some file (not my workspace, since after the reinstall, the same workspace it complained about suddenly was ok) - or in the registry.

    I have the CCS v3.3 that came with my EVM - what are my options for upgrading to v4?  Does anyone know?  It's not especially clear on the website if your an EVM owner.

    G

  • 0 in reply to Gregory Havenga
    TI__Guru**** 162895 points

    Gregory,

    The OMAPL137 EVM has onboard emulation so you would be able to use a free CCSv4 license.  You could download the image and then when you run it for the first time click on the "use free limited license" button.  When you are creating your target configuration I believe the one you want for L137 is "Spectrum Digital DSK-EVM PLUS onboard USB Emulator".  The PLUS part is important.

    If I run CCSv3.3 from cc_setup I get a crash most of the time when I exit.  If I run it from cc_app then I see this a lot less.  3.3 does a lot of windows registry manipulation that windows 7 really doesn't like.  CCSv4 doesn't do that.

    Regards,

    John

     

  • 0 in reply to JohnS
    Prodigy 60 points

    What is the difference between cc_setup and cc_app?  

    Can I just modify the shortcut (I'm using the DSP EVM startup shortcut) to use cc_app instead of cc_setup?  (actually, I just answered this one myself - yes, you can).

    Thanks,

    Greg

  • 0 in reply to Gregory Havenga
    TI__Guru**** 162895 points

    Greg,

    cc_setup is the setup tool that is used to configure what target CCS is going to be debugging.  Sounds like what the EVM software has done is setup a desktop shortcut to cc_setup that loads a specific configuration and then has a startCCS parameter after that.  That is going to crash a lot on win 7.

    cc_app is the CCS executable.  You can change the desktop shortcut to run it but remove all the other parameters being passed to it.  

    Or you could just create a new desktop shortcut to cc_app.exe, it is in the cc\bin folder

    Regards,

    John