[sdiy] Flash Memory Read Disturb

[Ben Bradley]

I hadn't heard of read disturb, but I just did some reading up on it,
and I'm 99.99 percent sure that all microcontrollers use NOR flash for
code memory, and that this problem only occurs in NAND flash.
https://en.wikipedia.org/wiki/Flash_memory#NOR_flash

This file talks about read disturb happening between 100,000 and
1,000,000 reads of NANA flash - a tight loop could easily cause that
many reads of code memory in minutes or seconds. Microcontrollers
aren't THAT unreliable - they should be able to run for years at full
clock speed, so I can't imagine this would be a problem.
https://www.segger.com/downloads/emfile/UM02001_emFile.pdf


On Thu, Jun 8, 2017 at 2:22 PM, Scott Gravenhorst <music.maker at gte.net> wrote:
>
> With many devices having Flash program memory, I wonder about read disturb,
> specifically, about leaving such devices powered up and running at full
> clock speed.  I've just started to play with a STM32F746NG which has Flash
> program memory and I wonder if there is a read disturb problem with it or
> if it's immune.  I tend to leave musical devices run, as in turn it on and
> leave it on.
>
> Does anyone here know it that is risky?  I had read about read disturb some
> few years ago working on a project that wanted NAND Flash which looked
> problematic with respect to read disturb.  Looking at the STM32F746NG
> datasheet, I'm not finding a reference to the type of Flash in the device
> and I'm not sure whether NOR Flash (if that is what is used) has a similar
> issue.
>
> -- ScottG
> ________________________________________________________________________
> -- Scott Gravenhorst
> -- http://scott.joviansynth.com/
> -- When the going gets tough, the tough use the command line.
> -- Matt 21:22
>
> _______________________________________________
> Synth-diy mailing list
> Synth-diy at synth-diy.org
> http://synth-diy.org/mailman/listinfo/synth-diy