MSPM0L1105: Factory reset auto UNIFLASH or CLI dslite

Hello Tiago,

I see you have another question related to this post -> https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1337651/mspm0l1105-factory-reset-via-command-line-cli

As I mention in the other post, I am attempting to create a solution for you, but this may take a day or two.

Hello Tiago,

I think I found a possible solution for you.  Are you familiar with openocd?  If not, check it ou.

Apparently this allows you to have complete control of the XDS110 (supports many others).  You are able to configure this to execute custom comands.

I discovered that someone here at TI that uses this and has already added support for MSPM0 (its open source so he contributes updates and features back to openocd).

Is this something that might interest you? If so, I can send you specific instructions on how to use it for MSPM0.

Yes. We use openocd in CLI to record micros from other brands.

I look forward to hearing from you.

Hi Tiago,

Here is the link to the GIT repo that has the commit for MSPM0.

(GitHub - nmenon/openocd at mspm0)

  Please keep in mind this has not been fully vetted.  I'm being told by our expert that this will provide full control of the DSSM and that he will continue to update the GIT repo.

Hi Dennis

Openocd without examples. I couldn't solve my problem.

uniflash generates a package for writing to the microcontroller via CLI... will it be possible to write a firmware open for reading, and then use a CLI command to block the reading and protect the device?

-----

My current error when trying to write the firmware with "Security level 1" : error: CORTEX_M0P: File Loader: Memory write failed: Flash Programmer: Error, Attempting NONMAIN write without erasing!

Something is missing in my reasoning...

Hi Tiago,

Regarding Uniflash, yes it is possible to generate a CLI package, but I'm not sure if it will give you control to do what you are attempting.  

Regarding your error, you must first erase NONMAIN before reprogramming with specific changes for your application. But be very careful.  If you erase NONMAIN without reprogramming NONMAIN correctly, or go through a RESET, the device will be permanently locked.  This is mentioned in several places in the TRM.

I need this CLI to clear NONMAIN before programming.
What are the steps to reprogram NONMAIN correctly?

Hi Tiago,

I'm working out the details with the other engineer to perform the clear NONMAIN and reprogram correctly using openocd.  I will do my best to get you a solution as quickly as possible.

Thanks Dennis, I look forward to it.