• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 79 subscribers
  • Views 7334 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCE V3.1 Service Pack Problem

Eli Hughes9863
Prodigy 180 points

I just installed the CCE service pack (slac135e.zip) to try out the new 5xx parts.   

After install, I notice that the the new code generation tools are not detected.   The only option is for V3.0.0.

It appears that the tools are installed into C:\program files\Texas Instrument\CC Essentials v3\tools\compiler\MSP430_31   but is will not detect this package.

Also,  if I goto the preferences dialog and then goto " C/C++  --> TI Code Generation Tools "    only the older tools show up under 'Discovered Code Generation tools.

I added 'C:\program files\Texas Instrument\CC Essentials v3\tools\compiler\MSP430_31' to the discover path and this did not work either.

 

Any suggestions?

  • 0
    Prodigy 180 points

    Also noticed that *After* I updated, it claims that I have the core edition and note the Full!!    I first installed the Full version with the CD.....

  • 0 in reply to Eli Hughes9863
    TI__Guru**** 173310 points

    Did you have the Free CCE (core edition) installed previously? If so, maybe it didn't do a clean uninstall of that version prior to installing Pro version and the update as it appears to not be recognizing the updated tools for some reason. You may want to try uninstalling and reinstalling the full Pro version followed by the 3.1 update.

    Here is a link to a FAQ on uninstalling/reinstalling CCE: http://tiexpressdsp.com/wiki/index.php?title=CCE_FAQ#How_do_I_fully_uninstall_and_re-install_CCE

  • 0 in reply to AartiG
    Prodigy 180 points

    No,  no other versions.   I did everythig from a clean system.

    Here is a zip file with some pictures of the problem....

     

     

  • 0 in reply to Eli Hughes9863
    Prodigy 30 points

    I had the exact same problem with v3.1 SP3 (slac135e.zip).  I tried two or three uninstall/install cycles with the same results--the 3.1.0 compiler tools were installed but not recognized.  Is it just me, or are there really no release notes explaining the update procedure?

    Finally, I completely uninstalled the core edition and the pro edition, uninstalled cygwin (just in case), updated Java to v6 update 12 from update 11 (also just in case), installed CCE v3 pro, installed the service pack, then rebooted the machine.   I don't know which of these things fixed the problem, but the new compiler tools were recognized.  

    There was one issue, though:  the "cstdint" header file is not present in tools\compiler\MSP430_31\include, which causes compile errors in my code.  From a bare machine, I tried installing CCE core v3.1 SP3, and it had the same problem.  Fortunately, the file is located in tools\compiler\MSP430_31\lib\rtssrc.zip and can be copied into the include directory.

    I really hope that I don't have as many problems with the upcoming eclipse-based C6000 tools as I've had with CCE....

       

  • 0 in reply to pnp
    Prodigy 30 points

    I just installed the subclipse plugin (for SVN integration) and *lost* the ability to use the 3.1.0 compiler tools! This is exactly what I did:

     

    1. Performed installation as described in last message.
    2. Created a workspace and a Managed C++/Asm project.   I was able to select the 3.1.0 compiler.
    3. Closed CCE  
    4. Downloaded and unpacked http://subclipse.tigris.org/files/documents/906/44501/site-1.4.7.zip
    5.  Installed subclipse plugin with the commands:
      • cd "C:\Program Files\Texas Instruments\CC Essentials v3\eclipse"
      • java -cp startup.jar org.eclipse.core.launcher.Main -application org.eclipse.update.core.standaloneUpdate -command install -featureId org.tigris.subversion.clientadapter.feature -version 1.5.2 -from file:///x:/downloads/site-1.4.7
      • java -cp startup.jar org.eclipse.core.launcher.Main -application org.eclipse.update.core.standaloneUpdate -command install -featureId org.tigris.subversion.clientadapter.javahl.feature -version 1.5.4.1 -from file:///x:/downloads/site-1.4.7
      • java -cp startup.jar org.eclipse.core.launcher.Main -application org.eclipse.update.core.standaloneUpdate -command install -featureId org.tigris.subversion.subclipse -version 1.4.7 -from file:///x:/downloads/site-1.4.7
    6. Started CCE and opened the workspace.  An error dialog appeared, stating "The Managed Make project file could not be read because of the following error: Error loading Managed Make project information for project test. The tool definitions for used to create the project are not available." 
    7. Closed CCE and restarted.
    8. Created a new workspace and created a new project.  The 3.1.0 compiler tools could not be selected.
    9. Uninstalled subclipse with the commands:
      • cd "C:\Program Files\Texas Instruments\CC Essentials v3\eclipse"
      • java -cp startup.jar org.eclipse.core.launcher.Main -application org.eclipse.update.core.standaloneUpdate -command disable -featureId org.tigris.subversion.subclipse -version 1.4.7 
      • java -cp startup.jar org.eclipse.core.launcher.Main -application org.eclipse.update.core.standaloneUpdate -command disable -featureId org.tigris.subversion.clientadapter.javahl.feature -version 1.5.4.1
      • java -cp startup.jar org.eclipse.core.launcher.Main -application org.eclipse.update.core.standaloneUpdate -command disable -featureId org.tigris.subversion.clientadapter.feature -version 1.5.2 
      • java -cp startup.jar org.eclipse.core.launcher.Main -application org.eclipse.update.core.standaloneUpdate -command uninstall -featureId org.tigris.subversion.subclipse -version 1.4.7 
      • java -cp startup.jar org.eclipse.core.launcher.Main -application org.eclipse.update.core.standaloneUpdate -command uninstall -featureId org.tigris.subversion.clientadapter.javahl.feature -version 1.5.4.1 
      • java -cp startup.jar org.eclipse.core.launcher.Main -application org.eclipse.update.core.standaloneUpdate -command uninstall -featureId org.tigris.subversion.clientadapter.feature -version 1.5.2 -from file:///x:/downloads/site-1.4.7
    10. Reopened CCE and created a new workspace.  Still couldn't select the 3.1.0 compiler tools. 
    11. Noticed that the 3.1.0 tools are no longer listed beneath Window | Preferences | TI Code Generation Tools.
    12. Uninstalled CCE pro and completely reinstalled CCE and SP3, after which the 3.1.0 compiler was accessible again.

    I realize that the addition of the subclipse plugin is probably not supported by TI, but I have had no problems with it under the free CCE core release. It is very convenient to be able to interact with SVN within eclipse.  

    Has anyone had luck with subversive (the other SVN plugin) with CCE pro v3.1?   I attempted to install that a few weeks ago but was unsuccessful: the command-line installation is not as straightforward as subclipse.     

     

  • 0 in reply to pnp
    Prodigy 180 points

    Thanks for the additional suggestions.

    I notice when I try to install CCEV2, the installer hangs at 2% for about 30 minutes.  The service pack does the same but at the 95% marker. 

    I did file a support case so hopefully there will be some resolution.   This might end up killing our adoption of the 5xx parts.   My window to evaluate is soon coming to an end.

     

     

     

     

  • 0 in reply to Eli Hughes9863
    TI__Genius 9185 points

    Eli, pnp,

    Are you by any chance installing CCE onto a FAT file-system?  If yes, this is a known issue with Eclipse 3.2.  It is documented in eclipse/readme/readme_eclipse.html file.  The workaround for this issue is to launch CCE with the -clean flag once after each upgrade (i.e. after you've installed the CCEv3.1 patch, launch CCE from command-line once by running this command "eclipse.exe -clean").  After you've done this once, you can then launch CCE normally after that.  For NTFS file-systems this should not be necessary, Eclipse will automatically detect the upgraded content.

    pnp, for your second issue (issue with installing subclipse) - you can workaround it (after you've installed subclipse) by deleting the platform.xml file from the eclipse/configuration/org.eclipse.update/ directory.  So, to summarize - install subclipse, delete the platform.xml file, then restart CCE.  That would fix your problem.  You must follow this workaround whenever you install any external third-party tools using the Eclipse command-line update-manager.   I will file a defect to track this problem - we will address this properly in future versions of CCE.

    Thanks, and let me know how the suggested workarounds worked for you,

    - Baltasar

  • 0 in reply to Baltasar Belyavsky
    Prodigy 30 points

    Baltasar,

    Thanks for your reply!  I installed subclipse and deleted platform.xml as you instructed. That solved the problem: the 3.1.0 compiler tools remained available. BTW,  I have eclipse installed on an NTFS filesystem.

    Best regards,

    -Paul

     

  • 0 in reply to pnp
    Prodigy 180 points

    I do have FAT32 but the problem was solved by completely blowing away the PC and reloading the OS, etc.

     

     

**Attention** This is a public forum