CORTEX_M4_0: Error connecting to the target: (Error -1063 @ 0x0) Device ID is not recognized or is not supported by driver. Confirm device and debug probe configuration is correct, or update device driver. (Emulation package 6.0.14.5)

Can you try performing a factory reset as per these posts and let us know if that helps?

https://e2e.ti.com/support/microcontrollers/msp430/f/166/t/431831

https://e2e.ti.com/support/microcontrollers/msp430/f/166/t/430158

OK, so a more detailed explanation of what I'm seeing after performing a factory reset, power cycling the board, and attempting to load the blinkLED example is here:

CORTEX_M4_0: GEL Output: Memory Map Initialization Complete
CORTEX_M4_0: GEL Output: Halting Watchdog Timer
CORTEX_M4_0: Flash Programmer: Erasing main memory
CORTEX_M4_0: Flash Programmer: Writing 4040 bytes to flash memory 0x00000000
CORTEX_M4_0: Failed CPU Reset
CORTEX_M4_0: Error occurred during flash operation: CPU Reset failed with error code 1
CORTEX_M4_0: Error occurred during flash operation: Target failed to read 0xE004300C
CORTEX_M4_0: Error occurred during flash operation: Target failed to read 0x4000480C
CORTEX_M4_0: Failed CPU Reset: (Error -2063 @ 0x0) Unable to reset device. Power-cycle the board. If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.14.5)
CORTEX_M4_0: JTAG Communication 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 6.0.14.5)

Also, if I power sycle the board again and re-start CCS, then I get the same original error:

CORTEX_M4_0: Error connecting to the target: (Error -1063 @ 0x0) Device ID is not recognized or is not supported by driver. Confirm device and debug probe configuration is correct, or update device driver. (Emulation package 6.0.14.5) 

Does this provide any clues as to what may be going on?

It sounds like the device is still locked up even after attempting the factory reset. I will move this thread to the MSP430 forum as the experts there might have additional recommendations.

Raged said:

Yes, I did the factory reset as specified in the posts. I have already done that using the directions starting at page 22 of this document www.ti.com/.../slau575b.pdf but I am still having trouble.

Have you tried the suggestion that's part of the FAQ 'Change debugger settings to Serial Wire Debug(SWD) without SWO' found on page 29 of the same PDF? This has helped me fix my communication problems in the past.

Scott

I hope someone can help. In case someone suggests I apply the recent Cortex emulation patch, I already did without any luck.

I was really hopeful.

Any help is appreciated.

Hi David,

I haven't been able to communicate with the boards. Right after I restore factory settings and upload the erase hex file, I get the following error:

After I restart CCS, then I get the original error message that got me here to begin with:

Let me know what the next steps are.

Thank you!

-Edgar

I do NOT have a solution, but perhaps some helpful information.

I get the same error "Error connecting to the target: (Error -1063 @ 0x0)" with my MSP432 Launchpad, but I will add this detail:

DSLite.exe IS able to program the MSP432 LaunchPad.

DSLite.exe was able to program the LaunchPad before I tried to use CCS.
After CCS "killed" the LaunchPad, DSLite could NOT program it either.
I re-enabled the JTAG with the procedure beginning on pg 22 in SLAU575B.pdf.
Then DSLite worked again! (But trying CCS again, killed the Launchpad again, so I repeated the JTAG fix).

Details:

When my MSP432 Launchpad was new, I was able to run:
BlinkLED_MSP432P401R.bat
from folder:
MSP-EXP432P401R_Software_Examples_windows\Firmware\Binary\BlinkLED_MSP432P401R
It programs the MSP432 Launchpad just fine.
Besides the REM's, the batch file is as follows:

:input
@echo MSP-EXP432P401R-LaunchPad Firmware Programmer
set targetconfig=..\DSLite\MSP432P401R.ccxml
set firmware=BlinkLED_MSP432P401R.out
@echo Programing %firmware% into %device% ......
..\DSLite\DebugServer\bin\DSLite.exe -c %targetconfig% -f %firmware%

NOTE: I got the batch files and DSLite from
software-dl.ti.com/.../index_FDS.html
(And, the other examples can also be programmed with their respective batch files.)

I imported the Project into Code Composer Studio Version: 6.1.0.00104 and clicked Debug. The Console said:

CORTEX_M4_0: GEL Output: Memory Map Initialization Complete
CORTEX_M4_0: GEL Output: Halting Watchdog Timer
CORTEX_M4_0: Flash Programmer: Erasing main memory
CORTEX_M4_0: Flash Programmer: Writing 23864 bytes to flash memory 0x00000000
CORTEX_M4_0: Failed CPU Reset
CORTEX_M4_0: Error occurred during flash operation: CPU Reset failed with error code 1
CORTEX_M4_0: Error occurred during flash operation: Target failed to read 0xE004300C
CORTEX_M4_0: Error occurred during flash operation: Target failed to read 0x4000480C
CORTEX_M4_0: Failed CPU Reset: (Error -2063 @ 0x0) Unable to reset device. Power-cycle the board. If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.14.5)
CORTEX_M4_0: JTAG Communication 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 6.0.14.5)


I closed, Unplugged, replugged, reopened CCS again, and clicked debug. This time (and from then on) the following came up in the Console:

CORTEX_M4_0: Error connecting to the target: (Error -1063 @ 0x0) Device ID is not recognized or is not supported by driver. Confirm device and debug probe configuration is correct, or update device driver. (Emulation package 6.0.14.5)

I closed CCS and tried the DSLite batch file BlinkLED_MSP432P401R.bat again.
It did NOT work any more. It said:

MSP-EXP432P401R-LaunchPad Firmware Programmer
Programing BlinkLED_MSP432P401R.out into ......
Initializing debug probe...
Configuring Debugger (may take a few minutes on first launch)...:
Initializing Register Database...
Initializing: CS_DAP_0
Executing Startup Scripts: CS_DAP_0
Initializing: CORTEX_M4_0
Executing Startup Scripts: CORTEX_M4_0
Connecting...
Fatal: CORTEX_M4_0: Error connecting to the target: (Error -1063 @ 0x0)
Device ID is not recognized or is not supported by driver. Confirm device and de
bug probe configuration is correct, or update device driver. (Emulation package
5.1.641.0)
Failed: Failed to evaluate GEL_Connect(): Connect failed
Press any key to continue . . .


Look familiar? Same error as CCS.

I started CCS and followed the procedure beginning on page 22 in SLAU575B.pdf to blank the device.

Then I closed CCS and tried the DSLite batch file BlinkLED_MSP432P401R.bat again.

IT WORKED again.

So DSLite is doing things correctly, but Code Composer Studio 6.1.0.00104 is NOT!

-------------

By the way, this was all done through the MSP432P401R Launchpad
with CCS Connection set to: Texas Instruments XDS110 USB Debug Probe [Default]
and Debug Device set to: Texas Instruments XDS110 USB Debug Probe/CORTEX_M4_0

And, both when it WILL program AND when it will NOT program, the Windows 7 Device Manager still shows:
Ports(COM & LPT)
XDS110 Class Application/User UART (COM4)
XDS110 Class Auxiliary Data Port (COM3)

Added information.

After first successfully using the DSLite to program several different example programs into my MSP432 Launchpad,
I used IAR Embedded Workbench for ARM version 7.40.7.9865 to program the MSP432 Launchpad.
It worked. I was able to create a project, program and debug it on the Launchpad, edit it, program it again. It worked using IAR for ARM.

Then after using CCS, getting the error, and finding that even DSLite could NOT program it any more, I also tried IAR again. And it will NOT program the MSP432 Launchpad any more.
Even after "fixing" the JTAG such that DSLite WILL program it, IAR still can NOT program it any more.

When I hit Download and Debug, whatever code was previously in the Launchpad STOPS running, but IAR just hangs up with a popup that says "Programming flash memory:"

Eventually I click cancel, and then I can see by the time stamp in the log that it did several things and then stopped at "Target reset" (until I hit cancel, then it does "Unloaded macro file").

Thu Oct 15, 2015 19:25:23: Loaded macro file: C:\Program Files (x86)\IAR Systems\Embedded Workbench 7.2\arm\config\debugger\TexasInstruments\MSP432P401R.dmac
Thu Oct 15, 2015 19:25:23: Loaded macro file: C:\Program Files (x86)\IAR Systems\Embedded Workbench 7.2\arm\config\flashloader\TexasInstruments\FlashMSP432P4.mac
Thu Oct 15, 2015 19:25:24: Connecting to TI XDS110 (Probe no: 00000000)
Thu Oct 15, 2015 19:25:25: TI XDS ARM, device revision: 0x00000001, big endian: false, cache: false, board revision: 0x00000000, driver revision: 0x0B020200
Thu Oct 15, 2015 19:25:26: Initial reset was performed
Thu Oct 15, 2015 19:25:26: Resetting device to restore clock configuration
Thu Oct 15, 2015 19:25:26: Halting watchdog timer
Thu Oct 15, 2015 19:25:26: Clearing PCM_CTL LOCK_SD and LOCK_RTC bits
Thu Oct 15, 2015 19:25:26: Enabling all SRAM banks
Thu Oct 15, 2015 19:25:26: 2560 bytes downloaded and verified (14.62 Kbytes/sec)
Thu Oct 15, 2015 19:25:26: Loaded debugee: C:\Program Files (x86)\IAR Systems\Embedded Workbench 7.2\arm\config\flashloader\TexasInstruments\FlashMSP432P4.out
Thu Oct 15, 2015 19:25:26: Target reset
Thu Oct 15, 2015 19:42:25: Unloaded macro file: C:\Program Files (x86)\IAR Systems\Embedded Workbench 7.2\arm\config\flashloader\TexasInstruments\FlashMSP432P4.mac

In IAR I have the Debugger set to: TI XDS110 Emulator

And if I exit IAR and use DSLite, it DOES still work. But I can no longer get IAR to work.

Hope this helps you narrow down the cause.  

PLEASE let us know when CCS is fixed, and if there's anything I can do to get the Launchpad back to working with CCS and IAR.

Thanks,

Jay

Me as well I got this kind of errors with a brand new launchpad (I was also asked to perform the debugger update) and CCS  6.1.0.00104 

CORTEX_M4_0: GEL Output: Memory Map Initialization Complete
CORTEX_M4_0: GEL Output: Halting Watchdog Timer
CORTEX_M4_0: Flash Programmer: Erasing main memory
CORTEX_M4_0: Flash Programmer: Writing 4040 bytes to flash memory 0x00000000
CORTEX_M4_0: Failed CPU Reset: (Error -2063 @ 0x0) Unable to reset device. Power-cycle the board. If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 6.0.14.5)
CORTEX_M4_0: JTAG Communication 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 6.0.14.5)

Annoying if you can't use the stuff provided by TI....

Any workaround ?

Thanks David,  that works for me as well.... 

Thank you for providing this answer and explanation.  I'm struggling with accepting the fact that such a productivity destroying change was rolled out by TI without more fanfare and flashing lights to inform users.   How can I trust the TI tools, which have continually bitten me, when they continue to release changes without considering the negative fallout?  I'm glad to have this particular issue resolved, so thanks again.

HI david,

I am working on dm355evm with  ccs 5.3.

while connecting and loading the basic helloworld code i am getting below error. i am not getting what is the problem.

kindly provide me the solution it will be a great help..

while connecting target getting below error:

ARM9: GEL Output:
DM350EVM ARM Startup Sequence

ARM9: GEL Output: Disable IRQ/FIQ
ARM9: GEL Output: Flush Cache
ARM9: GEL Output: Disable MMU
ARM9: GEL Output: Setup Power Modules (All on)...ARM9: GEL Output: [Done]
ARM9: GEL Output: Setup PinMux...ARM9: GEL Output: [Done]
ARM9: GEL Output: Setup PLL1...ARM9: Trouble Writing Memory Block at 0x1c40938 on Page 0 of Length 0x4: (Error -2030 @ 0x72D7EEF8) Internal error: Access to unknown or invalid register was requested. Restart the application. If error persists, please report the error. (Emulation package 6.0.14.5)
ARM9: GEL: Error while executing OnTargetConnect(): target access failed at (*(pll_cmd)|=0x0001) [evmdm355.gel:431] at Setup_PLL1() [evmdm355.gel:55] at OnTargetConnect() .

after loading hello.out file getting below error:

ARM9: Trouble Writing Memory Block at 0x80000000 on Page 0 of Length 0x46ac: (Error -2030 @ 0x72D68DE4) Internal error: Access to unknown or invalid register was requested. Restart the application. If error persists, please report the error. (Emulation package 6.0.14.5)
ARM9: GEL: File: C:\Users\mohammed.asif\workspace_v5_3_dm355evm\test\Debug\test.out: Load failed.
ARM9: Unable to terminate memory download: NULL buffer pointer at 0x322
ARM9: Error: (Error -1034 @ 0x400) Data bus is 'not ready'. Choose 'Abort' to try to abort the pending transaction. Choose 'Force' to try to force the bus ready state. (Emulation package 6.0.14.5)
ARM9: Unable to determine target status after 20 attempts
ARM9: 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

Regards,

Mohammed asif.

Hi Mohammed,

 Please post your question in the DM3x DaVinci Video Processor Forum

   Regards,

    David

Thanks for timely reply!!  I have the newer version 6.0.83.1 see below pasted ERROR Message.

Error connecting to the target:
(Error -1063 @ 0x0)
Device ID is not recognized or is not supported by driver. Confirm device and debug probe configuration is correct, or update device driver.
(Emulation package 6.0.83.1)

I have ordered a new MSP432 Launchpad and have been able to run the debugger with the same version with no problems.

This problem originated when I was creating separate links to setup a sort of Library type environment.  I lauched the debugger to test my code and the whole debugger environment crashed.  I have no idea what happened.  I do suspect that I had duplicated the targetConfigs file MSP432P401R.ccxml or msp432p401r.cmd file.

As previously mentioned, I have tried everything that I have found in posts, or online, with no sucess.  The only thing that I haven't tried is to get another JTAG debugger and bypass the USB xds110.