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.

MSP430F2619S-HT: Corrupted flash - potential causes?

Part Number: MSP430F2619S-HT


Hello-

  We have dozens of fielded units utilizing the above microcontroller with 1000's of hours logged with no issues.  Recently, a unit was sent back as unresponsive.  After debugging power rails and all other support circuitry (checked out good), the unit was reflashed and brought back to life.  Unfortunately, the memory was not dumped prior to the reflash so "evidence" is likely overwritten.  Are there any known issues with this part?

Environmentals below 80°C.

Power rails extremely clean.

Occasional writes to non-program memory (error logs - nothing)

Not an environment where radiation would be a concern.

Software did not initialize/configure clocks as oscillator was not being driven.

Other than a stray write to program memory (software issue), what could cause this?  Brownout?  

Thanks

-Bryan

  • Hi Bryan,

    With limited information it will be hard to determine the root cause. The MSP430F2619 errata contains known exceptions to the functional spec. Items BCL13 and BCL15 are potentially related to what you've described, but you will want to look thru the errata to see if those items are actually pertinent to your design. However, given that this issue is only present on one device it seems unlikely that an errata is affecting your design.

    Thanks,

    Evan

**Attention** This is a public forum