This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CORTEX_M4_0: Error connecting to the target: (Error -1063 @ 0x0)

Prodigy 70 points

Replies: 5

Views: 2762

I am following the instructions for the Code Composer Studio™ 6.1 for MSP432.

How to fix this 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.83.1) 

With XDS100 and XDS200:

5 Replies

  • Guru 301850 points
    Hello,
    I believe you are running into the same issue as described in: e2e.ti.com/.../1663082

    Hope this helps
    ki

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

    Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.

    Having CCS problems? Check out the CCS Troubleshooting Guide

    Looking for CCS Training/Documentation? Check out the CCS Resources page

    Curious about the status of a bug and know the tracking ID? Track it via the public bug tracking portal

    NOTE: When a bug is filed and a tracking ID is provided, the thread may then be suggested as "TI Thinks Resolved". Why? Please read the first FAQ of the CCS Forum Guidelines & FAQ

  • In reply to Ki:

    Hello Ki,

    I strongly disagree with your suggestion.

    If the configuration for the software is wrong, naturally it will not run on the micro-controller. The factory reset only applicable to the on board XDS100 debug probe but I also have the XDS200 which reports the exact same error.

    In order to confirm my suspicion I downloaded Ti's CCS UniFlash Version: 3.4.1.00012 and tried to delete the flash of the MSP432.

    The results are illustrated below. I have tow MSP432P401R LaunchPad none of them is working. The re is very minimal parts around the micro-controllers which  could get damaged. I did measured the 3.3 and 5V on the board.

    So where is the error? Is the MSP432P401R silicon originates from a  foully series or the board design is faulty?

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

    CCS UniFlash console:

    [20:53:27] Begin Launching session operation.
    [20:53:29] Operation Launching session returned.
    [20:53:29] Loaded target configuration from: C:\Users\root\AppData\Local\TEXASI~1\CCS\ti\4\0\/temptargetconfiguration.ccxml
    [20:53:29] Settings purged.
    [20:56:59] Erasing flash sectors on Core 0 < Texas Instruments XDS2xx USB Debug Probe/CORTEX_M4_0 > ...
    [20:56:59] Begin Erase Flash operation.
    [20:57:00] 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 debug probe configuration is correct, or update device driver. (Emulation package 6.0.83.1)

    [20:59:25] 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 debug probe configuration is correct, or update device driver. (Emulation package 6.0.83.1)

    [21:02:04] ERROR >> CS_DAP_0: Error: (Error -2172 @ 0x0) Unable to communicate with the debug probe. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 6.0.83.1)

    [21:02:04] ERROR >> CS_DAP_0: Unable to determine target status after 20 attempts

    [21:02:04] ERROR >> CS_DAP_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

    [21:07:20] ERROR >> CORTEX_M4_0: Error connecting to the target: (Error -2172 @ 0xD) Unable to communicate with the debug probe. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 6.0.83.1)

    [21:07:21] ERROR >> CORTEX_M4_0: Error connecting to the target: (Error -2172 @ 0xD) Unable to communicate with the debug probe. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 6.0.83.1)

    [21:07:22] ERROR >> CORTEX_M4_0: Error connecting to the target: (Error -2172 @ 0xD) Unable to communicate with the debug probe. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 6.0.83.1)

    [21:07:23] Operation Erase Flash returned.

  • Guru 148205 points

    In reply to Antal Soos:

    Hi,

    Antal Soos
    If the configuration for the software is wrong, naturally it will not run on the micro-controller. The factory reset only applicable to the on board XDS100 debug probe but I also have the XDS200 which reports the exact same error.

    For the error message, check section 5.10 of the wiki page below:

    http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems

    The issue you mentioned is tied to the device and not the JTAG debug probe, therefore anything you can try will fail with the same error. The Device ID error was ubiquitous a few months ago and from your description it seems due to a version mismatch between the MSP432 device support files and the example code shipped with MSPWare.

    Give the Factory reset a try and connect to the device manually - i.e., not actually loading code - and see if you are able to regain control of it. For details on how to manually launch the debugger and load code, check:

    http://processors.wiki.ti.com/index.php/GSG:Connecting_to_slave_cores_in_SoC_devices_v5

    If you want to give a try loading a code that does not have the bug mentioned above, download the attached .out file and manually load it to your board.

    Hope this helps,

    Rafael

    OutOfBox_MSP432P401R.zip


    When posting, click on the link Insert Code, Attach Files and more... to attach images, files or use nice formatting.

    If my reply answers your question please click on the green button "This resolved my issue".

  • In reply to desouza:

    Hello,

    Following your links I could spend the rest of my life reading Ti's wiki which are mostly irrelevant and obsolete.

    You are stating that there is some bad configuration in the MSP432P401R which prevents the JTAG access?

    Are any direct instructions to solve this problem? Can this be solved at all? 

    Can this be solved by the CCS UniFlash?  It has factory reset function and but neither the XDS110 nor the XDS200 can access it.

    Best Regards,

    Antal Soos

  • In reply to Antal Soos:

    I only see one explanation for this error the JTAG state machine design in the silicon (REVB) is faulty an no way that any external interaction can get access to the chip.

    I wasted so much time, if you are in this situation by a new board or two. Hopefully the new silicon  revision (REVC) will correct this.

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.