LP-MSPM0G3507: Error connecting to target when debugging

Hello Haoran,

There is a switch on the side of the Launchpad, S2, and next to it there is a header, J8 I believe.  Make sure there is a jumper there.  This switch, s2, is connected to the BSL pin of the device.  

If you hold this BSL switch in and reset the board (either via the reset button or by trying to program it again), this will force the device to enter BSL mode upon it's reset and will give you a 10-second window where your debugger should be able to reconnect.  

Please try programming an example project while holding the s2 button while you start to flash/debug the program.  

Let me know if this allows you to re-gain access.  

Thanks,

JD

hello JD:

thanks for your reply.

I tried to program device while pressing S2 button, but the error stills exists. (It seems BSL is not entered by pressing S2)

Would you please give more specific steps. 

Sincerely

Xu

Hello Xu,

Can you also make sure that the nRST jumper is populated on the J10 debugger header?  

If the nRST jumper connects the programmer and the reset button to the MSPM0Gxx.  The J8 jumper, connects S2 to the BSL invoke pin.  As long as these are both populated, then when you hold S2 while your reset (either via the button or via the programmer) then the device should enter the BSL and allow the debugger to connect.  

If this does not work, then I guess that the BSL invocation isn't working.  The only way I can imagine for the BSL invoke to be disabled, would be if the non-main flash inside the MSPM0Gxx has been altered.  

We you trying to change the non-main memory in the device?   This controls debugger access, BSL control, and a few other things.  What type of project were you debugging when you lost access to the Launchpad? 

Thanks,

JD  

Hello JD:

thanks for your reply.

I have confirmed that both jumpers are connected. And I have tried to download program while holding button S2.

unfortunately, the error 'Error connecting to the target:' still happens.

I think my program has not modified the NON-main memory.

Is there any other procedures I can try to fix this error?

By the way, is this error is the same as mentioned in file: MSPM0G and MSPM0L Families: Functional Differences With Early Samples / DEBUGSS_02

Thank you for your help.

Hi,

I have met the same problem. And I even don't know what is the non-main memory.

I have already broken three boards. I found they can run the program successfully(Because my program lights the LEDs) but can not be connect.

Both XDS110 USB and Jlink is failed. The botton is useless (S2 PA18).

I really want to solve this problem.

And if there's no way to save the launchpad, let me know.

Thank you for your help.

I have tried all possible procedures trying to fix this problem, but all failed.

I am now using new boards with some preventative methods implemented to continue developing.

I suggest you to use new boards as well.