• State Resolved
  • Locked Locked
  • Replies 14 replies
  • Subscribers 53 subscribers
  • Views 2054 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.

CCSv4 debugger not launching

Angelo Joseph
Expert 1240 points
Other Parts Discussed in Thread: CCSTUDIO

Did not change anything in my PC. Just went through a restart and now when I launch the debugger I get the following message. I have tried cleaning up workspace and also lanching eclispe with -clean option.

Excpetion occurred during launch

Reason: An internal error occurred during 'Creating Debug Server', Please see the Error log for details

Log is as follows

Could not createInstance(@ti.com//DebugServer1;1.{bfab7a88-14c8-48be-8729-f7701e4e0f35}) The function "createInstanceByContractID" returned an error condition (0x80004051) (0x80004005)

Btw following is the full error message

org.mozilla.xpcom.XPCOMException: Could not createInstance(@ti.com/DebugProperties;1,{f64a3818-aa00-4a2d-8404-20017ed45619})Java/XPCOM bridge thread: ExecutionException: java.lang.OutOfMemoryError: The function "createInstanceByContractID" returned an error condition  (0x80004005)  (0x80004005)
 at com.ti.debug.engine.xpcom.Runtime.createComponent(Runtime.java:182)
 at com.ti.debug.properties.impl.DebugPropertiesManager.<init>(DebugPropertiesManager.java:28)
 at com.ti.debug.engine.cce.CCEPropertiesEngine.<init>(CCEPropertiesEngine.java:12)
 at com.ti.debug.engine.cce.CCEPropertiesEngine.createInstance(CCEPropertiesEngine.java:20)
 at com.ti.debug.engine.cce.CCEPropertiesEngine$Factory.createInstance(CCEPropertiesEngine.java:31)
 at com.ti.ccstudio.debug.server.extensions.ExtDebugPropertiesManager.createInstance(ExtDebugPropertiesManager.java:40)
 at com.ti.ccstudio.debug.server.factory.PropertiesEngineFactory.createDebugPropertiesManager(PropertiesEngineFactory.java:37)
 at com.ti.ccstudio.debug.core.preferences.DebugPropertyPreferenceStore.createDebugPropertiesManager(DebugPropertyPreferenceStore.java:638)
 at com.ti.ccstudio.debug.core.preferences.DebugPropertyPreferenceStore.loadProperties(DebugPropertyPreferenceStore.java:203)
 at com.ti.ccstudio.debug.core.preferences.DebugPropertyPreferenceStore.setTarget(DebugPropertyPreferenceStore.java:177)
 at com.ti.ccstudio.debug.core.preferences.DebugPropertyPreferenceStore.<init>(DebugPropertyPreferenceStore.java:107)
 at com.ti.ccstudio.debug.ui.launch.ProjectDebugLauncher.initializeDebugProperties(ProjectDebugLauncher.java:453)
 at com.ti.ccstudio.debug.ui.launch.ProjectDebugLauncher.validateExistingLaunchConfiguration(ProjectDebugLauncher.java:325)
 at com.ti.ccstudio.debug.ui.launch.BaseCCEDebugLauncher.findExistingLaunchConfiguration(BaseCCEDebugLauncher.java:251)
 at com.ti.ccstudio.debug.ui.launch.BaseCCEDebugLauncher.getLaunchConfiguration(BaseCCEDebugLauncher.java:194)
 at com.ti.ccstudio.debug.ui.launch.BaseCCEDebugLauncher.internalLaunchHeadless(BaseCCEDebugLauncher.java:143)
 at com.ti.ccstudio.debug.ui.launch.ProjectDebugLauncher.launchHeadless(ProjectDebugLauncher.java:115)
 at com.ti.ccstudio.debug.ui.launch.BaseCCEDebugLauncher.launch(BaseCCEDebugLauncher.java:67)
 at com.ti.ccstudio.debug.ui.launch.DebugActiveProjectAction.launch(DebugActiveProjectAction.java:122)
 at com.ti.ccstudio.debug.ui.launch.DebugActiveProjectAction.doRun(DebugActiveProjectAction.java:89)
 at com.ti.ccstudio.debug.ui.launch.DebugActiveProjectAction.run(DebugActiveProjectAction.java:84)
 at org.eclipse.ui.actions.ActionDelegate.runWithEvent(ActionDelegate.java:70)
 at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:244)
 at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229)
 at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539)
 at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
 at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
 at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
 at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:928)
 at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3348)
 at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2968)
 at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
 at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
 at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
 at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
 at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:97)
 at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
 at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
 at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
 at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
 at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
 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.core.launcher.Main.invokeFramework(Main.java:336)
 at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
 at org.eclipse.core.launcher.Main.run(Main.java:996)
 at org.eclipse.core.launcher.Main.main(Main.java:971)

  • 0
    TI__Guru**** 162305 points

    Angelo,

     

    What version of CCSv4 is this?  Is this 4.1.0, 4.1.1?

     

    Thanks,

    John

  • 0 in reply to JohnS
    Expert 1240 points

    Version: 4.1.1.00014  - I installed updates to see if that would fix the problem.

    Thanks

    Angelo

  • 0 in reply to Angelo Joseph
    TI__Expert 5985 points

    Angelo,

    Can you try renaming DebugServer\win32\components\compreg.dat to something else and restarting eclipse?

    Darian

  • 0 in reply to Darian Sale
    Expert 1240 points

    Tried what you had suggested. Problem still persists. Please help.

     

    Angelo

  • 0 in reply to Angelo Joseph
    TI__Expert 5985 points

    Very likely a dependent dll is missing, or another application has added a conflicting dll to windows\system32.   If you have dependency walker (it comes with visual studio, but is likely available for download form microsoft with a google search), could you add ccsv4\common\bin, ccvs4\common\uscif, ccsv4\DebugServer\win32 to your path and then view the dependencies of ccsv4\DebugServer\win32\components\DebugServer.dll and let me know if anythings missing or unmatching?

    Darian

  • 0 in reply to Darian Sale
    Expert 1240 points

    Yes a problem was detected by dependency walker. How do I send you the dependency walker image file.

    MSVCR80.DLL
    NSPR4.DLL
    SETUP_PARSER.DLL
    XPCOM.DLL
    TIOFR11.DLL
    XPCOMUTILITY.DLL

    For the above dlls I get a message Error opening File. The system cannot find the file specified.

  • 0 in reply to Angelo Joseph
    Expert 1240 points

    I think I figured out what is going on. We had to install a RS-232 to USB converter to connect to the UART on the board,. I have a feeling that this conflicting with the driver on the Code Composer v4. I uninstalled this and it seems to workl. But we really need both to co-exist.

    Angelo

     

  • 0 in reply to Angelo Joseph
    TI__Guru**** 463941 points

    Did you set this up recently (when CCS started to have the issue)?

  • 0 in reply to Angelo Joseph
    TI__Expert 5985 points

    The emulation driver isn't loaded by the debugger until after debugserver.dll is registered, but the error message you got said it couldn't find debugserver.dll as registered.  We can confirm if the software is conflicting with debugserver.dll or the emulator by re-installing the USB converter and trying to launch with a simulator.

    One thing we had problems with before was logger.dll.  We expect to load it from ccsv4\common\bin, but some other software will install a similarly named dll in windows\system32.  Re-install the converter, and then check if there's a logger.dll in windows\system32.  If so, delete it and try CCS again.

    Regarding your previous post, if you want to attach the dependency walker image file, click on "Options" when you post (should be just above the quoted text) and there's an option to attach a file from there. 

    Regarding the files that are missing:

    • NSPR4 and XPCOM should exist in <install>\ccsv4\DebugServer\win32
    • setup_parser should exist in ccsv4\common\bin
    • tiofr11 and xpcomutility should exist in ccsv4\DebugServer\bin\win32

    Those files should all be loaded by the system prior to loading debugserver.  If you add those three directories to the path, and then run dependency walker with the new path, it should be able to find those files and show that everything's good, or that something can't be loaded.  MSVCR80 is loaded via microsoft's new manifest file thing, so if you have an older dependency walker it won't show up as found (but if all the other files are ok, we can always re-install just the ms libraries).

    Darian

  • 0 in reply to Darian Sale
    Expert 1240 points

    Darian

    I setup my connection as Texas simulator with C74x cycle accurate simulate. When I launch the debugger nothing happens. eclipse just does nothing, does not hang up or anything.

    I added the properr search paths for all the DLLs and then re-ran dependecy walker. I have attached the file as DebugServerUpdated.123 please rename as .dwi and look at the file. Looks like there is a problem with logger.dll

    Thanks

    Angelo

    DebugServerupdated.123
  • 0 in reply to Angelo Joseph
    TI__Expert 5985 points

    Angelo,

    There should be a logger.dll located in <install>\ccsv4\common\bin, but it's being overridden by the logger.dll that's in c:\windows\system32 (I'm guessing the usb driver installed it there).  You should be able to work around this by copying <install>\ccsv4\common\bin\logger.dll to <install>\ccsv4\eclipse\jre\bin\.

    There's code that's supposed to force the load from common\bin vs windows\system32, and I'm not sure what that's not working.  If the above works for you, could you right click on <install>\ccsv4\DebugServer\win32\components\DebugServer.dll select properties, click on the version tab, and then let me know the file version?

    Thanks,

    Darian

  • 0 in reply to Darian Sale
    Expert 1240 points

    Yes this actually fixes the problem. The version of DebugServer.dll is 4.1.0.837

    Thanks

  • 0 in reply to Angelo Joseph
    TI__Expert 5985 points

    Angelo,

    Glad to hear it.  I'll double check on my end if the software fix is in that version and if it is I'll investigate why it's not working.  In the meantime, if you ever patch your install be sure to re-copy the dll over (or delete it as the fix might be in the next patch).

    Regards,

    Darian

  • 0 in reply to Darian Sale
    TI__Expert 5985 points

    SDSCM00035681 has been filed to track this issue.

    Darian