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.

CCS/MSP432E401Y: XDS110 debug probe connect error -613

Part Number: MSP432E401Y


Tool/software: Code Composer Studio

Hi there,

We have custom designed board using an MSP432 controller. The first board has worked fine and I am trying to get a second board up and running. Same board but this one doesn't connect using the XDS110 probe. I get the error:

Error connecting to the target:
(Error -613 @ 0x0)
The target indicates that it is busy. Either try the SWD request
again, or abort the transaction.
(Emulation package 9.2.1.00042)

I know it's not a design or configuration error because the first board worked. There's very little hardware between the JTAG connector and the processor. Here's the circuit:

This is the connection properties from the .ccxml file:

I've tried different clock frequencies and the different JTAG modes.

At this point I suspect the problem is in the processor but I'd like to confirm it before resorting to replacing the processor. Is there anything else I can try?

Thanks

Andrew

  • Hi again,

    I notice that this has gone to the 'Other Microcontrollers Forum' instead of the MSP one because that's the only option for this part. Maybe because it's not an MSP430....

    Anyway, I also notice the images didn't load, so we try again:

    Here's the circuit:

    This is the connection properties from the .ccxml file:

    Regards,

    Andrew

  • I saw you have pull up all JTAG signals. I thank it is not necessary to do that can you have a try to remove them?

  • Hi Gary,

    This hardware is working on one board and not working on 2 other boards. I do not think the pull up resistors are the problem.

    I get the message:

    Error connecting to the target:
    (Error -613 @ 0x0)
    The target indicates that it is busy. Either try the SWD request
    again, or abort the transaction.
    (Emulation package 9.2.1.00042)

    How does the target indicate it is busy? 

    Regards,

    Andrew

  • This problem was traced to a loading error. One of the capacitors around the external crystal was the wrong value. This stopped the crystal from running. The  thread  explains why this kills the JTAG/SWD comms.  The test software I loaded after the first connect starts by switching to the external crystal as the clock source. Might have to add a check to see if the external crystal is running...

    Regards,

    Andrew