HY29LV320 Datasheet, PDF (13/44 Pages) Hynix Semiconductor – 32 Mbit (2M x 16) Low Voltage Flash Memory

Table 6. Sector Groups - Top Boot Version
Group
Sectors
(Table 1)
Group Address Block Size
A[20:12]
(KWords)
SG0
S0 0 0 0 0 0 0 X X X 32
0 0 0 0 0 1X X X
SG1 S1 - S3 0 0 0 0 1 0 X X X 96
0 0 0 0 1 1X X X
SG2 S4 - S7 0 0 0 1 X X X X X 128
SG3 S8 -S11 0 0 1 0 X X X X X 128
SG4 S12 - S15 0 0 1 1 X X X X X 128
SG5 S16 - S19 0 1 0 0 X X X X X 128
SG6 S20 - S23 0 1 0 1 X X X X X 128
SG7 S24 - S27 0 1 1 0 X X X X X 128
SG8 S28 - S31 0 1 1 1 X X X X X 128
SG9 S32 - S35 1 0 0 0 X X X X X 128
SG10 S36 - S39 1 0 0 1 X X X X X 128
SG11 S40 - S43 1 0 1 0 X X X X X 128
SG12 S44 - S47 1 0 1 1 X X X X X 128
SG13 S48 - S51 1 1 0 0 X X X X X 128
SG14 S52 - S55 1 1 0 1 X X X X X 128
SG15 S56 - S59 1 1 1 0 X X X X X 128
1 1 1 10 0XXX
SG16 S60 - S62 1 1 1 1 0 1 X X X 96
1 1 1 1 10XXX
SG17 S63 1 1 1 1 1 1 0 X X 16
SG18
S64 1 1 1 1 1 1 1 0 0
4
SG19 S65 1 1 1 1 1 1 1 0 1 4
SG20
S66 1 1 1 1 1 1 1 1 X
8
viously protected sector groups. This function can
be implemented either in-system or by using pro-
gramming equipment. Note that to unprotect any
sector, all unprotected sector groups must first be
protected prior to the first sector unprotect write
cycle. Also, the unprotect procedure will cause
all sectors to become unprotected, thus, sector
groups that require protection must be protected
again after the unprotect procedure is run.
This procedure requires V_ID on the RESET# pin
and uses standard microprocessor bus cycle tim-
ing to implement sector unprotection. The flow
chart in Figure 4 illustrates the algorithm.
Temporary Sector Unprotect Operation
This feature allows temporary unprotection of pre-
viously protected sector groups to allow changing
the data in-system. Temporary Sector Unprotect
mode is activated by setting the RESET# pin to
V_ID. While in this mode, formerly protected sec-
r1.3/May 02
HY29LV320
Table 7. Sector Groups - Bottom Boot Version
Group
Sectors
(Table 2)
Group Address Block Size
A[20:12]
(KWords)
SG0
S0 0 0 0 0 0 0 0 0 X
8
SG1
S1 0 0 0 0 0 0 0 1 0
4
SG2
S2 0 0 0 0 0 0 0 1 1
4
SG3
S3 0 0 0 0 0 0 1 X X 16
0 0 0 0 0 1X X X
SG4 S4 - S6 0 0 0 0 1 0 X X X 96
0 0 0 0 1 1X X X
SG5 S7 - S10 0 0 0 1 X X X X X 128
SG6 S11 - S14 0 0 1 0 X X X X X 128
SG7 S15 - S18 0 0 1 1 X X X X X 128
SG8 S19 - S22 0 1 0 0 X X X X X 128
SG9 S23 - S26 0 1 0 1 X X X X X 128
SG10 S27 - S30 0 1 1 0 X X X X X 128
SG11 S31 - S34 0 1 1 1 X X X X X 128
SG12 S35 - S38 1 0 0 0 X X X X X 128
SG13 S39 - S42 1 0 0 1 X X X X X 128
SG14 S43 - S46 1 0 1 0 X X X X X 128
SG15 S47 - S50 1 0 1 1 X X X X X 128
SG16 S51 - S54 1 1 0 0 X X X X X 128
SG17 S55 - S58 1 1 0 1 X X X X X 128
SG18 S59 - S62 1 1 1 0 X X X X X 128
1 1 1 10 0XXX
SG19 S63 - S65 1 1 1 1 0 1 X X X 96
1 1 1 1 10XXX
SG20 S66 1 1 1 1 1 1 X X X 32
tors can be programmed or erased by invoking
the appropriate commands (see Device Com-
mands section). Once V_ID is removed from RE-
SET#, all the previously protected sector groups
are protected again. Figure 5 illustrates the algo-
rithm.
NOTE: If WP#/ACC = V_IL, the boot sectors remain pro-
tected.
Electronic ID Operation (High Voltage Method)
The Electronic ID mode provides manufacturer
and device identification, sector protection verifi-
cation and Sec² region protection status through
identifier codes output on DQ[15:0]. This mode is
intended primarily for programming equipment to
automatically match a device to be programmed
with its corresponding programming algorithm.
Two methods are provided for accessing the Elec-
tronic ID data. The first requires V_ID on address
pin A[9], with additional requirements for obtain-
13