MSPM0G3519-Q1: MSPM0G3519 Microcontroller Data Flash Corruption

Shivaraj P

Part Number: MSPM0G3519-Q1
Other Parts Discussed in Thread: MSPM0G3519, SYSCONFIG

Hi TI Team,

We are using MSPM0G3519 microcontroller for automotive application. Data flash with 16KB of protected area (0x41D00000) we have used 1KB (1st Section) of Data flash to store the settings information.

During the initial phase of deployment, Data Flash read and write operations functioned as expected with less data read and write cycle. However, after more data read and write cycle greater than 100 (varied), we are observing instances of Data Flash corruption, as shown in the attached image (Image below sample data from one affected board).

The corruption does not consistently occur at the same memory location. instead, it has been observed at different flash addresses across occurrences. The issue is intermittent and not reproducible at a fixed address or time.

we are using following API for data flash read and write as shown below

Write

Read

lUI8_ReadVerifyCmdStatus=DL_FlashCTL_readVerifyFromRAM64WithECCGenerated(FLASHCTL,lUI32_ReadVerifyFlashAddress,lUI32_Data);

Microcontroller - MSPM0G3519 [ LQFP-64(PM) ]

CCS IDE - 20.02

Compiler - ti-cgt-armllvm_4.0.0.LTS

SDK - mspm0_sdk_2_03_00_07

Sys Config - sysconfig_1.21.2

Any support is much appreciated.

1 month ago

0 Gary Gao 28 days ago

TI__Mastermind 40830 points

Shivaraj P said:
However, after more data read and write cycle greater than 100 (varied),

For the failed device, dose it failed every time after 100 cycles?

For every device will have such issue after 100 cycles?

What's the failed rate so far?

0 Mohan Jayaramegowda 27 days ago in reply to Gary Gao

Prodigy 10 points

For the failed device, dose it failed every time after 100 cycles?no it is not related to no of cycles. we observed after 5 to 10 cycle also.

For every device will have such issue after 100 cycles? No we have not observed in all, but the failure rate is increasing

What's the failed rate so far?currently we got ~40 out of 15K

0 Gary Gao 27 days ago in reply to Mohan Jayaramegowda

TI__Mastermind 40830 points

Please see my comments below:

What’s the main clock frequency do you use and what's the flash wait states configured in the sysconfig?
I do not see disable global interrupt before flash write or erase operation. Highly recommended to disable global interrupt before flash write or erase operation and enable it after that. Customer can refer to the below code to do it

__disable_irq(); // disable global interrupt

__enable_irq(); // enable global interrupt

0 Shivaraj P 25 days ago in reply to Gary Gao

Prodigy 30 points

1. What’s the main clock frequency do you use and what's the flash wait states configured in the sysconfig?

- MCLK is 64.00 Mhz and ULPCK (Flash Controller clock) is 32.00 Mhz

Below Flash Controller settings is configured by sysconfig as default values, based on our MCLK and ULPCK is it required to change the wait states value ?

2. We incorporate your suggestion during Data flash write operation

0 Gary Gao 25 days ago in reply to Shivaraj P

TI__Mastermind 40830 points

Wait state set to 2 is fine here. Please help to follow the point 2 and feedback to me if failure happen with it.

0 Shivaraj P 25 days ago in reply to Gary Gao

Prodigy 30 points

I hope below modifications should be fine for erase and write data flash operations

Erase Flash

Write Flash

We are currently performing our standard/normal testing procedures.
Are there any additional or specific tests you would recommend to perform to isolate or resolve this issue?

0 Gary Gao 23 days ago in reply to Shivaraj P

TI__Mastermind 40830 points

That seems fine to me

0 Gary Gao 20 days ago in reply to Gary Gao

TI__Mastermind 40830 points

When I try to use a normal sample to a bench test using the code below, it running 1000*2 times erase operation and 1204000*2 times write and read verify operation with no issue.(Half during debug and half during free run)

flashctl_write_read_verify_LP_MSPM0G3519 copy.zip

Arm-based microcontrollers

Arm-based microcontrollers forum

MSPM0G3519-Q1: MSPM0G3519 Microcontroller Data Flash Corruption