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.

CCSTUDIO: mass erase under program control

Part Number: CCSTUDIO
Other Parts Discussed in Thread: MSP430FR2433

Hi Experts,

I need your assistance with this. Is it possible for the application program (written in C using CCS) to trigger a mass erase operation?

As a security precaution, my client wishes to do this if the JTAG signature has not been set to a disabled state by the programming operation.

I have read several documents, including the family user guide and the BSL guide(s) and it seems to be possible, but I cannot find the information I need to actually achieve this.

If it is possible, can you please provide a code snip showing how it can be achieved?

Thank you in advance for your support.

  • Hello,

    What is the device being used?

    Thanks

    ki

  • Reposting my question here.Thank you.

    I am using an MSP430FR2433

    I need your assistance with this. Is it possible for the application program (written in C using CCS) to trigger a mass erase operation?

    As a security precaution, my client wishes to do this if the JTAG signature has not been set to a disabled state by the programming operation.

    I have read several documents, including the family user guide and the BSL guide(s) and it seems to be possible, but I cannot find the information I need to actually achieve this.

    If it is possible, can you please provide a code snip showing how it can be achieved?

    Thank you in advance for your support.

    Best regards,

    Jonathan

  • I am using an MSP430FR2433

    I will bring this thread to the MSP430 experts for further suggestions.

    Thanks

    ki

  • Hi Jonathan, 

    This is possible, but it would require writing a program into RAM which looped through your application memory and erased it. 

    Looping through memory to do this is fairly simple, we have an example in the MSPFRBOOT FRAM Bootloader example (https://www.ti.com/tool/download/MSPFRBOOT/1.03.00.00). 

    They would not really need the check for the download vs application areas in their use case, but something similar to this running from RAM would work to Erase flash as a last ditch effort. Doing this in a custom bootloader is probably the most robust way.

    Typically however, just disabling JTAG and password protecting the BSL is enough for most customers. They could always just disable JTAG/SBW and ensure a password is set on BSL if their application detects that JTAG isn't locked for some reason. 

    Best Regards,
    Brandon Fisher