FTL for the NVM Flash on the MSPM0L130X

Hi Aj,

Sorry for the delay in a response.  To answer your question regarding 'who takes car of this', it is the application's responsibility.  This does not happen in the background

Hello Dennis. Thank you for the update. 

However looking at the 'Flashctl multiple size write' program, I do not see anything anywhere that can be construed as doing any FTL background tasks of any kind. Ditto for 'DMA block transfer project'.

So I am a bit skeptical if it indeed is even needed. Do you know of any project sample that does something similar?

Hi Aj,

The only example code is what is in the MSPM0 SDK.  Because the example is simply demonstrating multiple size flash writes, there is no consideration for managing the number of writes and performing any erasures.  This would be the applications responsibility.

That said, in my mind it shouldn't be that difficult to keep track of the number of writes to that sector and when you reach the write limit there are two ways to handle it:

1) First copy the contents to RAM, perform the erasure, then re-write the sector from RAM.

2)  Set aside an additional 'empty' sector of same size and ping-pong between the two.  What I mean is when its time to erase the first sector, copy the contents to the second sector and erase the first.  Keep updating your values in the second sector and when it's time to erase it, copy the contents to first sector and erase second sector, and so on.  Make sense?

BTW, it appears you actually need 2 sectors to fit the amount of data you intend to maintain, not one, because you are using 1080 bytes, which is 56 bytes larger than a sector (1024 bytes), right?