[A83] Re: What is the problem with flash writes (in general)
[Prev][Next][Index][Thread]
[A83] Re: What is the problem with flash writes (in general)
Programs/apps already write back to flash for storage. Take MirageOS, for
example, it stores its settings in an AppVar which is archived upon exiting.
Direct writing to the flash would be dangerous, even if it was possible,
because you lack the VAT structure to track variables then. As for the
minimum of 1,000,000, that's for erases, not writing. (not sure about this).
Michael Vincent
Detached Solutions - www.detacheds.com
Radical Software - www.radicalsoft.org
----- Original Message -----
From: "james l" <james@kirk.math.twsu.edu>
To: <assembly-83@lists.ticalc.org>
Sent: Monday, July 09, 2001 9:22 AM
Subject: [A83] What is the problem with flash writes (in general)
>
> Not really that no one has been able to do them in their programs, but the
> fear of failure.
>
> "Minimum 1,000,000 program/erase cycles per sector
guarantead" -Am29F400B.pdf
> (amd's tech doc on it)
>
> Writing to it for everything, would be a hazard, but having programs do
> write-back to the flash for storage, shouldn't hurt at all. (if we could
do
> it)
>
>
> Just my .02USD
> James L.
>
>
Follow-Ups:
References: