• State Resolved
  • Locked Locked
  • Replies 15 replies
  • Answers 1 answer
  • Subscribers 60 subscribers
  • Views 3636 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.

CCS 6.1.3 upgraded 6.1.2 project, hangs on launch of debug

David79
Intellectual 420 points
Other Parts Discussed in Thread: AM3359, CC2640, TM4C1294NCPDT, CCSTUDIO

Hello,

I have a project for the AM3359 ICE board that was working with CCS 6.1.2.  After upgrading to CCS 6.1.3, the project builds fine but fails to load up debug (F9).  CCS just stops after processing the GEL file.

How do I fix this?

Regards,

-david

  • 0
    TI__Intellectual 2010 points
    David,

    You might try closing CCS and running "<root>\ccsv6\ccs_base\common\bin\fs.exe -a". I typically run this when there is a hang during the launch of a debug session.

    Thanks,
    Mark
  • 0 in reply to Mark Garrett
    TI__Guru**** 173310 points

    David,

    In addition to Mark's suggestion please also take a look at the troubleshooting tips here: 
    http://processors.wiki.ti.com/index.php/Troubleshooting_CCSv6#Debugger

  • 0 in reply to AartiG
    Expert 1950 points
    Hello,

    I faced the same issue, but on a CC26xx platform using an XDS100v3 probe. Tried fs -a and went through the troubleshooting guide, nothing helped. I updated from 6.1.2 as well. Reinstalled from scratch as well, my workspace remained the same though (it was converted though). Target configuration is OK, testing connection to target is successful without any errors, JTAG interface is operational. I also tried to skip the download step by selecting load symbols only and the launch process failed still which indicates that not the actual download step hangs the process. The launch process really hangs, it cannot be cancelled without closing CCS. According to eclipse's installation details view the CC26xx Device Support package is v1.20.0.02 and TI Emulators is 6.0.222.0. Tive/ICDI Debug Probe package is v2.1.1.15350.

    Finally I created an entirely new workspace and started from scratch. Which helped... but was very painful.
  • 0 in reply to Tamas Kleiber
    Mastermind 9055 points

    My situation is a little bit different.

    My workspace for CC2640 is find after upgrading to 6.1.3. But my workspace for DM365 has the same issue as yours. CCS hangs when launching debugger. And thanks for your experience, after recreating the workspace, it works fine now.

  • 0 in reply to Robert Chen
    TI__Guru**** 173310 points

    David, Tamas and Robert,

    Are you all, by any chance, trying to debug a project that had breakpoints set in the debugger when you were working with the older 6.1.2 workspace prior to migration?

    I am able to recreate a situation where CCS 6.1.3 hangs when launching the debugger if I open a CCS 6.1.2 workspace and try to debug a project that previously had multiple breakpoints set. I tried a few other use-cases but in all those instances, the 6.1.3 debugger launched fine even with 6.1.2 workspaces. I'd like to understand if any of your situations is similar.

  • 0 in reply to AartiG
    Intellectual 420 points

    AartiG,

    I'm sure I have breakpoints configured, but I believe none were set.

    I managed to recreate my workspace as follows:

    -- rename original to workspace.old

    -- start CCS613, create new workspace

    -- import projects from workspace.old

    It's clear from a diff that the problem lies in workspace/.metadata/  but I have too many files, some of which are binary, to narrow it down further.

    Let me suggest that TI should adopt the commonly-accepted convention that version numbers mean:  Major.Minor.Patch  and Patch updates are strictly bug fixes, Minor updates may include slight feature enhancements or changes to file formats, only Major updates break compatibility.  

    Regards,

    -david

  • 0 in reply to David79
    TI__Guru**** 173310 points

    David Alessio79 said:
    I'm sure I have breakpoints configured, but I believe none were set.

    David,

    Thank you for clarifying. I can reproduce this with projects that have breakpoints configured (whether they are enabled or not). I will submit a bug report so we can track and fix this issue.

    David Alessio79 said:
    Let me suggest that TI should adopt the commonly-accepted convention that version numbers mean:  Major.Minor.Patch  and Patch updates are strictly bug fixes, Minor updates may include slight feature enhancements or changes to file formats, only Major updates break compatibility.  

    We appreciate the feedback, and I will forward this to the product team. 

    In general, I recommend (and use this myself in practice) creating a new workspace with every new release of CCS. I admit it is inconvenient and definitely not ideal, but greatly reduces the likelihood of the type of issue discussed in this thread.

  • 0 in reply to David79
    Guru 92251 points

    David Alessio79 said:
    It's clear from a diff that the problem lies in workspace/.metadata/  but I have too many files, some of which are binary, to narrow it down further.

    I believe the issue is a difference in how CCS 6.1.1 / 6.1.2 and CCS 6.1.3 persist the breakpoints in binary form. I haven't been able to find which of the files in workspace/.metadata stores the breakpoints, but did come up with a work-around which avoided the need to use a new workspace:

    1) Start with CCS 6.1.1 with a TI-RTOS for TivaC project using a TM4C1294NCPDT with a Stellaris In-Circuit Debug Interface. Set two hardware breakpoints.

    2) Open the existing workspace using CCS 6.1.3. Attempting to start a debug session, which hangs after executing the GEL script. Open the Breakpoints view. There are no breakpoints shown but an Eclipse dialog appears:

    Note the java typecast errors.

    3) Even though no breakpoints are shown, in the breakpoints view right click and select to Remove All Breakpoints.

    4) Start a new debug session, and this time successfully reach main.

    I also noted that if export the breakpoints from CCS 6.1.1 are unable to import the breakpoints into CCS 6.1.3.

    The breakpoints exported from CCS 6.1.1 are:

    <?xml version="1.0" encoding="UTF-8"?>
<breakpoints>
<breakpoint enabled="true" persistant="true" registered="true">
<resource path="/uartecho_EK_TM4C1294XL_TI_TivaTM4C1294NCPDT/uartecho.c" type="1"/>
<marker lineNumber="70" type="com.ti.ccstudio.debug.CCSBreakpointMarker">
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.symbolName" value="echoFxn"/>
<attrib name="org.eclipse.debug.core.id" value="com.ti.ccstudio.debug.debugModel"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.type" value="3"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.filePath" value="C:\Users\Mr_Halfword\workspace_v6_1_3\uartecho_EK_TM4C1294XL_TI_TivaTM4C1294NCPDT\uartecho.c"/>
<attrib name="location" value="C:\Users\Mr_Halfword\workspace_v6_1_3\uartecho_EK_TM4C1294XL_TI_TivaTM4C1294NCPDT\uartecho.c"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.addressPage" value="0"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.address" value="22432"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.addressBitSize" value="32"/>
<attrib name="message" value="echoFxn (0x000057A0)  [H/W BP]"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.threadname" value="Stellaris In-Circuit Debug Interface/CORTEX_M4_0"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.serialData" value="&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;no&quot; ?&gt;&#x0A;&lt;breakpoints xmlns:xsi=&quot;www.w3.org/.../XMLSchema-instance&quot; xsi:noNamespaceSchemaLocation=&quot;breakpoints.xsd&quot;&gt;&#x0A;&#x0A;  &lt;breakpoint type=&quot;AET&quot;&gt;&#x0A;    &lt;property&gt;&#x0A;      &lt;name&gt;Hardware Configuration&lt;/name&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Type&lt;/name&gt;&#x0A;        &lt;string&gt;Breakpoint&lt;/string&gt;&#x0A;        &lt;property&gt;&#x0A;          &lt;name&gt;Location&lt;/name&gt;&#x0A;          &lt;location&gt;&#x0A;            &lt;expression&gt;echoFxn&lt;/expression&gt;&#x0A;            &lt;page&gt;0&lt;/page&gt;&#x0A;          &lt;/location&gt;&#x0A;        &lt;/property&gt;&#x0A;      &lt;/property&gt;&#x0A;    &lt;/property&gt;&#x0A;    &lt;property&gt;&#x0A;      &lt;name&gt;Debugger Response&lt;/name&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Condition&lt;/name&gt;&#x0A;        &lt;string&gt;&lt;/string&gt;&#x0A;      &lt;/property&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Skip Count&lt;/name&gt;&#x0A;        &lt;integer&gt;0&lt;/integer&gt;&#x0A;        &lt;property&gt;&#x0A;          &lt;name&gt;Current Count&lt;/name&gt;&#x0A;          &lt;integer&gt;0&lt;/integer&gt;&#x0A;        &lt;/property&gt;&#x0A;      &lt;/property&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Action&lt;/name&gt;&#x0A;        &lt;string&gt;Remain Halted&lt;/string&gt;&#x0A;      &lt;/property&gt;&#x0A;    &lt;/property&gt;&#x0A;    &lt;property&gt;&#x0A;      &lt;name&gt;Miscellaneous&lt;/name&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Group&lt;/name&gt;&#x0A;        &lt;string&gt;Default Group&lt;/string&gt;&#x0A;      &lt;/property&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Name&lt;/name&gt;&#x0A;        &lt;string&gt;Breakpoint&lt;/string&gt;&#x0A;      &lt;/property&gt;&#x0A;    &lt;/property&gt;&#x0A;    &lt;enabled&gt;1&lt;/enabled&gt;&#x0A;  &lt;/breakpoint&gt;&#x0A;&#x0A;&lt;/breakpoints&gt;&#x0A;"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.lineNumber" value="70"/>
<attrib name="org.eclipse.cdt.debug.core.sourceHandle" value="C:\Users\Mr_Halfword\workspace_v6_1_3\uartecho_EK_TM4C1294XL_TI_TivaTM4C1294NCPDT\uartecho.c"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.hwType" value="1"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.timeStamp" value="1462173654208"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.iconMask" value="7"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.hardware" value="true"/>
<attrib name="org.eclipse.debug.core.enabled" value="true"/>
<attrib name="org.eclipse.cdt.debug.ui.cDebug.capable_of_show_full_paths" value="true"/>
<attrib name="workingset_name" value=""/>
<attrib name="workingset_id" value="org.eclipse.debug.ui.breakpointWorkingSet"/>
</marker>
</breakpoint>
<breakpoint enabled="true" persistant="true" registered="true">
<resource path="/uartecho_EK_TM4C1294XL_TI_TivaTM4C1294NCPDT/uartecho.c" type="1"/>
<marker lineNumber="84" type="com.ti.ccstudio.debug.CCSBreakpointMarker">
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.symbolName" value="$C$L2 + 0xE"/>
<attrib name="org.eclipse.debug.core.id" value="com.ti.ccstudio.debug.debugModel"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.type" value="2"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.filePath" value="C:\Users\Mr_Halfword\workspace_v6_1_3\uartecho_EK_TM4C1294XL_TI_TivaTM4C1294NCPDT\uartecho.c"/>
<attrib name="location" value="C:\Users\Mr_Halfword\workspace_v6_1_3\uartecho_EK_TM4C1294XL_TI_TivaTM4C1294NCPDT\uartecho.c"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.addressPage" value="0"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.address" value="22502"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.addressBitSize" value="32"/>
<attrib name="message" value="uartecho.c, line 84 ($C$L2 + 0xE)  [H/W BP]"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.threadname" value="Stellaris In-Circuit Debug Interface/CORTEX_M4_0"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.serialData" value="&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;no&quot; ?&gt;&#x0A;&lt;breakpoints xmlns:xsi=&quot;www.w3.org/.../XMLSchema-instance&quot; xsi:noNamespaceSchemaLocation=&quot;breakpoints.xsd&quot;&gt;&#x0A;&#x0A;  &lt;breakpoint type=&quot;Software&quot;&gt;&#x0A;    &lt;property&gt;&#x0A;      &lt;name&gt;Hardware Configuration&lt;/name&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Location&lt;/name&gt;&#x0A;        &lt;location&gt;&#x0A;          &lt;source&gt;&#x0A;            &lt;symbol_file&gt;C:/Users\Mr_Halfword\workspace_v6_1_3\uartecho_EK_TM4C1294XL_TI_TivaTM4C1294NCPDT\Debug\uartecho_EK_TM4C1294XL_TI_TivaTM4C1294NCPDT.out&lt;/symbol_file&gt;&#x0A;            &lt;filename&gt;C:\Users\Mr_Halfword\workspace_v6_1_3\uartecho_EK_TM4C1294XL_TI_TivaTM4C1294NCPDT\Debug/../uartecho.c&lt;/filename&gt;&#x0A;            &lt;line&gt;84&lt;/line&gt;&#x0A;          &lt;/source&gt;&#x0A;          &lt;page&gt;0&lt;/page&gt;&#x0A;        &lt;/location&gt;&#x0A;      &lt;/property&gt;&#x0A;    &lt;/property&gt;&#x0A;    &lt;property&gt;&#x0A;      &lt;name&gt;Debugger Response&lt;/name&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Condition&lt;/name&gt;&#x0A;        &lt;string&gt;&lt;/string&gt;&#x0A;      &lt;/property&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Skip Count&lt;/name&gt;&#x0A;        &lt;integer&gt;0&lt;/integer&gt;&#x0A;        &lt;property&gt;&#x0A;          &lt;name&gt;Current Count&lt;/name&gt;&#x0A;          &lt;integer&gt;0&lt;/integer&gt;&#x0A;        &lt;/property&gt;&#x0A;      &lt;/property&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Action&lt;/name&gt;&#x0A;        &lt;string&gt;Remain Halted&lt;/string&gt;&#x0A;      &lt;/property&gt;&#x0A;    &lt;/property&gt;&#x0A;    &lt;property&gt;&#x0A;      &lt;name&gt;Miscellaneous&lt;/name&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Group&lt;/name&gt;&#x0A;        &lt;string&gt;Default Group&lt;/string&gt;&#x0A;      &lt;/property&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Name&lt;/name&gt;&#x0A;        &lt;string&gt;Breakpoint&lt;/string&gt;&#x0A;      &lt;/property&gt;&#x0A;    &lt;/property&gt;&#x0A;    &lt;enabled&gt;1&lt;/enabled&gt;&#x0A;  &lt;/breakpoint&gt;&#x0A;&#x0A;&lt;/breakpoints&gt;&#x0A;"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.lineNumber" value="84"/>
<attrib name="org.eclipse.cdt.debug.core.sourceHandle" value="C:\Users\Mr_Halfword\workspace_v6_1_3\uartecho_EK_TM4C1294XL_TI_TivaTM4C1294NCPDT\uartecho.c"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.hwType" value="1"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.timeStamp" value="1462174597840"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.iconMask" value="7"/>
<attrib name="org.eclipse.debug.core.enabled" value="true"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.hardware" value="true"/>
<attrib name="org.eclipse.cdt.debug.ui.cDebug.capable_of_show_full_paths" value="true"/>
<attrib name="workingset_name" value=""/>
<attrib name="workingset_id" value="org.eclipse.debug.ui.breakpointWorkingSet"/>
</marker>
</breakpoint>
</breakpoints>

    When the same breakpoints were set and exported from CCS 6.1.3:

    <?xml version="1.0" encoding="UTF-8"?>
<breakpoints>
<breakpoint enabled="true" persistant="true" registered="true">
<resource path="/uartecho_EK_TM4C1294XL_TI_TivaTM4C1294NCPDT/uartecho.c" type="1"/>
<marker lineNumber="70" type="com.ti.ccstudio.debug.CCSBreakpointMarker">
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.symbolName" value="echoFxn"/>
<attrib name="org.eclipse.debug.core.id" value="com.ti.ccstudio.debug.debugModel"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.type" value="3"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.filePath" value="C:\Users\Mr_Halfword\workspace_v6_1_3\uartecho_EK_TM4C1294XL_TI_TivaTM4C1294NCPDT\Debug\..\uartecho.c"/>
<attrib name="location" value="C:\Users\Mr_Halfword\workspace_v6_1_3\uartecho_EK_TM4C1294XL_TI_TivaTM4C1294NCPDT\uartecho.c"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.addressPage" value="0"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.address" value="0x000057a0"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.addressBitSize" value="32"/>
<attrib name="message" value="echoFxn (0x000057a0)  [H/W BP]"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.threadname" value="Stellaris In-Circuit Debug Interface/CORTEX_M4_0"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.serialData" value="&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;no&quot; ?&gt;&#x0A;&lt;breakpoints xmlns:xsi=&quot;www.w3.org/.../XMLSchema-instance&quot; xsi:noNamespaceSchemaLocation=&quot;breakpoints.xsd&quot;&gt;&#x0A;&#x0A;  &lt;breakpoint type=&quot;AET&quot;&gt;&#x0A;    &lt;property&gt;&#x0A;      &lt;name&gt;Hardware Configuration&lt;/name&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Type&lt;/name&gt;&#x0A;        &lt;string&gt;Breakpoint&lt;/string&gt;&#x0A;        &lt;property&gt;&#x0A;          &lt;name&gt;Location&lt;/name&gt;&#x0A;          &lt;location&gt;&#x0A;            &lt;expression&gt;echoFxn&lt;/expression&gt;&#x0A;            &lt;page&gt;0&lt;/page&gt;&#x0A;          &lt;/location&gt;&#x0A;        &lt;/property&gt;&#x0A;      &lt;/property&gt;&#x0A;    &lt;/property&gt;&#x0A;    &lt;property&gt;&#x0A;      &lt;name&gt;Debugger Response&lt;/name&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Condition&lt;/name&gt;&#x0A;        &lt;string&gt;&lt;/string&gt;&#x0A;      &lt;/property&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Skip Count&lt;/name&gt;&#x0A;        &lt;integer&gt;0&lt;/integer&gt;&#x0A;        &lt;property&gt;&#x0A;          &lt;name&gt;Current Count&lt;/name&gt;&#x0A;          &lt;integer&gt;0&lt;/integer&gt;&#x0A;        &lt;/property&gt;&#x0A;      &lt;/property&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Action&lt;/name&gt;&#x0A;        &lt;string&gt;Remain Halted&lt;/string&gt;&#x0A;      &lt;/property&gt;&#x0A;    &lt;/property&gt;&#x0A;    &lt;property&gt;&#x0A;      &lt;name&gt;Miscellaneous&lt;/name&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Group&lt;/name&gt;&#x0A;        &lt;string&gt;Default Group&lt;/string&gt;&#x0A;      &lt;/property&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Name&lt;/name&gt;&#x0A;        &lt;string&gt;Breakpoint&lt;/string&gt;&#x0A;      &lt;/property&gt;&#x0A;    &lt;/property&gt;&#x0A;    &lt;enabled&gt;1&lt;/enabled&gt;&#x0A;  &lt;/breakpoint&gt;&#x0A;&#x0A;&lt;/breakpoints&gt;&#x0A;"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.lineNumber" value="70"/>
<attrib name="org.eclipse.cdt.debug.core.sourceHandle" value="C:\Users\Mr_Halfword\workspace_v6_1_3\uartecho_EK_TM4C1294XL_TI_TivaTM4C1294NCPDT\uartecho.c"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.hwType" value="1"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.timeStamp" value="1462177709559"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.iconMask" value="7"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.hardware" value="true"/>
<attrib name="org.eclipse.debug.core.enabled" value="true"/>
<attrib name="org.eclipse.cdt.debug.ui.cDebug.capable_of_show_full_paths" value="true"/>
<attrib name="workingset_name" value=""/>
<attrib name="workingset_id" value="org.eclipse.debug.ui.breakpointWorkingSet"/>
</marker>
</breakpoint>
<breakpoint enabled="true" persistant="true" registered="true">
<resource path="/uartecho_EK_TM4C1294XL_TI_TivaTM4C1294NCPDT/uartecho.c" type="1"/>
<marker lineNumber="84" type="com.ti.ccstudio.debug.CCSBreakpointMarker">
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.symbolName" value="$C$L2 + 0xE"/>
<attrib name="org.eclipse.debug.core.id" value="com.ti.ccstudio.debug.debugModel"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.type" value="2"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.filePath" value="C:\Users\Mr_Halfword\workspace_v6_1_3\uartecho_EK_TM4C1294XL_TI_TivaTM4C1294NCPDT\Debug/../uartecho.c"/>
<attrib name="location" value="C:\Users\Mr_Halfword\workspace_v6_1_3\uartecho_EK_TM4C1294XL_TI_TivaTM4C1294NCPDT\uartecho.c"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.addressPage" value="0"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.address" value="0x000057e6"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.addressBitSize" value="32"/>
<attrib name="message" value="uartecho.c, line 84 ($C$L2 + 0xE)  [H/W BP]"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.threadname" value="Stellaris In-Circuit Debug Interface/CORTEX_M4_0"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.serialData" value="&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;no&quot; ?&gt;&#x0A;&lt;breakpoints xmlns:xsi=&quot;www.w3.org/.../XMLSchema-instance&quot; xsi:noNamespaceSchemaLocation=&quot;breakpoints.xsd&quot;&gt;&#x0A;&#x0A;  &lt;breakpoint type=&quot;Software&quot;&gt;&#x0A;    &lt;property&gt;&#x0A;      &lt;name&gt;Hardware Configuration&lt;/name&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Location&lt;/name&gt;&#x0A;        &lt;location&gt;&#x0A;          &lt;source&gt;&#x0A;            &lt;symbol_file&gt;C:/Users\Mr_Halfword\workspace_v6_1_3\uartecho_EK_TM4C1294XL_TI_TivaTM4C1294NCPDT\Debug\uartecho_EK_TM4C1294XL_TI_TivaTM4C1294NCPDT.out&lt;/symbol_file&gt;&#x0A;            &lt;filename&gt;C:\Users\Mr_Halfword\workspace_v6_1_3\uartecho_EK_TM4C1294XL_TI_TivaTM4C1294NCPDT\Debug/../uartecho.c&lt;/filename&gt;&#x0A;            &lt;line&gt;84&lt;/line&gt;&#x0A;          &lt;/source&gt;&#x0A;          &lt;page&gt;0&lt;/page&gt;&#x0A;        &lt;/location&gt;&#x0A;      &lt;/property&gt;&#x0A;    &lt;/property&gt;&#x0A;    &lt;property&gt;&#x0A;      &lt;name&gt;Debugger Response&lt;/name&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Condition&lt;/name&gt;&#x0A;        &lt;string&gt;&lt;/string&gt;&#x0A;      &lt;/property&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Skip Count&lt;/name&gt;&#x0A;        &lt;integer&gt;0&lt;/integer&gt;&#x0A;        &lt;property&gt;&#x0A;          &lt;name&gt;Current Count&lt;/name&gt;&#x0A;          &lt;integer&gt;0&lt;/integer&gt;&#x0A;        &lt;/property&gt;&#x0A;      &lt;/property&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Action&lt;/name&gt;&#x0A;        &lt;string&gt;Remain Halted&lt;/string&gt;&#x0A;      &lt;/property&gt;&#x0A;    &lt;/property&gt;&#x0A;    &lt;property&gt;&#x0A;      &lt;name&gt;Miscellaneous&lt;/name&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Group&lt;/name&gt;&#x0A;        &lt;string&gt;Default Group&lt;/string&gt;&#x0A;      &lt;/property&gt;&#x0A;      &lt;property&gt;&#x0A;        &lt;name&gt;Name&lt;/name&gt;&#x0A;        &lt;string&gt;Breakpoint&lt;/string&gt;&#x0A;      &lt;/property&gt;&#x0A;    &lt;/property&gt;&#x0A;    &lt;enabled&gt;1&lt;/enabled&gt;&#x0A;  &lt;/breakpoint&gt;&#x0A;&#x0A;&lt;/breakpoints&gt;&#x0A;"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.lineNumber" value="84"/>
<attrib name="org.eclipse.cdt.debug.core.sourceHandle" value="C:\Users\Mr_Halfword\workspace_v6_1_3\uartecho_EK_TM4C1294XL_TI_TivaTM4C1294NCPDT\uartecho.c"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.hwType" value="1"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.timeStamp" value="1462177715602"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.iconMask" value="7"/>
<attrib name="org.eclipse.debug.core.enabled" value="true"/>
<attrib name="com.ti.ccstudio.debug.CCSBreakpointMarker.hardware" value="true"/>
<attrib name="org.eclipse.cdt.debug.ui.cDebug.capable_of_show_full_paths" value="true"/>
<attrib name="workingset_name" value=""/>
<attrib name="workingset_id" value="org.eclipse.debug.ui.breakpointWorkingSet"/>
</marker>
</breakpoint>
</breakpoints>

    CCS 6.1.1 stores the com.ti.ccstudio.debug.CCSBreakpointMarker.address as a decimal string, whereas CCS 6.1.3 uses a hexadecimal string. Not sure if that explains the problem.

  • 0 in reply to AartiG
    Expert 1950 points

    Dear AartiG,


     I had three passive (disabled) breakpoints in my workspace. After removing them, the debugger instance started up without hanging.

    Best regards,

     Tamas

    _

  • 0 in reply to Chester Gillon
    Intellectual 940 points
    Same problems with Hercules Launchpad. Removing breakpoints solve issue. Big tnx to Chester Gillon
  • 0 in reply to Vladimir Romanov
    TI__Guru**** 173310 points
    FYI, the tracking number for this bug is CCDSK-1987.
  • 0 in reply to AartiG
    Guru 24520 points
    Hi
    I am facing the same issue. Does anyone solve this issue?

    Best regards.
    Kaka
  • 0 in reply to Kaka
    TI__Guru**** 173310 points

    Kaka,

    This bug will be fixed in the next release of CCS. In the meantime, the workarounds are to:
    - open a new workspace with CCS 6.1.3 (rather then opening a workspace created for an older version of CCS) 
    - remove breakpoints as described in Chester's earlier post

  • 0 in reply to Chester Gillon
    Intellectual 490 points

    Thank you Gillon, I had same problem with TMS320F28xx chips and it resolved by removing all breakpoints.

    Your answer should be marked as answer to help others quicker.

    With regards,

    MHG

  • 0 in reply to Chester Gillon
    TI__Genius 10951 points
    Thank you. I just had this same problem (debug launch hanging in Code Composer) and clearing all breakpoints solved the problem.