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.

MSP432P401R: XDS110 giving error even after factory reset

Part Number: MSP432P401R

I am trying to debug code on MSP432P401R design board using XDS110 emulator with CCSV 7.0.0.. When I debug code it is showing following error: CS_DAP_0: Error connecting to the target: (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 9.2.0.00002). I have tried all the following solutions posted on e2e forum:-

1.Factory reset - same error occurs when I right click-> connect target on the device under non-debuggable devices after rightclick->show all cores.

2.Changing JTAG/SWD mode - I tried all the modes that are present in the drop down menu and factory reset did not work with any of them.

  • Hello Nikhil,

    Do you have the same issue with programming the device on the MSP432P401R LaunchPad? If not, then I would highly recommend comparing your JTAG circuitry on your custom board to the LaunchPad's. The connections and passives should match to ensure proper JTAG communication.

    Regards,

    James

  • Hi James

    Sorry about the late response, we had a long holiday over here.

    I have been using the same JTAG design in several of my boards and have not had any problems so far. I tried the problematic emulator on other different application boards also and, it did not work there. Interestingly I have a very old XDS100 v2 which works with this board so I doubt that this is an issue related to the board. If you want I can share my circuit and PCB layout with you.

    Regards

    Nikhil

  • Hi Nikhil,

    Can you try updating CCS to the latest version? Is the XDS110 emulator a standalone tool or are you using the on-board debugger on the LaunchPad? Is there a chance that the debugger has been damaged? You can share your JTAG circuit, but it does sound like it's the emulator rather than the JTAG circuit assuming it matches what's recommended. Also, by different boards, I'm assuming these are different designs based on the same MCU. If those designs used different MCUs, the JTAG connections may change depending on the MCU.

    Regards,

    James