Resolved

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)

Raged

Replies: 34

Views: 38593

Hi ,

I have a rather puzzling issue. I get the following error when trying to debug the MSP-EXP432P401R using the BlinkLED_MSP432P401R example:

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 have been able to run several programs up until earlier this morning, and, all of the sudden, the board just stopped communicating.

Was there a recent update?

I have downloaded and installed (re-installed?) the ti_emupack_setup_6.0.14.5_win_32.exe in an attempt to fix any software driver issues, but the problem remains unchanged.

Mastermind 24125 points

DavidL
- Oct 15, 2015 6:13 PM
In reply to Raged:

Hi Edgar,

Please send me a private message with your contact information (you can click on my profile and send me a private message that way), I would like to get your board and I will send you a new one.

Thanks,

David
- Locked
- Cancel
Do you have another question?

We are glad that we were able to resolve this issue, and will now proceed to close this thread.

If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.

Ask a related question Ask a new question
Mastermind 24125 points

DavidL
- Oct 15, 2015 9:06 PM
In reply to DavidL:

This is being handled offline.
- Locked
- Cancel
Do you have another question?

We are glad that we were able to resolve this issue, and will now proceed to close this thread.

If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.

Ask a related question Ask a new question
Prodigy 50 points

Jay Paxman
- Oct 15, 2015 11:41 PM
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
- Locked
- Cancel
Do you have another question?

We are glad that we were able to resolve this issue, and will now proceed to close this thread.

If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.

Ask a related question Ask a new question
Intellectual 775 points

Raged
- Oct 16, 2015 2:25 PM
In reply to Jay Paxman:

Hi Jay,
Thanks for sharing your experience. Yeah, it's been a very similar situation for me. I've been able to program using CCS for at least a week and then Monday all of the sudden, my board stopped working. Not only that, but my second board also stopped working as soon as I tried to connect it to CCS. Yeah, i think the issues is with CCS. At some point I even uninstalled/re-installed CCS but had no luck. I'm hopping they fix this quickly. It is eating into my development time.
Thanks,
-Edgar
- Locked
- Cancel
Do you have another question?

We are glad that we were able to resolve this issue, and will now proceed to close this thread.

If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.

Ask a related question Ask a new question
Intellectual 775 points

Raged
- Oct 19, 2015 5:54 PM
In reply to DavidL:

Hi David,
I received the board yo sent and was asked to first allow an update for the debugger. It said "do not unplug the debug probe" while update was taking place. I did that, and here's the error message I got:

CS_DAP_0: Error connecting to the target: (Error -1040 @ 0x0) A firmware update is required for the debug probe. Click the "Update" button to update the firmware and connect to the debug target. DO NOT UNPLUG THE DEBUG PROBE DURING THE UPDATE. (Emulation package 6.0.14.5)
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: JTAG Communication Error: (Error -615 @ 0x0) The target failed to see a correctly formatted SWD header. The connection to the target may be unreliable. Try lowering the TCLK setting before trying again. (Emulation package 6.0.14.5)
CORTEX_M4_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

And I am back to the same issues I previously had with my other two boards. I also got a brand new board in today from digikey....and I was also asked to update the debug probe. Same issues with this board. Let me know if you have any suggestions. I'm sending my original board and the board you sent me to you.
Thanks,
-Edgar
- Locked
- Cancel
Do you have another question?

We are glad that we were able to resolve this issue, and will now proceed to close this thread.

If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.

Ask a related question Ask a new question
Intellectual 470 points

Jean michel LECONTE1
- Oct 20, 2015 12:42 AM
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 ?
- Locked
- Cancel
Do you have another question?

We are glad that we were able to resolve this issue, and will now proceed to close this thread.

If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.

Ask a related question Ask a new question
Intellectual 775 points

Raged
- Oct 20, 2015 9:34 PM
In reply to Jean michel LECONTE1:

Hi Jean,
No fixes yet. TI is looking into this. If nothing works for you, I'd recommend getting an external debugger (that's going to be my next step). I think the TMDSEMU100V2U-ARM emulator ($80) is compatible with the MSP432 board but double check to confirm.
-Edgar
- Locked
- Cancel
Do you have another question?

We are glad that we were able to resolve this issue, and will now proceed to close this thread.

If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.

Ask a related question Ask a new question
Mastermind 24125 points

DavidL
- Oct 21, 2015 6:56 PM
In reply to Raged:

Hi Edgar,

First of all thanks for your patience. Finally, we were able to find the root cause of this problem.

There is an update on CCS (MSP432 Emulators 6.1.1.2) that modifies the default MSP432 linker (msp432p401r.cmd) and startup files (msp432_startup_ccs.c), these files are copied/used every time you create a new project and are located in C:\ti\ccsv6\ccs_base\arm\include\

What changed on these files??
The "--retain=interruptVectors" in the linker file was moved to the startup as "#pragma RETAIN(interruptVectors)

Why these changes cause the CORTEX_M4_0: Error connecting to the target: (Error -1063 @ 0x0) Device ID error??
Most of the MSPWare projects, tell CCS to use an specific startup file (part of mspware) when they got imported, the problem is that this startup file is not compatible with the default linker anymore, it is missing the #pragma RETAIN(interruptVectors).

Your project will build without reserving this area and it will place some of your application code in here, this will cause the MSP432 to behave unexpectedly , reset, ilop and the result of this will cause the Error connecting to the target.

Is there a Workaround??
Yes,
1. In your project, make sure that you have --retain=interruptVectors in your linker file or #pragma RETAIN(interruptVectors) in your startup
2. Run the Factory reset - e2e.ti.com/.../430158
3. Build/download your project with the updated linker or start up file

Best regards,

David
- Locked
- Cancel
Do you have another question?

We are glad that we were able to resolve this issue, and will now proceed to close this thread.

If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.

Ask a related question Ask a new question
Intellectual 775 points

Raged
- Oct 21, 2015 7:05 PM
In reply to DavidL:

Yes, this definitely fixed my problem.
Thanks David for really delving into this. Awesome job in tracking it down!
-Edgar
- Locked
- Cancel
Do you have another question?

We are glad that we were able to resolve this issue, and will now proceed to close this thread.

If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.

Ask a related question Ask a new question
Prodigy 50 points

Jay Paxman
- Oct 21, 2015 10:27 PM
In reply to DavidL:

This also fixed my problem. Thank you very much.

Will there be a CCS update that will fix this eventually? Will it just be that the startup or link file will include the suggested lines so we will know when we can stop adding it, or will it be some other "hidden" fix?
Thanks again.
Jay
- Locked
- Cancel
Do you have another question?

We are glad that we were able to resolve this issue, and will now proceed to close this thread.

If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.

Ask a related question Ask a new question