Other Parts Discussed in Thread: CCSTUDIO
Lisa,
I did a bit more messing around with my problem of CCS 5.2 freezing when trying to create a new project.
http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/201237.aspx
I decided to have a look at the Eclipse.exe supplied with the CCS installation and found that it also froze when creating a new project. I did a bit of searching around on the Eclipse forums and also on a lot of the Eclipse Wikis and came across an item on the .ini files, and forcing the eclipse.exe application to look at the correct version of the Java JVM.
So I modified the eclipse.ini file to add the -vm line
-startup
plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.100.v20110502
-product
org.eclipse.epp.package.cpp.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
256M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vm
c:\Program Files (x86)\Java\jre6\bin\javaw.exe
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx512m
and by empirical means found that eclipse.exe worked with the -vm address pointing to the 32 bit 1.6 javaw.exe
I then modified the ccstudio.ini to add the same line
-startup
plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
-product
com.ti.ccstudio.branding.product
--launcher.XXMaxPermSize
256M
-showsplash
com.ti.ccstudio.branding
--launcher.defaultAction
openFile
-vm
c:\Program Files (x86)\Java\jre6\bin\javaw.exe
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Dosgi.instance.area.default=@user.home/workspace_v5_2
-Xms40m
-Xmx512m
-XX:ErrorFile=C:\Users\Jim\AppData\Local\.TI\3814048011\0\dmp\hs_err_%p.log
and it works. :-) The splash screen is the Eclipse Indigo one but I can probably live with that. :-)
The operating system is Windows 7 Home 64 bit. I'm sure that everything worked OK when I first installed V5.1 of CCS at the start of the year, but I wasn't able to do any more work until a month or two ago, when the code was upgraded to V5.2 and stopped working. I suspect a Windows or java upgrade might have changed something in the interim which caused the problem.
Jim.
