This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSPM0L1303: error -614

Part Number: MSPM0L1303
Other Parts Discussed in Thread: LP-MSPM0L1306

Hi everyone, 

do you have any information about error -614? I didn't find anything about that in the https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html guide.

I am currently using IAR 9.50.1 but also tested on CCS and CCS Theia. I think the issue appeared after I enabled the stop0 low power policy.

NRST pin and BSL invoke pin are not accessible at the moment so... I cannot invoke BSL or something like that.

Thank you for your support!

  • Hello Fabio,

    There is an FAQ section regarding debugger and low power modes in the SDK.

    What programming tool are you using?

    Try the Factory Reset Tool.  Note: this only works with the XDS110 programming tool.

  • Hello Dennis,

    thanks for your reply.

    I am using XDS110.

    I read the FAQ and the Preventive Action #1.Use RUN or SLEEP mode during development will be useful in the future. But regarding the recovery actions, they can be used if you have access to the reset or BSL invoke pin. I would prefer to find another workaround, before deciding to change the hardware schematic.

    The 'factory reset tool' is an interesting suggestion but I get this error and I can not attach:

    failed to connect: There is not active configuration to connect with.

    Thank you again,

  • Hi Fabio,

    There is another post regarding this situation, but without access to your NRST or BSL pins it may not be helpful.

    Do you have any temporary control of the NRST pin?  What I mean is can you momentarily short it to ground while you remove then re-apply power?

  • Hi Dennis,

    I actually have a temporary access to the reset pin and I succeeded in performing a mass erase with CCS (Factory Reset Tool still not working for me). 

    So the device is recovered now.

    Meanwhile, I tried to write a custom BCR and BSL on the LP-MSPM0L1306 using an example from TI SDK but something went wrong and I think that the eval board is completely unrecoverable. But this is another story. 

    Thank you for your support!