TMDSEMU110-U: Intermittent DAP Connection Error with XDS110 Debugger

Hello,

What JTAG error code is it giving you? It's good to know the issue doesn't occur after a part swap.

You can also try re-downloading the XDS110 firmware, a README on how to do so it located in the CCDS folder at: ccs2011\ccs\ccs_base\common\uscif\xds110\XDS110SupportReadMe.pdf

Best,

Matt

DAP Connection Error. This could be caused by the device having gone to low power mode.
Try forcing an external reset.If the error persists, try forcing BSL, a Mass erase or a Factory Reset. Check device FAQs for more information. 

This is the error i am getting, Error code is not mentioned.

Hi Matt,

Thank you for the suggestion. I’ve tried re-downloading and updating the XDS100 firmware as per the instructions in the XDS110SupportReadMe.pdf located in the CCDS folder. However, I’m still encountering the same issue that I had previously.

Please let me know if there's anything else I should try from my end.

Hi,

Which device (MCU) is this happening on? The thread is not attached to any part besides the XDS110 debugger.

Best,

Matt

MCU IS MSPM0G3507,

I tried using other debugger it is working fine, 

Hi,

This thread was wrongfully routed to the C2000 forum, I've sent your thread to the MSP experts. Please expect a small delay in assistance.

Best,
Matt

I've also encountered this error after my power supply circuit wasn't functioning properly -- basically I had a resistor in series to determine the current draw in low power mode, and the value was high enough to cause the voltage to misbehave as seen at the processor.

Hi Ankush,

As for MSPM0 series, when it report the DAP connection error, there always related the SWD signal issues:

1. The connection is error

2. The MCU encounter some fault status (normally with a wrong firmware, and MCU run out of control)

3. There occurs reset to MCU (external NRST, WWDT, software reset in code, etc). The reset behavior will break the SWD connections, which might cause the DAP error issues.

4. NONMAIN area broken due to incorrect operation.

Hope this will be helpful for your reference.

For the #2, this might be high frequently happen to user side, we can connect PA18 (BSL invoke pin) to VCC, then it will run into ROM BSL, not to application code, and then it could reconnect again.

Others method to unlock device, you can refer to below chapter:

https://www.ti.com/lit/ug/slaaed1e/slaaed1e.pdf?ts=1745919400787 

B.R.

Sal

Hi,

I’ve checked the setup using another debugger, and it’s working fine — I was able to successfully program the device in a single attempt. However, I’ve been facing the same DAP connection error issue with three different debuggers over the last six months.

Is there any recommended method to troubleshoot this recurring issue?

Hi Ankush,

Sorry for the late response, I am OOO these days.

Ankush said:

I’ve checked the setup using another debugger, and it’s working fine

Are you means that the TMDSEMU110-U always works abnormal but it can be recongnized by PC (I see you have used uscif\xds110 to update the firmware) and success.

Ankush said:

To isolate the problem, I tested the setup using a different XDS110 debugger, and it worked without any issues.

What the different XDS110 debugger is? Another new TMDSEMU110-U, or LP-XDS110, or the LaunchPad debugger?

If use a new TMDSEMU110-U, then I suspect there has some issues with the debugger.

If use others, then I suspect there has some issues with hardware connection.

Ankush said:

Is there any recommended method to troubleshoot this recurring issue?

Could you describe the hardware connection here?

Then you can use a scope (or logic analyzer) to check the SWDIO, SWCLK, and NRST signal here.

B.R.

Sal