• State Resolved
  • Locked Locked
  • Replies 18 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 7224 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.

Hang-up during debugging an MSP430 in CCS v5.3

peter lagergren
Expert 1015 points
Other Parts Discussed in Thread: MSP430FR5739

I have just installed CCS V5.3 and when I try to restart my debug code I get a frozen and unstoppable debugger with the following error shown:

MSP430: Failed Software Reset: Not supported by selected Interface or Interface is not initialized
MSP430: Trouble Halting Target CPU: Could not terminate EEM polling thread.
MSP430: Trouble Halting Target CPU: Could not terminate EEM polling thread.

Needless to say this has brought progress to a screeching halt.

BR

Peter

  • 0
    TI__Guru*** 130875 points

    Hi Peter,

    we would need more information in order to be able to assist you.

    - what OS and msp430 do you use?

    - do you see this with all projects/workspaces?

    - how are you connecting to the device and what are you trying to do?

    Any details would help.

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Expert 1015 points

    Hi Lisa,

    MSP430FR5739, USB FET, this is a new installation that you pointed me toward and I loaded V5.3, created a new project to make sure the cmd file was correct, imported sort of working code and then built successfully and tried to debug.

    The latest error V5.3 is giving me in debug is:

    Can't find a source file at "/tmp/TI_MKLIBC72W1C/SRC/boot.c" 

    I get a radio button saying "locate file" but I haven't a clue what it is looking for and where it would be.

    BR

    Peter

  • 0 in reply to peter lagergren
    TI__Guru*** 130875 points

    Hi Peter,

    it is looking for the .c file in your project folder.  You can point ccs to it.  Alternatively you can, when in a debug session go Run->Load->Program.

    Please give that a try and keep us informed.

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Expert 1015 points

    Hi Lisa, 

    the project explorer window has all the .c and .h files in it and I copied them into the project instead of pointing to them. What else do I have to do to get ccs to see them?

    BR

    Peter

  • 0 in reply to peter lagergren
    TI__Guru*** 130875 points

    Hi Peter,

    what steps did you take?  How did you "copy" them into the project?

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Expert 1015 points

    Hi Lisa,

    I created a new empty CCS project and diddled all of the settings, like applying GCC extensions etc., compiler dependencies like __CCS__ etc. Then I went to the directory that held all my source files and selected all of them in Project - Add Files and when asked, I selected Copy Files to the workspace which was successful. Then I compiled successfully then I did Run - Debug and everything loaded up, stopped at Main and I hit the green arrow and it was off to the races. The more often I ran the debugger, the more information I get when it halts but still not getting the full dump and sometimes it will run to line, ctrl-R, and sometimes it won't and sometimes it won't and sometimes I get disassembly and sometimes I don't and sometimes I get to stop the debugger and sometimes it doesn't stop at all. Whew.

    BR Peter

  • 0 in reply to Lisa TI
    Expert 1015 points

    Hi Lisa, h

    Each time I stop the debugger and go back to Edit perspective and re-enter debug I get this mesage:

    Error initializing emulator:
    Could not find MSP-FET430UIF on specified COM port

    which is patently untrue since it is still sitting there plugged in so I have to unplug and replug and it loads up code.

    Any ideas what that is?

    Peter

  • 0 in reply to peter lagergren
    TI__Guru*** 130875 points

    Hi Peter,

    these types of problems are not easy to track down.   It seems this isintermittant?  Is this an eval board or your own board?  I ask because one of our best ideas at the moment is that the debugger seems to be hanging at reset.  This might also explain both behaviours you see.  It also means it might be good to isolate hardware vs software.

    Could you please turn on logging and send us the debugger logs?  This might bring us a step closer.

    http://processors.wiki.ti.com/index.php/Troubleshooting_CCS

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Expert 1015 points

    Big Problem:

    I went to turn on the debug error logs and  now the debugger just doesn't see the hardware at all. I get a 

    TI MSP430 USB1/MSP430 (Disconnected : Unknown)

    error message so now I can't download any code. It was working fine until a couple of minutes ago.

    Now what do I do?

    Peter

  • 0 in reply to peter lagergren
    Expert 1015 points

    hi Lisa,

    Here's the log I have just before the USB link went down:

    !SESSION 2012-11-29 13:58:03.642 -----------------------------------------------
eclipse.buildId=I20120608-1200
java.version=1.6.0_13
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_CA
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.ui 2 0 2012-11-29 13:58:08.414
!MESSAGE Warnings while parsing the viewer contributions from the 'org.eclipse.ui.popupMenus' extension point
!SUBENTRY 1 org.eclipse.ui 2 0 2012-11-29 13:58:08.414
!MESSAGE invalid keybinding: Cannot bind to an incomplete key sequence: plug-in='org.eclipse.cdt.debug.ui', id='AUTOGEN:::org.eclipse.cdt.debug.ui.CEditorRulerActions/org.eclipse.cdt.debug.internal.ui.actions.CBreakpointPropertiesRulerActionDelegate'
!SUBENTRY 1 org.eclipse.ui 2 0 2012-11-29 13:58:08.414
!MESSAGE invalid keybinding: Cannot bind to an incomplete key sequence: plug-in='org.eclipse.cdt.debug.ui', id='AUTOGEN:::org.eclipse.cdt.debug.ui.CEditorRulerActions/org.eclipse.cdt.debug.internal.ui.actions.EnableDisableBreakpointRulerActionDelegate'
!SUBENTRY 1 org.eclipse.ui 2 0 2012-11-29 13:58:08.414
!MESSAGE invalid keybinding: Cannot bind to an incomplete key sequence: plug-in='org.eclipse.cdt.debug.ui', id='AUTOGEN:::org.eclipse.cdt.debug.ui.CEditorRulerActions/org.eclipse.cdt.debug.ui.actions.RulerCreateBreakpointInteractiveAction'
!SUBENTRY 1 org.eclipse.ui 2 0 2012-11-29 13:58:08.414
!MESSAGE invalid keybinding: Cannot bind to an incomplete key sequence: plug-in='org.eclipse.cdt.debug.ui', id='AUTOGEN:::org.eclipse.cdt.debug.ui.AsmEditorRulerActions/org.eclipse.cdt.debug.internal.ui.actions.asm.CBreakpointPropertiesRulerActionDelegate'
!SUBENTRY 1 org.eclipse.ui 2 0 2012-11-29 13:58:08.414
!MESSAGE invalid keybinding: Cannot bind to an incomplete key sequence: plug-in='org.eclipse.cdt.debug.ui', id='AUTOGEN:::org.eclipse.cdt.debug.ui.AsmEditorRulerActions/org.eclipse.cdt.debug.internal.ui.actions.asm.EnableDisableBreakpointRulerActionDelegate'
!SUBENTRY 1 org.eclipse.ui 2 0 2012-11-29 13:58:08.414
!MESSAGE invalid keybinding: Cannot bind to an incomplete key sequence: plug-in='org.eclipse.cdt.debug.ui', id='AUTOGEN:::org.eclipse.cdt.debug.ui.AsmEditorRulerActions/org.eclipse.cdt.debug.ui.actions.asm.RulerCreateBreakpointInteractiveAction'
!SUBENTRY 1 org.eclipse.ui 2 0 2012-11-29 13:58:08.414
!MESSAGE invalid keybinding: Cannot bind to an incomplete key sequence: plug-in='org.eclipse.cdt.dsf.ui', id='AUTOGEN:::org.eclipse.cdt.dsf.debug.ui.disassemblyRulerActions/org.eclipse.debug.ui.actions.RulerAddBreakpointAction'
!SUBENTRY 1 org.eclipse.ui 2 0 2012-11-29 13:58:08.414
!MESSAGE invalid keybinding: Cannot bind to an incomplete key sequence: plug-in='org.eclipse.cdt.dsf.ui', id='org.eclipse.cdt.dsf.debug.ui.disassembly.commands.rulerToggleBreakpoint'

!ENTRY org.eclipse.cdt.core 1 0 2012-11-29 13:59:00.182
!MESSAGE Indexed 'COSMB' (15 sources, 36 headers) in 2.04 sec: 2,426 declarations; 5,535 references; 0 unresolved inclusions; 0 syntax errors; 9 unresolved names (0.11%)

!ENTRY org.eclipse.osgi 2 1 2012-11-29 13:59:11.329
!MESSAGE NLS unused message: Checking in: com.ti.ccstudio.project.ui.internal.messages

!ENTRY org.eclipse.ui 4 4 2012-11-29 14:13:13.530
!MESSAGE The proxied handler was the wrong class

!ENTRY org.eclipse.ui 4 0 2012-11-29 14:13:13.530
!MESSAGE The proxied handler was the wrong class
!STACK 0
java.lang.ClassCastException: com.ti.ccstudio.gui.composer.internal.ui.commands.ApplicationViewerHandler cannot be cast to org.eclipse.core.commands.IHandler
	at org.eclipse.ui.internal.handlers.HandlerProxy.loadHandler(HandlerProxy.java:350)
	at org.eclipse.ui.internal.handlers.HandlerProxy.isEnabled(HandlerProxy.java:319)
	at org.eclipse.core.commands.Command.isEnabled(Command.java:862)
	at org.eclipse.core.commands.Command.setHandler(Command.java:994)
	at org.eclipse.ui.internal.handlers.HandlerAuthority.updateCommand(HandlerAuthority.java:457)
	at org.eclipse.ui.internal.handlers.HandlerAuthority.deactivateHandler(HandlerAuthority.java:312)
	at org.eclipse.ui.internal.handlers.HandlerService.deactivateHandler(HandlerService.java:148)
	at org.eclipse.ui.internal.handlers.HandlerService.deactivateHandlers(HandlerService.java:157)
	at org.eclipse.ui.internal.handlers.HandlerPersistence.clearActivations(HandlerPersistence.java:104)
	at org.eclipse.ui.internal.handlers.HandlerPersistence.dispose(HandlerPersistence.java:125)
	at org.eclipse.ui.internal.handlers.HandlerService.dispose(HandlerService.java:163)
	at org.eclipse.ui.internal.services.ServiceLocator.dispose(ServiceLocator.java:142)
	at org.eclipse.ui.internal.Workbench.shutdown(Workbench.java:3057)
	at org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:1123)
	at org.eclipse.ui.internal.Workbench.access$15(Workbench.java:1040)
	at org.eclipse.ui.internal.Workbench$25.run(Workbench.java:1284)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
	at org.eclipse.ui.internal.Workbench.close(Workbench.java:1282)
	at org.eclipse.ui.internal.Workbench.close(Workbench.java:1254)
	at org.eclipse.ui.internal.WorkbenchWindow.busyClose(WorkbenchWindow.java:727)
	at org.eclipse.ui.internal.WorkbenchWindow.access$0(WorkbenchWindow.java:715)
	at org.eclipse.ui.internal.WorkbenchWindow$6.run(WorkbenchWindow.java:867)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
	at org.eclipse.ui.internal.WorkbenchWindow.close(WorkbenchWindow.java:865)
	at org.eclipse.jface.window.Window.handleShellCloseEvent(Window.java:741)
	at org.eclipse.jface.window.Window$3.shellClosed(Window.java:687)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:98)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062)
	at org.eclipse.swt.widgets.Decorations.closeWidget(Decorations.java:309)
	at org.eclipse.swt.widgets.Decorations.WM_CLOSE(Decorations.java:1694)
	at org.eclipse.swt.widgets.Control.windowProc(Control.java:4530)
	at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341)
	at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1627)
	at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2069)
	at org.eclipse.swt.widgets.Display.windowProc(Display.java:4976)
	at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
	at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2541)
	at org.eclipse.swt.widgets.Shell.callWindowProc(Shell.java:498)
	at org.eclipse.swt.widgets.Control.windowProc(Control.java:4623)
	at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341)
	at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1627)
	at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2069)
	at org.eclipse.swt.widgets.Display.windowProc(Display.java:4976)
	at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method)
	at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2541)
	at org.eclipse.swt.widgets.Shell.callWindowProc(Shell.java:498)
	at org.eclipse.swt.widgets.Control.windowProc(Control.java:4623)
	at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341)
	at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1627)
	at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2069)
	at org.eclipse.swt.widgets.Display.windowProc(Display.java:4976)
	at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
	at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2546)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3756)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
	at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
	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)
!SESSION 2012-11-29 15:16:20.400 -----------------------------------------------
eclipse.buildId=I20120608-1200
java.version=1.6.0_13
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_CA
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.ui 2 0 2012-11-29 15:16:25.390
!MESSAGE Warnings while parsing the viewer contributions from the 'org.eclipse.ui.popupMenus' extension point
!SUBENTRY 1 org.eclipse.ui 2 0 2012-11-29 15:16:25.390
!MESSAGE invalid keybinding: Cannot bind to an incomplete key sequence: plug-in='org.eclipse.cdt.debug.ui', id='AUTOGEN:::org.eclipse.cdt.debug.ui.CEditorRulerActions/org.eclipse.cdt.debug.internal.ui.actions.CBreakpointPropertiesRulerActionDelegate'
!SUBENTRY 1 org.eclipse.ui 2 0 2012-11-29 15:16:25.390
!MESSAGE invalid keybinding: Cannot bind to an incomplete key sequence: plug-in='org.eclipse.cdt.debug.ui', id='AUTOGEN:::org.eclipse.cdt.debug.ui.CEditorRulerActions/org.eclipse.cdt.debug.internal.ui.actions.EnableDisableBreakpointRulerActionDelegate'
!SUBENTRY 1 org.eclipse.ui 2 0 2012-11-29 15:16:25.390
!MESSAGE invalid keybinding: Cannot bind to an incomplete key sequence: plug-in='org.eclipse.cdt.debug.ui', id='AUTOGEN:::org.eclipse.cdt.debug.ui.CEditorRulerActions/org.eclipse.cdt.debug.ui.actions.RulerCreateBreakpointInteractiveAction'
!SUBENTRY 1 org.eclipse.ui 2 0 2012-11-29 15:16:25.391
!MESSAGE invalid keybinding: Cannot bind to an incomplete key sequence: plug-in='org.eclipse.cdt.debug.ui', id='AUTOGEN:::org.eclipse.cdt.debug.ui.AsmEditorRulerActions/org.eclipse.cdt.debug.internal.ui.actions.asm.CBreakpointPropertiesRulerActionDelegate'
!SUBENTRY 1 org.eclipse.ui 2 0 2012-11-29 15:16:25.391
!MESSAGE invalid keybinding: Cannot bind to an incomplete key sequence: plug-in='org.eclipse.cdt.debug.ui', id='AUTOGEN:::org.eclipse.cdt.debug.ui.AsmEditorRulerActions/org.eclipse.cdt.debug.internal.ui.actions.asm.EnableDisableBreakpointRulerActionDelegate'
!SUBENTRY 1 org.eclipse.ui 2 0 2012-11-29 15:16:25.391
!MESSAGE invalid keybinding: Cannot bind to an incomplete key sequence: plug-in='org.eclipse.cdt.debug.ui', id='AUTOGEN:::org.eclipse.cdt.debug.ui.AsmEditorRulerActions/org.eclipse.cdt.debug.ui.actions.asm.RulerCreateBreakpointInteractiveAction'
!SUBENTRY 1 org.eclipse.ui 2 0 2012-11-29 15:16:25.391
!MESSAGE invalid keybinding: Cannot bind to an incomplete key sequence: plug-in='org.eclipse.cdt.dsf.ui', id='AUTOGEN:::org.eclipse.cdt.dsf.debug.ui.disassemblyRulerActions/org.eclipse.debug.ui.actions.RulerAddBreakpointAction'
!SUBENTRY 1 org.eclipse.ui 2 0 2012-11-29 15:16:25.391
!MESSAGE invalid keybinding: Cannot bind to an incomplete key sequence: plug-in='org.eclipse.cdt.dsf.ui', id='org.eclipse.cdt.dsf.debug.ui.disassembly.commands.rulerToggleBreakpoint'

!ENTRY org.eclipse.osgi 2 1 2012-11-29 15:21:30.617
!MESSAGE NLS unused message: Checking in: com.ti.ccstudio.project.ui.internal.messages

!ENTRY org.eclipse.ui 4 0 2012-11-29 18:23:04.201
!MESSAGE Problems opening perspective 'com.ti.ccstudio.TICPerspective'
  • 0 in reply to peter lagergren
    Expert 1015 points

    Big Problem solved:

    Turns out that somewhere along the line in bringing up v5.3 the selection of refreshing the USB setup on each debugger launch got deselected. Now that takes a while to figure out....

  • 0 in reply to peter lagergren
    TI__Guru*** 130875 points

    Hi Peter,

    very very happy to hear you managed to track down the problem.  Thanks for the update and all the best with development.

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Expert 1015 points

    Hi Lisa,

    Unfortunately this just got me back to the original problem which is that this error always surfaces:

    Can't find a source file at "/tmp/TI_MKLIBC72W1C/SRC/boot.c"
    Locate the file or edit the source lookup path to include its location.

    Got any ideas?

    Peter

  • 0 in reply to peter lagergren
    TI__Guru*** 130875 points

    Hi Peter,

    have you searched to see if/where boot.c is?  Have you tried pointing ccs to it?  Without knowing more I would suggest this file is likely being included in some library/header file/etc somewhere within the project.  Have you tried Run->Load->Program when in debug mode?

    Best Regards,
    lisa

  • 0 in reply to Lisa TI
    Expert 1015 points

    Hi Lisa,

    No luck on the Run>Load>Program all I get is Load>Verify Program and the Verify Program is grayed out.

    One thing I am sure of is that for whatever reason my program is jumping into lala land and the debugger takes forever to get back when I hit the Terminate button. when I hit the Halt button I lose control and after a while of doing nothing the debugger returns to where the entire perspective isn't grayed out and the Terminate button is available.

    As far as finding boot.c it is nowhere to be found nor is /tmp/anything.

    I'm confused.

    BR

    Peter

  • 0 in reply to peter lagergren
    Expert 1015 points

    What I see when the debugger loses control is:

    MSP430: Trouble Halting Target CPU: Could not terminate EEM polling thread.

    Any thoughts?

    Peter

  • 0 in reply to peter lagergren
    Expert 1015 points

    Hi Lisa,

    Mystery is unraveling. The program I wrote had an error - there was an uninitialized string array that when I did a strcat operation exceeded the boundaries of the array and the mcu choked and jumped out of the address range of the mcu.

    Once I fixed that the debugger started behaving normally. Weird reaction and no diagnostic help at all from the debugger.

    Peter

  • 0 in reply to peter lagergren
    TI__Guru*** 130875 points

    Hi Peter,

    ok, very happy to hear you seem to have it solved.  All the best with development.  I will close off your new post as well.

    Best Regards,
    Lisa