• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 80 subscribers
  • Views 502 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSP430FR2433: Firmware getting erased/corrupted randomly.

Fasil Yousaf
Prodigy 10 points

Part Number: MSP430FR2433
Other Parts Discussed in Thread: MSP-FET

Hi,

I am loading MSP430 with firmware whose purpose is to boot up the main board according to external interrupts. Lately I have found that the firmware is getting corrupted and so I dumped the main memory using MSP-FET Debugger tool and found that the memory is erased completely. Can anyone tell me any possible reasons?

  • 0
    TI__Mastermind 25285 points

    Hi Fasil

    As I know, there will be several reason on the memory erased for example the password error during programming memory through the BSL.

    you say the main memory is erased during MSP-FET Debugger used, may I know which PC sides software your are using (for example CCS) and which operation you have done (for example "debug" operation)?

    Thanks!

  • 0 in reply to Xiaodong LI
    Prodigy 10 points

    Hi Xiaodong Ll,

    Let me clarify that the MSP was programmed at an earlier date and was working fine. So I think we can rule out any error happening during programming the memory. Also the memory is not erased during the usage of MSP-FET, what I meant was that the memory was found erased when I read the device memory using the MSP-FET(hex file populated by "FF"). On PC side I am using MSPFlasher_1.3.20

  • +1
    Guru 26175 points

    You can't erase FRAM, just write something new to it. One of the hazards of using FRAM for code is that bugs in that code can result in errant writes to the code. Enabling memory protection (see documentation for details) can block those writes but does not fix the original problem. Which is code doing something you didn't want it to.

**Attention** This is a public forum