MSPM0L1306: (Error -6305) PRSC module failed to write to a router register. (Emulation package 9.11.0.00128).

Hi Rohith,

Are you using a launchpad, or a custom board? Are your devices early samples or production devices? This thread says how to identify this: https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1204644/faq-mspm0-sdk-important-note-for-early-mspm0-customers

If this is a launchpad, try invoking BSL mode by holding down the PA18 switch (S1 on a Rev A. Launchpad), and resetting. For best results do this right before you flash your code. After BSL invocation the device will wait for 10 seconds and then go into a low power mode. 

Best Regards,
Brandon Fisher

Hi Brandon,

I was using launchpad, i tried your approach but the board is not responding.

If there is BSL enabled code inside the controller then it will triggers right ?? 

I think there is no code inside flash and Not able to check the configuration also.

Best Regards.

Rohith

Hi Brandon,

Thanks for your inputs.

I tried to use DSSM_Unlock application to factory reset the device.

I have installed Ti cloud application but not able to connect.

Can you please help me out in this ?

It was halting in SEC_AP Reconnect.

And i am getting error: failed to connect.

Hi Rohith,

Are you using the "Attach" button to attempt to connect to your board, or the connection icon in the lower left hand side of the screen?

You should be able to hit that Attach button and then the execute button will become active. 

Is your board a Rev 1.0 launchpad or a Rev A launchpad? 

Best Regards,
Brandon Fisher

Hi Brandon,

I am using attach button after getting Device ready to attach in output console.

After that when i click on execute button device is halting at SEC_AP Reconnect.

If i press connection icon i am getting that error message.

I am not sure about launchpad is Rev 1.0 or Rev A. How to find ??

https://www.ti.com/lit/ug/slau869c/slau869c.pdf?ts=1690890729282&ref_url=https%253A%252F%252Fwww.ti.com%252Ftool%252FLP-MSPM0L1306.

https://www.ti.com/tool/LP-MSPM0L1306#tech-docs I have referred this link to order the board.

I have also referred below links

e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1237262/mspm0l1306-implementation-of-dssm-factory-reset-over-swd/4681731?tisearch=e2e-sitesearch&keymatch=MSPM0%2525252525252520Factor%2525252525252520reset#4681731

software-dl.ti.com/msp430/esd/MSPM0-SDK/latest/docs/english/tools/ccs_ide_guide/doc_guide/doc_guide-srcs/ccs_ide_guide.html#dssm-commands

But not able to resolve.

Please refer to SEC_AP Reconnect in console and for messages.

Thanks

Rohith

Hi Rohith,

Rohith P N said:

I am using attach button after getting Device ready to attach in output console.

After that when i click on execute button device is halting at SEC_AP Reconnect.

If i press connection icon i am getting that error message.

I am not sure about launchpad is Rev 1.0 or Rev A. How to find ??

You can see the revision of the launchpad written in the silkscreen near the upper right hand corner of the board.

I think given that your experience is the same when using CCS and the standalone GUI it seems like your Factory reset may be disabled.

I see you were setting an SWD password. Are you using SysConfig to do that? Its important to know which revision of silicon you are using if you are going to be modifying NONMAIN memory. The Rev 1.0 boards we don't recommend modifying non-main by any means. For Rev A., if you are using sysconfig it should be okay. 

Best Regards,
Brandon Fisher

Hi Brandon 

I am using Rev. A Launchpad. 

If factory reset is disabled, Then how to Reset device and get back to working ??

Thanks

Rohith

Hi Rohith,

With a rev A launchpad you can use the non-main configuration options in SysConfig safely.

Rohith P N said:

If factory reset is disabled, Then how to Reset device and get back to working ??

I'm not sure how exactly you reconfigured non-main, but if it is truly erased and SWD, factory reset, and BSL are disabled, you are unlikely to be able to get back in. 

The possible recovery actions are listed in the SDK here. I believe you have already tried Mass Erase, Factory Reset, and BSL invocation:

https://dev.ti.com/tirex/content/mspm0_sdk_1_10_00_05/docs/english/known_issues_faq/known_issues_faq_mspm0_sdk_1_10_00_05.html#recovery-actions

That is the extent of what you can really try.

The other potential cause is a hardware issue such as a bad connection, damage to the board, or something similar that is causing SWD communication to fail. If you probe SWD and SWCLK while trying to program, do you at least see some traffic? 

Best Regards,
Brandon Fisher