PC28F512P33BF0 NUMONYX, PC28F512P33BF0 Datasheet - Page 31

• Manufacturer Part Number: PC28F512P33BF0
• Description: IC FLASH 512MBIT 95NS 64EZBGA
• Manufacturer: NUMONYX
• Series: Axcell™r

Specifications of PC28F512P33BF0

• Format - Memory: FLASH
• Memory Type: FLASH
• Memory Size: 512M (32Mx16)
• Speed: 95ns
• Interface: Parallel
• Voltage - Supply: 2.3 V ~ 3.6 V
• Operating Temperature: -40°C ~ 85°C
• Package / Case: 64-TBGA
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Other names: 902580; 902580; PC28F512P33BF Q LB0

P33-65nm
10.0
10.1
10.1.1
10.1.2
10.1.3
10.1.4
Datasheet
33
Security
The device features security modes used to protect the information stored in the flash
memory array. The following sections describe each security mode in detail.
Block Locking
Individual instant block locking is used to protect user code and/or data within the flash
memory array. All blocks power up in a locked state to protect array data from being
altered during power transitions. Any block can be locked or unlocked with no latency.
Locked blocks cannot be programmed or erased; they can only be read.
Software-controlled security is implemented using the Block Lock and Block Unlock
commands. Hardware-controlled security can be implemented using the Block Lock-
Down command along with asserting WP#. Also, VPP data security can be used to
inhibit program and erase operations (see
page 30
Lock Block
To lock a block, issue the Block Lock Setup command. The next command must be the
Block Lock command issued to the desired block’s address (see
Command Bus Cycles” on page 22
page
Block Lock Setup command, the device configures the RCR instead.
Block lock and unlock operations are not affected by the voltage level on VPP. The block
lock bits may be modified and/or read even if VPP is at or below V
Unlock Block
The Block Unlock command is used to unlock blocks (see
Command Bus Cycles” on page
erased. Unlocked blocks return to a locked state when the device is reset or powered
down. If a block is in a lock-down state, WP# must be deasserted before it can be
unlocked (see
Lock-Down Block
A locked or unlocked block can be locked-down by writing the Block Lock-Down
command sequence (see
Blocks in a lock-down state cannot be programmed or erased; they can only be read.
However, unlike locked blocks, their locked state cannot be changed by software
commands alone. A locked-down block can only be unlocked by issuing the Block
Unlock command with WP# deasserted. To return an unlocked block to locked-down
state, a Block Lock-Down command must be issued prior to changing WP# to V
Locked-down blocks revert to the locked state upon reset or power up the device (see
Figure 9, “Block Locking State Diagram” on page
Block Lock Status
The Read Device Identifier command is used to determine a block’s lock status (see
Section 7.2, “Read Device Identifier” on page
addressed block’s lock status; DQ0 is the addressed block’s lock bit, while DQ1 is the
addressed block’s lock-down bit.
79). If the Configure Read Configuration Register command is issued after the
and
Section 9.5, “Erase Protection” on page
Figure 9, “Block Locking State Diagram” on page
Section 6.2, “Device Command Bus Cycles” on page
22). Unlocked blocks can be read, programmed, and
and
Figure 35, “Block Lock Operations Flowchart” on
Section 8.6, “Program Protection” on
24). Data bits DQ[1:0] display the
34).
32).
Section 6.2, “Device
34).
Section 6.2, “Device
PPLK
Order Number:208043-05
.
22).
IL
Apr 2010
.