
************************************************************************
************************************************************************
**                                                                    **
**  Application notes for AMD FLASH memory devices                    **
**                                                                    **
** To find the application notes for your specific device you must    **
** search for the device using the 'core' device name.                **
** As an example using the Am30LV0064D 44 pin TSOPII you would        **
** search on '30LV0064'                                               **
**                                                                    **
************************************************************************
************************************************************************

************************************************************************

Am29LV065D
----------
Due to ram limitations on the Unisystem programmers, this 64Mbit device
had to be split into 2 equal 32Mbit Quadrants.

Note - Since this device operates with a 8 bit data bus, all the below
numbers are in byte values


                                         Device mapping:
                                 ----------------------  0Mbit
Unisystem RAM mapping:          | Quadrant L           |
                                | 0-3FFFFF hex         |
 --------------- 0Mbit          |                      |
| 0 hex         |               |                      |
|               |---------->    |                      |
|               |               |----------------------| 32Mbit
|               |               |                      |
|               |---------->    | Quadrant U           |
| 400000 hex    |               | 400000->7FFFFF hex   |
 --------------- 32Mbit         |                      |
                                 ----------------------  64Mbit

  Quadrant L   =  Device addresses 0 -> 3FFFFF hex

  Quadrant U   =  Device addresses 400000 -> 7FFFFF hex

  SecSi Secure =  Device addresses 0 ->FF and 400000 ->4000FF hex
                  accessible as the last sector within the upper quadrant
--------------------------------------------------------------------------
Example of downloading a data file:

An example of downloading a 8 Megabytes (0 - 7FFFFF hex) file. You will
need to download the files in two halves. The first half is for Quadrant L.
The second half is for Quadrant U.

** NOTE:
   Quadrant L = Device addresses 000000 -> 3FFFFF hex
   Quadrant L settings:

I/O Translation Format     99
I/O addr offset            0
Memory begin address       0
User data size             400000

Steps:
1) Download the first half (0-400000 hex) of the data file into Quadrant L.
2) Program the device.

** NOTE:
   Quadrant U = Device addresses 400000 -> 7FFFFF hex
   Quadrant U settings:

I/O Translation Format     99
I/O addr offset            400000
Memory begin address       0
User data size             400000

Steps:
1)Download the second half (400000-7FFFFF)of the data file into Quadrant U.
2)Program the device.


--------------------------------------------------------------------------
Example of editing device data in the memory editor:
If data editing needs to done in the user RAM memory editor the appropriate
Quadrant Menu Selection (see table above) must first be determined. As an
example if editing data at the device address starting at location 4F8000
hex, that device address location would fall into the Upper Quadrant.
To find where location 4F8000 hex corresponds to location in the Quadrant
U subtract the beginning device address range from the location you want
to edit.
In this case the location of device address location 4F8000 hex is in the
Quadrant U, memory address is F8000 hex
(F8000 hex = 4F8000 hex - 400000 hex).

--------------------------------------------------------------------------
IMPORTANT NOTE:
Sector ERASE operations may be performed within the selected quadrant and
the desired sectors. However the "Protect/Unprotect all sectors" prior to
the erase operation is performed ONLY within the lower quadrant algorithm.
Due to this, it is necessary to erase/program the lower quadrant first
prior to erasing the upper quadrant. This is ONLY needed when any sector
within the upper quadrant is previously protected.

--------------------------------------------------------------------------
The Secure Sector(SecSi) for this device consists of 256 bytes of One Time
Programmable (OTP) memory. This OTP sector is physically located at the two
none-continuos device locations 0x400000 -.0x4000FF. In UniFam programmers,
this sector is mapped as the last sector within the upper/last quadrant.
This OTP sector will have its program flag set to N (No by default) in
the Sector Configuration Screen.  This Program flag controls the following
device operations: Blank Check, Illegal Bit Check, Program and Verify.
In order to perform these operations on this sector, this flag must be set
to Y, by using More->Device Operation->Device configuration screen.

**************************************************************************

Am29LV652D
----------

Due to ram limitations on the Unisystem programmers, this device had to be
split into 4 equal 32Mbit quadrants. Make menu selections as:

  suffix A0 to program the first Quadrant, CE
  suffix A1 to program the second Quadrant, CE
  suffix A2 to program the third Quadrant, CE2
  suffix A3 to program the fourth Quadrant, CE2

Note - This device consists of two independent LV065D devices each being
enabled individually using CE and CE2.


Note - Since this device operates with a 8 bit data bus, all the below
numbers are in byte values


To load data from a data file for a particular Quadrant of the device you must
set the download options as shown in the table below.  The memory size of each
Quadrant corresponds to a 128Mbit device.
                I/O addr     Memory begin   User data     Device address
Menu selection: offset:      address:       size:         range:
Quadrant A0:    0 hex        0 hex          400000 hex    0      -> 3FFFFF hex
Quadrant A1:    400000 hex   0 hex          400000 hex    400000 -> 7FFFFF hex
Quadrant A2:    800000 hex   0 hex          400000 hex    000000 -> 3FFFFF hex
Quadrant A3:    C00000 hex   0 hex          400000 hex    400000 -> 7FFFFF hex

--------------------------------------------------------------------------
This device basically consists of two identical Am29LV065D devices stacked
together (CE, and CE2). There are two Secure Silicon (SecSi) Sectors of 256
bytes each within it, and are accessible using the algorithms with A1 and A3
suffices.
Upon selecting these algorithms, programming operations on these two
sectors are defaulted to "NO". In order to enable programming these sectors,
use More->Device Operations->Device configuration and set the Program flag
to YES for these sectors, if programming operations are needed.
Please see the notes for Am29LV065D for more information on this device.

--------------------------------------------------------------------------
IMPORTANT NOTE:
Sector ERASE operations may be performed within the selected quadrant and
the desired sectors in each of the independent LV065D dies. However the
"Protect/Unprotect all sectors" prior to the erase operation is performed
ONLY within the algorithm with A0 and A2 suffices respectively for the
first (CE) and the second (CE2) die. Due to this, it is necessary to erase
the quadrant with A0 suffix for the first die (CE) and the quadrant with A2
suffix for the second die (CE2). This is ONLY needed when any sector within
the upper quadrants of the individual chips (CE and CE2) are previously
protected.

**************************************************************************

DS42589
------------
Am41DL6408G
------------
Am42DL6404G
------------
Am42DL640AG
------------
Am49DL640BG
------------

This device has a 256 bytes SecSi sector and is accessible using the -L
algorithm.

--------------------------------------------------------------------------
Due to ram limitations on the Unisystem programmers, this 64Mbit device
had to be split into 2 equal 32Mbit Quadrants.


Note - Since this device operates with a 16 bit data bus, all the below
numbers are in word (double-bytes) values

                                         Device mapping:
                                 ----------------------  0Mbit
Unisystem RAM mapping:          | Quadrant L           |
                                | 0-1FFFFF hex         |
 --------------- 0Mbit          |                      |
| 0 hex         |               |                      |
|               |---------->    |                      |
|               |               |----------------------| 32Mbit
|               |               |                      |
|               |---------->    | Quadrant U           |
| 200000 hex    |               | 200000->3FFFFF hex   |
 --------------- 32Mbit         |                      |
                                 ----------------------  64Mbit

  Quadrant L   =  Device addresses 0 -> 1FFFFF hex

  Quadrant U   =  Device addresses 200000 -> 3FFFFF hex

--------------------------------------------------------------------------
Example of downloading a data file:

An example of downloading a 8 Megabytes (0 - 3FFFFF hex) file. You will
need to download the files in two halves. The first half is for Quadrant L.
The second half is for Quadrant U.

** NOTE:
   Quadrant L = Device addresses 000000 -> 1FFFFF hex
   Quadrant L settings:

I/O Translation Format     99
I/O addr offset            0
Memory begin address       0
User data size             200000 (word)

Steps:
1) Download the first half (0-1FFFFF hex) of the data file into Quadrant L.
2) Program the device.

** NOTE:
   Quadrant U = Device addresses 200000 -> 3FFFFF hex
   Quadrant U settings:

I/O Translation Format     99
I/O addr offset            200000 (word)
Memory begin address       0
User data size             200000 (word)

Steps:
1)Download the second half (200000-3FFFFF)of the data file into Quadrant U.
2)Program the device.

--------------------------------------------------------------------------
Example of editing device data in the memory editor:
If data editing needs to done in the user RAM memory editor the appropriate
Quadrant Menu Selection (see table above) must first be determined. As an
example if editing data at the device address starting at location 2F8000
hex, that device address location would fall into the Upper Quadrant.
To find where location 2F8000 hex corresponds to location in the Quadrant
U subtract the beginning device address range from the location you want
to edit.
In this case the location of device address location 2F8000 hex is in the
Quadrant U, memory address is F8000 hex
(F8000 hex = 2F8000 hex - 200000 hex).

--------------------------------------------------------------------------
IMPORTANT NOTE:
Sector ERASE operations may be performed within the selected quadrant and
the desired sectors. However the "Protect/Unprotect all sectors" prior to
the erase operation is performed ONLY within the lower quadrant algorithm.
Due to this, it is necessary to erase/program the lower quadrant first
prior to erasing the upper quadrant. This is ONLY needed when any sector
within the upper quadrant is previously protected.

**************************************************************************

Am29LV641M
------------
Am29LV640M
------------
Am29LV641G
------------
Am29LV640DU
------------
Am29LV640DL
------------
Am29LV640GU
------------
Am29LV641D
------------
Am29LV640DH
------------

Due to ram limitations on the Unisystem programmers, this 64Mbit device
had to be split into 2 equal 32Mbit Quadrants.

Note - Since this device operates with a 16 bit data bus, all the below
numbers are in word (double-bytes) values

                                         Device mapping:
                                 ----------------------  0Mbit
Unisystem RAM mapping:          | Quadrant L           |
                                | 0-1FFFFF hex         |
 --------------- 0Mbit          |                      |
| 0 hex         |               |                      |
|               |---------->    |                      |
|               |               |----------------------| 32Mbit
|               |               |                      |
|               |---------->    | Quadrant U           |
| 200000 hex    |               | 200000->3FFFFF hex   |
 --------------- 32Mbit         |                      |
                                 ----------------------  64Mbit

  Quadrant L   =  Device addresses 0 -> 1FFFFF hex

  Quadrant U   =  Device addresses 200000 -> 3FFFFF hex


--------------------------------------------------------------------------
Example of downloading a data file:

An example of downloading a 8 Megabytes (0 - 3FFFFF hex) file. You will
need to download the files in two halves. The first half is for Quadrant L.
The second half is for Quadrant U.

** NOTE:
   Quadrant L = Device addresses 000000 -> 1FFFFF hex
   Quadrant L settings:

I/O Translation Format     99
I/O addr offset            0
Memory begin address       0
User data size             200000 (word)

Steps:
1) Download the first half (0-1FFFFF hex) of the data file into Quadrant L.
2) Program the device.

** NOTE:
   Quadrant U = Device addresses 200000 -> 3FFFFF hex
   Quadrant U settings:

I/O Translation Format     99
I/O addr offset            200000 (word)
Memory begin address       0
User data size             200000 (word)

Steps:
1)Download the second half (200000-3FFFFF)of the data file into Quadrant U.
2)Program the device.


--------------------------------------------------------------------------
Example of editing device data in the memory editor:
If data editing needs to done in the user RAM memory editor the appropriate
Quadrant Menu Selection (see table above) must first be determined. As an
example if editing data at the device address starting at location 2F8000
hex, that device address location would fall into the Upper Quadrant.
To find where location 2F8000 hex corresponds to location in the Quadrant
U subtract the beginning device address range from the location you want
to edit.
In this case the location of device address location 2F8000 hex is in the
Quadrant U, memory address is F8000 hex
(F8000 hex = 2F8000 hex - 200000 hex).

--------------------------------------------------------------------------
IMPORTANT NOTE:
Sector ERASE operations may be performed within the selected quadrant and
the desired sectors. However the "Protect/Unprotect all sectors" prior to
the erase operation is performed ONLY within the lower quadrant algorithm.
Due to this, it is necessary to erase/program the lower quadrant first
prior to erasing the upper quadrant. This is ONLY needed when any sector
within the upper quadrant is previously protected.

--------------------------------------------------------------------------
The Secure Sector(SecSi) for this device consists of 256 bytes of One Time
Programmable (OTP) memory. The SecSi sector is accessible using the UPPER
algorithm and is mapped as the last sector.

**************************************************************************

Am29LV642D
------------
Am29LV642M
------------

Due to ram limitations on the Unisystem programmers, this device had to be
split into 4 equal 32Mbit quadrants. Make menu selections as:

  suffix A0 to program the first Quadrant, CE
  suffix A1 to program the second Quadrant, CE
  suffix A2 to program the third Quadrant, CE2
  suffix A3 to program the fourth Quadrant, CE2

Note - This device consists of two independent LV0641 devices each being
enabled individually using CE and CE2.


Note - Since this device operates with a 16 bit data bus, all the below
numbers are in word (16 bit) values.


To load data from a data file for a particular Quadrant of the device you must
set the download options as shown in the table below.  The memory size of each
Quadrant corresponds to a 128Mbit device.
                I/O addr     Memory begin   User data     Device address
Menu selection: offset:      address:       size:         range:
Quadrant A0:    0 hex        0 hex          200000 hex    0      -> 1FFFFF hex
Quadrant A1:    200000 hex   0 hex          200000 hex    200000 -> 3FFFFF hex
Quadrant A2:    400000 hex   0 hex          200000 hex    000000 -> 1FFFFF hex
Quadrant A3:    600000 hex   0 hex          200000 hex    200000 -> 3FFFFF hex

--------------------------------------------------------------------------
This device basically consists of two identical Am29LV641D devices stacked
together (CE, and CE2). There are two Secure Silicon (SecSi) Sectors of 256
bytes each within it, and are accessible using the algorithms with A1 and A3
suffices.
Upon selecting these algorithms, programming operations on these two
sectors are defaulted to "NO". In order to enable programming these sectors,
use More->Device Operations->Device configuration and set the Program flag
to YES for these sectors, if programming operations are needed.
Please see the notes for Am29LV641 for more information on this device.

--------------------------------------------------------------------------
IMPORTANT NOTE:
Sector ERASE operations may be performed within the selected quadrant and
the desired sectors in each of the independent LV641 dies. However the
"Protect/Unprotect all sectors" prior to the erase operation is performed
ONLY within the algorithm with A0 and A2 suffices respectively for the
first (CE) and the second (CE2) dies. Due to this, it is necessary to erase
the quadrant with A0 suffix for the first die (CE) and the quadrant with A2
suffix for the second die (CE2). This is ONLY needed when any sector within
the upper quadrants of the individual chips (CE and CE2) are previously
protected.

**************************************************************************

Am29DL642D
----------
Am29DL642G
----------

Due to ram limitations on the Unisystem programmers, this device had to be
split into 4 equal 32Mbit quadrants. Make menu selections as:

  suffix A0 to program the first Quadrant, CE
  suffix A1 to program the second Quadrant, CE
  suffix A2 to program the third Quadrant, CE2
  suffix A3 to program the fourth Quadrant, CE2

Note - This device consists of two independent 29DLV640 devices each being
enabled individually using CE and CE2.

Note - Since this device operates with a 16 bit data bus, all the below
numbers are in word (16 bit) values.


To load data from a data file for a particular Quadrant of the device you must
set the download options as shown in the table below.  The memory size of each
Quadrant corresponds to a 128Mbit device.
                I/O addr     Memory begin   User data     Device address
Menu selection: offset:      address:       size:         range:
Quadrant A0:    0 hex        0 hex          200000 hex    0      -> 1FFFFF hex
Quadrant A1:    200000 hex   0 hex          200000 hex    200000 -> 3FFFFF hex
Quadrant A2:    400000 hex   0 hex          200000 hex    000000 -> 1FFFFF hex
Quadrant A3:    600000 hex   0 hex          200000 hex    200000 -> 3FFFFF hex

--------------------------------------------------------------------------
This device basically consists of two identical Am29DL640 devices stacked
together (CE, and CE2). There are two Secure Silicon (SecSi) Sectors of 256
bytes each within it, and are accessible using the algorithms with A1 and A3
suffices.
Upon selecting these algorithms, programming operations on these two
sectors are defaulted to "NO". In order to enable programming these sectors,
use More->Device Operations->Device configuration and set the Program flag
to YES for these sectors, if programming operations are needed.
Please see the notes for Am29LV641 for more information on this device.

--------------------------------------------------------------------------
IMPORTANT NOTE:
Sector ERASE operations may be performed within the selected quadrant and
the desired sectors in each of the independent 29DL640 dies. However the
"Protect/Unprotect all sectors" prior to the erase operation is performed
ONLY within the algorithm with A0 and A2 suffices respectively for the
first (CE) and the second (CE2) dies. Due to this, it is necessary to erase
the quadrant with A0 suffix for the first die (CE) and the quadrant with A2
suffix for the second die (CE2). This is ONLY needed when any sector within
the upper quadrants of the individual chips (CE and CE2) are previously
protected.


**************************************************************************

Am29DL640D
----------
Am29DL640G
----------
Am29DL640H
----------

Due to ram limitations on the Unisystem programmers, this 64Mbit device
had to be split into 2 equal 32Mbit Quadrants.

Note - Since this device operates with a 16 bit data bus, all the below
numbers are in word (double-bytes) values


                                         Device mapping:
                                 ----------------------  0Mbit
Unisystem RAM mapping:          | Quadrant L           |
                                | 0-1FFFFF hex         |
 --------------- 0Mbit          |                      |
| 0 hex         |               |                      |
|               |---------->    |                      |
|               |               |----------------------| 32Mbit
|               |               |                      |
|               |---------->    | Quadrant U           |
| 200000 hex    |               | 200000->3FFFFF hex   |
 --------------- 32Mbit         |                      |
                                 ----------------------  64Mbit

  Quadrant L   =  Device addresses 0 -> 1FFFFF hex

  Quadrant U   =  Device addresses 200000 -> 3FFFFF hex


--------------------------------------------------------------------------
Example of downloading a data file:

An example of downloading a 8 Megabytes (0 - 3FFFFF hex) file. You will
need to download the files in two halves. The first half is for Quadrant L.
The second half is for Quadrant U.

** NOTE:
   Quadrant L = Device addresses 000000 -> 1FFFFF hex
   Quadrant L settings:

I/O Translation Format     99
I/O addr offset            0
Memory begin address       0
User data size             200000 (word)

Steps:
1) Download the first half (0-1FFFFF hex) of the data file into Quadrant L.
2) Program the device.

** NOTE:
   Quadrant U = Device addresses 200000 -> 3FFFFF hex
   Quadrant U settings:

I/O Translation Format     99
I/O addr offset            200000 (word)
Memory begin address       0
User data size             200000 (word)

Steps:
1)Download the second half (200000-3FFFFF)of the data file into Quadrant U.
2)Program the device.


--------------------------------------------------------------------------
Example of editing device data in the memory editor:
If data editing needs to done in the user RAM memory editor the appropriate
Quadrant Menu Selection (see table above) must first be determined. As an
example if editing data at the device address starting at location 2F8000
hex, that device address location would fall into the Upper Quadrant.
To find where location 2F8000 hex corresponds to location in the Quadrant
U subtract the beginning device address range from the location you want
to edit.
In this case the location of device address location 2F8000 hex is in the
Quadrant U, memory address is F8000 hex
(F8000 hex = 2F8000 hex - 200000 hex).

--------------------------------------------------------------------------
IMPORTANT NOTE:
Sector ERASE operations may be performed within the selected quadrant and
the desired sectors. However the "Protect/Unprotect all sectors" prior to
the erase operation is performed ONLY within the lower quadrant algorithm.
Due to this, it is necessary to erase/program the lower quadrant first
prior to erasing the upper quadrant. This is ONLY needed when any sector
within the upper quadrant is previously protected.

--------------------------------------------------------------------------
The Secure Sector(SecSi) for this device consists of 256 bytes of One Time
Programmable (OTP) memory. The SecSi sector is accessible using the LOWER
algorithm and is mapped as the last sector.

**************************************************************************

Am29PDL128G
-----------

Due to ram limitations on the Unisystem programmers, this device had to be
split into 4 equal 32Mbit quadrants. Make menu selections as:

  suffix A0 to program the first Quadrant
  suffix A1 to program the second Quadrant
  suffix A2 to program the third Quadrant
  suffix A3 to program the fourth Quadrant

Note - Since this device operates with a 16 bit data bus, all the below
numbers are in word (double-byte) values.

To load data from a data file for a particular Quadrant of the device you must
set the download options as shown in the table below.  The memory size of each
Quadrant corresponds to a 128Mbit device.
                I/O addr     Memory begin   User data     Device address
Menu selection: offset:      address:       size:         range:
Quadrant A0:    0 hex        0 hex          400000 hex    0      -> 1FFFFF hex
Quadrant A1:    400000 hex   0 hex          400000 hex    200000 -> 3FFFFF hex
Quadrant A2:    800000 hex   0 hex          400000 hex    400000 -> 5FFFFF hex
Quadrant A3:    C00000 hex   0 hex          400000 hex    600000 -> 7FFFFF hex
--------------------------------------------------------------------------
Notes on Sector Protection Flags
--------------------------------
This device contains four/five levels of Sector Protections as follow:
1. Dynamic Protection Bits (DPB) -
   These "per sector" protections flags loose their "set" state per power/reset
   cycle and are ignored by the UniFam programmers. They maybe set/reset
   individually as often as needed during operations.
2. Persistent Protection Bits (PPB) -
   These "per group" protections flags operate very similar to all the other
   AMD devices in terms of their "set" state. Upon power up/reset cycles these
   flags do not loose their set states. Their state may be altered (set or erased
   during erase) providing that the PPB Lock (next item) is not set. These flags
   may not be altered more than 100 cycles or they will loose their liability.
3. Persistent Protection Bit Lock (PPB Lock) -
   This single protection bit, if set, it globally disables any change to the PPBs
   (item 2 of above). This protection flag maybe be set during operation, and it
   will remain "set" as long as the device is not reset or power cycled. This
   protection flag gets "reset" upon power up/reset cycles only and if the
   following (item 4) below is not "set" upon power up.
4. Password Protection Mode Locking Bit (PPMLB) -
   This "permanent" protection bit controls the mode of the operation of device.
   If this protection bit is "set", the device will operate in "password" mode.
   In password mode (PPMLB=set) enabled, the PPB Lock bit (item 3 of above) will
   power up in the "set" state. With PPB Lock bit being set, there is no way to
   alter the state of PPB flags. i.e. PPB Protected sectors remain un-alterable.
   When this password future is used (set), the only way to alter the state of
   the PPB Lock, which in turn would allow "unsetting" the PPBs and device content
   modification, is to provide the previously programmed password (see below).
5. Password - There are 64 bits (4 words) of One Time Programmable (OTP) data
   which resides/overlaps the first 8 bytes of the SecSi sector and are used as
   password. Only bits with the state of "1" maybe reprogrammed to "0" state as
   long as the PPMLB is not "set" by the end-user or the SecSi sector flag is not
   factory/user protected. If the PPMLB is set, attempting to read these 64 bits
   will return blank state.
6. Persistent Protection Mode Locking Bit (SPMLB) -
   This single bit, when set, it disbales the password protection permanently.
   It can be set only if the PPMLB is not previously set. When this SPMLB is set
   the device will power up with the state of the PPB Lock cleared, allowing
   modification to the PPBs.

---------------------------------------------------------------------------------
The Sector Protection flags for this device currently is not supported.
The PASSWORD protection for this device is not currently supported.

**************************************************************************

Am30LV0064D
-----------

Please note that for the 40 pin FBGA package, pin one of the device is located
on lower left of the PPI-1137.

Due to the special Spare Area addressing for this device, all the Spare Area
data is grouped together as one sector starting at address 400000 hex.
Load operations will read all the spare areas, and stores them grouped
together at location 400000 hex.
Program operations will program the spare areas, using the data located at the
hex-address 400000.
Verify operations, will report mis-match of the Spare Area data at address
400000 hex.


Due to ram limitations on the Unisystem programmers, this 64Mbit device had to
be split into 2 equal 32Mbit Quadrants . Make menu selections as:

  suffix L = The Quadrant of the 64Mbit device that has
  Device addresses 0 -> 1FFFFF hex ( 0 -> 3FFFFF for 8-Bit devices)
  suffix U = The Quadrant of the 64Mbit device that has
  Device addresses 200000 -> 3FFFFF hex ( 400000 -> 7FFFFF for 8-Bit devices)

Protection register data can be programmed with either Quadrant selected.
To load data from a data file for either Quadrant of the device you must set
the download options as shown in the table below.  The memory size of each
Quadrant corresponds to a 64Mbit device.

                 I/O addr      Memory begin   User data    Device addr
Menu selection:  offset:       address:       size:        range:
Quadrant    L :  0 hex         0 hex          200000 hex   0      -> 1FFFFF hex
Quadrant    U :  400000 hex    0 hex          200000 hex   200000 -> 3FFFFF hex
Note - For an 8-Bit device the User Data Sizes and Device Address Ranges would
need to be doubled.


******************************************************************************

29LV128ML
------------
29LV128MH
------------

WARNING: Enabling Erase for one of the Quadrants Menu-selections will erase
the whole device; i.e. This Erase will perform a Full Chip Erase Operation.

*------- User RAM Partition as it relates to Menu Selections ------------*
Due to User RAM limitations on the UniFam programmers, this device had to be
split into 4 equal 32MegaBit Quadrants. The corresponding menu selections are:
29LV128Mx-Package-A0 to program the first Quadrant
29LV128Mx-Package-A1 to program the second Quadrant
29LV128Mx-Package-A2 to program the third Quadrant
29LV128Mx-Package-A3 to program the fourth Quadrant
NOTE:
     "x" is defined as either "L" or "H"
     "Package" is defined as "EC", "FC", "PC", etc...

To load data from a data file for a particular Quadrant of the device
you must set the download options as shown in the table below:
                                  Memory    User        Device
                      I/O addr    begin     data        address
Menu selection:       offset:     address:  size:       range:
29LV128Mx-Package-A0: 0 hex       0 hex     200000 hex  0      -> 1FFFFF hex
29LV128Mx-Package-A1: 400000 hex  0 hex     200000 hex  200000 -> 3FFFFF hex
29LV128Mx-Package-A2: 800000 hex  0 hex     200000 hex  400000 -> 5FFFFF hex
29LV128Mx-Package-A3: C00000 hex  0 hex     200000 hex  600000 -> 7FFFFF hex

*- Example: Downloading a data file for 29LV128Mx-Package-A1 menu selection -*
NOTE: This is the Quadrant of the 128Mbit device that has the device
addresses: 200000 -> 3FFFFF hex

This example would be in regard to loading data into the programmer
memory map from a datafile which is intended to be programmed into the
29LV128Mx-Package-A1 Quadrant of the device:

I/O Translation Format     99
I/O addr offset            400000
Memory begin address       0
User data size             200000

Example of editing device data in the memory editor:
If data editing needs to done in the user RAM memory editor the appropriate
Quadrant Menu Selection (see table above) must first be determined. As an
example if editing data at the device address starting at location 2F8000 hex,
that device address location would fall into the Second Quadrant.  To find
where location 2F8000 hex corresponds to location in a specific Quadrant you
must subtract the beginning device address range from the location you want to
edit.  Therefore, in this case, the location of device address location 2F8000
hex is in the Second Quadrant with a User RAM memory address of F8000 hex.
Example: 2F8000 hex - 200000 hex = F8000 hex

*------ SecSi Sector Data -----------*
SecSi Sector is not supported currently for these devices.

******************************************************************************
29LV256ML
------------
29LV256MH
------------

WARNING: Setting the Erase flag 'Y' or performing the Erase operation for one
of the Octants Menu-selections will erase the whole device; i.e. This Erase
will perform a Full Chip Erase Operation.

*------- User RAM Partition as it relates to Menu Selections ------------*
Due to User RAM limitations on the UniFam programmers, this device had to be
split into 8 equal 32MegaBit Octants. The corresponding menu selections are:
29LV256Mx-Package-A0 to program the first Octant
29LV256Mx-Package-A1 to program the second Octant
29LV256Mx-Package-A2 to program the third Octant
29LV256Mx-Package-A3 to program the fourth Octant
29LV256Mx-Package-A4 to program the fifth Octant
29LV256Mx-Package-A5 to program the sixth Octant
29LV256Mx-Package-A6 to program the seventh Octant
29LV256Mx-Package-A7 to program the eightth Octant

NOTE:
   1)"x" is defined as either "L" or "H"
     "Package" is defined as "EC", "FC", "PC", etc...

   2) Since this device operates with a 16 bit data bus, all the below
      numbers are in word (double-bytes) values

To load data from a data file for a particular Octant of the device
you must set the download options as shown in the table below:
                                  Memory    User        Device
                      I/O addr    begin     data        address
Menu selection:       offset:     address:  size:       range:
29LV256Mx-Package-A0: 0 hex       0 hex     200000 hex  0      -> 1FFFFF hex
29LV256Mx-Package-A1: 200000 hex  0 hex     200000 hex  200000 -> 3FFFFF hex
29LV256Mx-Package-A2: 400000 hex  0 hex     200000 hex  400000 -> 5FFFFF hex
29LV256Mx-Package-A3: 600000 hex  0 hex     200000 hex  600000 -> 7FFFFF hex
29LV256Mx-Package-A4: 800000 hex  0 hex     200000 hex  800000 -> 9FFFFF hex
29LV256Mx-Package-A5: A00000 hex  0 hex     200000 hex  A00000 -> BFFFFF hex
29LV256Mx-Package-A6: C00000 hex  0 hex     200000 hex  C00000 -> DFFFFF hex
29LV256Mx-Package-A7: E00000 hex  0 hex     200000 hex  E00000 -> FFFFFF hex


*- Example: Downloading a data file for 29LV256Mx-Package-A1 menu selection -*
NOTE: This is the Octant of the 256Mbit device that has the device
addresses: 200000 -> 3FFFFF hex

This example would be in regard to loading data into the programmer
memory map from a datafile which is intended to be programmed into the
29LV256Mx-Package-A1 Octant of the device:

I/O Translation Format     99
I/O addr offset            200000
Memory begin address       0
User data size             200000 (word)

Example of editing device data in the memory editor:
If data editing needs to done in the user RAM memory editor the appropriate
Octant Menu Selection (see table above) must first be determined. As an
example if editing data at the device address starting at location 2F8000 hex,
that device address location would fall into the Second Octant.  To find
where location 2F8000 hex corresponds to location in a specific Octant you
must subtract the beginning device address range from the location you want to
edit.  Therefore, in this case, the location of device address location 2F8000
hex is in the Second Octant with a User RAM memory address of F8000 hex.
Example: 2F8000 hex - 200000 hex = F8000 hex

*------ SecSi Sector Data -----------*

SecSi Sector is not supported currently for these devices.

******************************************************************************
******************************************************************************




