MSP430FR5994: MSP430FR5994 FRAM problem

Jian Chen

Part Number: MSP430FR5994
Other Parts Discussed in Thread: UNIFLASH

Hi team,

We recently have some FRAM data lost problems with our products using MSP430FR5994IZVWR.

The MCU was functioning properly at the beginning, while after running couple days(without reboot/reset), some of the MCU had the FRAM memory lost issues.

The memory allocation and partition is as shown below:

0x4000 ——0x17FFF：CODE1 （80KB）

0x18000——0x2BFFF：CODE2 （80KB）

0x2C000——0x437FF：DATA （94KB）

0x43800——0x43FFF：CODE3 （2KB）

The WPROT in the FRCTL0 register is set to be 0.

We used UniFlash to debug the FRAM issues and found that part of the data in CODE1 and all of the data in CODE2 were set to be 0xFF unexpected, and the data in DATA and CODE3 were still correct.

Once we reprogram the MCU, it works properly but the same problem happens accidentally.

We look forward to your reply and thank you for your time in advanced.

Thanks,

Chen

over 3 years ago

0 Johnson He over 3 years ago

TI__Mastermind 28496 points

Hi Jian,

Have you enable the MPU module?

We recommend enable MPU to protect your code:

You can refer this example: https://dev.ti.com/tirex/explore/node?node=AP7nrlhk5xV4B0INSnZ6Iw__IOGqZri__LATEST

Thanks!

Best Regards

Johnson

0 Jian Chen over 3 years ago in reply to Johnson He

Prodigy 10 points

Hi Johnson,

Thank you for your reply.

We didin't enable MPU. We will have a try. But it is difficult to recreate the issue.

What condition would cause FRAM data corruption?

Thanks!

Jian

0 Johnson He over 3 years ago in reply to Jian Chen

TI__Mastermind 28496 points

Hi Jian,

I fthe MCU run whti over spec will cause some issue.

Like over voltage, voltage current, etc..

Thanks!

Best Regards

Johnson

0 David Schultz over 3 years ago in reply to Jian Chen

Guru 22685 points

The MPU can prevent a rogue pointer from trashing your code but it just masks the real problem. The most likely cause is a loop that doesn't terminate when it should which allows it to write over your code.

Using the MPU in a debug environment so you can examine the program state after it detects an attempt to write over your code would help you locate the problem. Or just a careful look at your code and loop termination criteria.

0 Jian Chen over 3 years ago in reply to Johnson He

Prodigy 10 points

Thanks!

0 Jian Chen over 3 years ago in reply to David Schultz

Prodigy 10 points

Thanks!

**Attention** This is a public forum

MSP low-power microcontrollers

MSP low-power microcontroller forum

MSP430FR5994: MSP430FR5994 FRAM problem