Electronic Components Datasheet Search
  English  ▼
ALLDATASHEET.NET

X  

AM29LV065MU112REF Datasheet(PDF) 29 Page - Advanced Micro Devices

Part # AM29LV065MU112REF
Description  64 Megabit (8 M x 8-Bit) MirrorBit??3.0 Volt-only Uniform Sector Flash Memory with VersatileI/O??Control
PDF  62 Pages
Scroll/Zoom Zoom In 100%  Zoom Out
Manufacturer  AMD [Advanced Micro Devices]
Direct Link  http://www.amd.com
Logo AMD - Advanced Micro Devices

AM29LV065MU112REF Datasheet(HTML) 29 Page - Advanced Micro Devices

Back Button AM29LV065MU112REF Datasheet HTML 25Page - Advanced Micro Devices AM29LV065MU112REF Datasheet HTML 26Page - Advanced Micro Devices AM29LV065MU112REF Datasheet HTML 27Page - Advanced Micro Devices AM29LV065MU112REF Datasheet HTML 28Page - Advanced Micro Devices AM29LV065MU112REF Datasheet HTML 29Page - Advanced Micro Devices AM29LV065MU112REF Datasheet HTML 30Page - Advanced Micro Devices AM29LV065MU112REF Datasheet HTML 31Page - Advanced Micro Devices AM29LV065MU112REF Datasheet HTML 32Page - Advanced Micro Devices AM29LV065MU112REF Datasheet HTML 33Page - Advanced Micro Devices Next Button
Zoom Inzoom in Zoom Outzoom out
 29 / 62 page
background image
September 12, 2006
Am29LV065MU
27
DA TA
SH EET
and data requirements for the byte program command
sequence.
When the Embedded Program algorithm is complete,
the device then returns to the read mode and ad-
dresses are no longer latched. The system can deter-
mine the status of the program operation by using
DQ7, DQ6, or RY/BY#. See “Write Operation Status”
on page 35. for information on these status bits.
Any commands written to the device during the Em-
bedded Program Algorithm are ignored. Note that a
hardware reset immediately terminates the program
operation. The program command sequence should
be reinitiated once the device has returned to the read
mode, to ensure data integrity. Note that the SecSi
Sector, autoselect, and CFI functions are unavailable
when a program operation is in progress.
Programming is allowed in any sequence and across
sector boundaries. A bit cannot be programmed
from “0” back to a “1.” Attempting to do so may
cause the device to set DQ5 = 1, or cause the DQ7
and DQ6 status bits to indicate the operation was suc-
cessful. However, a succeeding read will show that the
data is still “0.” Only erase operations can convert a “0”
to a “1.”
Unlock Bypass Command Sequence
The unlock bypass feature allows the system to pro-
gram bytes to the device faster than using the stan-
dard program command sequence. The unlock bypass
command sequence is initiated by first writing two un-
lock cycles. This is followed by a third write cycle con-
taining the unlock bypass command, 20h. The device
then enters the unlock bypass mode. A two-cycle un-
lock bypass program command sequence is all that is
required to program in this mode. The first cycle in this
sequence contains the unlock bypass program com-
mand, A0h; the second cycle contains the program
address and data. Additional data is programmed in
the same manner. This mode dispenses with the initial
two unlock cycles required in the standard program
command sequence, resulting in faster total program-
ming time. Table 10 shows the requirements for the
command sequence.
During the unlock bypass mode, only the Unlock By-
pass Program and Unlock Bypass Reset commands
are valid. To exit the unlock bypass mode, the system
must issue the two-cycle unlock bypass reset com-
mand sequence. The first cycle must contain the data
90h. The second cycle must contain the data 00h. The
device then returns to the read mode.
Write Buffer Programming
Write buffer programming allows the system to write a
maximum of 32 bytes in one programming operation.
The effective programming time is faster than the stan-
dard programming algorithms. The write buffer pro-
gramming command sequence is initiated by first
writing two unlock cycles. This is followed by a third
write cycle containing the Write Buffer Load command
written at the Sector Address in which programming
will occur. The fourth cycle writes the sector address
and the number of byte locations, minus one, to be
programmed. For example, if the system will program
6 unique address locations, then 05h should be written
to the device. This tells the device how many write
buffer addresses will be loaded with data and therefore
when to expect the Program Buffer to Flash command.
The number of locations to program cannot exceed
the size of the write buffer or the operation will abort.
The fifth cycle writes the first address location and
data to be programmed. A write-buffer-page is se-
lected by address bits A
MAX–A5. All subsequent ad-
dress/data
pairs
m u st
f a ll
within
the
selected-write-buffer-page. The system then writes the
remaining address/data pairs into the write buffer.
Write buffer locations may be loaded in any order.
The write-buffer-page address must be the same for
all address/data pairs loaded into the write buffer. That
is, write buffer programming cannot occur across mul-
tiple write-buffer pages or sectors. If the system at-
tempts to load programming data outside of the
selected write-buffer page, the operation will abort.
Note that if a Write Buffer address location is loaded
multiple times, the address/data pair counter will be
decremented for every data load operation. The host
s ystem mu st therefore account fo r l oading a
write-buffer location more than once. The counter dec-
rements for each data load operation, not for each
unique write-buffer-address location. Additionally, the
last data loaded prior to the Program Buffer to Flash
command will be programmed into the device. Note
also that if an address location is loaded more than
once into the buffer, the final data loaded for that ad-
dress will be programmed.
Once the specified number of write buffer locations
have been loaded, the system must then write the Pro-
gram Buffer to Flash command at the sector address.
Any other address and data combination aborts the
Write Buffer Programming operation. The device then
begins programming. Data polling should be used
while monitoring the last address location loaded into
the write buffer. DQ7, DQ6, DQ5, and DQ1 should be
monitored to determine the device status during Write
Buffer Programming.
The write-buffer programming operation can be sus-
pended using the standard program suspend/resume
commands. Upon successful completion of the Write
Buffer Programming operation, the device is ready to
execute the next command.



Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62


Datasheet Download

Go To PDF Page


Link URL



Does ALLDATASHEET help your business so far?  [ DONATE ] 

About Alldatasheet   |   Advertisement   |   Contact us   |   Privacy Policy   |   Link to Datasheet    |   Link Exchange   |   Manufacturer List
All Rights Reserved©Alldatasheet.com


Mirror Sites
English : Alldatasheet.com  |   English : Alldatasheet.net  |   Chinese : Alldatasheetcn.com  |   German : Alldatasheetde.com  |   Japanese : Alldatasheet.jp
Russian : Alldatasheetru.com  |   Korean : Alldatasheet.co.kr  |   Spanish : Alldatasheet.es  |   French : Alldatasheet.fr  |   Italian : Alldatasheetit.com
Portuguese : Alldatasheetpt.com  |   Polish : Alldatasheet.pl  |   Vietnamese : Alldatasheet.vn
Indian : Alldatasheet.in  |   Mexican : Alldatasheet.com.mx  |   British : Alldatasheet.co.uk  |   New Zealand : Alldatasheet.co.nz
Family Site : ic2ic.com  |   icmetro.com