MSPM0L1305-Q1: MSPM0L fails to connect to XDS110 debugger in Customer board

Hi Owens,
Most of the time it means that the device can't be reached. Can you try doing a factory reset through Uniflash or CCS?

Best Regards,

Diego Abad

hi,Diego

  In uniflash, how should it be operated? Are there any documentation instructions for performing factory reset

Hi Owens,
Yes. Here's an User Guide to Uniflash: https://software-dl.ti.com/ccs/esd/uniflash/docs/v5_0/quick_start_guide/uniflash_quick_start_guide.html 

Here's some screenshots of how it should look like:

Best Regards,

Diego Abad

HI,Diego

  In my uniflash interface, the factory reset manual option is not visible

uniflash version：8.5.0.4593

Previously, this board could be burned normally. However, when burning the firmware again, the following problems occurred. In the successfully burned firmware, the BSL pin has been adjusted as follows.

We tried two boards and both showed the same phenomenon

After changing to version 9.0 or above, when I clicked this button, it kept getting stuck

I also tried to lower the reset pin, but it had no effect

The latest status is that an error is prompted during debug burning, but the connection test is normal。

uniflash still freezes when performing factory reset

Hi Owens,

Can you let me know how are you factory resetting the device? Normally, here's how you would do it:

1. Disconnect power from launchpad

2. Hold NRST Push button or connect NRST to ground

3. Connect the device to computer with the previous still being true

4. Run the Factory Reset script

5. Wait until it says "press Reset to continue," and then remove the jumper from ground or stop pressing NRST

This should unlock the device to the factory reset. If this doesn't work, your device is most likely bricked.

Best Regards,

Diego Abad

hi，Diego

   After following the above operations, it still gets stuck in the factory reset. It should be a brick. Is there any hope for this kind of chip?

Hi Owens,
My next guess will be that either the MSP432 debugger got bricked, or the device itself got bricked. Can you check if you notice any heat coming from either chip?

Best Regards,

Diego Abad

hi，Diego

 We didn't modify the XDS10 debugger. After replacing one customer board, it worked fine. It seems that there is something abnormal with the chip