Samsung S3C6400X User Manual page 137

S3C6400X RISC MICROPROCESSOR
FSA are
unused for
Write 0x01
Erase
Operations
and must
Write 0x03
be cleared.
- Lock, Unlock and Lock-Tight Operations
The OneNAND flash controller supports all flash locking operations. However, the memory device may have
limited support for these functions. If locking functions are not supported, all of these commands will be ignored. If
the "unlock all" function is not supported, an interrupt will be triggered.
A memory area that has been locked can also be "locked-tight". Once an area is "locked tight", it requires a reset
in order to be unlocked.
If the memory device supports per-block locking, then multiple commands can be issued to lock or unlock the
various ranges. This feature is controlled through the lock_bit_per_block register. When using this feature, if the
start and end addresses specified span the entire memory, then any block unlock command will be translated to
an "unlock all" command. The actual lock/unlock/lock-tight command used is determined by the type of
transaction on the AHB bus (read or write) and the low byte of the datain bus.
Address Cmd Datain
Type
[23:22] = Write 0x08
10
Write 0x09
DFS_DBS
Write 0x0A
and FBA
are used.
Write 0x0B
FPA and
Write 0x0C
FSA are
unused for
Lock
Operations
and must
be cleared.
Write 0x0D
Write 0x0E
1 = Erase is in progress.
Save the block address for a multi-block erase. This does NOT initiate the
erase.
Save the block address for a single-block erase and initiate the erase. Also
used to specify the final block of a multi-block erase and initiate the multi-block
erase.
Function
Save this address as the start address for the unlock.
Save this address as the end address for the unlock and initiate the unlock.
Save this address as the start address for the lock.
Save this address as the end address for the lock and initiate the lock.
Save this address as the start address for the lock-tight.
Note that the memory controller will not verify that the specified block is locked
before issuing the lock-tight command, but the lock-tight will only be successful
on locked blocks.
Save this address as the end address for the lock-tight and initiate the lock-
tight.
Note that the memory controller will not verify that the specified block is locked
before issuing the lock-tight command, but the lock-tight will only be successful
on locked blocks.
Unlock the entire memory array. If this function is not supported, a command
error interrupt will be generated.
Preliminary product information describe products that are in development,
for which full characterization data and associated errata are not yet available.
Specifications and information herein are subject to change without notice.
ONENAND CONTROLLER
7-7