!SESSION 2019-12-11 15:08:27.089 -----------------------------------------------
eclipse.buildId=4.7.3.M20180301-0715
java.version=1.8.0_112
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ko_KR
Framework arguments:  -product com.ti.ccstudio.branding.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -product com.ti.ccstudio.branding.product

This is a continuation of log file D:\work\PUMP\PUMP_V2\1129_CCS8.0\.metadata\.bak_0.log
Created Time: 2019-12-11 15:12:28.580

!ENTRY org.eclipse.ui 4 4 2019-12-11 15:12:28.581
!MESSAGE To avoid deadlock while executing Display.syncExec() with argument: com.ti.ccstudio.debug.internal.ui.CCSDebugUIDelegate$1@19f5185, thread Worker-5 will interrupt UI thread.
!SUBENTRY 1 org.eclipse.ui 4 4 2019-12-11 15:12:28.581
!MESSAGE Worker-5 thread is an instance of Worker or owns an ILock
!STACK 0
java.lang.IllegalStateException: Call stack for thread Worker-5
	at sun.management.ThreadImpl.dumpThreads0(Native Method)
	at sun.management.ThreadImpl.getThreadInfo(ThreadImpl.java:448)
	at org.eclipse.ui.internal.UILockListener.reportInterruption(UILockListener.java:206)
	at org.eclipse.ui.internal.UILockListener.interruptUI(UILockListener.java:176)
	at org.eclipse.ui.internal.PendingSyncExec.waitUntilExecuted(PendingSyncExec.java:82)
	at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:153)
	at org.eclipse.swt.widgets.Display.syncExec(Display.java:4889)
	at com.ti.ccstudio.debug.internal.ui.CCSDebugUIDelegate.openYesNoQuestion(CCSDebugUIDelegate.java:99)
	at com.ti.ccstudio.debug.internal.ui.program.load.options.ProgramFileChangeManager.resourceChanged(ProgramFileChangeManager.java:250)
	at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:299)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:289)
	at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:152)
	at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:374)
	at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1469)
	at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:46)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
!SUBENTRY 1 org.eclipse.ui 4 4 2019-12-11 15:12:28.582
!MESSAGE UI thread waiting on a job or lock.
!STACK 0
java.lang.IllegalStateException: Call stack for thread main
	at org.eclipse.swt.internal.win32.OS.WaitMessage(Native Method)
	at org.eclipse.swt.widgets.Display.sleep(Display.java:4856)
	at org.eclipse.jface.window.Window.runEventLoop(Window.java:819)
	at org.eclipse.jface.window.Window.open(Window.java:794)
	at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:396)
	at org.eclipse.jface.dialogs.MessageDialogWithToggle.open(MessageDialogWithToggle.java:119)
	at org.eclipse.jface.dialogs.MessageDialogWithToggle.openYesNoQuestion(MessageDialogWithToggle.java:365)
	at com.ti.ccstudio.debug.internal.ui.CCSDebugUIDelegate$1.run(CCSDebugUIDelegate.java:101)
	at org.eclipse.ui.internal.PendingSyncExec.run(PendingSyncExec.java:58)
	at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:168)
	at org.eclipse.ui.internal.UISynchronizer.lambda$0(UISynchronizer.java:150)
	at org.eclipse.ui.internal.UISynchronizer$$Lambda$346/17993769.run(Unknown Source)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4213)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3820)
	at org.eclipse.ui.internal.dialogs.EventLoopProgressMonitor.runEventLoop(EventLoopProgressMonitor.java:125)
	at org.eclipse.ui.internal.dialogs.EventLoopProgressMonitor.isCanceled(EventLoopProgressMonitor.java:99)
	at org.eclipse.core.internal.jobs.ThreadJob.isCanceled(ThreadJob.java:144)
	at org.eclipse.core.internal.jobs.ThreadJob.waitForRun(ThreadJob.java:273)
	at org.eclipse.core.internal.jobs.ThreadJob.joinRun(ThreadJob.java:202)
	at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:92)
	at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:308)
	at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:121)
	at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:2188)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2235)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2262)
	at com.ti.ccstudio.debug.internal.breakpoint.CCSBreakpoint.run(CCSBreakpoint.java:254)
	at com.ti.ccstudio.debug.internal.breakpoint.CCSBreakpoint.<init>(CCSBreakpoint.java:240)
	at com.ti.ccstudio.debug.internal.breakpoint.CCSBreakpoint.<init>(CCSBreakpoint.java:105)
	at com.ti.ccstudio.debug.internal.ui.breakpoint.togglers.EditorToggleBreakpointsTarget.insertBreakpoint(EditorToggleBreakpointsTarget.java:156)
	at com.ti.ccstudio.debug.internal.ui.breakpoint.togglers.EditorToggleBreakpointsTarget.toggleLineBreakpoints(EditorToggleBreakpointsTarget.java:72)
	at com.ti.ccstudio.debug.internal.ui.breakpoint.togglers.EditorToggleBreakpointsTarget.toggleBreakpoints(EditorToggleBreakpointsTarget.java:60)
	at org.eclipse.debug.internal.ui.actions.breakpoints.RetargetToggleBreakpointAction.performAction(RetargetToggleBreakpointAction.java:34)
	at org.eclipse.debug.internal.ui.actions.RetargetAction.run(RetargetAction.java:110)
	at org.eclipse.debug.internal.ui.actions.RetargetAction.runWithEvent(RetargetAction.java:274)
	at org.eclipse.ui.internal.handlers.ActionDelegateHandlerProxy.execute(ActionDelegateHandlerProxy.java:288)
	at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:92)
	at sun.reflect.GeneratedMethodAccessor105.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:305)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:239)
	at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
	at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
	at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
	at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487)
	at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.executeCommand(KeyBindingDispatcher.java:287)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.press(KeyBindingDispatcher.java:527)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.processKeyEvent(KeyBindingDispatcher.java:577)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.filterKeySequenceBindings(KeyBindingDispatcher.java:385)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.access$0(KeyBindingDispatcher.java:331)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher$KeyDownFilter.handleEvent(KeyBindingDispatcher.java:88)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
	at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1271)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1078)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1103)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1088)
	at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1130)
	at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1126)
	at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1547)
	at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4962)
	at org.eclipse.swt.widgets.Canvas.WM_CHAR(Canvas.java:364)
	at org.eclipse.swt.widgets.Control.windowProc(Control.java:4843)
	at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:359)
	at org.eclipse.swt.widgets.Display.windowProc(Display.java:5178)
	at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
	at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2560)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3815)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
	at org.eclipse.ui.internal.Workbench$$Lambda$65/6485000.run(Unknown Source)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1499)

!ENTRY org.eclipse.ui 4 4 2019-12-11 15:12:29.663
!MESSAGE To avoid deadlock while executing Display.syncExec() with argument: com.ti.ccstudio.debug.internal.ui.CCSDebugUIDelegate$1@19f5185, thread Worker-5 will interrupt UI thread.
!SUBENTRY 1 org.eclipse.ui 4 4 2019-12-11 15:12:29.663
!MESSAGE Worker-5 thread is an instance of Worker or owns an ILock
!STACK 0
java.lang.IllegalStateException: Call stack for thread Worker-5
	at sun.management.ThreadImpl.dumpThreads0(Native Method)
	at sun.management.ThreadImpl.getThreadInfo(ThreadImpl.java:448)
	at org.eclipse.ui.internal.UILockListener.reportInterruption(UILockListener.java:206)
	at org.eclipse.ui.internal.UILockListener.interruptUI(UILockListener.java:176)
	at org.eclipse.ui.internal.PendingSyncExec.waitUntilExecuted(PendingSyncExec.java:82)
	at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:153)
	at org.eclipse.swt.widgets.Display.syncExec(Display.java:4889)
	at com.ti.ccstudio.debug.internal.ui.CCSDebugUIDelegate.openYesNoQuestion(CCSDebugUIDelegate.java:99)
	at com.ti.ccstudio.debug.internal.ui.program.load.options.ProgramFileChangeManager.resourceChanged(ProgramFileChangeManager.java:250)
	at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:299)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:289)
	at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:152)
	at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:374)
	at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1469)
	at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:46)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
!SUBENTRY 1 org.eclipse.ui 4 4 2019-12-11 15:12:29.663
!MESSAGE UI thread waiting on a job or lock.
!STACK 0
java.lang.IllegalStateException: Call stack for thread main
	at org.eclipse.swt.internal.win32.OS.WaitMessage(Native Method)
	at org.eclipse.swt.widgets.Display.sleep(Display.java:4856)
	at org.eclipse.jface.window.Window.runEventLoop(Window.java:819)
	at org.eclipse.jface.window.Window.open(Window.java:794)
	at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:396)
	at org.eclipse.jface.dialogs.MessageDialogWithToggle.open(MessageDialogWithToggle.java:119)
	at org.eclipse.jface.dialogs.MessageDialogWithToggle.openYesNoQuestion(MessageDialogWithToggle.java:365)
	at com.ti.ccstudio.debug.internal.ui.CCSDebugUIDelegate$1.run(CCSDebugUIDelegate.java:101)
	at org.eclipse.ui.internal.PendingSyncExec.run(PendingSyncExec.java:58)
	at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:168)
	at org.eclipse.ui.internal.UISynchronizer.lambda$0(UISynchronizer.java:150)
	at org.eclipse.ui.internal.UISynchronizer$$Lambda$346/17993769.run(Unknown Source)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4213)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3820)
	at org.eclipse.ui.internal.dialogs.EventLoopProgressMonitor.runEventLoop(EventLoopProgressMonitor.java:125)
	at org.eclipse.ui.internal.dialogs.EventLoopProgressMonitor.isCanceled(EventLoopProgressMonitor.java:99)
	at org.eclipse.core.internal.jobs.ThreadJob.isCanceled(ThreadJob.java:144)
	at org.eclipse.core.internal.jobs.ThreadJob.waitForRun(ThreadJob.java:273)
	at org.eclipse.core.internal.jobs.ThreadJob.joinRun(ThreadJob.java:202)
	at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:92)
	at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:308)
	at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:121)
	at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:2188)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2235)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2262)
	at com.ti.ccstudio.debug.internal.breakpoint.CCSBreakpoint.run(CCSBreakpoint.java:254)
	at com.ti.ccstudio.debug.internal.breakpoint.CCSBreakpoint.<init>(CCSBreakpoint.java:240)
	at com.ti.ccstudio.debug.internal.breakpoint.CCSBreakpoint.<init>(CCSBreakpoint.java:105)
	at com.ti.ccstudio.debug.internal.ui.breakpoint.togglers.EditorToggleBreakpointsTarget.insertBreakpoint(EditorToggleBreakpointsTarget.java:156)
	at com.ti.ccstudio.debug.internal.ui.breakpoint.togglers.EditorToggleBreakpointsTarget.toggleLineBreakpoints(EditorToggleBreakpointsTarget.java:72)
	at com.ti.ccstudio.debug.internal.ui.breakpoint.togglers.EditorToggleBreakpointsTarget.toggleBreakpoints(EditorToggleBreakpointsTarget.java:60)
	at org.eclipse.debug.internal.ui.actions.breakpoints.RetargetToggleBreakpointAction.performAction(RetargetToggleBreakpointAction.java:34)
	at org.eclipse.debug.internal.ui.actions.RetargetAction.run(RetargetAction.java:110)
	at org.eclipse.debug.internal.ui.actions.RetargetAction.runWithEvent(RetargetAction.java:274)
	at org.eclipse.ui.internal.handlers.ActionDelegateHandlerProxy.execute(ActionDelegateHandlerProxy.java:288)
	at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:92)
	at sun.reflect.GeneratedMethodAccessor105.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:305)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:239)
	at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
	at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
	at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
	at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487)
	at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.executeCommand(KeyBindingDispatcher.java:287)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.press(KeyBindingDispatcher.java:527)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.processKeyEvent(KeyBindingDispatcher.java:577)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.filterKeySequenceBindings(KeyBindingDispatcher.java:385)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.access$0(KeyBindingDispatcher.java:331)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher$KeyDownFilter.handleEvent(KeyBindingDispatcher.java:88)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
	at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1271)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1078)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1103)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1088)
	at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1130)
	at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1126)
	at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1547)
	at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4962)
	at org.eclipse.swt.widgets.Canvas.WM_CHAR(Canvas.java:364)
	at org.eclipse.swt.widgets.Control.windowProc(Control.java:4843)
	at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:359)
	at org.eclipse.swt.widgets.Display.windowProc(Display.java:5178)
	at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
	at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2560)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3815)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
	at org.eclipse.ui.internal.Workbench$$Lambda$65/6485000.run(Unknown Source)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1499)

!ENTRY org.eclipse.ui 4 4 2019-12-11 15:12:30.731
!MESSAGE To avoid deadlock while executing Display.syncExec() with argument: com.ti.ccstudio.debug.internal.ui.CCSDebugUIDelegate$1@19f5185, thread Worker-5 will interrupt UI thread.
!SUBENTRY 1 org.eclipse.ui 4 4 2019-12-11 15:12:30.731
!MESSAGE Worker-5 thread is an instance of Worker or owns an ILock
!STACK 0
java.lang.IllegalStateException: Call stack for thread Worker-5
	at sun.management.ThreadImpl.dumpThreads0(Native Method)
	at sun.management.ThreadImpl.getThreadInfo(ThreadImpl.java:448)
	at org.eclipse.ui.internal.UILockListener.reportInterruption(UILockListener.java:206)
	at org.eclipse.ui.internal.UILockListener.interruptUI(UILockListener.java:176)
	at org.eclipse.ui.internal.PendingSyncExec.waitUntilExecuted(PendingSyncExec.java:82)
	at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:153)
	at org.eclipse.swt.widgets.Display.syncExec(Display.java:4889)
	at com.ti.ccstudio.debug.internal.ui.CCSDebugUIDelegate.openYesNoQuestion(CCSDebugUIDelegate.java:99)
	at com.ti.ccstudio.debug.internal.ui.program.load.options.ProgramFileChangeManager.resourceChanged(ProgramFileChangeManager.java:250)
	at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:299)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:289)
	at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:152)
	at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:374)
	at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1469)
	at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:46)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
!SUBENTRY 1 org.eclipse.ui 4 4 2019-12-11 15:12:30.731
!MESSAGE UI thread waiting on a job or lock.
!STACK 0
java.lang.IllegalStateException: Call stack for thread main
	at org.eclipse.swt.internal.win32.OS.WaitMessage(Native Method)
	at org.eclipse.swt.widgets.Display.sleep(Display.java:4856)
	at org.eclipse.jface.window.Window.runEventLoop(Window.java:819)
	at org.eclipse.jface.window.Window.open(Window.java:794)
	at org.eclipse.jface.dialogs.MessageDialog.open(MessageDialog.java:396)
	at org.eclipse.jface.dialogs.MessageDialogWithToggle.open(MessageDialogWithToggle.java:119)
	at org.eclipse.jface.dialogs.MessageDialogWithToggle.openYesNoQuestion(MessageDialogWithToggle.java:365)
	at com.ti.ccstudio.debug.internal.ui.CCSDebugUIDelegate$1.run(CCSDebugUIDelegate.java:101)
	at org.eclipse.ui.internal.PendingSyncExec.run(PendingSyncExec.java:58)
	at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:168)
	at org.eclipse.ui.internal.UISynchronizer.lambda$0(UISynchronizer.java:150)
	at org.eclipse.ui.internal.UISynchronizer$$Lambda$346/17993769.run(Unknown Source)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4213)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3820)
	at org.eclipse.ui.internal.dialogs.EventLoopProgressMonitor.runEventLoop(EventLoopProgressMonitor.java:125)
	at org.eclipse.ui.internal.dialogs.EventLoopProgressMonitor.isCanceled(EventLoopProgressMonitor.java:99)
	at org.eclipse.core.internal.jobs.ThreadJob.isCanceled(ThreadJob.java:144)
	at org.eclipse.core.internal.jobs.ThreadJob.waitForRun(ThreadJob.java:273)
	at org.eclipse.core.internal.jobs.ThreadJob.joinRun(ThreadJob.java:202)
	at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:92)
	at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:308)
	at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:121)
	at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:2188)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2235)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2262)
	at com.ti.ccstudio.debug.internal.breakpoint.CCSBreakpoint.run(CCSBreakpoint.java:254)
	at com.ti.ccstudio.debug.internal.breakpoint.CCSBreakpoint.<init>(CCSBreakpoint.java:240)
	at com.ti.ccstudio.debug.internal.breakpoint.CCSBreakpoint.<init>(CCSBreakpoint.java:105)
	at com.ti.ccstudio.debug.internal.ui.breakpoint.togglers.EditorToggleBreakpointsTarget.insertBreakpoint(EditorToggleBreakpointsTarget.java:156)
	at com.ti.ccstudio.debug.internal.ui.breakpoint.togglers.EditorToggleBreakpointsTarget.toggleLineBreakpoints(EditorToggleBreakpointsTarget.java:72)
	at com.ti.ccstudio.debug.internal.ui.breakpoint.togglers.EditorToggleBreakpointsTarget.toggleBreakpoints(EditorToggleBreakpointsTarget.java:60)
	at org.eclipse.debug.internal.ui.actions.breakpoints.RetargetToggleBreakpointAction.performAction(RetargetToggleBreakpointAction.java:34)
	at org.eclipse.debug.internal.ui.actions.RetargetAction.run(RetargetAction.java:110)
	at org.eclipse.debug.internal.ui.actions.RetargetAction.runWithEvent(RetargetAction.java:274)
	at org.eclipse.ui.internal.handlers.ActionDelegateHandlerProxy.execute(ActionDelegateHandlerProxy.java:288)
	at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:92)
	at sun.reflect.GeneratedMethodAccessor105.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:305)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:239)
	at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
	at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
	at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
	at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487)
	at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.executeCommand(KeyBindingDispatcher.java:287)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.press(KeyBindingDispatcher.java:527)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.processKeyEvent(KeyBindingDispatcher.java:577)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.filterKeySequenceBindings(KeyBindingDispatcher.java:385)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.access$0(KeyBindingDispatcher.java:331)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher$KeyDownFilter.handleEvent(KeyBindingDispatcher.java:88)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
	at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1271)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1078)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1103)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1088)
	at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1130)
	at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1126)
	at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1547)
	at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4962)
	at org.eclipse.swt.widgets.Canvas.WM_CHAR(Canvas.java:364)
	at org.eclipse.swt.widgets.Control.windowProc(Control.java:4843)
	at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:359)
	at org.eclipse.swt.widgets.Display.windowProc(Display.java:5178)
	at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
	at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2560)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3815)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
	at org.eclipse.ui.internal.Workbench$$Lambda$65/6485000.run(Unknown Source)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1499)

!ENTRY com.ti.ccstudio.debug 1 0 2019-12-11 15:19:51.248
!MESSAGE DS_ERROR: TMS320C671X: Can't Run Target CPU: Error 0x80000020/-1060 Fatal Error during: Execution,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-11 15:19:51.269
!MESSAGE DS_ERROR: Can't Run Target CPU:
Error 0x80000020/-1060
Fatal Error during: Execution, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-11 15:20:51.508
!MESSAGE DS_ERROR: TMS320C671X: Can't Run Target CPU: Error 0x80000020/-1060 Fatal Error during: Execution,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-11 15:20:51.573
!MESSAGE DS_ERROR: Can't Run Target CPU:
Error 0x80000020/-1060
Fatal Error during: Execution, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-11 15:22:07.366
!MESSAGE DS_ERROR: TMS320C671X: Failed to remove the debug state from the target before disconnecting.  There may still be breakpoint op-codes embedded in program memory.  It is recommended that you reset the emulator before you connect and reload your program before you continue debugging


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-11 15:22:12.030
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-11 15:22:12.056
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-11 15:22:16.559
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-11 15:22:16.583
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-11 15:30:09.245
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-11 15:30:09.275
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:10:18.014
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:10:18.253
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:10:23.425
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:10:23.459
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:10:25.329
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:10:25.364
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:10:32.798
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:10:32.832
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:10:33.982
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:10:34.012
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:10:37.993
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:10:38.019
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:10:43.334
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:10:43.362
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:10:48.417
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:10:48.437
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:16:18.857
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:16:18.891
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:16:20.236
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:16:20.266
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:16:21.669
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:16:21.704
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:16:31.391
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:16:31.399
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:17:59.587
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:17:59.622
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:18:07.538
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:18:07.567
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:18:10.571
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:18:10.603
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:18:11.651
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:18:11.686
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:18:14.310
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-141 Fatal Error during: OCS,  Error generated by SD scan controller module 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:18:14.339
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-141
Fatal Error during: OCS, 
Error generated by SD scan controller module


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:18:16.240
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:18:16.264
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:18:17.898
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:18:17.930
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:18:19.184
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-141 Fatal Error during: OCS,  Error generated by SD scan controller module 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 09:18:19.211
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-141
Fatal Error during: OCS, 
Error generated by SD scan controller module

!SESSION 2019-12-12 10:10:39.985 -----------------------------------------------
eclipse.buildId=4.7.3.M20180301-0715
java.version=1.8.0_112
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ko_KR
Framework arguments:  -product com.ti.ccstudio.branding.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -product com.ti.ccstudio.branding.product

!ENTRY com.ti.common.core 4 0 2019-12-12 10:10:44.983
!MESSAGE path=ccs_base/DebugServer

!ENTRY com.ti.common.core 4 0 2019-12-12 10:10:45.004
!MESSAGE debugServerDir=C:/ti/ccsv8/ccs_base/DebugServer

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-12 10:10:51.528
!MESSAGE Enablement expression is missing for descriptor type org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-12 10:10:51.551
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-12 10:10:51.551
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY com.ti.ccstudio.debug.server 4 214294189 2019-12-12 10:11:00.429
!MESSAGE Unexpected CCS exit detected [19. 12. 10 오후 5:04]!!!

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 10:11:00.521
!MESSAGE constructor

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 10:11:00.521
!MESSAGE done with directories

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 10:11:00.522
!MESSAGE loading ti_logger

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 10:11:00.523
!MESSAGE Platform os: win32

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 10:11:00.524
!MESSAGE loading cToolsIF

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 10:11:00.528
!MESSAGE loading cTools

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 10:11:00.535
!MESSAGE loading TraceFactory

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 10:11:00.540
!MESSAGE loading sqlite3

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 10:11:00.545
!MESSAGE loading CloudTrace

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 10:11:00.568
!MESSAGE CloudTrace interface loaded

!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 10:11:05.728
!MESSAGE DS_ERROR: TMS320C671X: Error initializing emulator 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 10:11:05.992
!MESSAGE DS_ERROR: Error initializing emulator

!SESSION 2019-12-12 10:20:42.064 -----------------------------------------------
eclipse.buildId=4.7.3.M20180301-0715
java.version=1.8.0_112
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ko_KR
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.core.resources 2 10035 2019-12-12 10:20:48.094
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

!ENTRY com.ti.common.core 4 0 2019-12-12 10:20:48.329
!MESSAGE path=ccs_base/DebugServer

!ENTRY com.ti.common.core 4 0 2019-12-12 10:20:48.330
!MESSAGE debugServerDir=C:/ti/ccsv8/ccs_base/DebugServer

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-12 10:21:14.347
!MESSAGE Enablement expression is missing for descriptor type org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-12 10:21:14.367
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-12 10:21:14.368
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY com.ti.ccstudio.debug.server 4 214294189 2019-12-12 10:21:15.413
!MESSAGE Unexpected CCS exit detected [19. 12. 10 오후 5:04]!!!

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 10:21:15.509
!MESSAGE constructor

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 10:21:15.510
!MESSAGE done with directories

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 10:21:15.510
!MESSAGE loading ti_logger

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 10:21:15.511
!MESSAGE Platform os: win32

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 10:21:15.512
!MESSAGE loading cToolsIF

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 10:21:15.516
!MESSAGE loading cTools

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 10:21:15.523
!MESSAGE loading TraceFactory

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 10:21:15.527
!MESSAGE loading sqlite3

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 10:21:15.532
!MESSAGE loading CloudTrace

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 10:21:15.558
!MESSAGE CloudTrace interface loaded

!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 10:23:09.278
!MESSAGE DS_ERROR: TMS320C671X: Error initializing emulator 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 10:23:09.469
!MESSAGE DS_ERROR: Error initializing emulator


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 13:06:11.671
!MESSAGE DS_ERROR: TMS320C671X: Error initializing emulator 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 13:06:11.930
!MESSAGE DS_ERROR: Error initializing emulator


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 13:06:23.533
!MESSAGE DS_ERROR: TMS320C671X: Error initializing emulator 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 13:06:23.549
!MESSAGE DS_ERROR: Error initializing emulator


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 13:37:39.668
!MESSAGE DS_ERROR: TMS320C671X: Error initializing emulator 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 13:37:39.876
!MESSAGE DS_ERROR: Error initializing emulator


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 13:40:47.267
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 13:40:47.285
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 13:40:51.064
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 13:40:51.076
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 13:40:52.208
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 13:40:52.219
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 13:41:12.833
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 13:41:12.843
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:55:26.859
!MESSAGE DS_ERROR: TMS320C671X: Error initializing emulator 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:55:27.073
!MESSAGE DS_ERROR: Error initializing emulator


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:55:29.165
!MESSAGE DS_ERROR: TMS320C671X: Error initializing emulator 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:55:29.191
!MESSAGE DS_ERROR: Error initializing emulator


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:55:29.942
!MESSAGE DS_ERROR: TMS320C671X: Error initializing emulator 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:55:29.982
!MESSAGE DS_ERROR: Error initializing emulator


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:55:30.564
!MESSAGE DS_ERROR: TMS320C671X: Error initializing emulator 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:55:30.603
!MESSAGE DS_ERROR: Error initializing emulator


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:55:31.829
!MESSAGE DS_ERROR: TMS320C671X: Error initializing emulator 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:55:32.012
!MESSAGE DS_ERROR: Error initializing emulator


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:55:32.342
!MESSAGE DS_ERROR: TMS320C671X: Error initializing emulator 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:55:32.393
!MESSAGE DS_ERROR: Error initializing emulator


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:55:32.601
!MESSAGE DS_ERROR: TMS320C671X: Error initializing emulator 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:55:32.655
!MESSAGE DS_ERROR: Error initializing emulator

!SESSION 2019-12-12 14:55:39.958 -----------------------------------------------
eclipse.buildId=4.7.3.M20180301-0715
java.version=1.8.0_112
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ko_KR
Framework arguments:  -product com.ti.ccstudio.branding.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -product com.ti.ccstudio.branding.product

!ENTRY com.ti.common.core 4 0 2019-12-12 14:55:44.980
!MESSAGE path=ccs_base/DebugServer

!ENTRY com.ti.common.core 4 0 2019-12-12 14:55:44.981
!MESSAGE debugServerDir=C:/ti/ccsv8/ccs_base/DebugServer

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-12 14:56:08.401
!MESSAGE Enablement expression is missing for descriptor type org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-12 14:56:08.407
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-12 14:56:08.407
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 14:56:09.790
!MESSAGE constructor

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 14:56:09.790
!MESSAGE done with directories

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 14:56:09.791
!MESSAGE loading ti_logger

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 14:56:09.792
!MESSAGE Platform os: win32

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 14:56:09.792
!MESSAGE loading cToolsIF

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 14:56:09.796
!MESSAGE loading cTools

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 14:56:09.801
!MESSAGE loading TraceFactory

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 14:56:09.805
!MESSAGE loading sqlite3

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 14:56:09.809
!MESSAGE loading CloudTrace

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-12 14:56:09.839
!MESSAGE CloudTrace interface loaded

!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:56:21.016
!MESSAGE DS_ERROR: TMS320C671X: Error initializing emulator 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:56:21.343
!MESSAGE DS_ERROR: Error initializing emulator


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:56:23.581
!MESSAGE DS_ERROR: TMS320C671X: Error initializing emulator 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:56:23.625
!MESSAGE DS_ERROR: Error initializing emulator


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:56:24.402
!MESSAGE DS_ERROR: TMS320C671X: Error initializing emulator 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:56:24.445
!MESSAGE DS_ERROR: Error initializing emulator


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:56:25.247
!MESSAGE DS_ERROR: TMS320C671X: Error initializing emulator 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:56:25.287
!MESSAGE DS_ERROR: Error initializing emulator


!ENTRY com.ti.ccstudio.app.center 4 0 2019-12-12 14:56:34.289
!MESSAGE Unable to read http://software-dl.ti.com/ccs/non-esd/ccs_appcenter/apps_8.3.1.json file.
!STACK 0
java.net.SocketTimeoutException
	at java.net.SocksSocketImpl.remainingMillis(SocksSocketImpl.java:111)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at sun.net.NetworkClient.doConnect(NetworkClient.java:178)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
	at sun.net.www.http.HttpClient.<init>(HttpClient.java:211)
	at sun.net.www.http.HttpClient.New(HttpClient.java:308)
	at sun.net.www.http.HttpClient.New(HttpClient.java:326)
	at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1202)
	at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1138)
	at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1032)
	at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:966)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1546)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474)
	at java.net.URL.openStream(URL.java:1045)
	at com.ti.ccstudio.app.center.internal.CCSAppCenter.readFile(CCSAppCenter.java:190)
	at com.ti.ccstudio.app.center.internal.CCSAppCenter.getAppJson_0(CCSAppCenter.java:206)
	at com.ti.ccstudio.app.center.internal.CCSAppCenter.access$1(CCSAppCenter.java:205)
	at com.ti.ccstudio.app.center.internal.CCSAppCenter$1.run(CCSAppCenter.java:177)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)

!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:56:36.410
!MESSAGE DS_ERROR: TMS320C671X: Error initializing emulator 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:56:36.453
!MESSAGE DS_ERROR: Error initializing emulator


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:56:37.096
!MESSAGE DS_ERROR: TMS320C671X: Error initializing emulator 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:56:37.151
!MESSAGE DS_ERROR: Error initializing emulator


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:56:37.698
!MESSAGE DS_ERROR: TMS320C671X: Error initializing emulator 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-12 14:56:37.738
!MESSAGE DS_ERROR: Error initializing emulator


!ENTRY org.eclipse.cdt.dsf 2 10005 2019-12-12 18:30:40.194
!MESSAGE Request for monitor: '_Application_3_Spectrum Digital XDS510USB Emulator_0/TMS320C671X_Spectrum Digital XDS510USB Emulator_0/TMS320C671X_BreakpointManager_Spectrum Digital XDS510USB Emulator_0/TMS320C671X_BreakpointManager_Breakpoint(479)' resulted in an error.
!SUBENTRY 1 com.ti.ccstudio.debug 2 10005 2019-12-12 18:30:40.194
!MESSAGE The function "add" returned an error condition  (0x80004005)
!STACK 0
com.ti.xpcom.XPCOMException: The function "add" returned an error condition  (0x80004005)
	at com.ti.xpcom.internal.XPCOMJavaProxy.callXPCOMMethod(Native Method)
	at com.ti.xpcom.internal.XPCOMJavaProxy.invoke(XPCOMJavaProxy.java:105)
	at com.sun.proxy.$Proxy59.add(Unknown Source)
	at com.ti.debug.engine.impl.BreakpointManager.add(BreakpointManager.java:68)
	at com.ti.ccstudio.debug.service.contexts.BreakpointManagerDMContext.dsAdd(BreakpointManagerDMContext.java:691)
	at com.ti.ccstudio.debug.service.contexts.BreakpointManagerDMContext.insertBreakpoint(BreakpointManagerDMContext.java:347)
	at com.ti.ccstudio.debug.service.contexts.BreakpointManagerDMContext.insertBreakpoint(BreakpointManagerDMContext.java:315)
	at com.ti.ccstudio.debug.service.BreakpointService.insertBreakpoint(BreakpointService.java:474)
	at com.ti.ccstudio.debug.service.BreakpointService.installDeferredBreakpoints(BreakpointService.java:299)
	at com.ti.ccstudio.debug.internal.breakpoint.BreakpointManagerListener.installDeferredBreakpoints(BreakpointManagerListener.java:654)
	at com.ti.ccstudio.debug.internal.breakpoint.BreakpointManagerListener.access$0(BreakpointManagerListener.java:649)
	at com.ti.ccstudio.debug.internal.breakpoint.BreakpointManagerListener$1$1.safeRun(BreakpointManagerListener.java:201)
	at com.ti.ccstudio.debug.SafeRunnable.run(SafeRunnable.java:30)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:09:26.149
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:09:26.236
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:09:30.520
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:09:30.553
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:09:31.944
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:09:31.984
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:09:33.391
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:09:33.424
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:09:34.864
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x00000202/-2081 Error during: Memory, OCS,  Device driver: Emulation Connection Loss Detected on Target CPU. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:09:34.917
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x00000202/-2081
Error during: Memory, OCS, 
Device driver: Emulation Connection Loss Detected on Target CPU.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:09:45.446
!MESSAGE DS_ERROR: TMS320C671X: File Loader: Verification failed: Values at address 0x80207C00 do not match Please verify target memory and memory map.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:09:45.449
!MESSAGE DS_ERROR: TMS320C671X: GEL: File: D:\work\PUMP\PUMP_V2\1129_CCS8.0\cEIP_PEv8\Debug\cEIP_PEv8.out: a data verification error occurred, file load failed.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:10:02.134
!MESSAGE DS_ERROR: TMS320C671X: File Loader: Verification failed: Values at address 0x80207C00 do not match Please verify target memory and memory map.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:10:03.378
!MESSAGE DS_ERROR: TMS320C671X: GEL: File: D:\work\PUMP\PUMP_V2\1129_CCS8.0\cEIP_PEv8\Debug\cEIP_PEv8.out: a data verification error occurred, file load failed.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:10:11.797
!MESSAGE DS_ERROR: TMS320C671X: File Loader: Verification failed: Values at address 0x80207C00 do not match Please verify target memory and memory map.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:10:12.197
!MESSAGE DS_ERROR: TMS320C671X: GEL: File: D:\work\PUMP\PUMP_V2\1129_CCS8.0\cEIP_PEv8\Debug\cEIP_PEv8.out: a data verification error occurred, file load failed.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:10:36.644
!MESSAGE DS_ERROR: TMS320C671X: File Loader: Verification failed: Values at address 0x80207C00 do not match Please verify target memory and memory map.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:10:36.899
!MESSAGE DS_ERROR: TMS320C671X: GEL: File: D:\work\PUMP\PUMP_V2\1129_CCS8.0\cEIP_PEv8\Debug\cEIP_PEv8.out: a data verification error occurred, file load failed.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:10:44.129
!MESSAGE DS_ERROR: TMS320C671X: Failed CPU Reset 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:07.610
!MESSAGE DS_ERROR: TMS320C671X: Failed CPU Reset 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:17.505
!MESSAGE DS_ERROR: TMS320C671X: File Loader: Verification failed: Values at address 0x80207C00 do not match Please verify target memory and memory map.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:17.752
!MESSAGE DS_ERROR: TMS320C671X: GEL: File: D:/work\PUMP\PUMP_V2\1129_CCS8.0\cEIP_PEv8\Debug\cEIP_PEv8.out: a data verification error occurred, file load failed.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:29.929
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:29.958
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:34.021
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:34.044
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:35.223
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:35.258
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:36.635
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:36.672
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:37.755
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x00000202/-2081 Error during: Memory, OCS,  Device driver: Emulation Connection Loss Detected on Target CPU. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:37.789
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x00000202/-2081
Error during: Memory, OCS, 
Device driver: Emulation Connection Loss Detected on Target CPU.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:39.081
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:39.113
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:40.409
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:40.448
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:41.726
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:41.768
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:43.011
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:43.046
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:44.358
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:44.395
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:45.714
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:45.748
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:46.915
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:46.952
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:48.043
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:48.073
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:49.278
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x00000202/-2081 Error during: Memory, OCS,  Device driver: Emulation Connection Loss Detected on Target CPU. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:49.304
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x00000202/-2081
Error during: Memory, OCS, 
Device driver: Emulation Connection Loss Detected on Target CPU.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:50.445
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:50.477
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:51.985
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:52.025
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:53.213
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:53.226
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:54.393
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:54.418
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:59.887
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:11:59.920
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:12:01.162
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x00000202/-2081 Error during: Memory, OCS,  Device driver: Emulation Connection Loss Detected on Target CPU. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:12:01.197
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x00000202/-2081
Error during: Memory, OCS, 
Device driver: Emulation Connection Loss Detected on Target CPU.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:37.714
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:37.743
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:41.874
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:41.910
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:43.226
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:43.262
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:44.515
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:44.553
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:46.012
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:46.044
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:47.887
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:47.925
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:49.362
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:49.395
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:50.535
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:50.568
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:51.644
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:51.679
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:52.985
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:53.020
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:54.287
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:54.321
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:55.865
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:55.900
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:57.662
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:21:57.697
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:22:00.038
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:22:00.070
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:22:01.563
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:22:01.598
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:22:03.046
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:22:03.079
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:22:04.255
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:22:04.290
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:22:05.548
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:22:05.582
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:22:13.139
!MESSAGE DS_ERROR: TMS320C671X: Trouble Removing Breakpoint with the Action "Terminate GEL_Go()" at 0x801c68c0: Error 0x00000008/-1066 Error during: Break Point,  Cannot set/verify breakpoint at 0x801C68C0  


!ENTRY org.eclipse.ui 4 4 2019-12-13 19:33:35.409
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@11157d7} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@15e6344}

!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:39:41.892
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:39:41.923
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:39:46.896
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:39:46.936
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:39:48.727
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x00000202/-2081 Error during: Memory, OCS,  Device driver: Emulation Connection Loss Detected on Target CPU. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:39:48.759
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x00000202/-2081
Error during: Memory, OCS, 
Device driver: Emulation Connection Loss Detected on Target CPU.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:39:50.208
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x00000202/-2081 Error during: Memory, OCS,  Device driver: Emulation Connection Loss Detected on Target CPU. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:39:50.246
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x00000202/-2081
Error during: Memory, OCS, 
Device driver: Emulation Connection Loss Detected on Target CPU.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:57:16.663
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 19:57:16.709
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:01:29.051
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:01:29.082
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:01:30.947
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:01:31.003
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:01:33.973
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:01:34.008
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:01:35.260
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x00000202/-2081 Error during: Memory, OCS,  Device driver: Emulation Connection Loss Detected on Target CPU. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:01:35.295
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x00000202/-2081
Error during: Memory, OCS, 
Device driver: Emulation Connection Loss Detected on Target CPU.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:01:56.757
!MESSAGE DS_ERROR: TMS320C671X: Trouble Halting Target CPU: Error 0x80000020/-1060 Fatal Error during: Execution,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:01:56.771
!MESSAGE DS_ERROR: Trouble Halting Target CPU:
Error 0x80000020/-1060
Fatal Error during: Execution, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:02:08.421
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x00000202/-2081 Error during: Memory, OCS,  Device driver: Emulation Connection Loss Detected on Target CPU. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:02:08.451
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x00000202/-2081
Error during: Memory, OCS, 
Device driver: Emulation Connection Loss Detected on Target CPU.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:02:10.465
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x00000202/-2081 Error during: Memory, OCS,  Device driver: Emulation Connection Loss Detected on Target CPU. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:02:10.504
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x00000202/-2081
Error during: Memory, OCS, 
Device driver: Emulation Connection Loss Detected on Target CPU.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:02:34.175
!MESSAGE DS_ERROR: TMS320C671X: Trouble Halting Target CPU: Error 0x80000020/-1060 Fatal Error during: Execution,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:02:34.196
!MESSAGE DS_ERROR: Trouble Halting Target CPU:
Error 0x80000020/-1060
Fatal Error during: Execution, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:02:40.969
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:02:40.997
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:02:46.369
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:02:46.404
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:02:47.638
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:02:47.672
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:02:51.545
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:02:51.588
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:09:21.433
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:09:21.447
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:09:25.524
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:09:25.559
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:09:28.619
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:09:28.653
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:09:30.308
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:09:30.345
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:14:16.896
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-141 Fatal Error during: OCS,  Error generated by SD scan controller module 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:14:16.927
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-141
Fatal Error during: OCS, 
Error generated by SD scan controller module


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:14:19.037
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:14:19.076
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:14:20.267
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:14:20.304
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:14:22.123
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:14:22.158
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:14:30.962
!MESSAGE DS_ERROR: TMS320C671X: File Loader: Verification failed: Values at address 0x80207C00 do not match Please verify target memory and memory map.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:14:31.270
!MESSAGE DS_ERROR: TMS320C671X: GEL: File: D:\work\PUMP\PUMP_V2\1129_CCS8.0\cEIP_PEv8\Debug\cEIP_PEv8.out: a data verification error occurred, file load failed.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:14:46.890
!MESSAGE DS_ERROR: TMS320C671X: File Loader: Verification failed: Values at address 0x80207C00 do not match Please verify target memory and memory map.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:14:46.891
!MESSAGE DS_ERROR: TMS320C671X: GEL: File: D:\work\PUMP\PUMP_V2\1129_CCS8.0\cEIP_PEv8\Debug\cEIP_PEv8.out: a data verification error occurred, file load failed.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:14:51.860
!MESSAGE DS_ERROR: TMS320C671X: Failed CPU Reset 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:33:47.268
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-141 Fatal Error during: OCS,  Error generated by SD scan controller module 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:33:47.299
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-141
Fatal Error during: OCS, 
Error generated by SD scan controller module


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:33:49.084
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:33:49.127
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:33:52.387
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:33:52.423
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:33:53.603
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x00000202/-2081 Error during: Memory, OCS,  Device driver: Emulation Connection Loss Detected on Target CPU. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:33:53.640
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x00000202/-2081
Error during: Memory, OCS, 
Device driver: Emulation Connection Loss Detected on Target CPU.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:39:41.049
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:39:41.075
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:39:43.417
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:39:43.436
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:39:46.450
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:39:46.484
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:46:27.646
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:46:27.675
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:46:31.661
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:46:31.703
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:46:32.900
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:46:32.933
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:46:41.210
!MESSAGE DS_ERROR: TMS320C671X: Failed CPU Reset 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:46:44.535
!MESSAGE DS_ERROR: TMS320C671X: Failed CPU Reset 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:48:25.262
!MESSAGE DS_ERROR: TMS320C671X: File Loader: Verification failed: Values at address 0x801AFFA0 do not match Please verify target memory and memory map.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:48:25.546
!MESSAGE DS_ERROR: TMS320C671X: GEL: File: D:\work\PUMP\PUMP_V2\1129_CCS8.0\cEIP_PEv8\Debug\cEIP_PEv8.out: a data verification error occurred, file load failed.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:48:55.280
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:48:55.295
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:48:58.028
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:48:58.043
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:48:59.671
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 20:48:59.689
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY org.eclipse.ui 4 4 2019-12-13 20:56:31.325
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@11157d7} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@324b79}

!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 21:08:13.813
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 21:08:13.856
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:08:09.874
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:08:09.901
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:12:23.672
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:12:23.705
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:12:27.385
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:12:27.429
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:12:29.140
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:12:29.176
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:12:30.428
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:12:30.465
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:12:35.649
!MESSAGE DS_ERROR: TMS320C671X: Failed CPU Reset 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:12:46.545
!MESSAGE DS_ERROR: TMS320C671X: Failed CPU Reset 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:12:57.549
!MESSAGE DS_ERROR: TMS320C671X: Failed CPU Reset 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:13:16.944
!MESSAGE DS_ERROR: TMS320C671X: File Loader: Verification failed: Values at address 0x80207C00 do not match Please verify target memory and memory map.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:13:16.947
!MESSAGE DS_ERROR: TMS320C671X: GEL: File: D:\work\PUMP\PUMP_V2\1129_CCS8.0\cEIP_PEv8\Debug\cEIP_PEv8.out: a data verification error occurred, file load failed.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:13:19.994
!MESSAGE DS_ERROR: TMS320C671X: File Loader: Verification failed: Values at address 0x80207C00 do not match Please verify target memory and memory map.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:13:19.996
!MESSAGE DS_ERROR: TMS320C671X: GEL: File: D:\work\PUMP\PUMP_V2\1129_CCS8.0\cEIP_PEv8\Debug\cEIP_PEv8.out: a data verification error occurred, file load failed.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:13:32.560
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:13:32.588
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:13:36.475
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:13:36.517
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:13:38.306
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:13:38.348
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:13:39.570
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:13:39.606
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:13:51.745
!MESSAGE DS_ERROR: TMS320C671X: Failed CPU Reset 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:14:02.694
!MESSAGE DS_ERROR: TMS320C671X: File Loader: Verification failed: Values at address 0x80207C00 do not match Please verify target memory and memory map.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:14:02.695
!MESSAGE DS_ERROR: TMS320C671X: GEL: File: D:\work\PUMP\PUMP_V2\1129_CCS8.0\cEIP_PEv8\Debug\cEIP_PEv8.out: a data verification error occurred, file load failed.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:14:27.463
!MESSAGE DS_ERROR: TMS320C671X: Failed CPU Reset 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:14:33.169
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:14:33.198
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:14:38.004
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:14:38.047
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:14:45.254
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:14:45.287
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:14:49.620
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:14:49.647
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:14:51.251
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:14:51.291
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:14:53.884
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:14:53.914
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:14:55.753
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:14:55.788
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY org.eclipse.ui 4 4 2019-12-13 22:16:05.540
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@11157d7} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@324b79}

!ENTRY org.eclipse.ui 4 4 2019-12-13 22:16:05.541
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@11157d7} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@324b79}

!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:17:00.236
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:17:00.265
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:17:03.253
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:17:03.292
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:18:18.454
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:18:18.483
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:18:20.878
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:18:20.922
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:18:22.374
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x00000202/-2081 Error during: Memory, OCS,  Device driver: Emulation Connection Loss Detected on Target CPU. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:18:22.412
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x00000202/-2081
Error during: Memory, OCS, 
Device driver: Emulation Connection Loss Detected on Target CPU.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:18:23.776
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x00000202/-2081 Error during: Memory, OCS,  Device driver: Emulation Connection Loss Detected on Target CPU. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:18:23.810
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x00000202/-2081
Error during: Memory, OCS, 
Device driver: Emulation Connection Loss Detected on Target CPU.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:22:18.711
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:22:18.742
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:22:25.341
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:22:25.376
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:23:44.517
!MESSAGE DS_ERROR: TMS320C671X: Power Failure on Target CPU 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:37:52.119
!MESSAGE DS_ERROR: TMS320C671X: Error initializing emulator 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:37:52.338
!MESSAGE DS_ERROR: Error initializing emulator


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:37:54.269
!MESSAGE DS_ERROR: TMS320C671X: Error initializing emulator 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:37:54.317
!MESSAGE DS_ERROR: Error initializing emulator

!SESSION 2019-12-13 22:38:04.238 -----------------------------------------------
eclipse.buildId=4.7.3.M20180301-0715
java.version=1.8.0_112
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ko_KR
Framework arguments:  -product com.ti.ccstudio.branding.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -product com.ti.ccstudio.branding.product

!ENTRY com.ti.common.core 4 0 2019-12-13 22:38:11.790
!MESSAGE path=ccs_base/DebugServer

!ENTRY com.ti.common.core 4 0 2019-12-13 22:38:11.791
!MESSAGE debugServerDir=C:/ti/ccsv8/ccs_base/DebugServer

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-13 22:38:37.562
!MESSAGE Enablement expression is missing for descriptor type org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-13 22:38:37.574
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-13 22:38:37.575
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-13 22:38:38.436
!MESSAGE constructor

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-13 22:38:38.436
!MESSAGE done with directories

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-13 22:38:38.437
!MESSAGE loading ti_logger

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-13 22:38:38.438
!MESSAGE Platform os: win32

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-13 22:38:38.438
!MESSAGE loading cToolsIF

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-13 22:38:38.445
!MESSAGE loading cTools

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-13 22:38:38.452
!MESSAGE loading TraceFactory

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-13 22:38:38.455
!MESSAGE loading sqlite3

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-13 22:38:38.458
!MESSAGE loading CloudTrace

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-13 22:38:38.479
!MESSAGE CloudTrace interface loaded

!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:55:15.187
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:55:15.208
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:55:18.683
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:55:18.719
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:55:20.101
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:55:20.135
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:55:21.510
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:55:21.547
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:55:22.735
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:55:22.747
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:55:23.812
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x00000202/-2081 Error during: Memory, OCS,  Device driver: Emulation Connection Loss Detected on Target CPU. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:55:23.861
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x00000202/-2081
Error during: Memory, OCS, 
Device driver: Emulation Connection Loss Detected on Target CPU.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:55:25.097
!MESSAGE DS_ERROR: TMS320C671X: GEL: Error while executing OnTargetConnect(): identifier not found: EMIF_SDRAMCTL
	 at (int *) EMIF_SDRAMCTL [ceNM_PE.gel:269]
	 at init_emif() [ceNM_PE.gel:56]
	 at OnTargetConnect()


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:55:52.159
!MESSAGE DS_ERROR: TMS320C671X: Failed CPU Reset 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:55:52.262
!MESSAGE DS_ERROR: TMS320C671X: GEL: Error while executing OnReset(1): identifier not found: EMIF_SDRAMCTL
	 at (int *) EMIF_SDRAMCTL [ceNM_PE.gel:269]
	 at init_emif() [ceNM_PE.gel:63]
	 at OnReset(1)


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:56:01.074
!MESSAGE DS_ERROR: TMS320C671X: Trouble Setting Breakpoint with the Action "Terminate GEL_Go()" at 0x801c68c0: Error 0x00000008/-1066 Error during: Break Point,  Cannot set/verify breakpoint at 0x801C68C0  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:56:06.662
!MESSAGE DS_ERROR: TMS320C671X: File Loader: Verification failed: Values at address 0x80207C00 do not match Please verify target memory and memory map.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 22:56:06.663
!MESSAGE DS_ERROR: TMS320C671X: GEL: File: D:\work\PUMP\PUMP_V2\1129_CCS8.0\cEIP_PEv8\Debug\cEIP_PEv8.out: a data verification error occurred, file load failed.


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-13 23:18:25.517
!MESSAGE DS_ERROR: TMS320C671X: Failed to remove the debug state from the target before disconnecting.  There may still be breakpoint op-codes embedded in program memory.  It is recommended that you reset the emulator before you connect and reload your program before you continue debugging


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 11:39:20.239
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 11:39:20.323
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 11:39:24.957
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 11:39:24.975
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 11:39:26.143
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x00000202/-2081 Error during: Memory, OCS,  Device driver: Emulation Connection Loss Detected on Target CPU. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 11:39:26.155
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x00000202/-2081
Error during: Memory, OCS, 
Device driver: Emulation Connection Loss Detected on Target CPU.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 11:39:27.265
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x00000202/-2081 Error during: Memory, OCS,  Device driver: Emulation Connection Loss Detected on Target CPU. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 11:39:27.318
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x00000202/-2081
Error during: Memory, OCS, 
Device driver: Emulation Connection Loss Detected on Target CPU.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 11:39:28.473
!MESSAGE DS_ERROR: TMS320C671X: GEL: Error while executing OnTargetConnect(): identifier not found: EMIF_SDRAMCTL
	 at (int *) EMIF_SDRAMCTL [ceNM_PE.gel:269]
	 at init_emif() [ceNM_PE.gel:56]
	 at OnTargetConnect()


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 12:22:24.410
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 12:22:24.437
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 12:22:27.958
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 12:22:27.997
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 12:22:44.893
!MESSAGE DS_ERROR: TMS320C671X: Trouble Halting Target CPU: Error 0x80000020/-1060 Fatal Error during: Execution,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 12:22:45.031
!MESSAGE DS_ERROR: Trouble Halting Target CPU:
Error 0x80000020/-1060
Fatal Error during: Execution, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 12:22:56.543
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 12:22:56.570
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 12:28:56.557
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 12:28:56.585
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 12:29:00.066
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 12:29:00.105
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 12:29:01.877
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 12:29:01.911
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 12:29:02.969
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x00000202/-2081 Error during: Memory, OCS,  Device driver: Emulation Connection Loss Detected on Target CPU. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 12:29:03.004
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x00000202/-2081
Error during: Memory, OCS, 
Device driver: Emulation Connection Loss Detected on Target CPU.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 12:29:19.924
!MESSAGE DS_ERROR: TMS320C671X: Trouble Setting Breakpoint with the Action "Remain Halted" at 0x801c6c84: Error 0x0000000A/-2130 Error during: Memory, Break Point,  Cannot access memory address at 0x01840000  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 12:29:20.067
!MESSAGE DS_ERROR: TMS320C671X: Can't Run Target CPU: Error 0x80000020/-1060 Fatal Error during: Execution,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 12:29:20.181
!MESSAGE DS_ERROR: Can't Run Target CPU:
Error 0x80000020/-1060
Fatal Error during: Execution, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 12:29:25.834
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 12:29:25.847
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 12:29:27.698
!MESSAGE DS_ERROR: TMS320C671X: GEL: Error while executing OnTargetConnect(): identifier not found: EMIF_SDRAMCTL
	 at (int *) EMIF_SDRAMCTL [ceNM_PE.gel:269]
	 at init_emif() [ceNM_PE.gel:56]
	 at OnTargetConnect()


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 13:58:13.306
!MESSAGE DS_ERROR: TMS320C671X: Error initializing emulator 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 13:58:13.662
!MESSAGE DS_ERROR: Error initializing emulator


!ENTRY org.eclipse.ui 4 4 2019-12-14 14:01:44.061
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@c2ea7f} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@1dd53f}

!ENTRY org.eclipse.ui 4 4 2019-12-14 14:01:44.414
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@165b7c7} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@1dd53f}

!ENTRY org.eclipse.ui 4 4 2019-12-14 14:01:45.072
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@1d087e8} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@1dd53f}

!ENTRY org.eclipse.ui 4 0 2019-12-14 14:02:21.786
!MESSAGE Unhandled event loop exception
!STACK 0
org.eclipse.e4.core.di.InjectionException: org.eclipse.core.commands.ExecutionException: While executing the action, an exception occurred
	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:65)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:305)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:239)
	at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
	at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
	at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
	at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487)
	at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.executeCommand(KeyBindingDispatcher.java:287)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.press(KeyBindingDispatcher.java:527)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.processKeyEvent(KeyBindingDispatcher.java:577)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.filterKeySequenceBindings(KeyBindingDispatcher.java:385)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.access$0(KeyBindingDispatcher.java:331)
	at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher$KeyDownFilter.handleEvent(KeyBindingDispatcher.java:88)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
	at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1271)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1078)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1103)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1088)
	at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1130)
	at org.eclipse.swt.widgets.Text.sendKeyEvent(Text.java:1789)
	at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1126)
	at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1547)
	at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4962)
	at org.eclipse.swt.widgets.Text.WM_CHAR(Text.java:2722)
	at org.eclipse.swt.widgets.Control.windowProc(Control.java:4843)
	at org.eclipse.swt.widgets.Text.windowProc(Text.java:2704)
	at org.eclipse.swt.widgets.Display.windowProc(Display.java:5178)
	at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
	at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2560)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3815)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
Caused by: org.eclipse.core.commands.ExecutionException: While executing the action, an exception occurred
	at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:123)
	at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:92)
	at sun.reflect.GeneratedMethodAccessor89.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
	... 51 more
Caused by: java.lang.ClassCastException: org.eclipse.swt.widgets.Text cannot be cast to org.eclipse.swt.widgets.Combo
	at com.ti.ccstudio.debug.ui.memoryView.actions.AbstractExportViewAction.processData(AbstractExportViewAction.java:76)
	at com.ti.ccstudio.debug.ui.memoryView.actions.AbstractExportViewAction.run(AbstractExportViewAction.java:233)
	at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
	at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:118)
	... 56 more

!ENTRY org.eclipse.ui 4 4 2019-12-14 14:03:09.925
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@165b7c7} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@1dd53f}

!ENTRY org.eclipse.ui 4 4 2019-12-14 14:03:09.926
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@165b7c7} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@17c42cf}

!ENTRY org.eclipse.ui 4 4 2019-12-14 14:03:51.740
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@165b7c7} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@17c42cf}

!ENTRY org.eclipse.ui 4 4 2019-12-14 14:03:51.741
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@165b7c7} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@17c42cf}

!ENTRY org.eclipse.ui 4 4 2019-12-14 14:04:13.695
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@165b7c7} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@12645f5}

!ENTRY org.eclipse.ui 4 4 2019-12-14 14:04:22.228
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@134d835} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@12645f5}

!ENTRY org.eclipse.ui 4 4 2019-12-14 14:04:27.372
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@134d835} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@12645f5}

!ENTRY com.ti.ccstudio.debug 1 0 2019-12-14 14:04:55.422
!MESSAGE DS_ERROR: TMS320C671X: GEL: Error loading file 'D:\work\PUMP\PUMP_V2\1129_CCS8.0\cEIP_PEv8\ceNM_PE.gel': function 'StartUp()' already defined


!ENTRY org.eclipse.ui 4 4 2019-12-14 14:07:02.917
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@134d835} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@12645f5}

!ENTRY org.eclipse.ui 4 4 2019-12-14 14:07:02.918
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@d47c2d} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@12645f5}

!ENTRY org.eclipse.ui 4 4 2019-12-14 14:07:33.647
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@d47c2d} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@12645f5}

!ENTRY org.eclipse.ui 4 4 2019-12-14 14:07:46.309
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@d47c2d} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@12645f5}

!ENTRY org.eclipse.ui 4 4 2019-12-14 14:08:03.472
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@d47c2d} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@12645f5}
!SESSION 2019-12-14 14:11:53.818 -----------------------------------------------
eclipse.buildId=4.7.3.M20180301-0715
java.version=1.8.0_112
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ko_KR
Framework arguments:  -product com.ti.ccstudio.branding.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -product com.ti.ccstudio.branding.product

!ENTRY com.ti.common.core 4 0 2019-12-14 14:11:58.536
!MESSAGE path=ccs_base/DebugServer

!ENTRY com.ti.common.core 4 0 2019-12-14 14:11:58.537
!MESSAGE debugServerDir=C:/ti/ccsv8/ccs_base/DebugServer

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-14 14:12:12.089
!MESSAGE Enablement expression is missing for descriptor type org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-14 14:12:12.102
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-14 14:12:12.102
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-14 14:12:13.223
!MESSAGE constructor

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-14 14:12:13.223
!MESSAGE done with directories

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-14 14:12:13.225
!MESSAGE loading ti_logger

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-14 14:12:13.226
!MESSAGE Platform os: win32

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-14 14:12:13.227
!MESSAGE loading cToolsIF

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-14 14:12:13.234
!MESSAGE loading cTools

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-14 14:12:13.245
!MESSAGE loading TraceFactory

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-14 14:12:13.251
!MESSAGE loading sqlite3

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-14 14:12:13.255
!MESSAGE loading CloudTrace

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-14 14:12:13.272
!MESSAGE CloudTrace interface loaded

!ENTRY org.eclipse.ui 4 4 2019-12-14 14:12:40.578
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@154cfd8} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@e96d5b}

!ENTRY org.eclipse.ui 4 4 2019-12-14 14:16:02.638
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@16501a9} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@e96d5b}

!ENTRY org.eclipse.help 4 0 2019-12-14 14:16:21.814
!MESSAGE Error reading help table of contents file /"com.framework_components_3_40_02_07/doxy_toc.xml" (skipping file)
!STACK 0
java.io.FileNotFoundException
	at org.eclipse.help.internal.toc.TocFileParser.parse(TocFileParser.java:44)
	at org.eclipse.help.internal.toc.TocFileProvider.getTocContributions(TocFileProvider.java:45)
	at org.eclipse.help.internal.toc.TocManager.getAndCacheTocContributions(TocManager.java:211)
	at org.eclipse.help.internal.toc.TocManager.getTocContributionsForToc(TocManager.java:199)
	at org.eclipse.help.internal.toc.TocManager.getRootTocContributions(TocManager.java:307)
	at org.eclipse.help.internal.toc.TocManager.getTocs(TocManager.java:68)
	at org.eclipse.help.internal.search.IndexingOperation.getAllDocuments(IndexingOperation.java:479)
	at org.eclipse.help.internal.search.IndexingOperation.getAddedDocuments(IndexingOperation.java:352)
	at org.eclipse.help.internal.search.IndexingOperation.execute(IndexingOperation.java:88)
	at org.eclipse.help.internal.search.LocalSearchManager.updateIndex(LocalSearchManager.java:630)
	at org.eclipse.help.internal.search.LocalSearchManager.ensureIndexUpdated(LocalSearchManager.java:604)
	at org.eclipse.help.internal.search.federated.IndexerJob.run(IndexerJob.java:32)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)

!ENTRY org.eclipse.help.base 2 0 2019-12-14 14:16:22.128
!MESSAGE Unable to consume Lucene index from bundle 'org.eclipse.cdt.doc.user_5.4.0.201802261533 [77]'. The index should be rebuilt with Lucene 6.1.

!ENTRY org.eclipse.help.base 2 0 2019-12-14 14:16:22.150
!MESSAGE Unable to consume Lucene index from bundle 'org.eclipse.platform.doc.user_4.7.3.v20171222-0602 [240]'. The index should be rebuilt with Lucene 6.1.

!ENTRY org.eclipse.help.base 4 4 2019-12-14 14:17:24.700
!MESSAGE Help documentation could not be indexed completely.
!SUBENTRY 1 org.eclipse.help.base 4 4 2019-12-14 14:17:24.700
!MESSAGE Help document /com.ti.rtsc.NDK.product.ui/ndk_3_60_00_13_release_notes.html cannot be opened.
!SUBENTRY 1 org.eclipse.help.base 4 4 2019-12-14 14:17:24.700
!MESSAGE Help document /com.ti.uia.product.ui/uia_2_30_01_02_release_notes.html cannot be opened.
!SUBENTRY 1 org.eclipse.help.base 4 4 2019-12-14 14:17:24.700
!MESSAGE Help document /com.ti.biosmcsdk.pdk.C6657_1.1.2.6/packages/ti/drv/tcp3e/docs/doxy/html/index.html cannot be opened.
!SUBENTRY 1 org.eclipse.help.base 4 4 2019-12-14 14:17:24.700
!MESSAGE Help document /com.ti.biosmcsdk.openem.product.ui/index.html cannot be opened.
!SUBENTRY 1 org.eclipse.help.base 4 4 2019-12-14 14:17:24.700
!MESSAGE Help document /com.ti.sdo.edma3.rtscRegistry_02.11.05/release_notes_edma3_lld_02_11_05.html cannot be opened.
!SUBENTRY 1 org.eclipse.help.base 4 4 2019-12-14 14:17:24.700
!MESSAGE Help document /com.ti.sdo.edma3.product_02.12.05/packages/ti/sdo/edma3/rm/docs/html/index.html cannot be opened.
!SUBENTRY 1 org.eclipse.help.base 4 4 2019-12-14 14:17:24.700
!MESSAGE Help document /com.ti.sdo.edma3.product_02.12.05/release_notes_edma3_lld.html cannot be opened.
!SUBENTRY 1 org.eclipse.help.base 4 4 2019-12-14 14:17:24.700
!MESSAGE Help document /com.ti.sdo.edma3.product_02.12.05/packages/ti/sdo/edma3/drv/docs/html/index.html cannot be opened.
!SUBENTRY 1 org.eclipse.help.base 4 4 2019-12-14 14:17:24.700
!MESSAGE Help document /com.ti.rtsc.SYSBIOS.product.ui/bios_6_75_02_00_release_notes.html cannot be opened.

!ENTRY com.ti.ccstudio.debug 1 0 2019-12-15 13:27:22.066
!MESSAGE DS_ERROR: TMS320C671X: GEL: Encountered a problem loading file: D:\work\PUMP\PUMP_V2\1129_CCS8.0\cEIP_PEv8\Debug\cEIP_PEv8.out Could not open file


!ENTRY org.eclipse.ui 4 0 2019-12-15 13:50:43.481
!MESSAGE Unhandled event loop exception
!STACK 0
org.eclipse.swt.SWTException: Widget is disposed
	at org.eclipse.swt.SWT.error(SWT.java:4533)
	at org.eclipse.swt.SWT.error(SWT.java:4448)
	at org.eclipse.swt.SWT.error(SWT.java:4419)
	at org.eclipse.swt.widgets.Widget.error(Widget.java:482)
	at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:354)
	at org.eclipse.swt.widgets.Control.setFocus(Control.java:3490)
	at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:1099)
	at com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$4.focusGained(TargetSpecificView.java:288)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:140)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4428)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1103)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1084)
	at org.eclipse.swt.widgets.Control.sendFocusEvent(Control.java:2979)
	at org.eclipse.swt.widgets.Widget.wmSetFocus(Widget.java:2437)
	at org.eclipse.swt.widgets.Control.WM_SETFOCUS(Control.java:5490)
	at org.eclipse.swt.widgets.Tree.WM_SETFOCUS(Tree.java:7309)
	at org.eclipse.swt.widgets.Control.windowProc(Control.java:4913)
	at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:6188)
	at org.eclipse.swt.widgets.Display.windowProc(Display.java:5178)
	at org.eclipse.swt.internal.win32.OS.SetFocus(Native Method)
	at org.eclipse.swt.widgets.Control.forceFocus(Control.java:1114)
	at org.eclipse.swt.widgets.Control.setFocus(Control.java:3492)
	at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:1101)
	at com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView.setFocus(TargetSpecificView.java:525)
	at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.delegateSetFocus(CompatibilityPart.java:216)
	at sun.reflect.GeneratedMethodAccessor89.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:305)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:311)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:233)
	at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:107)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.focusGui(PartRenderingEngine.java:789)
	at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer$1.setFocus(ContributedPartRenderer.java:103)
	at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:1099)
	at org.eclipse.swt.custom.CTabItem.setFocus(CTabItem.java:332)
	at org.eclipse.swt.custom.CTabFolder.setFocus(CTabFolder.java:2619)
	at org.eclipse.swt.widgets.Control.fixFocus(Control.java:1069)
	at org.eclipse.swt.widgets.Control.setVisible(Control.java:4017)
	at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3163)
	at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3171)
	at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:1858)
	at org.eclipse.swt.custom.CTabFolder.lambda$0(CTabFolder.java:328)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4428)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4238)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3817)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1499)

!ENTRY org.eclipse.ui 4 4 2019-12-15 13:50:44.175
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@183d67} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@e96d5b}

!ENTRY org.eclipse.ui 4 4 2019-12-15 13:50:47.118
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@180cc51} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@e96d5b}

!ENTRY com.ti.ccstudio.debug 1 0 2019-12-15 13:55:58.394
!MESSAGE DS_ERROR: TMS320C671X: Trouble Removing Breakpoint with the Action "Remain Halted" at 0x801c9b98: Error 0x00000008/-1066 Error during: Break Point,  Cannot set/verify breakpoint at 0x801C9B98  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-16 10:53:19.880
!MESSAGE DS_ERROR: TMS320C671X: GEL: Target must be connected before calling the function


!ENTRY org.eclipse.cdt.dsf 4 10005 2019-12-16 10:53:19.928
!MESSAGE Request for monitor: 'RequestMonitor (org.eclipse.cdt.dsf.concurrent.RequestMonitor@f4934e): Status ERROR: com.ti.ccstudio.debug code=20003 Target must be connected before calling the function null' resulted in an error.
!SUBENTRY 1 com.ti.ccstudio.debug 4 20003 2019-12-16 10:53:19.928
!MESSAGE Target must be connected before calling the function

!ENTRY com.ti.ccstudio.debug 1 0 2019-12-16 11:38:08.712
!MESSAGE DS_ERROR: TMS320C671X: GEL: Program loader is busy


!ENTRY org.eclipse.cdt.dsf 4 10005 2019-12-16 11:38:08.774
!MESSAGE Request for monitor: 'RequestMonitor (org.eclipse.cdt.dsf.concurrent.RequestMonitor@1b3edfc): Status ERROR: com.ti.ccstudio.debug code=20003 Program loader is busy null' resulted in an error.
!SUBENTRY 1 com.ti.ccstudio.debug 4 20003 2019-12-16 11:38:08.774
!MESSAGE Program loader is busy

!ENTRY com.ti.ccstudio.debug 1 0 2019-12-16 13:01:59.674
!MESSAGE DS_ERROR: TMS320C671X: GEL: Program loader is busy


!ENTRY org.eclipse.cdt.dsf 4 10005 2019-12-16 13:02:00.568
!MESSAGE Request for monitor: 'RequestMonitor (org.eclipse.cdt.dsf.concurrent.RequestMonitor@c8b689): Status ERROR: com.ti.ccstudio.debug code=20003 Program loader is busy null' resulted in an error.
!SUBENTRY 1 com.ti.ccstudio.debug 4 20003 2019-12-16 13:02:00.568
!MESSAGE Program loader is busy

!ENTRY org.eclipse.ui 4 0 2019-12-16 13:13:03.529
!MESSAGE Unhandled event loop exception
!STACK 0
org.eclipse.swt.SWTException: Widget is disposed
	at org.eclipse.swt.SWT.error(SWT.java:4533)
	at org.eclipse.swt.SWT.error(SWT.java:4448)
	at org.eclipse.swt.SWT.error(SWT.java:4419)
	at org.eclipse.swt.widgets.Widget.error(Widget.java:482)
	at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:354)
	at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:1091)
	at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:1099)
	at com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$4.focusGained(TargetSpecificView.java:288)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:140)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4428)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1103)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1084)
	at org.eclipse.swt.widgets.Control.sendFocusEvent(Control.java:2979)
	at org.eclipse.swt.widgets.Widget.wmSetFocus(Widget.java:2437)
	at org.eclipse.swt.widgets.Control.WM_SETFOCUS(Control.java:5490)
	at org.eclipse.swt.widgets.Tree.WM_SETFOCUS(Tree.java:7309)
	at org.eclipse.swt.widgets.Control.windowProc(Control.java:4913)
	at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:6188)
	at org.eclipse.swt.widgets.Display.windowProc(Display.java:5178)
	at org.eclipse.swt.internal.win32.OS.SetFocus(Native Method)
	at org.eclipse.swt.widgets.Control.forceFocus(Control.java:1114)
	at org.eclipse.swt.widgets.Control.setFocus(Control.java:3492)
	at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:1101)
	at com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView.setFocus(TargetSpecificView.java:525)
	at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.delegateSetFocus(CompatibilityPart.java:216)
	at sun.reflect.GeneratedMethodAccessor89.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:305)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:311)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:233)
	at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:107)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.focusGui(PartRenderingEngine.java:789)
	at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer$1.setFocus(ContributedPartRenderer.java:103)
	at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:1099)
	at org.eclipse.swt.custom.CTabItem.setFocus(CTabItem.java:332)
	at org.eclipse.swt.custom.CTabFolder.setFocus(CTabFolder.java:2619)
	at org.eclipse.swt.widgets.Control.fixFocus(Control.java:1069)
	at org.eclipse.swt.widgets.Control.setVisible(Control.java:4017)
	at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3163)
	at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3171)
	at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:1858)
	at org.eclipse.swt.custom.CTabFolder.lambda$0(CTabFolder.java:328)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4428)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4238)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3817)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1499)

!ENTRY com.ti.ccstudio.debug 1 0 2019-12-16 13:56:31.264
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-141 Fatal Error during: OCS,  Error generated by SD scan controller module 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-16 13:56:31.600
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-141
Fatal Error during: OCS, 
Error generated by SD scan controller module


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-16 14:23:52.828
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-141 Fatal Error during: OCS,  Error generated by SD scan controller module 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-16 14:23:52.860
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-141
Fatal Error during: OCS, 
Error generated by SD scan controller module


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-16 16:40:31.975
!MESSAGE DS_ERROR: TMS320C671X: GEL: Target must be connected before calling the function


!ENTRY org.eclipse.cdt.dsf 4 10005 2019-12-16 16:40:31.979
!MESSAGE Request for monitor: 'RequestMonitor (org.eclipse.cdt.dsf.concurrent.RequestMonitor@1157be5): Status ERROR: com.ti.ccstudio.debug code=20003 Target must be connected before calling the function null' resulted in an error.
!SUBENTRY 1 com.ti.ccstudio.debug 4 20003 2019-12-16 16:40:31.979
!MESSAGE Target must be connected before calling the function
!SESSION 2019-12-17 10:45:39.698 -----------------------------------------------
eclipse.buildId=4.7.3.M20180301-0715
java.version=1.8.0_112
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ko_KR
Framework arguments:  -product com.ti.ccstudio.branding.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -product com.ti.ccstudio.branding.product

!ENTRY com.ti.common.core 4 0 2019-12-17 10:45:54.424
!MESSAGE path=ccs_base/DebugServer

!ENTRY com.ti.common.core 4 0 2019-12-17 10:45:54.516
!MESSAGE debugServerDir=C:/ti/ccsv8/ccs_base/DebugServer

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-17 10:46:12.351
!MESSAGE Enablement expression is missing for descriptor type org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-17 10:46:12.448
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-17 10:46:12.450
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 10:46:13.322
!MESSAGE constructor

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 10:46:13.322
!MESSAGE done with directories

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 10:46:13.323
!MESSAGE loading ti_logger

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 10:46:13.324
!MESSAGE Platform os: win32

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 10:46:13.325
!MESSAGE loading cToolsIF

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 10:46:13.332
!MESSAGE loading cTools

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 10:46:13.341
!MESSAGE loading TraceFactory

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 10:46:13.348
!MESSAGE loading sqlite3

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 10:46:13.386
!MESSAGE loading CloudTrace

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 10:46:13.440
!MESSAGE CloudTrace interface loaded
!SESSION 2019-12-17 18:23:51.657 -----------------------------------------------
eclipse.buildId=4.7.3.M20180301-0715
java.version=1.8.0_112
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ko_KR
Framework arguments:  -product com.ti.ccstudio.branding.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -product com.ti.ccstudio.branding.product

!ENTRY com.ti.common.core 4 0 2019-12-17 18:23:56.845
!MESSAGE path=ccs_base/DebugServer

!ENTRY com.ti.common.core 4 0 2019-12-17 18:23:56.941
!MESSAGE debugServerDir=C:/ti/ccsv8/ccs_base/DebugServer

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-17 18:24:13.757
!MESSAGE Enablement expression is missing for descriptor type org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-17 18:24:13.761
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-17 18:24:13.762
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 18:24:14.806
!MESSAGE constructor

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 18:24:14.849
!MESSAGE done with directories

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 18:24:14.850
!MESSAGE loading ti_logger

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 18:24:14.850
!MESSAGE Platform os: win32

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 18:24:14.851
!MESSAGE loading cToolsIF

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 18:24:14.861
!MESSAGE loading cTools

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 18:24:14.872
!MESSAGE loading TraceFactory

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 18:24:14.876
!MESSAGE loading sqlite3

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 18:24:14.883
!MESSAGE loading CloudTrace

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 18:24:14.930
!MESSAGE CloudTrace interface loaded

!ENTRY org.eclipse.equinox.p2.updatechecker 4 0 2019-12-17 18:24:50.805
!MESSAGE Exception in update check thread
!STACK 0
org.eclipse.core.runtime.OperationCanceledException
	at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:125)
	at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156)
	at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadIndexFile(AbstractRepositoryManager.java:735)
	at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:657)
	at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
	at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
	at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.addChild(CompositeMetadataRepository.java:166)
	at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.<init>(CompositeMetadataRepository.java:106)
	at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:122)
	at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57)
	at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:768)
	at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:668)
	at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
	at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
	at org.eclipse.equinox.internal.p2.updatechecker.UpdateChecker.getAvailableRepositories(UpdateChecker.java:152)
	at org.eclipse.equinox.internal.p2.updatechecker.UpdateChecker.checkForUpdates(UpdateChecker.java:130)
	at org.eclipse.equinox.internal.p2.updatechecker.UpdateChecker$UpdateCheckThread.run(UpdateChecker.java:74)
!SESSION 2019-12-17 18:27:04.157 -----------------------------------------------
eclipse.buildId=4.7.3.M20180301-0715
java.version=1.8.0_112
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ko_KR
Framework arguments:  -product com.ti.ccstudio.branding.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -product com.ti.ccstudio.branding.product

!ENTRY com.ti.common.core 4 0 2019-12-17 18:27:07.201
!MESSAGE path=ccs_base/DebugServer

!ENTRY com.ti.common.core 4 0 2019-12-17 18:27:07.203
!MESSAGE debugServerDir=C:/ti/ccsv8/ccs_base/DebugServer

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-17 18:27:14.576
!MESSAGE Enablement expression is missing for descriptor type org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-17 18:27:14.583
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-17 18:27:14.584
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 18:27:15.515
!MESSAGE constructor

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 18:27:15.516
!MESSAGE done with directories

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 18:27:15.516
!MESSAGE loading ti_logger

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 18:27:15.517
!MESSAGE Platform os: win32

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 18:27:15.518
!MESSAGE loading cToolsIF

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 18:27:15.520
!MESSAGE loading cTools

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 18:27:15.522
!MESSAGE loading TraceFactory

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 18:27:15.523
!MESSAGE loading sqlite3

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 18:27:15.525
!MESSAGE loading CloudTrace

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-17 18:27:15.533
!MESSAGE CloudTrace interface loaded
!SESSION 2019-12-19 09:16:59.563 -----------------------------------------------
eclipse.buildId=M20120914-1540
java.version=1.6.0_13
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ko_KR
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 2019-12-19 09:17:09.433
!MESSAGE Warnings while parsing the viewer contributions from the 'org.eclipse.ui.popupMenus' extension point
!SUBENTRY 1 org.eclipse.ui 2 0 2019-12-19 09:17:09.433
!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 2019-12-19 09:17:09.433
!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 2019-12-19 09:17:09.433
!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 2019-12-19 09:17:09.433
!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 2019-12-19 09:17:09.433
!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 2019-12-19 09:17:09.433
!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 2019-12-19 09:17:09.433
!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 2019-12-19 09:17:09.433
!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 2019-12-19 09:17:23.750
!MESSAGE Indexed 'cEIP_PEv8' (20 sources, 126 headers) in 3.13 sec: 11,502 declarations; 43,526 references; 1 unresolved inclusions; 5 syntax errors; 387 unresolved names (0.70%)
!SESSION 2019-12-19 09:17:59.719 -----------------------------------------------
eclipse.buildId=4.7.3.M20180301-0715
java.version=1.8.0_112
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ko_KR
Framework arguments:  -product com.ti.ccstudio.branding.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -product com.ti.ccstudio.branding.product

!ENTRY com.ti.common.core 4 0 2019-12-19 09:18:11.032
!MESSAGE path=ccs_base/DebugServer

!ENTRY com.ti.common.core 4 0 2019-12-19 09:18:11.033
!MESSAGE debugServerDir=C:/ti/ccsv8/ccs_base/DebugServer

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-19 09:18:25.884
!MESSAGE Enablement expression is missing for descriptor type org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-19 09:18:25.893
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-19 09:18:25.894
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-19 09:18:26.998
!MESSAGE constructor

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-19 09:18:26.999
!MESSAGE done with directories

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-19 09:18:26.999
!MESSAGE loading ti_logger

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-19 09:18:27.000
!MESSAGE Platform os: win32

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-19 09:18:27.000
!MESSAGE loading cToolsIF

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-19 09:18:27.009
!MESSAGE loading cTools

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-19 09:18:27.031
!MESSAGE loading TraceFactory

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-19 09:18:27.037
!MESSAGE loading sqlite3

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-19 09:18:27.045
!MESSAGE loading CloudTrace

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-19 09:18:27.074
!MESSAGE CloudTrace interface loaded

!ENTRY org.eclipse.cdt.core 1 0 2019-12-19 09:18:30.269
!MESSAGE Indexed 'cEIP_PEv8' (20 sources, 108 headers) in 2.88 sec: 10,946 declarations; 43,759 references; 1 unresolved inclusions; 28 syntax errors; 409 unresolved names (0.74%)

!ENTRY org.eclipse.ui 4 4 2019-12-19 18:16:51.058
!MESSAGE Conflicting handlers for com.ti.ccstudio.multi.purpose.view.ui.TargetSpecificView.rememberSettings: {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@75dbf3} vs {com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$7@1d1170b}

!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 19:48:19.273
!MESSAGE DS_ERROR: TMS320C671X: GEL: Target must be connected before calling the function


!ENTRY org.eclipse.cdt.dsf 4 10005 2019-12-19 19:48:19.287
!MESSAGE Request for monitor: 'RequestMonitor (org.eclipse.cdt.dsf.concurrent.RequestMonitor@63d6f): Status ERROR: com.ti.ccstudio.debug code=20003 Target must be connected before calling the function null' resulted in an error.
!SUBENTRY 1 com.ti.ccstudio.debug 4 20003 2019-12-19 19:48:19.287
!MESSAGE Target must be connected before calling the function

!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 19:58:13.977
!MESSAGE DS_ERROR: TMS320C671X: Trouble Halting Target CPU: Error 0x80000020/-1060 Fatal Error during: Execution,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 19:58:14.058
!MESSAGE DS_ERROR: Trouble Halting Target CPU:
Error 0x80000020/-1060
Fatal Error during: Execution, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 20:06:59.862
!MESSAGE DS_ERROR: TMS320C671X: Trouble Halting Target CPU: Error 0x80000020/-1060 Fatal Error during: Execution,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 20:06:59.890
!MESSAGE DS_ERROR: Trouble Halting Target CPU:
Error 0x80000020/-1060
Fatal Error during: Execution, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 20:07:03.998
!MESSAGE DS_ERROR: TMS320C671X: GEL: Target must be connected before calling the function


!ENTRY org.eclipse.cdt.dsf 4 10005 2019-12-19 20:07:04.000
!MESSAGE Request for monitor: 'RequestMonitor (org.eclipse.cdt.dsf.concurrent.RequestMonitor@1ee7c3): Status ERROR: com.ti.ccstudio.debug code=20003 Target must be connected before calling the function null' resulted in an error.
!SUBENTRY 1 com.ti.ccstudio.debug 4 20003 2019-12-19 20:07:04.000
!MESSAGE Target must be connected before calling the function

!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 20:17:36.143
!MESSAGE DS_ERROR: TMS320C671X: Trouble Halting Target CPU: Error 0x80000020/-1060 Fatal Error during: Execution,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 20:17:36.400
!MESSAGE DS_ERROR: Trouble Halting Target CPU:
Error 0x80000020/-1060
Fatal Error during: Execution, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 20:17:51.475
!MESSAGE DS_ERROR: TMS320C671X: Trouble Halting Target CPU: Error 0x80000020/-1060 Fatal Error during: Execution,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 20:17:51.509
!MESSAGE DS_ERROR: Trouble Halting Target CPU:
Error 0x80000020/-1060
Fatal Error during: Execution, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 20:18:20.777
!MESSAGE DS_ERROR: TMS320C671X: Trouble Halting Target CPU: Error 0x80000020/-1060 Fatal Error during: Execution,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 20:18:20.800
!MESSAGE DS_ERROR: Trouble Halting Target CPU:
Error 0x80000020/-1060
Fatal Error during: Execution, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 20:30:11.670
!MESSAGE DS_ERROR: TMS320C671X: Trouble Halting Target CPU: Error 0x80000020/-1060 Fatal Error during: Execution,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 20:30:11.684
!MESSAGE DS_ERROR: Trouble Halting Target CPU:
Error 0x80000020/-1060
Fatal Error during: Execution, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 20:30:15.953
!MESSAGE DS_ERROR: TMS320C671X: GEL: Target must be connected before calling the function


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 20:53:00.462
!MESSAGE DS_ERROR: TMS320C671X: Trouble Removing Breakpoint with the Action "Remain Halted" at 0x801c5c5c: Error 0x00000008/-1066 Error during: Break Point,  Cannot set/verify breakpoint at 0x801C5C5C  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 20:55:30.778
!MESSAGE DS_ERROR: TMS320C671X: Trouble Halting Target CPU: Error 0x80000020/-1060 Fatal Error during: Execution,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 20:55:30.812
!MESSAGE DS_ERROR: Trouble Halting Target CPU:
Error 0x80000020/-1060
Fatal Error during: Execution, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 20:55:36.058
!MESSAGE DS_ERROR: TMS320C671X: 1 other operation(s) were automatically canceled as a result 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 20:55:41.155
!MESSAGE DS_ERROR: TMS320C671X: Trouble Halting Target CPU: Error 0x80000020/-1060 Fatal Error during: Execution,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 20:55:41.171
!MESSAGE DS_ERROR: Trouble Halting Target CPU:
Error 0x80000020/-1060
Fatal Error during: Execution, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 20:55:43.154
!MESSAGE DS_ERROR: TMS320C671X: 1 other operation(s) were automatically canceled as a result 


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 20:55:53.993
!MESSAGE DS_ERROR: TMS320C671X: Trouble Halting Target CPU: Error 0x80000020/-1060 Fatal Error during: Execution,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 20:55:54.013
!MESSAGE DS_ERROR: Trouble Halting Target CPU:
Error 0x80000020/-1060
Fatal Error during: Execution, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 20:55:58.598
!MESSAGE DS_ERROR: TMS320C671X: File Loader: Verification failed: Could not write 0x80203800: target is not connected


!ENTRY com.ti.ccstudio.debug 1 0 2019-12-19 20:55:58.599
!MESSAGE DS_ERROR: TMS320C671X: GEL: File: D:\work\PUMP\PUMP_V2\1219_CCS8.0\cEIP_PEv8\Debug\cEIP_PEv8.out: Load failed.


!ENTRY org.eclipse.ui 4 0 2019-12-19 21:12:16.537
!MESSAGE Unhandled event loop exception
!STACK 0
org.eclipse.swt.SWTException: Widget is disposed
	at org.eclipse.swt.SWT.error(SWT.java:4533)
	at org.eclipse.swt.SWT.error(SWT.java:4448)
	at org.eclipse.swt.SWT.error(SWT.java:4419)
	at org.eclipse.swt.widgets.Widget.error(Widget.java:482)
	at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:354)
	at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:1091)
	at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:1099)
	at com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView$4.focusGained(TargetSpecificView.java:288)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:140)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4428)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1103)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1084)
	at org.eclipse.swt.widgets.Control.sendFocusEvent(Control.java:2979)
	at org.eclipse.swt.widgets.Widget.wmSetFocus(Widget.java:2437)
	at org.eclipse.swt.widgets.Control.WM_SETFOCUS(Control.java:5490)
	at org.eclipse.swt.widgets.Tree.WM_SETFOCUS(Tree.java:7309)
	at org.eclipse.swt.widgets.Control.windowProc(Control.java:4913)
	at org.eclipse.swt.widgets.Tree.windowProc(Tree.java:6188)
	at org.eclipse.swt.widgets.Display.windowProc(Display.java:5178)
	at org.eclipse.swt.internal.win32.OS.SetFocus(Native Method)
	at org.eclipse.swt.widgets.Control.forceFocus(Control.java:1114)
	at org.eclipse.swt.widgets.Control.setFocus(Control.java:3492)
	at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:1101)
	at com.ti.ccstudio.multi.purpose.view.ui.internal.TargetSpecificView.setFocus(TargetSpecificView.java:525)
	at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.delegateSetFocus(CompatibilityPart.java:216)
	at sun.reflect.GeneratedMethodAccessor62.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:305)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:311)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:233)
	at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:107)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.focusGui(PartRenderingEngine.java:789)
	at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer$1.setFocus(ContributedPartRenderer.java:103)
	at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:1099)
	at org.eclipse.swt.custom.CTabItem.setFocus(CTabItem.java:332)
	at org.eclipse.swt.custom.CTabFolder.setFocus(CTabFolder.java:2619)
	at org.eclipse.swt.widgets.Control.fixFocus(Control.java:1069)
	at org.eclipse.swt.widgets.Control.setVisible(Control.java:4017)
	at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3163)
	at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3171)
	at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:1858)
	at org.eclipse.swt.custom.CTabFolder.lambda$0(CTabFolder.java:328)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4428)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4238)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3817)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
!SESSION 2019-12-20 09:21:16.409 -----------------------------------------------
eclipse.buildId=4.7.3.M20180301-0715
java.version=1.8.0_112
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ko_KR
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.core.resources 2 10035 2019-12-20 09:21:19.576
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

!ENTRY com.ti.common.core 4 0 2019-12-20 09:21:19.656
!MESSAGE path=ccs_base/DebugServer

!ENTRY com.ti.common.core 4 0 2019-12-20 09:21:19.657
!MESSAGE debugServerDir=C:/ti/ccsv8/ccs_base/DebugServer

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-20 09:21:30.290
!MESSAGE Enablement expression is missing for descriptor type org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-20 09:21:30.295
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-20 09:21:30.295
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 09:21:31.068
!MESSAGE constructor

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 09:21:31.097
!MESSAGE done with directories

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 09:21:31.098
!MESSAGE loading ti_logger

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 09:21:31.099
!MESSAGE Platform os: win32

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 09:21:31.099
!MESSAGE loading cToolsIF

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 09:21:31.102
!MESSAGE loading cTools

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 09:21:31.104
!MESSAGE loading TraceFactory

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 09:21:31.108
!MESSAGE loading sqlite3

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 09:21:31.110
!MESSAGE loading CloudTrace

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 09:21:31.128
!MESSAGE CloudTrace interface loaded
!SESSION 2019-12-20 11:33:03.021 -----------------------------------------------
eclipse.buildId=4.7.3.M20180301-0715
java.version=1.8.0_112
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ko_KR
Framework arguments:  -product com.ti.ccstudio.branding.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -product com.ti.ccstudio.branding.product

!ENTRY com.ti.common.core 4 0 2019-12-20 11:33:08.980
!MESSAGE path=ccs_base/DebugServer

!ENTRY com.ti.common.core 4 0 2019-12-20 11:33:08.992
!MESSAGE debugServerDir=C:/ti/ccsv8/ccs_base/DebugServer

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-20 11:33:28.715
!MESSAGE Enablement expression is missing for descriptor type org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-20 11:33:28.728
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-20 11:33:28.730
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 11:33:30.166
!MESSAGE constructor

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 11:33:30.168
!MESSAGE done with directories

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 11:33:30.169
!MESSAGE loading ti_logger

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 11:33:30.170
!MESSAGE Platform os: win32

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 11:33:30.171
!MESSAGE loading cToolsIF

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 11:33:30.177
!MESSAGE loading cTools

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 11:33:30.181
!MESSAGE loading TraceFactory

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 11:33:30.187
!MESSAGE loading sqlite3

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 11:33:30.193
!MESSAGE loading CloudTrace

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 11:33:30.209
!MESSAGE CloudTrace interface loaded

!ENTRY org.eclipse.core.jobs 2 2 2019-12-20 11:34:47.864
!MESSAGE Job found still running after platform shutdown.  Jobs should be canceled by the plugin that scheduled them during shutdown: com.ti.ccstudio.app.center.internal.CCSAppCenter$2

!ENTRY org.eclipse.core.jobs 2 2 2019-12-20 11:34:47.865
!MESSAGE Job found still running after platform shutdown.  Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob

!ENTRY org.eclipse.core.jobs 2 2 2019-12-20 11:34:47.866
!MESSAGE Job found still running after platform shutdown.  Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.equinox.internal.p2.transport.ecf.FileInfoReader

!ENTRY org.eclipse.core.jobs 2 2 2019-12-20 11:34:47.867
!MESSAGE Job found still running after platform shutdown.  Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob

!ENTRY org.eclipse.core.jobs 2 2 2019-12-20 11:34:47.867
!MESSAGE Job found still running after platform shutdown.  Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.equinox.internal.p2.transport.ecf.FileInfoReader
!SESSION 2019-12-20 16:23:52.592 -----------------------------------------------
eclipse.buildId=4.7.3.M20180301-0715
java.version=1.8.0_112
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ko_KR
Framework arguments:  -product com.ti.ccstudio.branding.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -product com.ti.ccstudio.branding.product

!ENTRY com.ti.common.core 4 0 2019-12-20 16:23:56.509
!MESSAGE path=ccs_base/DebugServer

!ENTRY com.ti.common.core 4 0 2019-12-20 16:23:56.519
!MESSAGE debugServerDir=C:/ti/ccsv8/ccs_base/DebugServer

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-20 16:24:10.861
!MESSAGE Enablement expression is missing for descriptor type org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-20 16:24:11.024
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2019-12-20 16:24:11.027
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 16:24:13.778
!MESSAGE constructor

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 16:24:13.780
!MESSAGE done with directories

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 16:24:13.780
!MESSAGE loading ti_logger

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 16:24:13.781
!MESSAGE Platform os: win32

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 16:24:13.782
!MESSAGE loading cToolsIF

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 16:24:13.786
!MESSAGE loading cTools

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 16:24:13.789
!MESSAGE loading TraceFactory

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 16:24:13.793
!MESSAGE loading sqlite3

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 16:24:13.797
!MESSAGE loading CloudTrace

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2019-12-20 16:24:13.808
!MESSAGE CloudTrace interface loaded
!SESSION 2020-01-06 18:58:34.475 -----------------------------------------------
eclipse.buildId=4.7.3.M20180301-0715
java.version=1.8.0_112
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ko_KR
Framework arguments:  -product com.ti.ccstudio.branding.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -product com.ti.ccstudio.branding.product

!ENTRY com.ti.common.core 4 0 2020-01-06 18:58:37.983
!MESSAGE path=ccs_base/DebugServer

!ENTRY com.ti.common.core 4 0 2020-01-06 18:58:37.985
!MESSAGE debugServerDir=C:/ti/ccsv8/ccs_base/DebugServer

!ENTRY org.eclipse.launchbar.core 2 0 2020-01-06 19:00:04.911
!MESSAGE Enablement expression is missing for descriptor type org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2020-01-06 19:00:04.927
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2020-01-06 19:00:04.927
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-06 19:00:06.197
!MESSAGE constructor

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-06 19:00:06.198
!MESSAGE done with directories

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-06 19:00:06.198
!MESSAGE loading ti_logger

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-06 19:00:06.199
!MESSAGE Platform os: win32

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-06 19:00:06.200
!MESSAGE loading cToolsIF

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-06 19:00:06.214
!MESSAGE loading cTools

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-06 19:00:06.252
!MESSAGE loading TraceFactory

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-06 19:00:06.267
!MESSAGE loading sqlite3

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-06 19:00:06.293
!MESSAGE loading CloudTrace

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-06 19:00:06.366
!MESSAGE CloudTrace interface loaded
!SESSION 2020-01-07 19:26:56.691 -----------------------------------------------
eclipse.buildId=4.7.3.M20180301-0715
java.version=1.8.0_112
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ko_KR
Framework arguments:  -product com.ti.ccstudio.branding.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -product com.ti.ccstudio.branding.product

!ENTRY com.ti.common.core 4 0 2020-01-07 19:27:04.186
!MESSAGE path=ccs_base/DebugServer

!ENTRY com.ti.common.core 4 0 2020-01-07 19:27:04.190
!MESSAGE debugServerDir=C:/ti/ccsv8/ccs_base/DebugServer

!ENTRY org.eclipse.launchbar.core 2 0 2020-01-07 19:27:24.194
!MESSAGE Enablement expression is missing for descriptor type org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2020-01-07 19:27:24.223
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2020-01-07 19:27:24.224
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-07 19:27:25.538
!MESSAGE constructor

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-07 19:27:25.542
!MESSAGE done with directories

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-07 19:27:25.547
!MESSAGE loading ti_logger

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-07 19:27:25.550
!MESSAGE Platform os: win32

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-07 19:27:25.550
!MESSAGE loading cToolsIF

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-07 19:27:25.565
!MESSAGE loading cTools

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-07 19:27:25.581
!MESSAGE loading TraceFactory

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-07 19:27:25.589
!MESSAGE loading sqlite3

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-07 19:27:25.600
!MESSAGE loading CloudTrace

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-07 19:27:25.658
!MESSAGE CloudTrace interface loaded

!ENTRY com.ti.ccstudio.debug 1 0 2020-01-07 19:27:40.252
!MESSAGE DS_ERROR: TMS320C671X: GEL: Error loading file 'C:\ti\0523_bootloader\SS_Bootloader_New_UploadPlus_20131212\ceNM_PE_Dbg_v1.3b.gel': unable to open GEL file 'C:\ti\0523_bootloader\SS_Bootloader_New_UploadPlus_20131212\ceNM_PE_Dbg_v1.3b.gel'


!ENTRY com.ti.ccstudio.app.center 4 0 2020-01-07 19:27:49.936
!MESSAGE Unable to read http://software-dl.ti.com/ccs/non-esd/ccs_appcenter/apps_8.3.1.json file.
!STACK 0
java.net.SocketTimeoutException
	at java.net.SocksSocketImpl.remainingMillis(SocksSocketImpl.java:111)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
	at java.net.Socket.connect(Socket.java:589)
	at sun.net.NetworkClient.doConnect(NetworkClient.java:178)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)
	at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)
	at sun.net.www.http.HttpClient.<init>(HttpClient.java:211)
	at sun.net.www.http.HttpClient.New(HttpClient.java:308)
	at sun.net.www.http.HttpClient.New(HttpClient.java:326)
	at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1202)
	at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1138)
	at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1032)
	at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:966)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1546)
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474)
	at java.net.URL.openStream(URL.java:1045)
	at com.ti.ccstudio.app.center.internal.CCSAppCenter.readFile(CCSAppCenter.java:190)
	at com.ti.ccstudio.app.center.internal.CCSAppCenter.getAppJson_0(CCSAppCenter.java:206)
	at com.ti.ccstudio.app.center.internal.CCSAppCenter.access$1(CCSAppCenter.java:205)
	at com.ti.ccstudio.app.center.internal.CCSAppCenter$1.run(CCSAppCenter.java:177)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)

!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 09:26:31.774
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 09:26:32.518
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 09:26:42.631
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 09:26:44.197
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 09:26:51.887
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 09:26:51.918
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 09:26:53.334
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 09:26:53.353
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 09:26:54.657
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 09:26:54.668
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.


!SESSION 2020-01-08 10:00:05.766 -----------------------------------------------
eclipse.buildId=4.7.3.M20180301-0715
java.version=1.8.0_112
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ko_KR
Framework arguments:  -product com.ti.ccstudio.branding.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -product com.ti.ccstudio.branding.product

!ENTRY com.ti.common.core 4 0 2020-01-08 10:00:12.882
!MESSAGE path=ccs_base/DebugServer

!ENTRY com.ti.common.core 4 0 2020-01-08 10:00:12.887
!MESSAGE debugServerDir=C:/ti/ccsv8/ccs_base/DebugServer

!ENTRY org.eclipse.launchbar.core 2 0 2020-01-08 10:00:30.893
!MESSAGE Enablement expression is missing for descriptor type org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2020-01-08 10:00:30.920
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY org.eclipse.launchbar.core 2 0 2020-01-08 10:00:30.921
!MESSAGE Enablement expression is missing for config provider for org.eclipse.cdt.debug.core.coreBuildDescriptorType

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-08 10:00:33.002
!MESSAGE constructor

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-08 10:00:33.003
!MESSAGE done with directories

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-08 10:00:33.003
!MESSAGE loading ti_logger

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-08 10:00:33.004
!MESSAGE Platform os: win32

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-08 10:00:33.005
!MESSAGE loading cToolsIF

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-08 10:00:33.019
!MESSAGE loading cTools

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-08 10:00:33.032
!MESSAGE loading TraceFactory

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-08 10:00:33.038
!MESSAGE loading sqlite3

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-08 10:00:33.045
!MESSAGE loading CloudTrace

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2020-01-08 10:00:33.094
!MESSAGE CloudTrace interface loaded

!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:00:42.521
!MESSAGE DS_ERROR: TMS320C671X: Error initializing emulator 


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:00:42.724
!MESSAGE DS_ERROR: Error initializing emulator


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:00:47.300
!MESSAGE DS_ERROR: TMS320C671X: GEL: Error loading file 'C:\ti\0523_bootloader\SS_Bootloader_New_UploadPlus_20131212\ceNM_PE_Dbg_v1.3b.gel': unable to open GEL file 'C:\ti\0523_bootloader\SS_Bootloader_New_UploadPlus_20131212\ceNM_PE_Dbg_v1.3b.gel'


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:00:51.081
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1063 Fatal Error during: OCS,  Bad Target Silicon Revision Number Please check your multi-processor configuration. The number of devices in the JTAG scan path must be correct for the silicon revision to be read. Or, you may have selected the wrong DSP device driver.  


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:00:51.120
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1063
Fatal Error during: OCS, 
Bad Target Silicon Revision Number
Please check your multi-processor configuration.
The number of devices in the JTAG scan path
must be correct for the silicon revision to be read.
Or, you may have selected the wrong DSP device driver.



!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:00:55.186
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:00:55.205
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:00:57.010
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:00:57.023
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:00:58.316
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:00:58.345
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:00:59.588
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:00:59.607
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:01:13.819
!MESSAGE DS_ERROR: TMS320C671X: File Loader: Verification failed: Values at address 0x80F37000 do not match Please verify target memory and memory map.


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:01:14.055
!MESSAGE DS_ERROR: TMS320C671X: GEL: File: D:\work\PUMP\PUMP_V2\Boot\191212_1 BL_Pump\COMIZOA-PUMP_BLDL10.out: a data verification error occurred, file load failed.


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:01:33.579
!MESSAGE DS_ERROR: TMS320C671X: Failed CPU Reset 


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:01:33.676
!MESSAGE DS_ERROR: TMS320C671X: GEL: Error while executing OnReset(1): identifier not found: EMIF_SDRAMCTL
	 at (int *) EMIF_SDRAMCTL [ceNM_PE.gel:269]
	 at init_emif() [ceNM_PE.gel:63]
	 at OnReset(1)


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:01:38.557
!MESSAGE DS_ERROR: TMS320C671X: Failed CPU Reset 


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:01:38.659
!MESSAGE DS_ERROR: TMS320C671X: GEL: Error while executing OnReset(1): identifier not found: EMIF_SDRAMCTL
	 at (int *) EMIF_SDRAMCTL [ceNM_PE.gel:269]
	 at init_emif() [ceNM_PE.gel:63]
	 at OnReset(1)


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:01:41.518
!MESSAGE DS_ERROR: TMS320C671X: File Loader: Verification failed: Values at address 0x80F37000 do not match Please verify target memory and memory map.


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:01:41.799
!MESSAGE DS_ERROR: TMS320C671X: GEL: File: D:\work\PUMP\PUMP_V2\Boot\191212_1 BL_Pump\COMIZOA-PUMP_BLDL10.out: a data verification error occurred, file load failed.


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:01:48.136
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:01:48.150
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:01:51.461
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:01:51.496
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:01:52.881
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:01:52.912
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.



!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:06:11.762
!MESSAGE DS_ERROR: TMS320C671X: Error connecting to the target: Error 0x80000200/-1060 Fatal Error during: OCS,  An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target.  


!ENTRY com.ti.ccstudio.debug 1 0 2020-01-08 10:06:11.796
!MESSAGE DS_ERROR: Error connecting to the target:
Error 0x80000200/-1060
Fatal Error during: OCS, 
An unknown error prevented the emulator from accessing the processor
in a timely fashion.
It is recommended to RESET EMULATOR.  This will disconnect each 
target from the emulator.  The targets should then be power cycled
or hard reset followed by an emureset and reconnect to each target.


