View -> Target Configurations -> User Defined -> xml (I renamed this file) -> Basic tab (select XDS110 debugger, MSP432) -> Advanced tab -> Texas Instruments XDS110 USB Debug Probe_0. XDS200), related to this thread.įor your board that's encountering "Error connecting to the target: Error -613", can you try the following steps? Using a project that intentionally bricked the MSP432 (thanks DavidL), I encountered this error but was able to successfully complete the Factory Reset. Connect only to the Non-Debuggable Devices > DAP.Īnother approach may be to perform the factory reset using an external debugger (e.g. ccmxl file being the root > something_CORTEX_M4_something (unknown) Under Debug window you should now see some tree structure starting with the. Within Target Configuration navigate to your MSP432 project > the. Open CCS, assume you already have at least one MSP432 project open. Connect the failing LaunchPad/unit to your PC. Are these the steps you've been following? 
If this error is originated in software, it can potentially be recovered by accessing the DAP directly and trying to either reset the offending core, lock it or erase its flash memory via a GEL script (some microcontrollers have pre-loaded routines to allow that).įor detailed factory reset instructions, take a look at Section 8 in the Code Composer Studio 6.1 for MSP432 User's Guide. This is usually caused by either a hardware failure on the board or invalid code on the subcore that causes it to reset itself continuously.
According to the Debugging JTAG Connectivity Problems wiki page, this error is caused by the inability of the JTAG debugger to access the DAP or one of its ARM subcores.
0 kommentar(er)
