<!DOCTYPE html>
<html><head>
<meta charset="UTF-8">
</head><body><p>I've know of this as bit rot. Never have had a problem with that.</p><p><br></p><p>But I have seen parts wear out in development since there were a lot of programming cycles on uCs.</p><p><br></p><p>Another issue I've seen is that some parts need to have a settling time before power cycling. It's like there is an internal engine doing the programming and that isn't done before the power is turned off. Come to think about it that was with large flash chips and not uCs.</p><p><br></p><p>Jay S.</p><blockquote><p>On June 8, 2017 at 11:22 AM Scott Gravenhorst <music.maker@gte.net> wrote:</p><p>With many devices having Flash program memory, I wonder about read disturb,<br>specifically, about leaving such devices powered up and running at full<br>clock speed. I've just started to play with a STM32F746NG which has Flash<br>program memory and I wonder if there is a read disturb problem with it or<br>if it's immune. I tend to leave musical devices run, as in turn it on and<br>leave it on.</p><p>Does anyone here know it that is risky? I had read about read disturb some<br>few years ago working on a project that wanted NAND Flash which looked<br>problematic with respect to read disturb. Looking at the STM32F746NG<br>datasheet, I'm not finding a reference to the type of Flash in the device<br>and I'm not sure whether NOR Flash (if that is what is used) has a similar<br>issue.</p><p>-- ScottG</p><p>________________________________________________________________________<br>-- Scott Gravenhorst<br>-- <a href="http://scott.joviansynth.com/">http://scott.joviansynth.com/</a><br>-- When the going gets tough, the tough use the command line.<br>-- Matt 21:22</p><p>_______________________________________________<br>Synth-diy mailing list<br>Synth-diy@synth-diy.org<br><a href="http://synth-diy.org/mailman/listinfo/synth-diy">http://synth-diy.org/mailman/listinfo/synth-diy</a></p></blockquote></body></html>