!SESSION 2021-11-03 23:08:25.898 -----------------------------------------------
eclipse.buildId=4.14.0.I20191210-0610
java.version=1.8.0_144
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=zh_CN
Framework arguments:  -product com.ti.ccstudio.branding.product
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product com.ti.ccstudio.branding.product

This is a continuation of log file D:\Program\workspace_CCS\1443_low_power_4k_V23_V1\.metadata\.bak_0.log
Created Time: 2021-11-03 23:12:03.206

!ENTRY org.eclipse.equinox.p2.metadata.repository 4 1000 2021-11-03 23:12:03.207
!MESSAGE No repository found at file:/C:/Users/MuMu/AppData/Local/Temp/ccs_264d5901-ee27-41ba-74d9-f4c516c887fe/INSTALLER.

!ENTRY com.ti.ccstudio.project.core 2 0 2021-11-03 23:48:29.964
!MESSAGE Unrecognized option setting '--elf' for tool 'com.ti.ccstudio.buildDefinitions.TMS470_20.2.exe.compilerDebug.308274791'

!ENTRY com.ti.ccstudio.debug 1 0 2021-11-04 09:48:33.614
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-04 09:48:33.655
!MESSAGE DS_ERROR: Cortex_R4_0: Unable to determine target status after 20 attempts


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-04 09:48:33.656
!MESSAGE DS_ERROR: Cortex_R4_0: 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

!SESSION 2021-11-04 10:35:49.156 -----------------------------------------------
eclipse.buildId=4.14.0.I20191210-0610
java.version=1.8.0_144
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=zh_CN
Framework arguments:  -product com.ti.ccstudio.branding.product
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product com.ti.ccstudio.branding.product

!ENTRY com.ti.common.core 1 0 2021-11-04 10:35:58.525
!MESSAGE path=ccs_base/DebugServer

!ENTRY com.ti.common.core 1 0 2021-11-04 10:35:58.526
!MESSAGE debugServerDir=D:/ti/ccs1020/ccs/ccs_base/DebugServer

!ENTRY com.ti.ccstudio.ui 1 0 2021-11-04 10:36:08.375
!MESSAGE CCS IDE session started!
	CCS build: 10.2.0.00009
	CCS location: D:/ti/ccs1020/ccs
	Workspace location: D:/Program/workspace_CCS/1443_low_power_4k_V23_V1

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-04 10:36:08.480
!MESSAGE constructor

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-04 10:36:08.480
!MESSAGE done with directories

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-04 10:36:08.481
!MESSAGE loading ti_logger

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-04 10:36:08.482
!MESSAGE Platform os: win32

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-04 10:36:08.482
!MESSAGE loading cToolsIF

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-04 10:36:08.483
!MESSAGE loading cTools

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-04 10:36:08.485
!MESSAGE loading TraceFactory

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-04 10:36:08.486
!MESSAGE loading sqlite3

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-04 10:36:08.487
!MESSAGE loading CloudTrace

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-04 10:36:08.494
!MESSAGE CloudTrace interface loaded

!ENTRY com.ti.ccstudio.project.ui.webcontent 1 0 2021-11-04 10:36:08.538
!MESSAGE CCS HTTP adapter started! [ccs.port:52103] - Open 'http://localhost:52103/ide' in web browser to see listing of available APIs...

!ENTRY org.eclipse.equinox.p2.metadata.repository 4 1000 2021-11-04 10:38:59.169
!MESSAGE No repository found at file:/C:/Users/MuMu/AppData/Local/Temp/ccs_264d5901-ee27-41ba-74d9-f4c516c887fe/INSTALLER.
!SESSION 2021-11-04 11:26:09.310 -----------------------------------------------
eclipse.buildId=4.14.0.I20191210-0610
java.version=1.8.0_144
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=zh_CN
Framework arguments:  -product com.ti.ccstudio.branding.product
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product com.ti.ccstudio.branding.product

!ENTRY com.ti.common.core 1 0 2021-11-04 11:26:13.325
!MESSAGE path=ccs_base/DebugServer

!ENTRY com.ti.common.core 1 0 2021-11-04 11:26:13.326
!MESSAGE debugServerDir=D:/ti/ccs1020/ccs/ccs_base/DebugServer

!ENTRY com.ti.ccstudio.ui 1 0 2021-11-04 11:26:23.960
!MESSAGE CCS IDE session started!
	CCS build: 10.2.0.00009
	CCS location: D:/ti/ccs1020/ccs
	Workspace location: D:/Program/workspace_CCS/1443_low_power_4k_V23_V1

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-04 11:26:24.080
!MESSAGE constructor

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-04 11:26:24.081
!MESSAGE done with directories

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-04 11:26:24.081
!MESSAGE loading ti_logger

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-04 11:26:24.082
!MESSAGE Platform os: win32

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-04 11:26:24.082
!MESSAGE loading cToolsIF

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-04 11:26:24.084
!MESSAGE loading cTools

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-04 11:26:24.085
!MESSAGE loading TraceFactory

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-04 11:26:24.086
!MESSAGE loading sqlite3

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-04 11:26:24.087
!MESSAGE loading CloudTrace

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-04 11:26:24.095
!MESSAGE CloudTrace interface loaded

!ENTRY com.ti.ccstudio.project.ui.webcontent 1 0 2021-11-04 11:26:24.135
!MESSAGE CCS HTTP adapter started! [ccs.port:59443] - Open 'http://localhost:59443/ide' in web browser to see listing of available APIs...

!ENTRY org.eclipse.equinox.p2.metadata.repository 4 1000 2021-11-04 11:28:37.896
!MESSAGE No repository found at file:/C:/Users/MuMu/AppData/Local/Temp/ccs_264d5901-ee27-41ba-74d9-f4c516c887fe/INSTALLER.

!ENTRY com.ti.ccstudio.debug 1 0 2021-11-04 17:22:59.202
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-04 17:22:59.212
!MESSAGE DS_ERROR: Cortex_R4_0: Unable to determine target status after 20 attempts


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-04 17:22:59.214
!MESSAGE DS_ERROR: Cortex_R4_0: 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 2021-11-05 13:30:04.686
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.687
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.688
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.689
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.689
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.690
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.690
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.691
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.691
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.692
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.693
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.693
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.694
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.694
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.695
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.695
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.696
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.696
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.697
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.697
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.698
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.698
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.699
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.699
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.700
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.700
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.701
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.701
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.702
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.703
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.703
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.704
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.704
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.705
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.705
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.706
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.706
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.707
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.707
!MESSAGE DS_ERROR: Cortex_R4_0: Unable to determine target status after 20 attempts


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:30:04.708
!MESSAGE DS_ERROR: Cortex_R4_0: 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 2021-11-05 13:36:44.548
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:36:44.553
!MESSAGE DS_ERROR: Cortex_R4_0: Unable to determine target status after 20 attempts


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:36:44.554
!MESSAGE DS_ERROR: Cortex_R4_0: 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 2021-11-05 13:37:33.774
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:37:34.243
!MESSAGE DS_ERROR: Cortex_R4_0: Unable to determine target status after 20 attempts


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:37:34.244
!MESSAGE DS_ERROR: Cortex_R4_0: 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 2021-11-05 13:38:11.198
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:38:11.667
!MESSAGE DS_ERROR: Cortex_R4_0: Unable to determine target status after 20 attempts


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 13:38:11.668
!MESSAGE DS_ERROR: Cortex_R4_0: 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 4 0 2021-11-05 15:17:19.896
!MESSAGE An internal error was logged by 'com.ti.ccstudio.debug'.
!STACK 0
java.util.concurrent.ExecutionException: org.json.JSONException: Unable to open USB device - ensure drivers are installed (LIBUSB_ERROR_ACCESS)
	at java.util.concurrent.CompletableFuture.reportGet(Unknown Source)
	at java.util.concurrent.CompletableFuture.get(Unknown Source)
	at com.ti.ccstudio.debug.service.ApplicationService.getConnectedDebugProbes(ApplicationService.java:296)
	at com.ti.ccstudio.debug.service.ApplicationService.detectXDS110ConnectedProbes(ApplicationService.java:356)
	at com.ti.ccstudio.debug.service.ApplicationService.initDebugger(ApplicationService.java:418)
	at com.ti.ccstudio.debug.service.ApplicationService.access$0(ApplicationService.java:408)
	at com.ti.ccstudio.debug.service.ApplicationService$ThreadContextCache.retrieve(ApplicationService.java:136)
	at com.ti.ccstudio.debug.dsf.extensions.concurrent.DataCache.wait(DataCache.java:59)
	at com.ti.ccstudio.debug.service.ApplicationService.getCpuBeingDebugged(ApplicationService.java:1057)
	at com.ti.ccstudio.debug.launch.CCSLaunchDelegate$2.execute(CCSLaunchDelegate.java:139)
	at org.eclipse.cdt.dsf.concurrent.Query.run(Query.java:179)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Caused by: org.json.JSONException: Unable to open USB device - ensure drivers are installed (LIBUSB_ERROR_ACCESS)
	at com.ti.cloudagent.communication.JSONInterface.handleError(JSONInterface.java:211)
	at com.ti.cloudagent.communication.JSONInterface.handleMessage(JSONInterface.java:153)
	at com.ti.cloudagent.communication.JSONInterface.handleIncoming(JSONInterface.java:134)
	at com.ti.cloudagent.communication.JSONInterface.access$000(JSONInterface.java:18)
	at com.ti.cloudagent.communication.JSONInterface$1.run(JSONInterface.java:31)
	... 1 more

!ENTRY com.ti.ccstudio.debug 4 0 2021-11-05 15:17:43.965
!MESSAGE An internal error was logged by 'com.ti.ccstudio.debug'.
!STACK 0
java.util.concurrent.ExecutionException: org.json.JSONException: Unable to open USB device - ensure drivers are installed (LIBUSB_ERROR_ACCESS)
	at java.util.concurrent.CompletableFuture.reportGet(Unknown Source)
	at java.util.concurrent.CompletableFuture.get(Unknown Source)
	at com.ti.ccstudio.debug.service.ApplicationService.getConnectedDebugProbes(ApplicationService.java:296)
	at com.ti.ccstudio.debug.service.ApplicationService.detectXDS110ConnectedProbes(ApplicationService.java:356)
	at com.ti.ccstudio.debug.service.ApplicationService.initDebugger(ApplicationService.java:418)
	at com.ti.ccstudio.debug.service.ApplicationService.access$0(ApplicationService.java:408)
	at com.ti.ccstudio.debug.service.ApplicationService$ThreadContextCache.retrieve(ApplicationService.java:136)
	at com.ti.ccstudio.debug.dsf.extensions.concurrent.DataCache.wait(DataCache.java:59)
	at com.ti.ccstudio.debug.service.ApplicationService.getCpuBeingDebugged(ApplicationService.java:1057)
	at com.ti.ccstudio.debug.launch.CCSLaunchDelegate$2.execute(CCSLaunchDelegate.java:139)
	at org.eclipse.cdt.dsf.concurrent.Query.run(Query.java:179)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Caused by: org.json.JSONException: Unable to open USB device - ensure drivers are installed (LIBUSB_ERROR_ACCESS)
	at com.ti.cloudagent.communication.JSONInterface.handleError(JSONInterface.java:211)
	at com.ti.cloudagent.communication.JSONInterface.handleMessage(JSONInterface.java:153)
	at com.ti.cloudagent.communication.JSONInterface.handleIncoming(JSONInterface.java:134)
	at com.ti.cloudagent.communication.JSONInterface.access$000(JSONInterface.java:18)
	at com.ti.cloudagent.communication.JSONInterface$1.run(JSONInterface.java:31)
	... 1 more

!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 15:17:44.105
!MESSAGE DS_ERROR: CS_DAP_0: Error initializing emulator: (Error -260 @ 0x0) An attempt to connect to the XDS110 failed. The cause may be one or more of: no XDS110 is connected, invalid firmware update, invalid XDS110 serial number, or faulty USB cable. The firmware and serial number may be updated using the xdsdfu utility found in the .../ccs_base/common/uscif/xds110 directory of your installation. View the XDS110SupportReadMe.pdf file there for instructions. (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 15:17:45.704
!MESSAGE DS_ERROR: Error initializing emulator:
(Error -260 @ 0x0)
An attempt to connect to the XDS110 failed.
The cause may be one or more of: no XDS110 is connected, invalid
firmware update, invalid XDS110 serial number, or faulty USB
cable. The firmware and serial number may be updated using the
xdsdfu utility found in the .../ccs_base/common/uscif/xds110
directory of your installation. View the XDS110SupportReadMe.pdf
file there for instructions.
(Emulation package 9.3.0.00032)


!ENTRY org.eclipse.core.jobs 2 2 2021-11-05 15:19:20.438
!MESSAGE Job found still running after platform shutdown.  Jobs should be canceled by the plugin that scheduled them during shutdown: com.ti.ccstudio.debug.internal.ui.ProgressManager$DSJob
!SESSION 2021-11-05 15:19:22.186 -----------------------------------------------
eclipse.buildId=4.14.0.I20191210-0610
java.version=1.8.0_144
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=zh_CN
Framework arguments:  -product com.ti.ccstudio.branding.product
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product com.ti.ccstudio.branding.product

!ENTRY com.ti.common.core 1 0 2021-11-05 15:19:26.857
!MESSAGE path=ccs_base/DebugServer

!ENTRY com.ti.common.core 1 0 2021-11-05 15:19:26.858
!MESSAGE debugServerDir=D:/ti/ccs1020/ccs/ccs_base/DebugServer

!ENTRY com.ti.ccstudio.ui 1 0 2021-11-05 15:19:37.584
!MESSAGE CCS IDE session started!
	CCS build: 10.2.0.00009
	CCS location: D:/ti/ccs1020/ccs
	Workspace location: D:/Program/workspace_CCS/1443_low_power_4k_V23_V1

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-05 15:19:37.699
!MESSAGE constructor

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-05 15:19:37.699
!MESSAGE done with directories

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-05 15:19:37.700
!MESSAGE loading ti_logger

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-05 15:19:37.700
!MESSAGE Platform os: win32

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-05 15:19:37.701
!MESSAGE loading cToolsIF

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-05 15:19:37.703
!MESSAGE loading cTools

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-05 15:19:37.705
!MESSAGE loading TraceFactory

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-05 15:19:37.707
!MESSAGE loading sqlite3

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-05 15:19:37.708
!MESSAGE loading CloudTrace

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-05 15:19:37.719
!MESSAGE CloudTrace interface loaded

!ENTRY com.ti.ccstudio.project.ui.webcontent 1 0 2021-11-05 15:19:37.769
!MESSAGE CCS HTTP adapter started! [ccs.port:58320] - Open 'http://localhost:58320/ide' in web browser to see listing of available APIs...

!ENTRY org.eclipse.equinox.p2.metadata.repository 4 1000 2021-11-05 15:21:47.481
!MESSAGE No repository found at file:/C:/Users/MuMu/AppData/Local/Temp/ccs_264d5901-ee27-41ba-74d9-f4c516c887fe/INSTALLER.

!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 15:23:52.173
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 15:23:52.183
!MESSAGE DS_ERROR: Cortex_R4_0: Unable to determine target status after 20 attempts


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 15:23:52.184
!MESSAGE DS_ERROR: Cortex_R4_0: 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 2021-11-05 15:26:04.532
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 15:26:05.002
!MESSAGE DS_ERROR: Cortex_R4_0: Unable to determine target status after 20 attempts


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 15:26:05.003
!MESSAGE DS_ERROR: Cortex_R4_0: 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 2021-11-05 16:24:40.712
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 16:24:40.717
!MESSAGE DS_ERROR: Cortex_R4_0: Unable to determine target status after 20 attempts


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 16:24:40.718
!MESSAGE DS_ERROR: Cortex_R4_0: 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

!SESSION 2021-11-05 19:13:22.433 -----------------------------------------------
eclipse.buildId=4.14.0.I20191210-0610
java.version=1.8.0_144
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=zh_CN
Framework arguments:  -product com.ti.ccstudio.branding.product
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product com.ti.ccstudio.branding.product

!ENTRY org.eclipse.core.resources 2 10035 2021-11-05 19:13:34.407
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

!ENTRY com.ti.common.core 1 0 2021-11-05 19:13:34.447
!MESSAGE path=ccs_base/DebugServer

!ENTRY com.ti.common.core 1 0 2021-11-05 19:13:34.448
!MESSAGE debugServerDir=D:/ti/ccs1020/ccs/ccs_base/DebugServer

!ENTRY com.ti.ccstudio.ui 1 0 2021-11-05 19:13:45.473
!MESSAGE CCS IDE session started!
	CCS build: 10.2.0.00009
	CCS location: D:/ti/ccs1020/ccs
	Workspace location: D:/Program/workspace_CCS/demo_test (previously: D:/Program/workspace_CCS/1443_low_power_4k_V23_V1)

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-05 19:13:45.663
!MESSAGE constructor

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-05 19:13:45.664
!MESSAGE done with directories

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-05 19:13:45.664
!MESSAGE loading ti_logger

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-05 19:13:45.665
!MESSAGE Platform os: win32

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-05 19:13:45.666
!MESSAGE loading cToolsIF

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-05 19:13:45.669
!MESSAGE loading cTools

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-05 19:13:45.672
!MESSAGE loading TraceFactory

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-05 19:13:45.674
!MESSAGE loading sqlite3

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-05 19:13:45.677
!MESSAGE loading CloudTrace

!ENTRY com.ti.dbgtrc.webapp.CloudTraceInterface 0 0 2021-11-05 19:13:45.691
!MESSAGE CloudTrace interface loaded

!ENTRY com.ti.ccstudio.project.ui.webcontent 1 0 2021-11-05 19:13:45.770
!MESSAGE CCS HTTP adapter started! [ccs.port:58131] - Open 'http://localhost:58131/ide' in web browser to see listing of available APIs...

!ENTRY com.ti.ccstudio.debug 4 0 2021-11-05 19:17:24.720
!MESSAGE An internal error was logged by 'com.ti.ccstudio.debug'.
!STACK 0
java.util.concurrent.ExecutionException: org.json.JSONException: Unable to open USB device - ensure drivers are installed (LIBUSB_ERROR_ACCESS)
	at java.util.concurrent.CompletableFuture.reportGet(Unknown Source)
	at java.util.concurrent.CompletableFuture.get(Unknown Source)
	at com.ti.ccstudio.debug.service.ApplicationService.getConnectedDebugProbes(ApplicationService.java:296)
	at com.ti.ccstudio.debug.service.ApplicationService.detectXDS110ConnectedProbes(ApplicationService.java:356)
	at com.ti.ccstudio.debug.service.ApplicationService.initDebugger(ApplicationService.java:418)
	at com.ti.ccstudio.debug.service.ApplicationService.access$0(ApplicationService.java:408)
	at com.ti.ccstudio.debug.service.ApplicationService$ThreadContextCache.retrieve(ApplicationService.java:136)
	at com.ti.ccstudio.debug.dsf.extensions.concurrent.DataCache.wait(DataCache.java:59)
	at com.ti.ccstudio.debug.service.ApplicationService.getCpuBeingDebugged(ApplicationService.java:1057)
	at com.ti.ccstudio.debug.launch.CCSLaunchDelegate$2.execute(CCSLaunchDelegate.java:139)
	at org.eclipse.cdt.dsf.concurrent.Query.run(Query.java:179)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Caused by: org.json.JSONException: Unable to open USB device - ensure drivers are installed (LIBUSB_ERROR_ACCESS)
	at com.ti.cloudagent.communication.JSONInterface.handleError(JSONInterface.java:211)
	at com.ti.cloudagent.communication.JSONInterface.handleMessage(JSONInterface.java:153)
	at com.ti.cloudagent.communication.JSONInterface.handleIncoming(JSONInterface.java:134)
	at com.ti.cloudagent.communication.JSONInterface.access$000(JSONInterface.java:18)
	at com.ti.cloudagent.communication.JSONInterface$1.run(JSONInterface.java:31)
	... 1 more

!ENTRY org.eclipse.equinox.p2.metadata.repository 4 1000 2021-11-05 19:17:30.954
!MESSAGE No repository found at file:/C:/Users/MuMu/AppData/Local/Temp/ccs_264d5901-ee27-41ba-74d9-f4c516c887fe/INSTALLER.

!ENTRY com.ti.ccstudio.debug 4 0 2021-11-05 19:17:48.824
!MESSAGE An internal error was logged by 'com.ti.ccstudio.debug'.
!STACK 0
java.util.concurrent.ExecutionException: org.json.JSONException: Unable to open USB device - ensure drivers are installed (LIBUSB_ERROR_ACCESS)
	at java.util.concurrent.CompletableFuture.reportGet(Unknown Source)
	at java.util.concurrent.CompletableFuture.get(Unknown Source)
	at com.ti.ccstudio.debug.service.ApplicationService.getConnectedDebugProbes(ApplicationService.java:296)
	at com.ti.ccstudio.debug.service.ApplicationService.detectXDS110ConnectedProbes(ApplicationService.java:356)
	at com.ti.ccstudio.debug.service.ApplicationService.initDebugger(ApplicationService.java:418)
	at com.ti.ccstudio.debug.service.ApplicationService.access$0(ApplicationService.java:408)
	at com.ti.ccstudio.debug.service.ApplicationService$ThreadContextCache.retrieve(ApplicationService.java:136)
	at com.ti.ccstudio.debug.dsf.extensions.concurrent.DataCache.wait(DataCache.java:59)
	at com.ti.ccstudio.debug.service.ApplicationService.getCpuBeingDebugged(ApplicationService.java:1057)
	at com.ti.ccstudio.debug.launch.CCSLaunchDelegate$2.execute(CCSLaunchDelegate.java:139)
	at org.eclipse.cdt.dsf.concurrent.Query.run(Query.java:179)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Caused by: org.json.JSONException: Unable to open USB device - ensure drivers are installed (LIBUSB_ERROR_ACCESS)
	at com.ti.cloudagent.communication.JSONInterface.handleError(JSONInterface.java:211)
	at com.ti.cloudagent.communication.JSONInterface.handleMessage(JSONInterface.java:153)
	at com.ti.cloudagent.communication.JSONInterface.handleIncoming(JSONInterface.java:134)
	at com.ti.cloudagent.communication.JSONInterface.access$000(JSONInterface.java:18)
	at com.ti.cloudagent.communication.JSONInterface$1.run(JSONInterface.java:31)
	... 1 more

!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 19:17:48.991
!MESSAGE DS_ERROR: CS_DAP_0: Error initializing emulator: (Error -260 @ 0x0) An attempt to connect to the XDS110 failed. The cause may be one or more of: no XDS110 is connected, invalid firmware update, invalid XDS110 serial number, or faulty USB cable. The firmware and serial number may be updated using the xdsdfu utility found in the .../ccs_base/common/uscif/xds110 directory of your installation. View the XDS110SupportReadMe.pdf file there for instructions. (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 19:17:49.499
!MESSAGE DS_ERROR: Error initializing emulator:
(Error -260 @ 0x0)
An attempt to connect to the XDS110 failed.
The cause may be one or more of: no XDS110 is connected, invalid
firmware update, invalid XDS110 serial number, or faulty USB
cable. The firmware and serial number may be updated using the
xdsdfu utility found in the .../ccs_base/common/uscif/xds110
directory of your installation. View the XDS110SupportReadMe.pdf
file there for instructions.
(Emulation package 9.3.0.00032)


!ENTRY com.ti.ccstudio.debug 4 0 2021-11-05 20:36:49.290
!MESSAGE An internal error was logged by 'com.ti.ccstudio.debug'.
!STACK 0
java.util.concurrent.ExecutionException: org.json.JSONException: Unable to open USB device - ensure drivers are installed (LIBUSB_ERROR_ACCESS)
	at java.util.concurrent.CompletableFuture.reportGet(Unknown Source)
	at java.util.concurrent.CompletableFuture.get(Unknown Source)
	at com.ti.ccstudio.debug.service.ApplicationService.getConnectedDebugProbes(ApplicationService.java:296)
	at com.ti.ccstudio.debug.service.ApplicationService.detectXDS110ConnectedProbes(ApplicationService.java:356)
	at com.ti.ccstudio.debug.service.ApplicationService.initDebugger(ApplicationService.java:418)
	at com.ti.ccstudio.debug.service.ApplicationService.access$0(ApplicationService.java:408)
	at com.ti.ccstudio.debug.service.ApplicationService$ThreadContextCache.retrieve(ApplicationService.java:136)
	at com.ti.ccstudio.debug.dsf.extensions.concurrent.DataCache.wait(DataCache.java:59)
	at com.ti.ccstudio.debug.service.ApplicationService.getCpuBeingDebugged(ApplicationService.java:1057)
	at com.ti.ccstudio.debug.launch.CCSLaunchDelegate$2.execute(CCSLaunchDelegate.java:139)
	at org.eclipse.cdt.dsf.concurrent.Query.run(Query.java:179)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)
Caused by: org.json.JSONException: Unable to open USB device - ensure drivers are installed (LIBUSB_ERROR_ACCESS)
	at com.ti.cloudagent.communication.JSONInterface.handleError(JSONInterface.java:211)
	at com.ti.cloudagent.communication.JSONInterface.handleMessage(JSONInterface.java:153)
	at com.ti.cloudagent.communication.JSONInterface.handleIncoming(JSONInterface.java:134)
	at com.ti.cloudagent.communication.JSONInterface.access$000(JSONInterface.java:18)
	at com.ti.cloudagent.communication.JSONInterface$1.run(JSONInterface.java:31)
	... 1 more

!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:36:49.492
!MESSAGE DS_ERROR: CS_DAP_0: Error initializing emulator: (Error -260 @ 0x0) An attempt to connect to the XDS110 failed. The cause may be one or more of: no XDS110 is connected, invalid firmware update, invalid XDS110 serial number, or faulty USB cable. The firmware and serial number may be updated using the xdsdfu utility found in the .../ccs_base/common/uscif/xds110 directory of your installation. View the XDS110SupportReadMe.pdf file there for instructions. (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:36:49.926
!MESSAGE DS_ERROR: Error initializing emulator:
(Error -260 @ 0x0)
An attempt to connect to the XDS110 failed.
The cause may be one or more of: no XDS110 is connected, invalid
firmware update, invalid XDS110 serial number, or faulty USB
cable. The firmware and serial number may be updated using the
xdsdfu utility found in the .../ccs_base/common/uscif/xds110
directory of your installation. View the XDS110SupportReadMe.pdf
file there for instructions.
(Emulation package 9.3.0.00032)


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.295
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.320
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.346
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.371
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.396
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.422
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.447
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.472
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.497
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.523
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.548
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.573
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.599
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.624
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.649
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.675
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.700
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.725
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.751
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.776
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.801
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.826
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.852
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.877
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.902
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.927
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.953
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:46.978
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:47.003
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:47.029
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:47.042
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:47.043
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:47.043
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:47.044
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:47.044
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:47.045
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:47.045
!MESSAGE DS_ERROR: Cortex_R4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:47.046
!MESSAGE DS_ERROR: Cortex_R4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 9.3.0.00032) 


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:47.046
!MESSAGE DS_ERROR: Cortex_R4_0: Unable to determine target status after 20 attempts


!ENTRY com.ti.ccstudio.debug 1 0 2021-11-05 20:47:47.048
!MESSAGE DS_ERROR: Cortex_R4_0: 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 org.eclipse.core.jobs 4 2 2021-11-05 21:28:49.737
!MESSAGE Unhandled error
!STACK 0
org.eclipse.swt.SWTException: Device is disposed
	at org.eclipse.swt.SWT.error(SWT.java:4720)
	at org.eclipse.swt.SWT.error(SWT.java:4635)
	at org.eclipse.swt.SWT.error(SWT.java:4606)
	at org.eclipse.swt.widgets.Display.error(Display.java:1193)
	at org.eclipse.swt.widgets.Display.asyncExec(Display.java:689)
	at org.eclipse.jface.operation.AccumulatingProgressMonitor.done(AccumulatingProgressMonitor.java:183)
	at java.lang.Iterable.forEach(Unknown Source)
	at java.util.Collections$UnmodifiableCollection.forEach(Unknown Source)
	at org.eclipse.ui.internal.progress.ProgressManager$JobMonitor.done(ProgressManager.java:268)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:74)

!ENTRY org.eclipse.core.jobs 2 2 2021-11-05 21:28:50.135
!MESSAGE Job found still running after platform shutdown.  Jobs should be canceled by the plugin that scheduled them during shutdown: com.ti.ccstudio.debug.internal.ui.ProgressManager$DSJob
