• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 84 subscribers
  • Views 373 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.

How to reinstall 28069 controlStick SW Tools

Justin Gullotta
Intellectual 420 points

Other Parts Discussed in Thread: CONTROLSUITE

I bought the 28069 USB controlStick kit last week.  I installed the software (controlSUITE and CCSv5) and was up and running with the example projects in a matter of minutes.  I had no problems and everything worked perfectly.  After a bit of messing around with the projects (trying to incorporate CLA functionality into one of the example projects) the example project that I was working with was a mess, and I wanted to restore it to its original state.  I tried to get them off the installation disk, but it didn't work.  I reinstalled the controlSuite software, and that didn't work.  I uninstalled and reinstalled, and that didn't work.  I erased controlSuite and CCSv5 off the disk and reinstalled, and that finally got the project to restore to its original state, but now CCSv5 is complaining about all kinds of errors including RAM address ranges being incorrect, compiler versions not suported or not installed, include.h files not found, etc.  Any further attempts to uninstall and reinstall do not help and I have very little hope of salvaging it.  I would very much like to completely start over with this kit, since it worked flawlessly when I first installed it.  Can anyone please help me wipe this installation off my disk so I can start fresh?

Thank you,

Justin

  • 0
    TI__Expert 8560 points

    Justin,

    I've had this happen before too.  Have you tried completely removing controlSUITE and then reinstalling it from the original disk?  Since it doesn't have an uninstall, the only way I've found to completely remove it is to go to c:\TI and physically delete the controlSUITE directory, then reinstall the original.

    Give me a call if you want to talk through it.

    John

  • 0 in reply to John Walker
    TI__Mastermind 22025 points

    Hi Justin,

    Sorry to hear you are having some trouble getting up and running with CCSv5 and ControlSUITE.  Many things have changed in how CCS works between version 4 and 5, and it appears that some of the new "features" are actually behaving more like "bugs".  We are working to ensure all of the controlSUITE examples work seamlessly in both versions 4 and 5, but it will take some time to comb through and fix everything that CCSv5 has broken.

    I took a look at the blinky example and here is what I found:

    The exact issue appears to be the fact that there is no device associated with the blinky example project.  When the user follows the steps in resource explorer to build and run the project, they must select a device before the debugger configuration may be setup (step 3).  When the user does this CCSv5 automatically pulls in the default RAM linker command file.  This creates overlapping memory ranges which CCS isn't happy about.  It also appears that when you specify the device type, the runtime model options are getting modified to included floating point support which conflicts with the runtime support library which is used in this project.

    I also had issues removing the project and getting back to square one easily, but I think I've figured out what is going on.  When you import a project through the resource explorer, the project actually gets copied into your workspace (source files and all...), any modifications you make will only be present in the copy in your workspace directory (which leaves the original copy pristine).  If you import a project via the normal File->Import mechanism and do not copy the project into the workspace, then when you make modifications you will be messing with the original copy.  In the future with CCSv5 always copy the example projects into your workspace so that the original copy stays intact. In the future if you import a project and it gets copied into your workspace, you can get back to square one by simply deleting the copy in your workspace and reimporting via the resource explorer.  In the case that you accidentally did import without copying into your workspace, I've attached a pristine copy of the example that you can extract into:

    C:\TI\controlSUITE\development_kits\F28069 controlSTICK

    in order to replace the messed up copy you currently have.

    2021.Timer - BlinkingLED.zip

    Hopefully this answers your question.  Let me know if you need any more help getting up and running.

    Trey German

  • 0 in reply to Trey German289
    TI__Mastermind 22025 points

    Justin,

    I thought I'd also mention this issue is documented in a sticky post in the forums currently.  Take a look at this guide for more information:

    http://processors.wiki.ti.com/index.php/C2000_Getting_Started_with_Code_Composer_Studio_v5#Known_Issues

    Trey