CCS keeps forgetting the board

Here's a way to work around the issue:

1. Go into cc_setup and get it configured properly for your board.
2. Save your setup and then export to a ccs file, e.g. C:\myprojects\myboard.ccs.
3. Find a copy of the cc_setup.exe shortcut (e.g. in the start menu) and make a copy on your desktop or wherever you want to launch ccs.
4. Right-click on your cc_setup shortcut and go to properties.  It should have a target that looks like "C:\CCStudio_v3.3\cc\bin\cc_setup.exe".
5. Modify the target by adding -i"C:\myprojects\myboard.ccs" -startCCS
6. If you want, you can even click on "Change Icon" and then click on "Browse" and select ccAppIcon.exe to have a "normal" CCS icon.

Now when you want to launch CCS you can use this new icon.  It will clear out whatever is in cc_setup, load the configuration specified by your ccs file, and then automatically launch CCS.  In this way, even if your setup gets screwed up it should get straightened out on launch.

That said, I think I should point out that many/most CCS stability issues are a result of something broken in the hardware/software.  You should double-check all your power rails as well as the power up sequence to make sure reset is being asserted until after all the clocks and power have stabilized.  From a software perspective I recommend writing a very simple project that can run a simple loop and test that out for a bit to see if you ever get any crashes.  If you don't see any emulation crashes with your simple project that is a good indication that something in your more complicated project is doing something it shouldn't.  Often this sort of behavior arises due to the CPU accessing reserved memory locations.  This could happen due to using an unitialized pointer, stack corruption, etc.

Brad

 Great! Thanks Brad!

 Details: I was using a shortcut that was importing the ezDsp setup each time; I am a bit surprised that it worked at all. 

 Works like a charm now.