Update sites for included Eclipse plugins??

Hi John, 

Thanks for the quick response :)

My main reason so far for wanting to update is better EGit handling of linked resources; a minor issue. I didn't at first realise that mylynn and so on were also installed and would need updating in concert.

However, reading your response I may give it a try on my secondary machine and see how things far with a GitHub clone. Will let you know how I get on :)

Do you know if the eclipse update synchronization issue you mentioned being worked on for upcoming CCS releases?

Thanks

Toby,

We bundle the latest Eclipse service release for the version of Eclipse that we use in our updates.  So the 5.5 release that comes out in September would have the latest Eclipse 3.8 service release.  However on the Eclipse side they seem to have the updates for 3.8 and 4.2 on the same update site so this leads to 3.8 based products like CCS seeing newer incompatible updates.

In CCSv6 we switch over to Eclipse 4.3 so that will get rid of the problem.  We hadn't switched earlier due to performance issues with Eclipse 4.x which have since been resolved in Eclipse 4.3.

Regards,

John

Brilliant, cheers John.

I have to take this opportunity to congratulate the CCS team as it has come on in leaps and bounds in the last year or two (especially since the switch to stock Eclipse)! It makes our workflows better and our jobs easier - much appreciated :)

Thanks Toby, the team will be happy to hear that.  It was a major effort to switch to stock Eclipse from our own branch but has been worth it.

John

I was having the exact same problem so I uninstalled Egit and Egit Support as recommended above.

I then got  a message that CCS must restart. On restart I got an error message  “An error has occurred, See the log file”.

I am now dead in the water, CCS will not run.

 The log file shows :

!SESSION 2014-06-26 13:43:45.697 -----------------------------------------------

eclipse.buildId=

java.version=1.6.0_13

java.vendor=Sun Microsystems Inc.

BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US

Framework arguments:  -product com.ti.ccstudio.branding.product

Command-line arguments:  -os win32 -ws win32 -arch x86 -product com.ti.ccstudio.branding.product

!ENTRY org.eclipse.osgi 4 0 2014-06-26 13:43:47.212

!MESSAGE Application error

!STACK 1

java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini).

            at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74)

            at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)

            at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)

            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

            at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

            at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

            at java.lang.reflect.Method.invoke(Unknown Source)

            at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)

            at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)

            at org.eclipse.equinox.launcher.Main.run(Main.java:1438)

Hi Dan,

I never actually tried this as the next update to CCS (5.5?) had sufficient updates to the EGit plugin to fix the issues I was seeing. What CCS version are you using? CCS 6 uses 3.0.3. I believe this may be advanced from previous CCS versions but the Eclipse website says the latest EGit version is 3.4.1, though attempting to run the update within CCS tells me there are no updates. I guess this means this is the latest supported version for use with the version of eclipse used by CCS 6.

It seems to be working OK for me so far (only had v6 installed for a week or so). I havet come across any other bugs in the older versions of EGit I had been using ill recently either. Was there a particular issue you were trying to overcome by updating?

Anyway, to solve the issue you are seeing now my first recourse (though I'm no expert on CCS or eclipse) would be to just uninstall CCS and reinstall... If eclipse wont uninstall you can just delete the install folder (usually C:/ti/ccsvN (where N is the version number) and then run the install for the new install over the top.

Hope that helps some :)

Thanks for the reply Toby,

I am running CCS v5.5 and I was getting warnings about not being able to resolve linked file resources. I found that this is a known bug in this version of EGit and it had been fixed in the newer versions.

Then I found this thread stating how it was safe to uninstall the current version and install EGit version 3.x.

That is how I got myself in this mess.

Dan

Hi Dan,

Yes, this is the same bug I tripped over. My solution (Im still using CCS5.5 on one machine) is as follows:

If the linked files are of my own creation I have a separate repository for their own, root, project. If they are library files or TI distributed, e.g. such as 'CodeStartBranch.asm' I stopped tracking these in the repo and made sure my project file is using relative paths for all resource paths. I have found that not all pathes are relative out-of the-box if working from one for the example projects and that, pre-v.6, there are a couple of places that the paths need to be checked in the project settings. Some from the top of my head are

Properties > Resource > Linked Resources > Linked Resources tab,

Properties > CCS Build > C2000 Compiler > Include Options,

Properties > CCS Build > C2000 Linker > File Search Path and

Properties > C/C++ Build > Build Variables,

though there may be more places also!

Hope that helps you out some.