Electronic Components Datasheet Search
  English  ▼

X  

S29CD032J Datasheet(PDF) 45 Page - SPANSION

Part # S29CD032J
Description  32/16 Megabit CMOS 2.6 Volt or 3.3 Volt-Only Simultaneous Read/Write, Dual Boot, Burst Mode Flash Memory with VersatileI/O?
PDF  81 Pages
Scroll/Zoom Zoom In 100%  Zoom Out
Manufacturer  SPANSION [SPANSION]
Direct Link  http://www.spansion.com
Logo SPANSION - SPANSION

S29CD032J Datasheet(HTML) 45 Page - SPANSION

Back Button S29CD032J Datasheet HTML 41Page - SPANSION S29CD032J Datasheet HTML 42Page - SPANSION S29CD032J Datasheet HTML 43Page - SPANSION S29CD032J Datasheet HTML 44Page - SPANSION S29CD032J Datasheet HTML 45Page - SPANSION S29CD032J Datasheet HTML 46Page - SPANSION S29CD032J Datasheet HTML 47Page - SPANSION S29CD032J Datasheet HTML 48Page - SPANSION S29CD032J Datasheet HTML 49Page - SPANSION Next Button
Zoom Inzoom in Zoom Outzoom out
 45 / 81 page
background image
October 11, 2012 S29CD-J_CL-J_00_B7
S29CD-J and S29CL-J Flash Family
45
Data
She e t
9.1
Advanced Sector Protection Overview
As shipped from the factory, all devices default to the persistent mode when power is applied, and all sector
groups are unprotected. The device programmer or host system must then choose which sector group
protection method to use. Programming (setting to “0”) any one of the following two one-time programmable,
non-volatile bits locks the device permanently in that mode:
 Persistent Protection Mode Lock Bit
 Password Protection Mode Lock Bit
After selecting a sector group protection method, each sector group can operate in any of the following three
states:
1. Persistently Locked. A sector group is protected and cannot be changed.
2. Dynamically locked. The selected sector groups are protected and can be altered via software
commands.
3. Unlocked. The sector groups are unprotected and can be erased and/or programmed.
These states are controlled by the bit types described in sections Persistent Protection Bits on page 45 to
Hardware Data Protection Methods on page 49.
Notes
1. If the password mode is chosen, the password must be programmed before setting the
corresponding lock register bit. The user must be sure that the password is correct when the
Password Mode Locking Bit is set, as there is no means to verify the password afterwards.
2. If both lock bits are selected to be programmed (to zeros) at the same time, the operation aborts.
3. Once the Password Mode Lock Bit is programmed, the Persistent Mode Lock Bit is permanently
disabled, and no changes to the protection scheme are allowed. Similarly, if the Persistent Mode
Lock Bit is programmed, the Password Mode is permanently disabled.
4. It is important that the mode is explicitly selected when the device is first programmed, rather than
relying on the default mode alone. This is so that it is impossible for a system program or virus to
later set the Password Mode Locking Bit, which would cause an unexpected shift from the default
Persistent Sector Protection Mode into the Password Protection Mode.
5. If the user attempts to program or erase a protected sector, the device ignores the command and
returns to read mode. A program command to a protected sector enables status polling for
approximately 1 µs before the device returns to read mode without modifying the contents of the
protected sector. An erase command to a protected sector enables status polling for approximately
50 µs, after which the device returns to read mode without having erased the protected sector.
6. For the command sequence required for programming the lock register bits, refer to Command
Definitions on page 75.
9.2
Persistent Protection Bits
The Persistent Protection Bits are unique and nonvolatile. A single Persistent Protection Bit is assigned to a
maximum for four sectors (see the sector address tables for specific sector protection groupings). All eight-
Kbyte boot-block sectors have individual sector Persistent Protection Bits (PPBs) for greater flexibility.
Notes
1. Each PPB is individually programmed and all are erased in parallel. There are no means for
individually erasing a specific PPB and no specific sector address is required for this operation.
2. If a PPB requires erasure, all of the sector PPBs must first be programmed prior to PPB erasing. It
is the responsibility of the user to perform the preprogramming operation. Otherwise, an already
erased sector PPB has the potential of being over-erased. There is no hardware mechanism to
prevent sector PPB over-erasure.
3. If the PPB Lock Bit is set, the PPB Program or erase command does not execute and times-out
without programming or erasing the PPB.



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 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81


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