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.

MSP430FR5043: Do and Donts in FRAM device

Part Number: MSP430FR5043

Tool/software:

Hi team,

Customer have not been using FRAM device from the past. Customer's application is below. Please let me know if there are points to note.

The parameters required for customer's MCU processing (measurement) are rewritten in a designated area while the MCU programme is running and used as a parameter storage area.
If there are any precautions to be taken when Read/Writing the FRAM for this kind of use, please let me know.

Customer used to code the values directly into the programme, compile and change the parameters, but now I want to change the values during operation and record the measurement results using those values (and retain them even after the MCU is reset).

REgards,

Hayashi

  • Hi Hayashi,

    I am not sure I understand the use case correctly; they just want to reconfigure some parameters and store the measurement results for each parameter in the FRAM? 

    Generally speaking, they are ok to do this. FRAM has quite high w/e endurance and you can write the values to FRAM that is unused by the application code.

**Attention** This is a public forum