Flash Memory Erase Mode Comparison

Flash Memory Erase Mode Comparison
Flash Memory Erase Mode Comparison
Simultaneous Read/Write vs Erase Suspend
Application Note
Simultaneous Read/Write devices are designed to allow reading from a Flash device at the same
time an erase (or program) operation is being executed. The Erase Suspend/Resume feature is
intended to be used occasionally to interrupt an erase operation to read data from the Flash device. With this in mind the question arises: How often can an erase be suspended before it affects
system performance and a Simultaneous Read/Write device needs to be used instead?
Timing and Performance Comparison
Most systems that use either Simultaneous Read/Write or Erase Suspend do so because of interrupt-driven events that read from the flash during an erase. When using a simultaneous read/
write device, an erase operation will be not be affected by reading the device (assuming the data
is in a separate bank), because both the read and erase happen in parallel. When Erase Suspend
is used to handle an interrupt, the erase operation is paused while data is read from the device.
This serial approach can drastically increase the total time of the erase operation (see Figure 1).
Simultaneous Operation
Eras e Sus pend / R e a d
Figure 1.
Simultaneous Operation vs. Erase Suspend
During a sector erase, as the number of Erase Suspend operations increases, the erase operation
becomes less efficient. During an erase operation the flash is issuing a number of erase pulses
to the memory array. When an erase is suspended, any erase pulse that wasn’t completed must
be restarted.
If a flash device is continually issued suspend/resume commands in rapid succession, the device
will frequently be restarting the same erase pulse. This will greatly degrade the performance of
the erase function, and possibly extend the total erase time beyond the stated maximum values,
but will not affect device reliability or future performance. The solution to this problem is to either,
set a minimum time between the beginning of an erase (or resume) and the suspend command,
or use a simultaneous read/write device.
Publication Number erase_mode_comp_AN
Revision A
Amendment 0
Issue Date August 4, 2005
Regardless of the type of flash device used, a complete erase pulse is needed to make any
progress during an erase operation. But how long is an erase pulse? The length of an erase pulse
changes depending on the process technology and device family. The general rule is that highspeed parts have shorter erase pulses than data storage parts, but even the longest erase pulses
are under 10 ms.
Some would assume that a system issuing regular suspends every 4 ms would not affect the erase
performance of a S29WS256N (a 256M-bit, 1.8 V burst device with MirrorBitTM technology), which
uses 2 ms erase pulses. This is not true because the system is not synchronized with the internal
pulse generator of the flash device. Therefore, approximately half of the erase pulses would not
have completed, doubling the time required to erase a sector (see Figure 2).
Increase in Erase Time vs. Frequency of Suspends
For the S29WS256N
Times Longer than Normal
2.25 2.50
3.00 3.25
3.75 4.00
4.25 4.50
5.00 5.25
Time Between Suspends (ms)
Figure 2.
Effect of Erase Suspend on Total Erase Time
A simple equation can be used to calculate the performance impact of using Erase Suspend vs.
Simultaneous Read/Write:
Times longer than normal =
Length of Erase Pulse
1 -
Time Between Suspends
Flash Memory Erase Mode Comparison
erase_mode_comp_AN_A0 August 4, 2005
Erase Suspension Capacity
On all floating gate devices built using a 170 nm or large process technology (except the
Am29BDD and S29CD families), a sector erase may fail if suspended more than 5,680 times. Reissuing the sector erase command will erase the sector correctly (assuming the number of
suspends is limited to under 5,680). MirrorBit devices don't have a preset limit, but still do require that a complete erase pulse (which are between 0.5 ms and 4 ms long) is issued before any
progress can be made on an erase operation.
For systems that need to suspend program/erase operations sporadically, but infrequently, like
most interrupt-driven controllers or computer systems, simultaneous read/write is not needed.
Systems that continuously need to read from the device (such as real-time systems), or those
that must repeatedly suspend program/erase operations, should use a simultaneous read/write
August 4, 2005 erase_mode_comp_AN_A0
Flash Memory Erase Mode Comparison
Revision History
Revision A0 (August 4, 2004)
Initial release.
The products described in this document are designed, developed and manufactured as contemplated for general use, including without limitation, ordinary
industrial use, general office use, personal use, and household use, but are not designed, developed and manufactured as contemplated (1) for any use that
includes fatal risks or dangers that, unless extremely high safety is secured, could have a serious effect to the public, and could lead directly to death, personal
injury, severe physical damage or other loss (i.e., nuclear reaction control in nuclear facility, aircraft flight control, air traffic control, mass transport control,
medical life support system, missile launch control in weapon system), or (2) for any use where chance of failure is intolerable (i.e., submersible repeater and
artificial satellite). Please note that Spansion will not be liable to you and/or any third party for any claims or damages arising in connection with above-mentioned uses of the products. Any semiconductor devices have an inherent chance of failure. You must protect against injury, damage or loss from such failures
by incorporating safety design measures into your facility and equipment such as redundancy, fire protection, and prevention of over-current levels and other
abnormal operating conditions. If any products described in this document represent goods or technologies subject to certain restrictions on export under
the Foreign Exchange and Foreign Trade Law of Japan, the US Export Administration Regulations or the applicable laws of any other country, the prior authorization by the respective government entity will be required for export of those products.
Trademarks and Notice
The contents of this document are subject to change without notice. This document may contain information on a Spansion product under development by
Spansion LLC. Spansion LLC reserves the right to change or discontinue work on any product without notice. The information in this document is provided
as is without warranty or guarantee of any kind as to its accuracy, completeness, operability, fitness for particular purpose, merchantability, non-infringement
of third-party rights, or any other warranty, express, implied, or statutory. Spansion LLC assumes no liability for any damages of any kind arising out of the
use of the information in this document.
Copyright © 2005 Spansion LLC. All rights reserved. Spansion, the Spansion logo, MirrorBit, combinations thereof, and ExpressFlash are trademarks of Spansion LLC. Other company and product names used in this publication are for identification purposes only and may be trademarks of their respective companies.
Flash Memory Erase Mode Comparison
erase_mode_comp_AN_A0 August 4, 2005
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF