!SESSION 2020-02-11 08:56:15.442 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_141
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=ru_RU
Command-line arguments:  -os win32 -ws win32 -arch x86_64

!ENTRY org.eclipse.cdt.ui 2 0 2020-02-11 08:56:34.496
!MESSAGE Default project not found in New C/C++ Project Wizard

!ENTRY dsp1967.toolchain.llvm 1 0 2020-02-11 08:56:57.532
!MESSAGE Project Test_SDRAM_prj has been converted to new format version 1.8.0.
Total options converted - 4

!ENTRY org.eclipse.cdt.core 1 0 2020-02-11 08:56:58.672
!MESSAGE Indexed 'Test_SDRAM_prj' (21 sources, 32 headers) in 1,03 sec: 4 529 declarations; 9 779 references; 0 unresolved inclusions; 2 syntax errors; 40 unresolved names (0,28 %)

!ENTRY org.eclipse.cdt.core 1 0 2020-02-11 08:59:05.742
!MESSAGE Indexed 'Test_SDRAM' (21 sources, 32 headers) in 0,391 sec: 4 529 declarations; 9 779 references; 0 unresolved inclusions; 2 syntax errors; 40 unresolved names (0,28 %)

!ENTRY org.eclipse.cdt.dsf.gdb 4 5012 2020-02-11 09:31:24.587
!MESSAGE Error in final launch sequence
!STACK 1
org.eclipse.core.runtime.CoreException: Failed to execute MI command:
-jem-connect
Error message from debugger back end:
Command 'jem-connect'. Error: JEM ERROR 276: Отсутствует питание на целевом устройстве
	at org.eclipse.cdt.dsf.concurrent.Query.get(Query.java:111)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugSession(GdbLaunchDelegate.java:235)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugger(GdbLaunchDelegate.java:111)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launch(GdbLaunchDelegate.java:99)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at dsp1967.debug.lldb.MultiSessionLaunchDelegate.buildAndLaunch(MultiSessionLaunchDelegate.java:236)
	at dsp1967.debug.lldb.MultiSessionLaunchDelegate.launch(MultiSessionLaunchDelegate.java:92)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
	at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.lang.Exception: 
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:926)
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:755)
!SUBENTRY 1 org.eclipse.cdt.dsf.gdb 4 10004 2020-02-11 09:31:24.587
!MESSAGE Failed to execute MI command:
-jem-connect
Error message from debugger back end:
Command 'jem-connect'. Error: JEM ERROR 276: Отсутствует питание на целевом устройстве
!STACK 0
java.lang.Exception: 
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:926)
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:755)

!ENTRY org.eclipse.core.jobs 4 2 2020-02-11 09:31:48.786
!MESSAGE An internal error occurred during: "Suspend monitor job.".
!STACK 0
java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@29d04acd rejected from org.eclipse.cdt.dsf.concurrent.DefaultDsfExecutor@5a81f1fd[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 1669]
	at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063)
	at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830)
	at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:326)
	at java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:533)
	at org.eclipse.cdt.dsf.concurrent.DefaultDsfExecutor.schedule(DefaultDsfExecutor.java:438)
	at java.util.concurrent.ScheduledThreadPoolExecutor.submit(ScheduledThreadPoolExecutor.java:632)
	at org.eclipse.cdt.dsf.concurrent.DefaultDsfExecutor.submit(DefaultDsfExecutor.java:470)
	at org.eclipse.cdt.dsf.gdb.service.GDBRunControl_7_0_NS$MonitorSuspendJob.run(GDBRunControl_7_0_NS.java:684)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

!ENTRY org.eclipse.cdt.dsf.gdb 4 5012 2020-02-11 10:29:01.825
!MESSAGE Error in final launch sequence
!STACK 1
org.eclipse.core.runtime.CoreException: Failed to execute MI command:
-jem-connect
Error message from debugger back end:
Command 'jem-connect'. Error: JEM ERROR 276: Отсутствует питание на целевом устройстве
	at org.eclipse.cdt.dsf.concurrent.Query.get(Query.java:111)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugSession(GdbLaunchDelegate.java:235)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugger(GdbLaunchDelegate.java:111)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launch(GdbLaunchDelegate.java:99)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at dsp1967.debug.lldb.MultiSessionLaunchDelegate.buildAndLaunch(MultiSessionLaunchDelegate.java:236)
	at dsp1967.debug.lldb.MultiSessionLaunchDelegate.launch(MultiSessionLaunchDelegate.java:92)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
	at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.lang.Exception: 
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:926)
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:755)
!SUBENTRY 1 org.eclipse.cdt.dsf.gdb 4 10004 2020-02-11 10:29:01.825
!MESSAGE Failed to execute MI command:
-jem-connect
Error message from debugger back end:
Command 'jem-connect'. Error: JEM ERROR 276: Отсутствует питание на целевом устройстве
!STACK 0
java.lang.Exception: 
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:926)
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:755)
!SESSION 2020-02-12 09:30:00.598 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_141
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=ru_RU
Command-line arguments:  -os win32 -ws win32 -arch x86_64

!ENTRY org.eclipse.cdt.dsf.gdb 4 5012 2020-02-12 09:43:44.907
!MESSAGE Error in final launch sequence
!STACK 1
org.eclipse.core.runtime.CoreException: Failed to execute MI command:
-jem-reset --hard --halt --cores 0,1
Error message from debugger back end:
Command 'jem-reset'. Error: hard reset failed: JEM ERROR 276: Отсутствует питание на целевом устройстве
	at org.eclipse.cdt.dsf.concurrent.Query.get(Query.java:111)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugSession(GdbLaunchDelegate.java:235)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugger(GdbLaunchDelegate.java:111)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launch(GdbLaunchDelegate.java:99)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at dsp1967.debug.lldb.MultiSessionLaunchDelegate.buildAndLaunch(MultiSessionLaunchDelegate.java:236)
	at dsp1967.debug.lldb.MultiSessionLaunchDelegate.launch(MultiSessionLaunchDelegate.java:92)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
	at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.lang.Exception: 
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:926)
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:755)
!SUBENTRY 1 org.eclipse.cdt.dsf.gdb 4 10004 2020-02-12 09:43:44.907
!MESSAGE Failed to execute MI command:
-jem-reset --hard --halt --cores 0,1
Error message from debugger back end:
Command 'jem-reset'. Error: hard reset failed: JEM ERROR 276: Отсутствует питание на целевом устройстве
!STACK 0
java.lang.Exception: 
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:926)
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:755)

!ENTRY org.eclipse.cdt.dsf.gdb 4 5012 2020-02-12 09:44:02.159
!MESSAGE Error in final launch sequence
!STACK 1
org.eclipse.core.runtime.CoreException: Failed to execute MI command:
-jem-connect
Error message from debugger back end:
Command 'jem-connect'. Error: JEM ERROR 276: Отсутствует питание на целевом устройстве
	at org.eclipse.cdt.dsf.concurrent.Query.get(Query.java:111)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugSession(GdbLaunchDelegate.java:235)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugger(GdbLaunchDelegate.java:111)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launch(GdbLaunchDelegate.java:99)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at dsp1967.debug.lldb.MultiSessionLaunchDelegate.buildAndLaunch(MultiSessionLaunchDelegate.java:236)
	at dsp1967.debug.lldb.MultiSessionLaunchDelegate.launch(MultiSessionLaunchDelegate.java:92)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
	at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.lang.Exception: 
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:926)
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:755)
!SUBENTRY 1 org.eclipse.cdt.dsf.gdb 4 10004 2020-02-12 09:44:02.159
!MESSAGE Failed to execute MI command:
-jem-connect
Error message from debugger back end:
Command 'jem-connect'. Error: JEM ERROR 276: Отсутствует питание на целевом устройстве
!STACK 0
java.lang.Exception: 
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:926)
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:755)

!ENTRY org.eclipse.cdt.dsf.gdb 4 5012 2020-02-12 09:44:21.680
!MESSAGE Error in final launch sequence
!STACK 1
org.eclipse.core.runtime.CoreException: Failed to execute MI command:
-jem-connect
Error message from debugger back end:
Command 'jem-connect'. Error: JEM ERROR 276: Отсутствует питание на целевом устройстве
	at org.eclipse.cdt.dsf.concurrent.Query.get(Query.java:111)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugSession(GdbLaunchDelegate.java:235)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugger(GdbLaunchDelegate.java:111)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launch(GdbLaunchDelegate.java:99)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at dsp1967.debug.lldb.MultiSessionLaunchDelegate.buildAndLaunch(MultiSessionLaunchDelegate.java:236)
	at dsp1967.debug.lldb.MultiSessionLaunchDelegate.launch(MultiSessionLaunchDelegate.java:92)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
	at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.lang.Exception: 
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:926)
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:755)
!SUBENTRY 1 org.eclipse.cdt.dsf.gdb 4 10004 2020-02-12 09:44:21.680
!MESSAGE Failed to execute MI command:
-jem-connect
Error message from debugger back end:
Command 'jem-connect'. Error: JEM ERROR 276: Отсутствует питание на целевом устройстве
!STACK 0
java.lang.Exception: 
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:926)
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:755)

!ENTRY org.eclipse.cdt.dsf.gdb 4 5012 2020-02-12 09:49:28.940
!MESSAGE Error in final launch sequence
!STACK 1
org.eclipse.core.runtime.CoreException: Failed to execute MI command:
-jem-connect
Error message from debugger back end:
Command 'jem-connect'. Error: JEM ERROR 276: Отсутствует питание на целевом устройстве
	at org.eclipse.cdt.dsf.concurrent.Query.get(Query.java:111)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugSession(GdbLaunchDelegate.java:235)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugger(GdbLaunchDelegate.java:111)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launch(GdbLaunchDelegate.java:99)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at dsp1967.debug.lldb.MultiSessionLaunchDelegate.buildAndLaunch(MultiSessionLaunchDelegate.java:236)
	at dsp1967.debug.lldb.MultiSessionLaunchDelegate.launch(MultiSessionLaunchDelegate.java:92)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
	at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.lang.Exception: 
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:926)
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:755)
!SUBENTRY 1 org.eclipse.cdt.dsf.gdb 4 10004 2020-02-12 09:49:28.940
!MESSAGE Failed to execute MI command:
-jem-connect
Error message from debugger back end:
Command 'jem-connect'. Error: JEM ERROR 276: Отсутствует питание на целевом устройстве
!STACK 0
java.lang.Exception: 
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:926)
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:755)

!ENTRY org.eclipse.cdt.dsf.gdb 4 5012 2020-02-12 10:48:46.999
!MESSAGE Error in final launch sequence
!STACK 1
org.eclipse.core.runtime.CoreException: Failed to execute MI command:
-jem-connect
Error message from debugger back end:
Command 'jem-connect'. Error: JEM ERROR 276: Отсутствует питание на целевом устройстве
	at org.eclipse.cdt.dsf.concurrent.Query.get(Query.java:111)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugSession(GdbLaunchDelegate.java:235)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugger(GdbLaunchDelegate.java:111)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launch(GdbLaunchDelegate.java:99)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at dsp1967.debug.lldb.MultiSessionLaunchDelegate.buildAndLaunch(MultiSessionLaunchDelegate.java:236)
	at dsp1967.debug.lldb.MultiSessionLaunchDelegate.launch(MultiSessionLaunchDelegate.java:92)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
	at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.lang.Exception: 
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:926)
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:755)
!SUBENTRY 1 org.eclipse.cdt.dsf.gdb 4 10004 2020-02-12 10:48:46.999
!MESSAGE Failed to execute MI command:
-jem-connect
Error message from debugger back end:
Command 'jem-connect'. Error: JEM ERROR 276: Отсутствует питание на целевом устройстве
!STACK 0
java.lang.Exception: 
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:926)
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:755)

!ENTRY org.eclipse.cdt.dsf 4 10005 2020-02-12 10:53:39.539
!MESSAGE Request for monitor: 'RequestMonitor (org.eclipse.cdt.dsf.concurrent.RequestMonitor@48e07207): Status ERROR: org.eclipse.cdt.dsf.gdb code=10001 Connection is shut down null' resulted in an error.
!SUBENTRY 1 org.eclipse.cdt.dsf.gdb 4 10001 2020-02-12 10:53:39.539
!MESSAGE Connection is shut down

!ENTRY org.eclipse.cdt.dsf.gdb 4 5012 2020-02-12 11:30:48.441
!MESSAGE Error in final launch sequence
!STACK 1
org.eclipse.core.runtime.CoreException: Failed to execute MI command:
-jem-reset --halt --soft 2 --cores 1
Error message from debugger back end:
Command 'jem-reset'. Error: reset failed: JEM ERROR 519: Unknown error occured, please contact developers.
	at org.eclipse.cdt.dsf.concurrent.Query.get(Query.java:111)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugSession(GdbLaunchDelegate.java:235)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugger(GdbLaunchDelegate.java:111)
	at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launch(GdbLaunchDelegate.java:99)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at dsp1967.debug.lldb.MultiSessionLaunchDelegate.buildAndLaunch(MultiSessionLaunchDelegate.java:236)
	at dsp1967.debug.lldb.MultiSessionLaunchDelegate.launch(MultiSessionLaunchDelegate.java:126)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
	at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
	at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
	at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.lang.Exception: 
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:926)
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:755)
!SUBENTRY 1 org.eclipse.cdt.dsf.gdb 4 10004 2020-02-12 11:30:48.441
!MESSAGE Failed to execute MI command:
-jem-reset --halt --soft 2 --cores 1
Error message from debugger back end:
Command 'jem-reset'. Error: reset failed: JEM ERROR 519: Unknown error occured, please contact developers.
!STACK 0
java.lang.Exception: 
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:926)
	at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:755)
