lpcware

ISP/IAP: Is there a maximum related to copyRamToFlash after sector erase?

Discussion created by lpcware Employee on Jun 15, 2016
Content originally posted in LPCWare by OldManVimes on Wed Aug 27 01:05:02 MST 2014
Hi,

I've been wondering about the following for quite some time and my knowledge of flash memory in general is not that in depth, nor can I easily find resources that explain it to me.

Take the following use-case:

1. Prepare + Erase flash sector
2. Prepare sector + copyRamToFlash (where 256 bytes are copied to the next portion of the sector that has not been written to yet)
3. Repeat step 2 until flash sector is full.

Will this work, or is there some limit to the number of prepare+copy actions that a flash page supports after erasing? In other words, does the prepare command influence the contents of flash that were written in earlier iterations of the loop?

For a 32 KB sector, the number of iterations is 128. So for a bonus question: Will these 128 writes count as 128 writes with respect to aging of the flash memory, or is that related to the erase + full write? This has implications for wear-leveling strategies and I'd love to know which of the two options is correct.

I'd be awesome if someone can put my brain itch to rest, so thanks in advance.

Regards,
Vimes

Outcomes