MSPM0L1305: MCU locked using UniFlash for programming it

Hi,

Have you tried to connect the MCU with BSL?  There is a BSL tool in the sdk installation path. The default path should be C:/ti/mspm0_sdk_xx/tools/bsl/BSL_GUI_EXE.

You can run the tool and download a new project to the MCU, the file you need for programming is in Input folder. You can also use the tool to update the XDS110 firmware in the MoreOpertion menu. 

Best regards,

Cash Hao

Hello Cash Hao,

please can you show me how to connect my XDS110 debugger to MSPM0L1305 MCU for entering and programming in BSL mode?

Thank you,

Nicola

Hi,

Keep all the jumpers on the board expect the RXD and TXD. Use a wire to connect the RXD to PA22. Use another wire to connect TXD to PA23.

Best regards,

Cash Hao

Hello Cash Hao,

please note that I'm not using TI demo kit but the MCU is mounted on our own UUT. I attach part of the schematic diagram related the MCU area:

Thank you,

Nicola

Hi,

Okay, so I assume you also use the standalone xds110 for your board. 

For BSL connection, Connect PA22 to RXD, PA23 to TXD, RST to RST,  VCC and GND. And for default BSL configuration, You need connect the PA18 to VCC and reset the MCU to ensure it goes into the BSL mode.

Best regards,

Cash Hao 

Hi Cash Hao,

I've connected the lines as you wrote. I've connected NRST to nRESET (pin 15) of XDS110 and PA18 (Invoke pin) to VDD. Then I powered up the UUT and reset the MCU connecting NRST to GND for about 1s.

After that I've tried to connect but it failed. I see this message in the MSPM0 Bootloader GUI:

Find MSP COM port:COM9
Configure UART: 9600 baudrate, 8 data bits (LSB first), no parity, and 1 stop bit.
Error: No response！

I see with the oscilloscope XDS110 sending data over the UARTTX line but not receiving any feedback.

Thanks,

Nicola

Hi Cash Hao,

do you have any update about it?

Thank you,

Nicola

HI Nicola,

I checked again and there are some mistakes I said before. Please refer the the following information for the hardware connection. Refer to the table 3-2 https://www.ti.com/lit/pdf/slaae88

You also need to connect a 3.3V to the TGTVDD(SENSE) to the xdx110. And if you power the MCU from the xds110, you need to connect the TGTSYPPLYOUT to the device VCC. 

Than on the GUI side, you need to change to the standalone xds110.

Best regards,

Cash Hao

Hello Cash Hao,

I've tried like you suggested but I can't connect to the IC. I get alway the same error:

Find MSP COM port:COM9
Configure UART: 9600 baudrate, 8 data bits (LSB first), no parity, and 1 stop bit.
Error: No response！

Nicola

Hi Nicola,

Could you check if you have the same connections in the following figures?

Best regards,

Cash Hao

Hello Cash Hao,

yes I confirm I made your same connections. However I still get this error:

Find MSP COM port:COM9
Configure UART: 9600 baudrate, 8 data bits (LSB first), no parity, and 1 stop bit.
Error: No response!

Nicola

Hi,

Well, there is one more method you can try with. Use the SWD interface and do a mass erase for the MCU. 

You can refer to this document. 0726.Factory_reset_v2.pdf

Best regards,

Cash Hao

Hi Cash Hao,

I've tried also this method. I've connected the SWD cable from XDS110 debugger to target MCU, but I still get errors:

Nicola

Hi,

I do not have more method to offer. Check with you on two more things. Could you take a picture of the MCU? And what version of SDK you are using now?

Best regards,

Cash Hao

Hello Cash Hao,

I've installed both mspm0 sdk versions 0.56.00.01 and 1.00.00.04:

And here is a picture of the MCU marking:

Thanks,

Nicola

Hi,

This MCU is an early sample. I would recommend to replace it with the production version MCU.

Best regards,

Cash Hao

Hi Cash Hao,

ok I understand. I didn't know the programming/debugging module was defected, I just hoped there was a way to unlock it.

Thanks,

Nicola

Hi,

You have tried with the SWD and BSL methods. There is no more method you can try with as far as I know. 

Best regards,

Cash Hao

Hello Cash Hao,

today we've received new UUTs with other MCUs mounted. This is the code printed on it:

No the debugger doesn't show me anymore the message "The connected device is preliminary silicon...", however when it tries to download the firmware it always gets stuck on:

The address is always 0x1A60. After that, if I power off and on the MCU and connect with the debugger (but also with UniFlash) I get this message:

and the MCU can't be unlocked. I've tried to unlock it using the BSL connections and the BSL_GUI utility you shown me, but there's no way to recover it.

If I try to debug a new empty project on a brand new MCU, I don't have problems: the debugger can load it more times without issues (but the Flash area 0x1A60 doesn't contain data).

If you want I can send you my project (in a separate email as it's confidential), so you can check if there's something wrong.

Please help me to solve this issue, as the project will be jeopardized if we can't find a way to debug our UUTs.

Thank you,

Nicola

Hi,

The mark "XM0L" means that it is still an early sample. The mark should be "MSPM0L1306" for production version. 

You can send me your project through email cash-hao@ti.com. 

Best regards,

Cash Hao

Hi Cash Hao,

I sent you the project over email.

Thank you,

Nicola

Hi,

Received and feedback to you on email. 

Best regards,

Cash Hao