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.

Problem launching debug configuration

Other Parts Discussed in Thread: CCSTUDIO

I'm trying to use a launch configuration to load two cores of a 6678. This worked until the latest MCSDK release (2.00.07.19). I don't know if that was the cause or maybe it was something else I did. I tried rebuilding in a fresh workspace but it still gets the same error. I'm using CCSv5.5.1.

When I launch the debug configuration an error dialog appears saying that an internal error occurred. Here's the Error Log information. What can I do to fix this?

eclipse.buildId=M20110909-1335
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 -product com.ti.ccstudio.branding.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -product com.ti.ccstudio.branding.product -data C:\Documents and Settings\fbrehm\workspace_v5_1 -product com.ti.ccstudio.branding.product

Error
Tue Apr 03 08:54:24 EDT 2012
An internal error occurred during: "Launching router-stab-release".

java.lang.NullPointerException
    at com.ti.common.project.core.internal.CommonProjectCorePlugin.getDelegateFactory(CommonProjectCorePlugin.java:491)
    at com.ti.common.project.core.internal.CommonProjectCorePlugin.getToolChainPropertyProvider(CommonProjectCorePlugin.java:478)
    at com.ti.common.project.core.util.CTIProjectCoreUtils.getToolChainPropertyProvider(CTIProjectCoreUtils.java:415)
    at com.ti.common.project.core.util.CTIProjectCoreUtils.getConfigurationSettings(CTIProjectCoreUtils.java:975)
    at com.ti.common.project.core.util.CTIProjectCoreUtils.getDependencies(CTIProjectCoreUtils.java:1070)
    at com.ti.common.project.core.util.CTIProjectCoreUtils.getDependencies(CTIProjectCoreUtils.java:1085)
    at com.ti.ccstudio.debug.launch.CCSLaunchDelegate.addReferencedProjects(CCSLaunchDelegate.java:497)
    at com.ti.ccstudio.debug.launch.CCSLaunchDelegate.addReferencedProjects(CCSLaunchDelegate.java:501)
    at com.ti.ccstudio.debug.launch.CCSLaunchDelegate.getAllProjects(CCSLaunchDelegate.java:290)
    at com.ti.ccstudio.debug.launch.CCSLaunchDelegate.getProjectsForProblemSearch(CCSLaunchDelegate.java:281)
    at com.ti.ccstudio.debug.launch.CCSLaunchDelegate.getBuildOrder(CCSLaunchDelegate.java:439)
    at org.eclipse.debug.core.model.LaunchConfigurationDelegate.saveBeforeLaunch(LaunchConfigurationDelegate.java:255)
    at com.ti.ccstudio.debug.launch.CCSLaunchDelegate.preLaunchCheck(CCSLaunchDelegate.java:213)
    at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:809)
    at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
    at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:928)
    at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1132)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

  • Fred,

    Can you attach your target configuration file (.ccxml) here so we can attempt to reproduce the problem? Do you simply right-click on the .ccxml file and try to launch a debug session when it crashes? You may also want to try the troubleshooting tips in this wiki section to see if that helps.

  • Everything works fine if I right-click on the ccxml file and launch a debug session and reset the chips and load the cores all by hand. This process is pretty tedious when loading only two cores. I eventually need to load all 8 cores so I want to use a Debug Configuration to automate this. The Debug Configuration was working fine until recently.

    Run->Debug Configurations...
    Create a new configuration with the ccxml file in the Target Configuration field
    Click on the Program tab
    Define programs for C66xx_0 and C66xx_1
    Click Apply
    Click Debug

    That's when it crashes with the log I sent in the last message.

    I'm attaching the zipped ccxml file that I use. I should be the same as the one in mcsdk_2_00_05_17\tools\program_evm\configs\evm6678l

    Thanks,
    Fred

    8400.evmc6678l_xds100.zip

  • Oh, and I forgot to mention. After setting the ccxml file in the Target Configuration field, deselect cores 2 through 7.

    Fred

  • Fred,

    I don't have a target board handy at the moment to actually try loading executables but I did create a debug configuration following the steps you said and CCS did not crash during launch.

    Did you try deleting the launch configuration and target cache files as described in the wiki page I sent earlier?

    If that did not help, could you please look for other diagnostic log files in addition to the error log you sent earlier? If you can also send any crash dump files, and debug server log (which needs to be explicitly enabled), we can get someone to look into them. This page describes how/where these logs are generated.

  • Attached are the log files. The event details from the Error Log are probably the same.

    Fred

    eclipse.buildId=M20110909-1335
    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

    Error
    Wed Apr 04 17:02:33 EDT 2012
    An internal error occurred during: "Launching router-stab".

    java.lang.NullPointerException
        at com.ti.common.project.core.internal.CommonProjectCorePlugin.getDelegateFactory(CommonProjectCorePlugin.java:491)
        at com.ti.common.project.core.internal.CommonProjectCorePlugin.getToolChainPropertyProvider(CommonProjectCorePlugin.java:478)
        at com.ti.common.project.core.util.CTIProjectCoreUtils.getToolChainPropertyProvider(CTIProjectCoreUtils.java:415)
        at com.ti.common.project.core.util.CTIProjectCoreUtils.getConfigurationSettings(CTIProjectCoreUtils.java:975)
        at com.ti.common.project.core.util.CTIProjectCoreUtils.getDependencies(CTIProjectCoreUtils.java:1070)
        at com.ti.common.project.core.util.CTIProjectCoreUtils.getDependencies(CTIProjectCoreUtils.java:1085)
        at com.ti.ccstudio.debug.launch.CCSLaunchDelegate.addReferencedProjects(CCSLaunchDelegate.java:497)
        at com.ti.ccstudio.debug.launch.CCSLaunchDelegate.addReferencedProjects(CCSLaunchDelegate.java:501)
        at com.ti.ccstudio.debug.launch.CCSLaunchDelegate.getAllProjects(CCSLaunchDelegate.java:290)
        at com.ti.ccstudio.debug.launch.CCSLaunchDelegate.getProjectsForProblemSearch(CCSLaunchDelegate.java:281)
        at com.ti.ccstudio.debug.launch.CCSLaunchDelegate.getBuildOrder(CCSLaunchDelegate.java:439)
        at org.eclipse.debug.core.model.LaunchConfigurationDelegate.saveBeforeLaunch(LaunchConfigurationDelegate.java:255)
        at com.ti.ccstudio.debug.launch.CCSLaunchDelegate.preLaunchCheck(CCSLaunchDelegate.java:213)
        at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:809)
        at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
        at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:928)
        at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1132)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)


    8422.CCSdebug-20120404.zip

  • Fred,

    The exception happens when CCS attempts to build the project before launching a debug-session.  To isolate the problem, try getting your project to build (without launching a debug-session).  Let me know what errors/warnings you see in the Build Console and Problems view.  And send me the complete <workspace>/.metadata/.log file after you try that.

    Thanks,

    - Baltasar

  • Baltasar,

    Attached is a zip file with the .log file, two console outputs (Router0.txt and Server1Stab.txt), and the Error Log events that happened during the compiles (Error Log.txt).

    The console logs do not indicate any errors or warnings. One odd thing about Server1Stab build is that it always performs a relink even though nothing else has changed.

    You will note that I I am using projects to build custom platforms for the two main projects. I followed the directions in this forum thread to get that to work.

        http://e2e.ti.com/support/embedded/bios/f/355/t/176819.aspx#636464

    Thanks,
    Fred

    6013.logs.zip

  • Looks like your projects build OK.  Can you try launching a debug-session now?  If you still see the same error, could you send me your projects so I could try reproducing the problem?

    Thanks,

    - Baltasar

  • It gets the same error.

    I'll have to check what I am allowed to send you from my projects. Do you need everything including source code or just some files like .project?

    Fred

  • Preferably, the entire project, so that I could reproduce the problem.  Or if you could create a smaller test project that reproduces the same problem.

    But before you do that, please give CCSv5.2.0 a try.  Beta2 is already available for download for MSP430 and C6000.  Please try it with a new workspace.

    - Baltasar

  • OK. I'll give the beta version a try.

    Is there a way to install the beta version but keep the current version on the same machine? I share projects with other developers through a source code management system and need to continue using the same version of CCS that they use.

    Fred

  • Yes, you can install multiple CCS versions on the same machine.  Just make sure that you install CCSv5.2.0 into a separate, new directory in the file-system.

    - Baltasar

  • Baltasar,

    CCSv5.2.0beta does not exhibit the problem.

    Do you have an estimate for when it will be released? All developers on the project will have to upgrade at the same time and I don't want to upgrade to a beta version.

    Thanks,
    Fred

  • Fred,

    Thanks for verifying.  CCSv5.2.0 is currently scheduled for release some time in the middle of May.

    - Baltasar