• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 78 subscribers
  • Views 240 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

MSP430F1612: Flash corrupting in production or in the field on some devices.

MSP430F1612: Information Memory Segments Corrupting issue

Dawid van Niekerk
Prodigy 20 points
Part Number: MSP430F1612

We have an MSP430F1612 processor that we have been using on our product. We are using address 0x1000 to 0x103F to store device information. This flash corrupts on some units when writing to the flash (sometimes from startup or other times after saving information to the flash), resulting in incorrect results being displayed on our device. The last time the image was compiled was in 2016. The issue only started to become an issue recently with the fault occurring in 1/40 devices.

Is this a known issue? Was there any hardware changes made to the chip?? Any suggestions or recommendations will be appreciated.

  • 0
    TI__Mastermind 28955 points

    Hello Dawid,

    This is not a known issue and there have been no hardware changes that I'm aware of for this device for a decade.

    In my experience, Flash corruption like this has two sources: Voltage-related noise/violation or a software bug.  Since your code has been in production for so long, I doubt that would be the issue just showing up now.

    Is this issue happening during programming?  Has anything changed with that setup? 

    What is supplying the voltage to the MCU, during programming and after?   I see this device has a built in SVS, are you using that?  

    Are there any flash writes in the application software?      

    The most common spec violations that I see result in flash corruptions are related to VCC vs MCLK speed or flash write levels:

    Thanks,

    JD

**Attention** This is a public forum