• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 55 subscribers
  • Views 1403 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.

Want CCS v3.1 working on Windows 7 with SD DSK? -> Read Here (+CCS v4 question)

stijn
Prodigy 40 points
Other Parts Discussed in Thread: CCSTUDIO

I've been using CCSv3.1 (with C6713 and C6416 DSKs from Spectrum Digital) for years on XP, but recently I moved to Windows 7 and I had some problems getting it to work; likely other people tried so I'll share my efforts! I guess the same steps should work for CCSv3.3.

- install as usual, first CCS, then DSK content (I only got one error from windows script installer which I cancelled away, seems not to affect anything)
- at this point, I was able to add the board in CCSetup, yet the USB enumeration didn't work, hence you cannot run the diagnostics nor let CCS connect to the board. Compiling projects was fine though.
- I figured I could get the USB enumeration (CCStduio\drivers\c6713dsk.exe) and the diagnostics (6713DSKDiag.exe) working if I set their compatibility mode to "Windows XP Service Pack 3). At that point, CCStudio itself can still not connect to the target so that wasn't of much use. And putting CCStudio in that same compatibility mode makes the application crash, so no avail there as well.
- I found out that the key to talking to the board is the in the sdgo6713dsk.dvr file: it produces a log file (Sdgo6713DskLog.txt) which basically gave errors saying that it's not supported for this windows version
- Next I downloaded a demo of CCsv4, because it advertised having the Spectrum Digital drivers. And indeed it did. (note that you can also get these from the SD site but I only noticed that afterwards..)
- I just copied the new c6713dsk.exe and sdgo6713dsk.dvr files to my current v3.1 installation, and tadaaaa: works flawlessly

 

Now for my question: can anyone give me some insight and opinions on upgrading to CCS v4? Is it worth the price? Is it worth learning how to use the IDE properly (I never really liked eclipse..)? Are the new codegen tools/SDK better than what I have now? My applications are all very time-critical, will there be a performace gain?

 

Thanks in advance for any answers!

  • 0
    TI__Guru**** 162315 points

    Interesting trick with copying in the newer drivers from CCSv4.  

    I am pretty biased when it comes to CCSv4 as I have a vested interest in getting you on to the latest software.

    You are correct that the IDE is going to take a bit of time to get used to as compared to 3.1.  When we first started using Eclipse a few years ago the thing that took me the longest to get used to was that the projects are file system based.  If a file is in your project directory then it is in your project (you can exclude it if you want).  There are lots of other differences but that one took me the longest to adjust to.  At the end of the overview section on the CCSv4 wiki there is a presentation that goes through some of the benefits of upgrading: http://tiexpressdsp.com/index.php/Category:Code_Composer_Studio_v4

    There have been a lot of changes in the compiler since the version you would have in CCSv3.1, what you might want to do is import your project into v4 measure things with the newer compiler.  Note that build options may have changed since that old compiler was released, the import wizard tries to take care of that for you but I would double check the optimization settings to make sure you are doing an apples to apples comparison.

     

    john

     

     

  • 0 in reply to JohnS
    Prodigy 40 points

    thanks for the reply.

    the fact that Eclipse uses file system based projects is no problem for me: I've been using that for years in Visual Studio.  But that's at the same time my main problem with Eclips: being so used to VS, I find Eclipse's general layout really weird to work with. But I guess spening more time with it should get rid of that problem.

    And indeed, it's probably the best to just use CCS4 for my projects and check/measure if everything still works as expected.