MSPM0C1103-Q1: Error connecting to the target: DAP Connection Error.[MSPM0C1103]

Hi Ramalingam,

Can you take a picture of the board you are using?

Ramalingam Pachamuthu said:

I also tried the MSPM0_Mailbox_FactoryReset_Manual script, but it’s not working reliably on this    board.

What do you mean by "not working reliably?"

Are you disabling the NRST pin or using it for something else?

What is the program that you are flashing onto the board? What pins/peripherals does it use? What low power mode policy is being used (if any).

Best,

Owen

Hi Owen,

I’m working with the LP-MSPM0C1104 LaunchPad, which contains the MSPM0C1103 device, and using the XDS110 USB Debug Probe through CCS. I was able to flash the firmware successfully a couple of times, but later it started failing with the following error:

Error connecting to the target: Connection to MSPM0 core failed. Possible root causes:

• Debug access within NONMAIN was disabled or enabled with password

• Peripheral misconfiguration (e.g., improper watchdog or clock)

As suggested earlier in the forum, I followed the recovery steps and used the MSPM0_Mailbox_FactoryReset_Manual script via CCS. This resolved the issue initially and allowed me to flash again. However, a similar error has now reappeared:

CS_DAP_0: Error connecting to the target: DAP Connection Error. This may be caused by the device entering low power mode. It suggests trying an external reset, BSL mode, mass erase, or factory reset.

I’ve repeated the same recovery steps using the XDS110 USB Debug Probe, but the issue persists. That’s what I meant when I said the solution is “not working reliably” — it worked once, but is no longer effective in resolving the current issue.

Firmware Overview:

The firmware includes a GPIO-based MDIO/MDC implementation, bit-banged using two GPIOs to initialize a Marvell PHY.
Can you please help me on this ji.

Thanks ,
Ramalingam.

Hi Ramalingam,

I understand what you are using, but if you could provide more information it would allow me to assist you better.

1. Can you take a picture of the board you are using? This will help me see exactly how your board is set up and the board version you are using.
2. Are you disabling the NRST pin or using it for something else?
3. What low power mode policy is being used? (if any)
4. What exact pins/peripherals does your program use?
5. Is it possible for you to share the project?

Best,

Owen

Hi Owen Li,

 Regarding your question "Are you disabling the NRST pin or using it for something else?"
I followed the  below steps for recover from this issue as mentioned in the forum.

1) put the uC in unpower mode.
2) put the NRST pin to gnd (by direct shortcu to gnd).
3) put the uC in power mode.
4) run the script  "MSPM0_Mailbox_FactoryReset_Manual" via CCS and Uniflash.
5) remove the short cut from NRST.

after this i am facing this error.
Trouble Writing Register SECAP_TCR: (Error -2131 @ 0x20204) Unable to access device register. 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 20.1.0.3372) [6/20/2025, 5:37:25 PM] [ERROR] CS_DAP_0: GEL: Error while executing GEL_DAPInit_SECAPCommand(): Target failed to write register SECAP_TCR at 'REG'::SECAP_TCR=command

Can you support me in this ?

Thanks and Regards
Ramalingam