EP2801096A1 - Device selection schemes in multi chip package nand flash memory system - Google Patents

Device selection schemes in multi chip package nand flash memory system

Info

Publication number
EP2801096A1
EP2801096A1 EP12864164.4A EP12864164A EP2801096A1 EP 2801096 A1 EP2801096 A1 EP 2801096A1 EP 12864164 A EP12864164 A EP 12864164A EP 2801096 A1 EP2801096 A1 EP 2801096A1
Authority
EP
European Patent Office
Prior art keywords
command
memory
read
code
page
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP12864164.4A
Other languages
German (de)
French (fr)
Other versions
EP2801096A4 (en
Inventor
Jin-Ki Kim
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Mosaid Technologies Inc
Original Assignee
Mosaid Technologies Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Mosaid Technologies Inc filed Critical Mosaid Technologies Inc
Publication of EP2801096A1 publication Critical patent/EP2801096A1/en
Publication of EP2801096A4 publication Critical patent/EP2801096A4/en
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C15/00—Digital stores in which information comprising one or more characteristic parts is written into the store and in which information is read-out by searching for one or more of these characteristic parts, i.e. associative or content-addressed stores
    • G11C15/04—Digital stores in which information comprising one or more characteristic parts is written into the store and in which information is read-out by searching for one or more of these characteristic parts, i.e. associative or content-addressed stores using semiconductor elements
    • G11C15/046—Digital stores in which information comprising one or more characteristic parts is written into the store and in which information is read-out by searching for one or more of these characteristic parts, i.e. associative or content-addressed stores using semiconductor elements using non-volatile storage elements
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C8/00—Arrangements for selecting an address in a digital store
    • G11C8/12—Group selection circuits, e.g. for memory block selection, chip selection, array selection
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C16/00—Erasable programmable read-only memories
    • G11C16/02—Erasable programmable read-only memories electrically programmable
    • G11C16/06—Auxiliary circuits, e.g. for writing into memory
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C16/00—Erasable programmable read-only memories
    • G11C16/02—Erasable programmable read-only memories electrically programmable
    • G11C16/06—Auxiliary circuits, e.g. for writing into memory
    • G11C16/08—Address circuits; Decoders; Word-line control circuits
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C7/00—Arrangements for writing information into, or reading information out from, a digital store
    • G11C7/10—Input/output [I/O] data interface arrangements, e.g. I/O data control circuits, I/O data buffers
    • G11C7/1078—Data input circuits, e.g. write amplifiers, data input buffers, data input registers, data input level conversion circuits
    • G11C7/109—Control signal input circuits
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C16/00—Erasable programmable read-only memories
    • G11C16/02—Erasable programmable read-only memories electrically programmable
    • G11C16/04—Erasable programmable read-only memories electrically programmable using variable threshold transistors, e.g. FAMOS
    • G11C16/0483—Erasable programmable read-only memories electrically programmable using variable threshold transistors, e.g. FAMOS comprising cells having several storage transistors connected in series

Definitions

  • the present invention relates generally to semiconductor devices, for example, flash devices.
  • NAND flash devices have become very popular with respect to their use in mobile applications and mobile storage applications such as flash cards, digital audio/video players, cell phones, USB flash drives and solid state drives (SSDs) for hard disk drive (HDD) replacement.
  • SSDs solid state drives
  • HDD hard disk drive
  • NAND flash memories are described in, for example,
  • the invention provides a memory system comprising: a memory controller; a plurality of memory devices connected to the controller via a common bus with a multi-drop connection; wherein the memory controller performs device selection by command.
  • the invention provides a memory system comprising: a memory controller; a plurality of memory devices connected to the controller via a common bus with a multi-drop connection; wherein the memory controller performs device selection by input address; each memory device comprising: a register containing a device identifier; a device identifier comparator that compares selected bits of a received input address to contents of the register to determine if there is a match, and wherein a given device is selected if the device identifier comparator of the given device determines there is a match.
  • the invention provides a memory controller for use in a system comprising the memory controller and a plurality of memory devices connected to the controller via a common bus with a multi-drop connection, wherein the memory controller performs device selection by command.
  • the invention provides a memory device for use in a system comprising a memory controller and a plurality of memory devices connected to the controller via a common bus with a multi-drop connection inclusive of the memory device, the memory device comprising: a command processor configured to process a command received via the common bus to determine if the command selects that particular memory device, and to act upon the command if the command selects that particular memory device.
  • the invention provides a memory device for use in memory system comprising a memory controller, and a plurality of memory devices inclusive of the memory device connected to the controller via a common bus with a multidrop connection, the memory device comprising: a register containing a device identifier; a device identifier comparator that compares selected bits of a received input address to contents of the register to determine if there is a match, and wherein the memory device is selected if the device identifier comparator determines there is a match.
  • the invention provides a method in a memory system comprising a memory controller and a plurality of memory devices connected to the controller via a common bus with a multi-drop connection, the method comprising: performing device selection by command.
  • the invention provides a method for use in a memory system comprising a memory controller and a plurality of memory devices connected to the controller via a common bus with a multi-drop connection, the method comprising: the memory controller performing device selection by input address; each memory device maintaining a device identifier in a register; a device identifier comparator in each memory device comparing selected bits of a received input address to contents of the register of the memory device to determine if there is a match, and wherein a given device is selected if the device identifier comparator of the given device determines there is a match.
  • Figure 1 illustrates a NAND flash functional block
  • Figure 2 illustrates a NAND flash cell array structure
  • Figure 3 illustrates a NAND flash block structure
  • Figure 4 illustrates a NAND flash page structure
  • Figure 5 illustrates a page basis read operation in NAND flash
  • Figure 6 illustrates a page basis program operation in NAND flash
  • Figure 7 illustrates a block basis erase operation in NAND flash
  • Figure 8 illustrates a general system with flash memory
  • Figure 9 illustrates a flash memory system using a single flash memory device
  • Figure 10 illustrates a flash memory system using multiple flash memory devices
  • Figure 11 illustrates NAND flash devices in multi-drop connection
  • Figure 12 illustrates NAND flash devices in multi-drop connection
  • Figure 13 illustrates a page program in two NAND flash devices
  • Figure 14 illustrates an interleave page program in two NAND flash devices
  • Figure 15 illustrates a page read in two NAND flash devices
  • Figure 16 illustrates two NAND flash devices in a MCP according to one embodiment of the present invention
  • Figure 17 illustrates four NAND flash devices in a MCP according to another embodiment of the present invention.
  • Figure 18 illustrates a command structure according to another embodiment of the present invention.
  • Figure 19 illustrates an interleave page program in two NAND flash devices according to another embodiment of the present invention.
  • Figure 20 illustrates an interleave page read in two NAND flash devices according to another embodiment of the present invention.
  • Figure 21 illustrates an interleave page read and program in two NAND flash devices according to another embodiment of the present invention.
  • Figure 22 illustrates example circuits for device selection by input address
  • Figure 23 illustrates a command/address/data input timing
  • Figure 24 illustrates command/address/data output timing.
  • MCP multi chip package
  • CE# chip enable pin
  • Figure 1 illustrates a NAND flash functional block. Various inputs/outputs to the NAND functional block are depicted. In the following, # denotes active low (i.e. enable when the signal input is Low).
  • Command Latch Enable (CLE) input signal 18 is used to control loading of an operation mode command into an internal command register 38.
  • the command is latched into the command register 38 from the I/O port 28 on the rising edge of the WE# signal 22 while CLE is High.
  • the Address Latch Enable (ALE) signal 20 is used to control loading address information into the internal address register 40. Address information is latched into the address register from the I/O port 28 on the rising edge of the WE# signal 22 while ALE is High.
  • ALE Address Latch Enable
  • Chip Enable (CE#) 16 the device goes into a low-power Standby mode if CE# goes High while the device is in Ready state.
  • the Write Enable (WE#) signal 22 is used to control the acquisition of data from the I/O port 28.
  • I/O Port (I/O0 to 7) 28 I/O0 to I/07 pins are used as a port for transferring address, command and input/output data to and from the device.
  • WP# Write Protect
  • Ready/Busy (R/B#) 14 is an open drain pin and the output signal is used to indicate the operating condition of the device.
  • Vcc 10 and Vss 12 are power supply inputs.
  • the memory core of NAND flash consists of NAND memory cell array 50, row decoder 52, sense amp & page buffer 54 and column decoder 56. The detailed memory cell array organization is described below.
  • a page for either read or program operation is selected by the row decoder 52.
  • a block for erase operation is also selected by the row decoder.
  • the data of the selected page is sensed and latched into sense amp & page buffer 54.
  • the data stored in the page buffer 54 are sequentially read out through column decoder 56 and global buffers 44.
  • the input data from global buffers 44 are sequentially loaded into the page buffer 54 via column decoder 56.
  • the input data latched in the page buffer are finally programmed into the selected page.
  • High voltage generator 32 provides high voltages and reference voltages during read, program and erase operations.
  • Global buffers 44 temporarily hold and buffer input and output data via common I/O pins (I/O 0 to 7) 28.
  • the common I/O pins serve as the port for command, address and input/output data.
  • Status register 42 tracks the device status during read, program or erase operation.
  • Ready/Busy# 30 has an open drain transistor, and generates the Ready/Busy
  • Command register 38 decodes an input command from the global buffer 44 and the decoded command is input to the control circuit 36 having a state machine.
  • Control circuit 36 is a central unit to control the entire device during various operating modes.
  • Control buffers 34 determine one of operating modes such as command input, address input, data input, data output and status output in accordance with combination of control pins as CE#, CLE, ALE, WE#, RE# and WP#.
  • Figure 2 illustrates the cell array structure of NAND flash memory which consists of n erasable blocks labeled Block 0, Block 1 , Block n-1. Each block is subdivided into m programmable pages as shown Figure 3, labeled Page 0, Page 1 , Page m-1.
  • Each page consists of (j+k) bytes (x8b) as shown in Figure 4.
  • the pages are further divided into a j-byte data storage region 100 (data field) with a separate k-byte area 102 (spare field).
  • the k-byte area is typically used for error management functions.
  • 1 page (j + k) bytes
  • the internal memory array is accessed on a page basis.
  • the read operation starts after writing READ command followed by addresses via common I/O pins (I/O0 to I/O 7) to the device.
  • the 4,224 bytes of data within the selected page are sensed and transferred to the page register (or page buffer) in less than tR (data transfer time from flash array to page register) shown in Figure 5.
  • tR data transfer time from flash array to page register
  • the memory array is programmed on a page basis. For program operations, a
  • PROGRAM command followed by addresses and input data of 4,224 bytes is issued to the device through common I/O pins (I/O0 to I/07).
  • the 4,224 bytes of data are transferred to the page register (or page buffer) during input data loading cycles and finally programmed to the selected page of the cell array less than tPROG (page program time) as shown in Figure 6.
  • the memory array is erased on a block basis. For block erase operations, a
  • BLOCK ERASE command followed by block addresses is issued to the device through common I/O pins (I/O0 to I/07).
  • the (256K + 8K) bytes of data are erased less than tBERS (block erase time) as shown in Figure 7.
  • FIG. 8 shows a block diagram of an example of a general system that includes a flash memory system.
  • the flash memory system 114 communicates with a main system or processor 110 via a flash controller 112.
  • a typical flash memory system has either a single flash memory device 118 as shown in Figure 9 or multiple flash memory devices 120,122,124,126 as shown in Figure 10.
  • a flash memory system using a single flash device might be used in applications which require relatively small memory space.
  • a flash memory system using multiple flash memory devices can be implemented such as the system of Figure 10.
  • the flash controller 112 can access each flash memory device 120,122,124,126 via a common bus 128. Only one flash device can be selected at a time by asserting a chip enable signal on one of devices.
  • MCP Multi Chip Package
  • a multi chip package (MCP: multiple chips in a single package) is a very popular solution to increase packing density.
  • An MCP typically uses multi-drop bus such as shown in Figure 11 and Figure 12.
  • Figure 12 illustrates a MCP having four NAND flash devices
  • the output signals of the rest devices are high impedance (i.e. Hi-Z) state.
  • This type of device connection is a multi-drop bus connection or topology.
  • Figure 13 illustrates an example of page program operational timing for two
  • NAND flash devices in a single package. All input and output pins except CE# pins are commonly connected in multi-drop configuration as shown in Figure 1 1. This example shows consecutive program operations into device 1 130 and device 2 132.
  • the 2nd command cycle (10h) (408) for page program is asserted and device 1 starts page program operation (410) governed by auto-timed, internal program algorithm. During this period, the R/B# of device 1 goes Low to represent device 1 is in busy state (412). Once the internal page program operation is completed, the R/B# of device 1 goes High (414). Hence the next command can be issued to device 1.
  • the 1st command cycle (80h) for page program is issued to device 2 (420).
  • Five bytes input addresses (AO to A30 for 8Gb NAND Flash) (422) and 4K bytes input data (424) are loaded to device 2.
  • the 2nd command cycle (10h) (426) for page program is asserted and device 1 starts page program operation governed by auto- timed, internal program algorithm. During this period, the R/B# of device 1 goes Low (428) to represent device 1 is in busy state. Once the internal page program operation is completed, the R/B# of device 2 goes High (430). Hence the next command can be issued to device 2.
  • the unselected NAND flash device waits until the selected device completes any operation.
  • the auto-timed page program typically takes 200us in SLC NAND flash and 600us in MLC NAND flash.
  • a NAND flash device may have a "CE# don't care state.” Once the selected device starts an internal page program operation, the selected device will continue the internal page program operation even when the CE# is High. With the "CE# don't care" feature, the next device can perform any other operation once the previous device enters the internal page program operation. This is referred to as a device interleave operation between two NAND flash devices and an example of this is shown in Figure 14, again in the context of the MCP of Figure 1 1 containing 2 flash devices.
  • the 1st command cycle (80h) for page program is issued to device 1 130 (442).
  • Five bytes input addresses (AO to A30 for 8Gb NAND Flash) (444) and 4K bytes input data (446) are loaded to device 1.
  • the 2nd command cycle (10h) (448) for page program is asserted and device 1 starts page program operation governed by auto-timed, internal program algorithm (450). During this period, the R/B# of device 1 goes 'Low' to represent device 1 is in busy state (452). Once the internal page program operation in the 1 st device started, which can be indicated by R/B#, the CE1# can return to High (454). Therefore the next page program command can be issued to the 2nd device 132.
  • Figure 15 shows interleave page read operational timing for two NAND flash devices in a single package, for example, the MCP of Figure 11.
  • the interleave page read operation is very similar to the interleave page program operation described previously.
  • R/B# of device 1 goes Low to represent device 1 is in busy state (480). Once the internal page read operation is completed, the R/B# of device 1 goes High (482). Hence device 1 is ready for burst read operation of 4KB data. During page read operation for device 1 , device
  • CE2# High (484).
  • CE2# Low (486)
  • the 1st command cycle (OOh) (488) for page program to device 2 is issued and five bytes input addresses (AO to A30 for 8Gb NAND Flash) (490) are loaded to device 2.
  • the 2nd command cycle (10h) (492) for page read is asserted and device 2 starts page read operation governed by auto-timed, read algorithm (494). During this period, the R/B# of device 2 goes Low to represent device 2 is in busy state (496). Once the internal page read operation is completed, the R/B# of device 2 goes High (498). Hence the next command can be issued to device 2.
  • An objective of MCP in flash memory is increasing memory capacity while maintaining same package pinout and configuration.
  • the chip enable (CE#) pin needs to be separated as described in section 1.4. If the MCP device has 4 flash devices in a single package, four chip enable pins (CE1# ⁇ CE4#) are needed as opposed to two in an MCP with two flash devices. The result is that the 4-device MCP needs a different pin assignment and PCB layout compared to a 2-device MCP. In addition, this chip enable pin increase is a burden to the flash memory controller.
  • Figure 16 and Figure 17 show examples of device connection for two NAND flash devices in a single package and four NAND flash devices in a single package.
  • For the two device embodiment of Figure 16 there are two NAND flash devices 160,162 connected to a common bus 164. Unlike the arrangement of Figure 11 , there are no individual CE# pins.
  • FIG. 18 depicts a 1 byte command structure according to an embodiment of the present invention.
  • the command consists of OP code 200 and device ID 202.
  • upper 4 bits (Bit 4 to Bit 7) are assigned to the OP code and lower 4 bits (Bit 0 to Bit 3) are assigned to the device ID.
  • 4-bit device ID total 16 devices can be exclusively selected. Note that the number of bits assigned to OP code and device ID may vary and the command structure shown in Figure 18 is just an example.
  • each NAND flash device connected in a multi-drop configuration for example the NAND flash devices of Figure 16 or 17, contains a command processor (not shown) configured to process a command received via the common bus to determine if the command selects that particular memory device, and to act upon the command if the command selects that particular memory device.
  • a command processor not shown
  • Table 1 lists an example set of commands for use in an embodiment of the present invention.
  • the lower 4 bits in the 1st command select one of up to 16 flash devices.
  • a difference between the proposed NAND flash command and conventional NAND flash commands is that the lower 4 bits of each command in the example of the present invention are assigned to the device ID.
  • Table 1 Example Set of Commands Including Device ID
  • Table 2 and Table 3 show read commands and page program commands having device ID to select one of up to 16 flash devices.
  • Figure 19 illustrates operational timing of interleave page program in two
  • NAND flash devices according to an embodiment of the present invention. Note that the following interleave page operations can be also applied to more than two flash devices in a system.
  • All flash devices in this case, two flash devices always accept any command.
  • 3rd address input (3rd byte) row address 1 ;
  • 5th address input (5th byte) row address 3.
  • Device 2 will recognize from the 1st command cycle (80h) that the input address and input data are not for device 2. Thus device 2 will block following 5 bytes input address and 4K bytes input data from the common bus (i.e. device 2 is deselected by the 1st command cycle (80h)) (520).
  • the 2nd command cycle (10h) (518) for page program is asserted and device 1 starts page program operation governed by auto-timed, internal program algorithm (522). During this period, the R/B# of device 1 goes Low to represent device 1 is in busy state (524)
  • Device 2 will ignore the 2nd command cycle (10h) because the 1 st command cycle (80h) was not for device 2. Once the internal page program operation in device 1 started, which can be indicated by R/B#, the next page program command can be issued to device 2.
  • the 1st command cycle having device ID (81 h) (526) for page program to device 2 is issued to device 2.
  • Five bytes input addresses (AO to A30 for 8Gb NAND Flash) (530) and 4K bytes input data (532) are loaded to device 1.
  • the internal page program operation in device 1 is not interrupted by the 1 st command cycle (81 h) for page program to device 2.
  • the 2nd command cycle (10h) (534) for page program is asserted and device 2 starts page program operation governed by auto-timed, internal program algorithm (536). During this period, the R/B# of device 2 goes Low to represent device 2 is in busy state (538).
  • a read status command having device ID (70h) is issued to check the status of device 1 (540). If device 1 is ready to take a next operation, another page program command can be inputted to device 1.
  • the 1 st command cycle having device ID (80h) (542) for page program is issued to device 1.
  • Five bytes input addresses (AO to A30 for 8Gb NAND Flash) (544) and 4K bytes input data (546) are loaded to device 1.
  • the 2nd command cycle (1 Oh) (548) for page program is issued and device 1 starts page program operation governed by auto-timed, internal program algorithm (550). During this period, the R/B# of device 1 goes Low to represent device 1 is in busy state (552).
  • Figure 20 illustrates operational timing of interleave page read in two NAND flash devices according to an embodiment of the present invention. Note following interleave page operations can be also applied to more than two flash devices in a system.
  • All flash devices in this case, two flash devices always accept any command.
  • the 1 st command cycle (OOh) (562) for page read to device 1 is asserted and five bytes input addresses (AO to A30 for 8Gb NAND Flash) (564) are loaded to device 1.
  • Device 2 will recognize from the 1 st command cycle (OOh) that the input address are not for device 2.
  • device 2 will block following 5 bytes input address from the common bus (i.e. device 2 is deselected by the 1 st command cycle (00h)) (570).
  • the 2nd command cycle (30h) (566) for page read is asserted and device 1 starts page read operation governed by auto-timed, internal read algorithm (568). During this period, the R/B# of device 1 goes Low to represent device 1 is in busy state (572).
  • Device 2 will ignore the 2nd command cycle (30h) because the 1 st command cycle having device ID (OOh) is not for device 2.
  • the 1st command cycle (01 h) (580) for page read to device 2 is asserted and five bytes input addresses (AO to A30 for 8Gb NAND Flash) (582) are loaded to device 2.
  • the 2nd command cycle (30h) (584) for page read is asserted and device 2 starts page read operation governed by auto-timed, read algorithm (586). During this period, the R/B# of device 2 goes Low to represent device 2 is in busy state (588).
  • a read status command having device ID (70h) is issued to device 1 to check the device status (590). If device 1 is ready to take a next operation, another command can be inputted to device 1.
  • the 1st command cycle (20h) (592) for burst read to device 1 is asserted and five bytes input addresses (AO to A30 for 8Gb NAND Flash) (594) are loaded to device 2.
  • the 2nd command cycle (30h) (596) for burst read is asserted and device 1 starts burst read operation to access 4K bytes data stored in the page buffers of device 1 during previous page read operation in device 1 (598).
  • a read status command (71 h) is issued to check the status of device 2 (600).
  • Device 1 will ignore the read status command (71 h) because this command is not for the device 1. If device 2 is ready to take a next operation, another command can be inputted to device 2.
  • the 1 st command cycle (21 h) (602) for burst read to device 2 is asserted and five bytes input addresses (604) are loaded to device 2.
  • the 2nd command cycle (30h) (606) for burst read is asserted and device 2 starts burst read operation to access 4K bytes data stored in the page buffers of device 2 during previous page read operation in device 2 (608).
  • Figure 21 shows operational timing of interleave page read and program in two NAND flash devices according to an embodiment of the present invention.
  • All flash devices in this case, two flash devices always accept any command.
  • the 1 st command cycle (OOh) (612) for page read to device 1 is asserted and five bytes input addresses (AO to A30 for 8Gb NAND Flash) (614) are loaded to device 1.
  • Device 2 will recognize from the 1 st command cycle (OOh) that the input address are not for device 2. Thus device 2 will block following 5 bytes input address from the common bus (i.e. device 2 is deselected by the 1st command cycle (00h)) (620).
  • the 2nd command cycle (30h) (616) for page read is asserted and device 1 starts page read operation governed by auto-timed, internal read algorithm (618). During this period, the R/B# of device 1 goes Low to represent device 1 is in busy state (622).
  • Device 2 will ignore the 2nd command cycle (30h) because the 1 st command cycle (OOh) is not device 2.
  • the 1 st command cycle having device ID (81 h) (624) for page program to device 2 is issued to device 2.
  • Five bytes input addresses (AO to A30 for 8Gb NAND Flash) (628) and 4K bytes (630) input data are loaded to device 1.
  • the internal page program operation in device 1 is not interrupted by the 1 st command cycle (81 h) for page program to device 2.
  • the 2nd command cycle (10h) (632) for page program is asserted and device 2 starts page program operation governed by auto-timed, internal program algorithm (634). During this period, the R/B# of device 2 goes Low to represent device 2 is in busy state (636).
  • a read status command (70h) is issued to check the status of device 1 (640). If device 1 is ready to take a next operation, another command can be inputted to device 1.
  • the 1st command cycle (20h) (642) for burst read to device 1 is asserted and five bytes input addresses (644) are loaded to device 1.
  • the 2nd command cycle (30h) (646) for burst read is asserted and device 1 starts burst read operation to access 4K bytes data stored in the page buffers of device 1 during previous page read operation in device 1 (648).
  • device selection is achieved through the use of input address, for example one or more MSB of the row address.
  • input address for example one or more MSB of the row address.
  • the command and sequence shown in Table 4 are identical to those of conventional proposed NAND flash . It should be clearly understood a different command structure could be used.
  • a full command cycle for read, burst read, block erase, page program includes an address.
  • the address contains 4 bytes, containing 32 bits AO to A31. Address bits AO to A12 are assigned to the column address, and address bits A13 to A30 are assigned to the row address.
  • additional bits in of the address are used to select one of multiple devices that are commonly connected in a single package (e.g. MCP using multi-drop connection).
  • A31 can be used to perform device selection.
  • A31 and A32 can be used to perform device selection. Note this requires an additional byte in the address to convey A32. However, since the command and address are conveyed to the devices in sequence over the common bus, this does not change the pinout requirement.
  • A31 to A33 can be used to perform device selection. Note that this also requires an additional byte in the address to convey A32 and A33. However, since the command and address are conveyed to the devices in sequence over the common bus, this does not change the pinout requirement.
  • address information for read, burst read, block erase, and page program, for this embodiment of the invention, address information is also included for other device-specific commands, such as read status.
  • Figure 22 shows one example of circuits for device selection by input address. Such a circuit is included in each NAND flash device connected in a multi-drop configuration.
  • # denotes enable when logic Low (i.e. active when Low).
  • CE#, WE#, RE#, WP#, ALE, CLE are external control input signals.
  • CEf#, WEf#, REf#, WPf#, ALEf, CLEf are buffered, internal control signals.
  • I/O0 ⁇ 1/07 are external input and output signals (common I/O signals).
  • DeviceJD register 300 is a register containing a unique deviceJD - that is, unique between the devices connected in the multi-drop configuration. This can, for example, where the DeviceJD register of each device contains respective values for the bits ID_A32 and ID_A31. be programmed by one of nonvolatile programming methods such as laser fuse, electrical fuse, pad bonding option, metal layer option or nonvolatile memory cells.
  • nonvolatile programming methods such as laser fuse, electrical fuse, pad bonding option, metal layer option or nonvolatile memory cells.
  • A31 and A32 whenever input addresses are loaded. Input address A31 and A32 via the global buffer are compared with device ID address ID_A31 and ID_A32 in Device ID Comparator 302. If the input addresses are matched with the device ID addresses, the output IOEN 306 of the DeviceJD Comparator is High. WE# buffer and RE# buffer are controlled by not only CE# but also DSEL of the Burst Data Control block. Specifically, when DSEL is high, these buffers are disabled.
  • a burst data control block 310 generates the DSEL outputs 320 as a function of IOEN 306, ALEf 312 and CLEf 314.
  • the burst data control block 310 receives IOEN 306, and inverts this with invertor 316 to produce IOEN#.
  • ALEf 312 is an input that is high during address input
  • CLEf 314 is an input that is high during command input.
  • ALEf 312, CLEf 314 and IOEN# are input to NOR gate 318 the output of which input to inverter 319, the output of which is the DSEL output 320.
  • DSEL low means that a device is not de-selected, while DSEL high means a device is de-selected.
  • Table 5 shows device selection table by input address for four flash devices in MCP.
  • Table 5 Device Selection by Input Address Input Address (A32, A31) from 5th Address
  • ID_A32 ID_A31 0, 0 0, 1 1 , 0 1, 1
  • Figure 23 illustrates an example of command/address/data input timing with the circuits shown in Figure 22.
  • Device 1 is selected and devices 2 to 4 are deselected.
  • the IOEN in device 1 is High while the IOEN in device 2 is Low.
  • Figure 24 illustrates command/address/data output timing with the circuits shown in Figure 22.
  • the output timing is very similar to the input timing shown in Figure 23.
  • Device 1 is selected and devices 2 to 4 are deselected.
  • the IOEN in device 1 is High while the IOEN in device 2 is Low.
  • the device interleave operations (e.g., page program, interleave page read and interleave page read & program and so on) can be performed in same fashion as the device interleave operations described previously.
  • the device elements and circuits are connected to each other as shown in the figures for the sake of simplicity. In practical applications these devices, elements circuits, etc., may be connected directly to each other or indirectly through other devices elements, circuits, etc. Thus, in an actual configuration, the elements, circuits and devices are coupled either directly or indirectly with each other.

Landscapes

  • Engineering & Computer Science (AREA)
  • Microelectronics & Electronic Packaging (AREA)
  • Read Only Memory (AREA)

Abstract

Device selection schemes in multi-chip package NAND flash memory systems are provided. A memory system is provided that has a memory controller, and a number of memory devices connected to the controller via a common bus with a multi-drop connection. The memory controller performs device selection by command. A corresponding memory controller is provided which performs device selection by command. Alternatively, device selection is performed by address. A memory device is provided use in memory system comprising a memory controller, and a number of memory devices inclusive of the memory device connected to the controller via a common bus with a multi-drop connection. The memory device has a register containing a device identifier, and a device identifier comparator that compares selected bits of a received input address to contents of the register to determine if there is a match. The memory device is selected if the device identifier comparator determines there is a match.

Description

DEVICE SELECTION SCHEMES IN MULTI CHIP PACKAGE NAND FLASH MEMORY
SYSTEM
RELATED APPLICATION
[0001] This application claims the benefit of U.S. Provisional Patent Application
No. 61/583,408 filed January 5, 2012, which is hereby incorporated by reference in its entirety.
TECHNICAL FIELD
[0002] The present invention relates generally to semiconductor devices, for example, flash devices.
BACKGROUND
[0003] Recently, NAND flash devices have become very popular with respect to their use in mobile applications and mobile storage applications such as flash cards, digital audio/video players, cell phones, USB flash drives and solid state drives (SSDs) for hard disk drive (HDD) replacement. With an increase in the density requirement in the market, NAND flash provides high density with low cost.
[0004] NAND flash memories are described in, for example,
Kenichi Imamiya, et al., "A 125-mm2 1-Gb NAND Flash Memory With 10- MByte/s Program Speed," IEEE J Solid-State Circuits, vol. 37, no. 11 , pp. 1493-1500, Nov. 2002;
June Lee et al., "A 90-nm CMOS 1.8-V 2-Gb NAND Flash Memory for Mass Storage Applications," IEEE J Solid-State Circuits, vol. 38, no. 11 , pp. 1934-1942, Nov. 2003;
Ken Takeuchi, et al., "A 56nm CMOS 99mm2 8Gb Multi-level NAND Flash Memory with 10MB/S Program Throughput," ISSCC Dig. Tech. Paper, pp. 144-145, Feb. 2006. SUMMARY
[0005] According to one broad aspect, the invention provides a memory system comprising: a memory controller; a plurality of memory devices connected to the controller via a common bus with a multi-drop connection; wherein the memory controller performs device selection by command.
[0006] According to another broad aspect, the invention provides a memory system comprising: a memory controller; a plurality of memory devices connected to the controller via a common bus with a multi-drop connection; wherein the memory controller performs device selection by input address; each memory device comprising: a register containing a device identifier; a device identifier comparator that compares selected bits of a received input address to contents of the register to determine if there is a match, and wherein a given device is selected if the device identifier comparator of the given device determines there is a match.
[0007] According to another broad aspect, the invention provides a memory controller for use in a system comprising the memory controller and a plurality of memory devices connected to the controller via a common bus with a multi-drop connection, wherein the memory controller performs device selection by command.
[0008] According to another broad aspect, the invention provides a memory device for use in a system comprising a memory controller and a plurality of memory devices connected to the controller via a common bus with a multi-drop connection inclusive of the memory device, the memory device comprising: a command processor configured to process a command received via the common bus to determine if the command selects that particular memory device, and to act upon the command if the command selects that particular memory device.
[0009] According to another broad aspect, the invention provides a memory device for use in memory system comprising a memory controller, and a plurality of memory devices inclusive of the memory device connected to the controller via a common bus with a multidrop connection, the memory device comprising: a register containing a device identifier; a device identifier comparator that compares selected bits of a received input address to contents of the register to determine if there is a match, and wherein the memory device is selected if the device identifier comparator determines there is a match. [0010] According to another broad aspect, the invention provides a method in a memory system comprising a memory controller and a plurality of memory devices connected to the controller via a common bus with a multi-drop connection, the method comprising: performing device selection by command.
[0011] According to another broad aspect, the invention provides a method for use in a memory system comprising a memory controller and a plurality of memory devices connected to the controller via a common bus with a multi-drop connection, the method comprising: the memory controller performing device selection by input address; each memory device maintaining a device identifier in a register; a device identifier comparator in each memory device comparing selected bits of a received input address to contents of the register of the memory device to determine if there is a match, and wherein a given device is selected if the device identifier comparator of the given device determines there is a match.
[0012] Other aspects and features of the present invention will become apparent to those ordinarily skilled in the art upon review of the following description of specific embodiments of the invention in conjunction with the accompanying figures.
BRIEF DESCRIPTION OF THE DRAWINGS
[0013] Embodiments of the present invention will now be described, by way of example only, with reference to the attached Figures, wherein:
Figure 1 illustrates a NAND flash functional block;
Figure 2 illustrates a NAND flash cell array structure;
Figure 3 illustrates a NAND flash block structure;
Figure 4 illustrates a NAND flash page structure;
Figure 5 illustrates a page basis read operation in NAND flash;
Figure 6 illustrates a page basis program operation in NAND flash;
Figure 7 illustrates a block basis erase operation in NAND flash;
Figure 8 illustrates a general system with flash memory;
Figure 9 illustrates a flash memory system using a single flash memory device;
Figure 10 illustrates a flash memory system using multiple flash memory devices; Figure 11 illustrates NAND flash devices in multi-drop connection;
Figure 12 illustrates NAND flash devices in multi-drop connection;
Figure 13 illustrates a page program in two NAND flash devices;
Figure 14 illustrates an interleave page program in two NAND flash devices;
Figure 15 illustrates a page read in two NAND flash devices;
Figure 16 illustrates two NAND flash devices in a MCP according to one embodiment of the present invention;
Figure 17 illustrates four NAND flash devices in a MCP according to another embodiment of the present invention;
Figure 18 illustrates a command structure according to another embodiment of the present invention;
Figure 19 illustrates an interleave page program in two NAND flash devices according to another embodiment of the present invention;
Figure 20 illustrates an interleave page read in two NAND flash devices according to another embodiment of the present invention;
Figure 21 illustrates an interleave page read and program in two NAND flash devices according to another embodiment of the present invention;
Figure 22 illustrates example circuits for device selection by input address;
Figure 23 illustrates a command/address/data input timing; and
Figure 24 illustrates command/address/data output timing.
DETAILED DESCRIPTION
[0014] The demand for memory capacity increase in flash memory systems has become significant and a multi chip package (MCP: multiple chips in a single package) is a very popular solution to increase packing density. However, the use of a separate chip enable pin (CE#) to each flash device in a single package requires system configuration changes (e.g., pin assignment change, PCB change) when the number of flash devices in a MCP increases.
NAND Flash Functional Block [0015] Figure 1 illustrates a NAND flash functional block. Various inputs/outputs to the NAND functional block are depicted. In the following, # denotes active low (i.e. enable when the signal input is Low).
Command Latch Enable (CLE) input signal 18 is used to control loading of an operation mode command into an internal command register 38. The command is latched into the command register 38 from the I/O port 28 on the rising edge of the WE# signal 22 while CLE is High.
The Address Latch Enable (ALE) signal 20 is used to control loading address information into the internal address register 40. Address information is latched into the address register from the I/O port 28 on the rising edge of the WE# signal 22 while ALE is High.
Chip Enable (CE#) 16: the device goes into a low-power Standby mode if CE# goes High while the device is in Ready state. The CE# signal is ignored while the device is in Busy state (R/B# = L), such as during a Program or Erase or Read operation, and will not enter Standby mode even if the CE# input goes High.
The Write Enable (WE#) signal 22 is used to control the acquisition of data from the I/O port 28.
The Read Enable signal (RE#) 24 controls serial data output. Data is available after the falling edge of RE#. The content of address register is also incremented (Address = Address + I) on this falling edge.
I/O Port (I/O0 to 7) 28: I/O0 to I/07 pins are used as a port for transferring address, command and input/output data to and from the device.
Write Protect (WP#) signal 26 is used to protect the device from accidental programming or erasing. The internal voltage regulator (high voltage generator 32) is reset when WP# is Low. This signal is usually used for protecting the data during the power-on/off sequence when input signals are invalid.
Ready/Busy (R/B#) 14 is an open drain pin and the output signal is used to indicate the operating condition of the device. The R/B# signal is in Busy state (R/B# = L) during the Program, Erase and Read operations and will return to Ready state (R/B# = H) after completion of the operation.
Vcc 10 and Vss 12 are power supply inputs. [0016] The memory core of NAND flash consists of NAND memory cell array 50, row decoder 52, sense amp & page buffer 54 and column decoder 56. The detailed memory cell array organization is described below. A page for either read or program operation is selected by the row decoder 52. A block for erase operation is also selected by the row decoder. During read operation, the data of the selected page is sensed and latched into sense amp & page buffer 54. After that, the data stored in the page buffer 54 are sequentially read out through column decoder 56 and global buffers 44. During programming, the input data from global buffers 44 are sequentially loaded into the page buffer 54 via column decoder 56. The input data latched in the page buffer are finally programmed into the selected page.
[0017] High voltage generator 32 provides high voltages and reference voltages during read, program and erase operations.
[0018] Global buffers 44 temporarily hold and buffer input and output data via common I/O pins (I/O 0 to 7) 28. The common I/O pins serve as the port for command, address and input/output data.
[0019] Status register 42 tracks the device status during read, program or erase operation.
[0020] Ready/Busy# 30 has an open drain transistor, and generates the Ready/Busy
(R/B#) signal 14 referenced above.
[0021] Command register 38 decodes an input command from the global buffer 44 and the decoded command is input to the control circuit 36 having a state machine.
[0022] Control circuit 36 is a central unit to control the entire device during various operating modes.
[0023] Control buffers 34 determine one of operating modes such as command input, address input, data input, data output and status output in accordance with combination of control pins as CE#, CLE, ALE, WE#, RE# and WP#.
[0024] Multiplexed column address and row address are stored in the address register 40 and transferred into row pre decoder 46 and column decoder 56 via column pre decoder 48.
[0025] An example of operational timing details and device operations for the NAND flash functional block of Figure 1 can be found in NAND Flash specifications such as
Samsung's 8Gb SLC NAND Flash Specification k9f8g08x0m entitled "1G x 8 Bit/2G x 8 Bit NAND Flash Memory" dated March 31 , 2007 and Samsung's 16Gb/32Gb/64Gb SLC NAND Flash Specification: k9xxg08uxm entitled "2G x 8 Bit/4G x 8 Bit/8G x 8 Bit NAND Flash Memory" dated march 31 , 2007, both of which are incorporated by reference herein.
Device Operation in NAND Flash
[0026] In this section, basic operations and cell array organization of NAND flash memory are described. Figure 2 illustrates the cell array structure of NAND flash memory which consists of n erasable blocks labeled Block 0, Block 1 , Block n-1. Each block is subdivided into m programmable pages as shown Figure 3, labeled Page 0, Page 1 , Page m-1.
[0027] Each page consists of (j+k) bytes (x8b) as shown in Figure 4. The pages are further divided into a j-byte data storage region 100 (data field) with a separate k-byte area 102 (spare field). The k-byte area is typically used for error management functions. With this arrangement, 1 page = (j + k) bytes, 1 block = m pages = (j + k) bytes * m, and the total memory array size = n blocks = (j + k) bytes * m * n.
[0028] In NAND flash devices, read and program operations are executed on a page basis while erase operations are executed on a block basis. All operations may, for example, be driven by commands specified in the above-referenced Samsung specifications. In a specific example, j=4096, k=128, m=64 and n=2048. Using these numbers, 1 Page = (4K + 128) Bytes, 1 Block = 64 Pages = (4K + 128) Bytes x 64 = (256K + 8K) Bytes, 1 Plane = 2048 Blocks = (256K + 8K) Bytes x 2048 = (4 G + 128M) Bits, and 1 Device = 2 Planes = (4G + 128M) Bits * 2 = (8G + 256M) Bits. Typically, the stated memory capacity in NAND flash does not include the spare field.
[0029] The internal memory array is accessed on a page basis. The read operation starts after writing READ command followed by addresses via common I/O pins (I/O0 to I/O 7) to the device. The 4,224 bytes of data within the selected page are sensed and transferred to the page register (or page buffer) in less than tR (data transfer time from flash array to page register) shown in Figure 5. Once the 4,224 bytes of data are sensed and transferred from the selected page in the cell array to the data register, the data in the data register can be sequentially read from the device.
[0030] The memory array is programmed on a page basis. For program operations, a
PROGRAM command followed by addresses and input data of 4,224 bytes is issued to the device through common I/O pins (I/O0 to I/07). The 4,224 bytes of data are transferred to the page register (or page buffer) during input data loading cycles and finally programmed to the selected page of the cell array less than tPROG (page program time) as shown in Figure 6.
[0031] The memory array is erased on a block basis. For block erase operations, a
BLOCK ERASE command followed by block addresses is issued to the device through common I/O pins (I/O0 to I/07). The (256K + 8K) bytes of data are erased less than tBERS (block erase time) as shown in Figure 7.
General Flash Memory System
[0032] Figure 8 shows a block diagram of an example of a general system that includes a flash memory system. The flash memory system 114 communicates with a main system or processor 110 via a flash controller 112.
[0033] A typical flash memory system has either a single flash memory device 118 as shown in Figure 9 or multiple flash memory devices 120,122,124,126 as shown in Figure 10. A flash memory system using a single flash device might be used in applications which require relatively small memory space.
[0034] For applications requiring large memory space, a flash memory system using multiple flash memory devices can be implemented such as the system of Figure 10. The flash controller 112 can access each flash memory device 120,122,124,126 via a common bus 128. Only one flash device can be selected at a time by asserting a chip enable signal on one of devices.
NAND Flash Memory in Multi Chip Package (MCP)
[0035] A multi chip package (MCP: multiple chips in a single package) is a very popular solution to increase packing density. An MCP typically uses multi-drop bus such as shown in Figure 11 and Figure 12.
[0036] Figure 11 illustrates a MCP having two NAND flash devices 130,132. All input and output signals except chip select (CE#) signals 136,138 in each flash memory device are connected to a common bus 134. Each flash memory device can be selected by asserting the appropriate CE# signal. For example, the flash device 1 130 can be selected and accessed by asserting CE1# 136 (CE1# = "Low"). The 2nd flash device 132 is unselected (CE2# = "High") and ignores any input like commands or addresses from the flash controller. Also the output signals of the rest devices are high impedance (i.e. Hi-Z) state. [0037] Similarly Figure 12 illustrates a MCP having four NAND flash devices
140, 142, 144,146 with respective CE# signals CE1# 152, CE2# 154, CE3# 156, and CE4# 158. The 1 st flash device 1 140 can be selected and accessed by asserting CE1# (CE1# = "Low"). The rest of the devices are unselected (CE2# = "High", CE3# = "High", CE4# = "High") and ignore any input like commands or addresses from the flash controller. Also the output signals of the rest devices are high impedance (i.e. Hi-Z) state. This type of device connection is a multi-drop bus connection or topology.
[0038] Figure 13 illustrates an example of page program operational timing for two
NAND flash devices in a single package. All input and output pins except CE# pins are commonly connected in multi-drop configuration as shown in Figure 1 1. This example shows consecutive program operations into device 1 130 and device 2 132.
When CE1# is Low (400), the st command cycle (80h) for page program is issued (402) to device 1 130. Five bytes input addresses (AO to A30 for 8Gb NAND Flash) (404) and 4K bytes input data (406) are loaded to device 1.
The 2nd command cycle (10h) (408) for page program is asserted and device 1 starts page program operation (410) governed by auto-timed, internal program algorithm. During this period, the R/B# of device 1 goes Low to represent device 1 is in busy state (412). Once the internal page program operation is completed, the R/B# of device 1 goes High (414). Hence the next command can be issued to device 1. During page program operation in device 1 , device 2 132 is disabled (deselected) by CE2# = High (416).
When CE2# is Low (418), the 1st command cycle (80h) for page program is issued to device 2 (420). Five bytes input addresses (AO to A30 for 8Gb NAND Flash) (422) and 4K bytes input data (424) are loaded to device 2. The 2nd command cycle (10h) (426) for page program is asserted and device 1 starts page program operation governed by auto- timed, internal program algorithm. During this period, the R/B# of device 1 goes Low (428) to represent device 1 is in busy state. Once the internal page program operation is completed, the R/B# of device 2 goes High (430). Hence the next command can be issued to device 2. During page program operation in device 2, device 1 is disabled (deselected) by CE2# = High (432).
[0039] With page program operations shown in Figure 13, the unselected NAND flash device waits until the selected device completes any operation. The auto-timed page program typically takes 200us in SLC NAND flash and 600us in MLC NAND flash. [0040] In order to reduce the waiting time, a NAND flash device may have a "CE# don't care state." Once the selected device starts an internal page program operation, the selected device will continue the internal page program operation even when the CE# is High. With the "CE# don't care" feature, the next device can perform any other operation once the previous device enters the internal page program operation. This is referred to as a device interleave operation between two NAND flash devices and an example of this is shown in Figure 14, again in the context of the MCP of Figure 1 1 containing 2 flash devices.
When CE1# is Low (440), the 1st command cycle (80h) for page program is issued to device 1 130 (442). Five bytes input addresses (AO to A30 for 8Gb NAND Flash) (444) and 4K bytes input data (446) are loaded to device 1. The 2nd command cycle (10h) (448) for page program is asserted and device 1 starts page program operation governed by auto-timed, internal program algorithm (450). During this period, the R/B# of device 1 goes 'Low' to represent device 1 is in busy state (452). Once the internal page program operation in the 1 st device started, which can be indicated by R/B#, the CE1# can return to High (454). Therefore the next page program command can be issued to the 2nd device 132.
When CE2# is Low (456), the 1st command cycle (80h) for page program to device 2 is issued (458). Five bytes input addresses (AO to A30 for 8Gb NAND Flash) (460) and 4K bytes input data (462) are loaded to device 2. The 2nd command cycle (10h) (464) for page program is asserted and device 2 starts page program operation governed by auto- timed, internal program algorithm (466). Once the internal page program operation is completed, the R/B# of device 2 goes High (468).
[0041] Figure 15 shows interleave page read operational timing for two NAND flash devices in a single package, for example, the MCP of Figure 11. The interleave page read operation is very similar to the interleave page program operation described previously.
When CE1# is Low (470), the 1 st command cycle (OOh) (472) for page read to device 1 130 is issued and five bytes input addresses (AO to A30 for 8Gb NAND Flash) (474) are loaded to device 1 The 2nd command cycle (30h) (476) for page read is asserted and device 1 starts page read operation governed by auto-timed, internal read algorithm. During this period, the
R/B# of device 1 goes Low to represent device 1 is in busy state (480). Once the internal page read operation is completed, the R/B# of device 1 goes High (482). Hence device 1 is ready for burst read operation of 4KB data. During page read operation for device 1 , device
2 132 is disabled (deselected) by CE2# = High (484). When CE2# is Low (486), the 1st command cycle (OOh) (488) for page program to device 2 is issued and five bytes input addresses (AO to A30 for 8Gb NAND Flash) (490) are loaded to device 2. The 2nd command cycle (10h) (492) for page read is asserted and device 2 starts page read operation governed by auto-timed, read algorithm (494). During this period, the R/B# of device 2 goes Low to represent device 2 is in busy state (496). Once the internal page read operation is completed, the R/B# of device 2 goes High (498). Hence the next command can be issued to device 2. During page read operation for device 2, device 1 is disabled (deselected) by CE2# = High (500).
In MCP Configuration
[0042] An objective of MCP in flash memory is increasing memory capacity while maintaining same package pinout and configuration. However, in conventional implementations the chip enable (CE#) pin needs to be separated as described in section 1.4. If the MCP device has 4 flash devices in a single package, four chip enable pins (CE1# ~ CE4#) are needed as opposed to two in an MCP with two flash devices. The result is that the 4-device MCP needs a different pin assignment and PCB layout compared to a 2-device MCP. In addition, this chip enable pin increase is a burden to the flash memory controller.
[0043] The embodiments described below use only two flash devices in a single package or flash memory system. However, these embodiments are easily extended to be applicable to larger numbers of flash devices in a single package or flash memory system. Device Selection by Command in MCP
[0044] Figure 16 and Figure 17 show examples of device connection for two NAND flash devices in a single package and four NAND flash devices in a single package. For the two device embodiment of Figure 16, there are two NAND flash devices 160,162 connected to a common bus 164. Unlike the arrangement of Figure 11 , there are no individual CE# pins. Similarly, for the four device embodiment of Figure 17, there are four NAND flash devices 170,172,174,176 connected to a common bus 178. Unlike the arrangement of Figure 12, there are no individual CE# pins. In the illustrated examples, the pinout is identical regardless of the number of flash memory devices in a package and all pins are commonly connected.
[0045] Some conventional NAND flash systems use a one byte command structure.
No device ID is included in the command structure. Figure 18 depicts a 1 byte command structure according to an embodiment of the present invention. The command consists of OP code 200 and device ID 202. In this example, upper 4 bits (Bit 4 to Bit 7) are assigned to the OP code and lower 4 bits (Bit 0 to Bit 3) are assigned to the device ID. With 4-bit device ID, total 16 devices can be exclusively selected. Note that the number of bits assigned to OP code and device ID may vary and the command structure shown in Figure 18 is just an example.
[0046] In some embodiments, each NAND flash device connected in a multi-drop configuration, for example the NAND flash devices of Figure 16 or 17, contains a command processor (not shown) configured to process a command received via the common bus to determine if the command selects that particular memory device, and to act upon the command if the command selects that particular memory device.
[0047] Table 1 lists an example set of commands for use in an embodiment of the present invention. The lower 4 bits in the 1st command select one of up to 16 flash devices. A difference between the proposed NAND flash command and conventional NAND flash commands is that the lower 4 bits of each command in the example of the present invention are assigned to the device ID.
Table 1 : Example Set of Commands Including Device ID
X = Device ID: 0 ~ F up to 16 devices
[0048] Table 2 and Table 3 show read commands and page program commands having device ID to select one of up to 16 flash devices.
Table 2: Read Command having Device ID Read Device 2 01 h 30h
Read Device 3 02h 30h
Read Device 16 OFh 30h
Table 3: Pag e Program Command having Device ID
Function 1st Command Cycle 2nd Command Cycle
Page Program Device 1 80h 10h
Page Program Device 2 81 h 10h
Page Program Device 3 82h 10h
Page Program Device 16 8Fh 10h
[0049] Figure 19 illustrates operational timing of interleave page program in two
NAND flash devices according to an embodiment of the present invention. Note that the following interleave page operations can be also applied to more than two flash devices in a system.
All flash devices (in this case, two flash devices) always accept any command.
When CE# is Low (510), the 1st command cycle having device ID (80h) (512) for page program is issued to device 1. Five bytes input addresses (AO to A30 for 8Gb NAND Flash) (514) and 4K bytes input data (516) are loaded to device 1 , where:
1st address input (1st byte) = column address 1 ;
2nd address input (2nd byte) = column address 2;
3rd address input (3rd byte) = row address 1 ;
4th address input (4th byte) = row address 2;
5th address input (5th byte) = row address 3.
Device 2 will recognize from the 1st command cycle (80h) that the input address and input data are not for device 2. Thus device 2 will block following 5 bytes input address and 4K bytes input data from the common bus (i.e. device 2 is deselected by the 1st command cycle (80h)) (520). The 2nd command cycle (10h) (518) for page program is asserted and device 1 starts page program operation governed by auto-timed, internal program algorithm (522). During this period, the R/B# of device 1 goes Low to represent device 1 is in busy state (524) Device 2 will ignore the 2nd command cycle (10h) because the 1 st command cycle (80h) was not for device 2. Once the internal page program operation in device 1 started, which can be indicated by R/B#, the next page program command can be issued to device 2.
The 1st command cycle having device ID (81 h) (526) for page program to device 2 is issued to device 2. Five bytes input addresses (AO to A30 for 8Gb NAND Flash) (530) and 4K bytes input data (532) are loaded to device 1. The internal page program operation in device 1 is not interrupted by the 1 st command cycle (81 h) for page program to device 2. The 2nd command cycle (10h) (534) for page program is asserted and device 2 starts page program operation governed by auto-timed, internal program algorithm (536). During this period, the R/B# of device 2 goes Low to represent device 2 is in busy state (538).
A read status command having device ID (70h) is issued to check the status of device 1 (540). If device 1 is ready to take a next operation, another page program command can be inputted to device 1. The 1 st command cycle having device ID (80h) (542) for page program is issued to device 1. Five bytes input addresses (AO to A30 for 8Gb NAND Flash) (544) and 4K bytes input data (546) are loaded to device 1. The 2nd command cycle (1 Oh) (548) for page program is issued and device 1 starts page program operation governed by auto-timed, internal program algorithm (550). During this period, the R/B# of device 1 goes Low to represent device 1 is in busy state (552).
[0050] Figure 20 illustrates operational timing of interleave page read in two NAND flash devices according to an embodiment of the present invention. Note following interleave page operations can be also applied to more than two flash devices in a system.
All flash devices (in this case, two flash devices) always accept any command.
When CE# is 'Low' (560), the 1 st command cycle (OOh) (562) for page read to device 1 is asserted and five bytes input addresses (AO to A30 for 8Gb NAND Flash) (564) are loaded to device 1. Device 2 will recognize from the 1 st command cycle (OOh) that the input address are not for device 2. Thus device 2 will block following 5 bytes input address from the common bus (i.e. device 2 is deselected by the 1 st command cycle (00h)) (570). The 2nd command cycle (30h) (566) for page read is asserted and device 1 starts page read operation governed by auto-timed, internal read algorithm (568). During this period, the R/B# of device 1 goes Low to represent device 1 is in busy state (572). Device 2 will ignore the 2nd command cycle (30h) because the 1 st command cycle having device ID (OOh) is not for device 2.
The 1st command cycle (01 h) (580) for page read to device 2 is asserted and five bytes input addresses (AO to A30 for 8Gb NAND Flash) (582) are loaded to device 2. The 2nd command cycle (30h) (584) for page read is asserted and device 2 starts page read operation governed by auto-timed, read algorithm (586). During this period, the R/B# of device 2 goes Low to represent device 2 is in busy state (588).
A read status command having device ID (70h) is issued to device 1 to check the device status (590). If device 1 is ready to take a next operation, another command can be inputted to device 1. The 1st command cycle (20h) (592) for burst read to device 1 is asserted and five bytes input addresses (AO to A30 for 8Gb NAND Flash) (594) are loaded to device 2. The 2nd command cycle (30h) (596) for burst read is asserted and device 1 starts burst read operation to access 4K bytes data stored in the page buffers of device 1 during previous page read operation in device 1 (598).
After burst reading the data from device 1 , a read status command (71 h) is issued to check the status of device 2 (600). Device 1 will ignore the read status command (71 h) because this command is not for the device 1. If device 2 is ready to take a next operation, another command can be inputted to device 2. The 1 st command cycle (21 h) (602) for burst read to device 2 is asserted and five bytes input addresses (604) are loaded to device 2. The 2nd command cycle (30h) (606) for burst read is asserted and device 2 starts burst read operation to access 4K bytes data stored in the page buffers of device 2 during previous page read operation in device 2 (608).
[0051] Similarly any device interleave operation among read, program and block erase can be executed with an embodiment of the present invention. Figure 21 shows operational timing of interleave page read and program in two NAND flash devices according to an embodiment of the present invention.
All flash devices (in this case, two flash devices) always accept any command.
When CE# is Low (610) , the 1 st command cycle (OOh) (612) for page read to device 1 is asserted and five bytes input addresses (AO to A30 for 8Gb NAND Flash) (614) are loaded to device 1. Device 2 will recognize from the 1 st command cycle (OOh) that the input address are not for device 2. Thus device 2 will block following 5 bytes input address from the common bus (i.e. device 2 is deselected by the 1st command cycle (00h)) (620). The 2nd command cycle (30h) (616) for page read is asserted and device 1 starts page read operation governed by auto-timed, internal read algorithm (618). During this period, the R/B# of device 1 goes Low to represent device 1 is in busy state (622). Device 2 will ignore the 2nd command cycle (30h) because the 1 st command cycle (OOh) is not device 2.
The 1 st command cycle having device ID (81 h) (624) for page program to device 2 is issued to device 2. Five bytes input addresses (AO to A30 for 8Gb NAND Flash) (628) and 4K bytes (630) input data are loaded to device 1. The internal page program operation in device 1 is not interrupted by the 1 st command cycle (81 h) for page program to device 2. The 2nd command cycle (10h) (632) for page program is asserted and device 2 starts page program operation governed by auto-timed, internal program algorithm (634). During this period, the R/B# of device 2 goes Low to represent device 2 is in busy state (636).
A read status command (70h) is issued to check the status of device 1 (640). If device 1 is ready to take a next operation, another command can be inputted to device 1. The 1st command cycle (20h) (642) for burst read to device 1 is asserted and five bytes input addresses (644) are loaded to device 1. The 2nd command cycle (30h) (646) for burst read is asserted and device 1 starts burst read operation to access 4K bytes data stored in the page buffers of device 1 during previous page read operation in device 1 (648).
Device Selection by Input Address in MCP
[0052] In another embodiment, device selection is achieved through the use of input address, for example one or more MSB of the row address. The command and sequence shown in Table 4 are identical to those of conventional proposed NAND flash . It should be clearly understood a different command structure could be used.
Table 4: Example Command Set
Function 1st Command Cycle 2nd Command Cycle
Read OOh 30h
Burst Read (Additional 20h 30h
Command)
Block Erase 60h DOh
Read Status 70h - Page Program 80h 10h
Reset FFh -
[0053] In addition to the command, a full command cycle for read, burst read, block erase, page program includes an address. In the conventional 8 GB NAND flash design, the address contains 4 bytes, containing 32 bits AO to A31. Address bits AO to A12 are assigned to the column address, and address bits A13 to A30 are assigned to the row address.
[0054] According to an embodiment of the invention, additional bits in of the address are used to select one of multiple devices that are commonly connected in a single package (e.g. MCP using multi-drop connection).
[0055] In a first example, for two 8Gb flash devices, A31 can be used to perform device selection.
[0056] In a second example, for four 8Gb flash devices, A31 and A32 can be used to perform device selection. Note this requires an additional byte in the address to convey A32. However, since the command and address are conveyed to the devices in sequence over the common bus, this does not change the pinout requirement.
[0057] In a second example, for eight 8Gb flash devices, A31 to A33 can be used to perform device selection. Note that this also requires an additional byte in the address to convey A32 and A33. However, since the command and address are conveyed to the devices in sequence over the common bus, this does not change the pinout requirement.
[0058] Note that in addition to including address information for read, burst read, block erase, and page program, for this embodiment of the invention, address information is also included for other device-specific commands, such as read status.
[0059] To explain the device selection (e.g., input and output data control) by input address, the case of 4 flash devices in MCP is described. Figure 22 shows one example of circuits for device selection by input address. Such a circuit is included in each NAND flash device connected in a multi-drop configuration. Refer to Figure 1 for an example functional block diagram of a whole NAND flash. In Figure 22, # denotes enable when logic Low (i.e. active when Low). CE#, WE#, RE#, WP#, ALE, CLE are external control input signals. CEf#, WEf#, REf#, WPf#, ALEf, CLEf are buffered, internal control signals. I/O0 ~ 1/07 are external input and output signals (common I/O signals). 1/OfO ~ l/Of7 are buffered, internal input and output signals. A31 and A32 are address signals from the address register. DeviceJD register 300 is a register containing a unique deviceJD - that is, unique between the devices connected in the multi-drop configuration. This can, for example, where the DeviceJD register of each device contains respective values for the bits ID_A32 and ID_A31. be programmed by one of nonvolatile programming methods such as laser fuse, electrical fuse, pad bonding option, metal layer option or nonvolatile memory cells. An example of unique device ID information stored in DeviceJD register of the four devices of an MCP is shown in Table 5 below.
[0060] The device ID in each flash device in MCP is compared with input address
A31 and A32 whenever input addresses are loaded. Input address A31 and A32 via the global buffer are compared with device ID address ID_A31 and ID_A32 in Device ID Comparator 302. If the input addresses are matched with the device ID addresses, the output IOEN 306 of the DeviceJD Comparator is High. WE# buffer and RE# buffer are controlled by not only CE# but also DSEL of the Burst Data Control block. Specifically, when DSEL is high, these buffers are disabled.
[0061] A burst data control block 310 generates the DSEL outputs 320 as a function of IOEN 306, ALEf 312 and CLEf 314. The burst data control block 310 receives IOEN 306, and inverts this with invertor 316 to produce IOEN#. ALEf 312 is an input that is high during address input, and CLEf 314 is an input that is high during command input. ALEf 312, CLEf 314 and IOEN# are input to NOR gate 318 the output of which input to inverter 319, the output of which is the DSEL output 320. DSEL low means that a device is not de-selected, while DSEL high means a device is de-selected. It can be seen that during command input (CLEf = High) or address input (ALEf = High), the DSEL is always High. Therefore any command or address input to each device in MCP is not blocked by the Burst Data Control (i.e. DSEL = Low). In addition, the device that has a device ID match is not de-selected.
Table 5 shows device selection table by input address for four flash devices in MCP.
Table 5: Device Selection by Input Address Input Address (A32, A31) from 5th Address
Input Cycle
ID_A32 ID_A31 0, 0 0, 1 1 , 0 1, 1
Device 1 0 0 Selected - - -
Device 2 0 1 - Selected - -
Device 3 1 0 - - Selected -
Device 4 1 1 - - - Selected
[0062] Figure 23 illustrates an example of command/address/data input timing with the circuits shown in Figure 22. Device 1 is selected and devices 2 to 4 are deselected. For operational timing in Figure 23, only devices 1 and 2 are shown, but internal timing of devices 3 and 4 are identical to that of device 2. Input address A32 (= 0) and A31 (= 0) at the 5th address cycle are compared with device ID address ID_A31 and ID_A32 in the Device ID Comparator. The IOEN in device 1 is High while the IOEN in device 2 is Low. The DSEL in device 1 is Low (due to IOEN = High) and doesn't disable the WE# buffer. Therefore following 4K byte input data from external pins are inputted to the Device 1 during data input cycles. The DSEL in device 2 is High (due to IOEN = Low) and disables the WE# buffer. Therefore the buffered WEf# signal remains at 'High' and following 4K byte input data to the Device 2 are not inputted to device 1 during data input cycles. Devices 3 and 4 behave as device 2.
[0063] Figure 24 illustrates command/address/data output timing with the circuits shown in Figure 22. The output timing is very similar to the input timing shown in Figure 23. Device 1 is selected and devices 2 to 4 are deselected. For operational timing in Figure 23, only devices 1 and 2 are shown, but internal timing of devices 3 and 4 are identical to that of device 2. Input address A32 (= 0) and A31 (= 0) at the 5th address cycle are compared with device ID address ID_A31 and ID_A32 in the Device ID Comparator. The IOEN in device 1 is High while the IOEN in device 2 is Low. The DSEL in device 1 is Low (due to IOEN = High) and doesn't disable the RE# buffer. Therefore 4K bytes read data can be accessed from device 1 during burst data read cycles. The DSEL in device 2 is High (due to IOEN = Low) and disables the WE# buffer. Therefore the buffered REf# signal remains at High, which disables global buffers in device 2 and l/OfO to l/Of7 remain at Hi-Z state. Devices 3 and 4 behave as device 2. [0064] With the device selection method by input address described here, the device interleave operations (e.g., page program, interleave page read and interleave page read & program and so on) can be performed in same fashion as the device interleave operations described previously.
[0065] Operational timing and sequence for device interleave operations with the device selection by input address are not shown because two examples of device selection schemes (e.g., device selection by command and device selection by input address) are nearly identical.
[0066] In the embodiments described above, the device elements and circuits are connected to each other as shown in the figures for the sake of simplicity. In practical applications these devices, elements circuits, etc., may be connected directly to each other or indirectly through other devices elements, circuits, etc. Thus, in an actual configuration, the elements, circuits and devices are coupled either directly or indirectly with each other.
[0067] The above-described embodiments of the present invention are intended to be examples only. Alterations, modifications and variations may be effected to the particular embodiments by those of skill in the art without departing from the scope of the invention, which is defined solely by the claims appended hereto.

Claims

What is claimed is:
1. A memory system comprising:
a memory controller;
a plurality of memory devices connected to the controller via a common bus with a multi-drop connection;
wherein the memory controller performs device selection by command.
2. The memory system of claim 1 , wherein the memory controller performs device selection by command by, for each command, transmitting the command comprising a command op code portion and a device identifier portion; and
wherein each of the plurality of memory devices acts upon the command when the device identifier portion of the command matches a device identifier of the memory device.
3. The memory system of claim 1 wherein the command is a command selected from the following: for a read status operation for a device having device identifier <device_ID>:
<read op_code>; <device_ID>, where <read op_code> is an op code specifying read operation; for a burst read operation for a device having device identifier <device_ID>:
<burst read op_code>; <device_ID> where <burst read op_code> is an op code specifying burst read operation; for a block erase operation for a device having device identifier <device_ID>:
<block erase op_code>; <device_ID>, where <block erase op_code> is an op code specifying block erase operation; for a read operation for a device having device identifier <device_ID>: <read status op_code>; <device_ID>, where <read status op_code> is an op code specifying read status operation; for a page program operation for a device having device identifier <device_ID>:
<page program op_code>; <device_ID>, where <page program op_code> is an op code specifying page program operation.
4. The memory system of claim 2 wherein the command is an 8 bit command, of which the command portion is 4 bits and the device identifier portion is 4 bits.
5. The memory system of claim 1 wherein device selection is performed by command with device interleave operations.
6. The memory system of claim 5 wherein the interleave operation comprises one of: page program of a first device interleaved with page program of a second device; page program of a first device interleaved with page read of a second device;
page read of a first device interleaved with page read of a second device.
7. The memory system of claim 1 wherein the plurality of devices comprises a plurality of NAND flash devices that are part of a multi-chip package.
8. The memory system of claim 7 comprising:
a common chip enable for the plurality of NAND flash devices.
9. The memory system of claim 1 wherein the common bus comprises:
a write protect line;
a write enable line;
a read enable line;
an address latch enable line;
a command latch enable line;
a chip enable line;
an I/O for command, address and data; and a ready/busy line.
10. A memory system comprising:
a memory controller;
a plurality of memory devices connected to the controller via a common bus with a multi-drop connection;
wherein the memory controller performs device selection by input address; each memory device comprising:
a register containing a device identifier;
a device identifier comparator that compares selected bits of a received input address to contents of the register to determine if there is a match, and wherein a given device is selected if the device identifier comparator of the given device determines there is a match.
1 1 . The memory system of claim 10 comprising:
a global buffer in which command, data and input address are initially stored upon receipt
wherein the device identifier comparator obtains the selected bits of the received input address via the global buffer.
12. The memory system of claim 10 wherein each memory device further comprises a burst data controller that causes the memory device to be selected:
when the device identifier comparator determines there is a match;
while a command input is in progress; and
while an address input is in progress.
13. The memory system of claim 12 wherein in each memory device, the burst data controller comprises an output that indicates whether the memory device is selected or deselected.
14. The memory system of claim 12 wherein each burst data controller comprises: a logic circuit that receives an output of the device identifier comparator, an address latch enable signal that indicates whether an address input is in progress, and a command latch enable signal that indicates whether a command input is in progress, and wherein the logic circuit generates an output that indicates whether the memory device is selected or deselected.
15. The memory system of claim 10 wherein each memory device further comprises: a write enable buffer for buffering a received write enable signal, the write buffer having an input for receiving an indication of whether that memory device is selected or deselected, and wherein the write enable buffer is disabled when the memory device is deselected;
a read enable buffer for buffering a received read enable signal, the read buffer having an input for receiving an indication of whether that memory device is selected or deselected, and wherein the read enable buffer is disabled when the memory device is deselected.
16. The memory system of claim 10 wherein device selection is performed by input address with device interleave operations.
17. The memory system of claim 16 wherein the interleave operation comprises one of: page program of a first device interleaved with page program of a second device; page program of a first device interleaved with page read of a second device;
page read of a first device interleaved with page read of a second device.
18. The memory system of claim 10 wherein the plurality of devices comprises a plurality of NAND flash devices that are part of a multi-chip package.
19. The memory system of claim 18 comprising:
a common chip enable for the plurality of NAND flash devices.
The memory system of claim 10 wherein the common bus comprises: a write protect line;
a write enable line;
a read enable line;
an address latch enable line;
a command latch enable line;
a chip enable line;
an I/O for command, address and data; and
a ready/busy line.
21. A memory controller for use in a system comprising the memory controller and a plurality of memory devices connected to the controller via a common bus with a multi-drop connection, wherein the memory controller performs device selection by command.
22. The memory controller of claim 21 , wherein the memory controller performs device selection by command by, for each command, transmitting the command comprising a command op code portion and a device identifier portion.
23. The memory controller of claim 21 wherein the command is a command selected from the following: for a read status operation for a device having device identifier <device_ID>:
<read op_code>; <device_ID>, where <read op_code> is an op code specifying read operation; for a burst read operation for a device having device identifier <device_ID>:
<burst read op_code>; <device_ID>, where <burst read op_code> is an op code specifying burst read operation; for a block erase operation for a device having device identifier <device_ID>:
<block erase op_code>; <device_ID>, where <block erase op_code> is an op code specifying block erase operation; for a read operation for a device having device identifier <device_ID>:
<read status op_code>; <device_ID>, where <read status op_code> is an op code specifying read status operation; for a page program operation for a device having device identifier <device_ID>:
<page program op_code>; <device_ID>, where <page program op_code> is an op code specifying page program operation.
24. The memory controller of claim 22 wherein the command is an 8 bit command, of which the command portion is 4 bits and the device identifier portion is 4 bits.
25. The memory controller of claim 21 wherein device selection is performed by command with device interleave operations.
26. The memory controller of claim 25 wherein the interleave operation comprises one of: page program of a first device interleaved with page program of a second device; page program of a first device interleaved with page read of a second device;
page read of a first device interleaved with page read of a second device.
27. The memory controller of claim 21 for use in the system in which the plurality of devices comprises a plurality of NAND flash devices that are part of a multi-chip package.
28. The memory controller of claim 27 comprising:
a common chip enable for the plurality of NAND flash devices.
29. The memory controller of claim 21 wherein the common bus comprises:
a write protect line;
a write enable line;
a read enable line;
an address latch enable line;
a command latch enable line;
a chip enable line; an I/O for command, address and data; and
a ready/busy line.
30. A memory device for use in a system comprising a memory controller and a plurality of memory devices connected to the controller via a common bus with a multi-drop connection inclusive of the memory device, the memory device comprising: a command processor configured to process a command received via the common bus to determine if the command selects that particular memory device, and to act upon the command if the command selects that particular memory device.
31. The memory device of claim 30, wherein:
the command comprises e a command op code portion and a device identifier portion; and
wherein the command processor acts upon the command when the device identifier portion of the command matches a device identifier of the memory device.
32. The memory device of claim 30 wherein the command is a command selected from the following: for a read operation for a device having device identifier <device_ID>:
<read op_code>; <device_ID>, where <read op_code> is an op code specifying read operation; for a burst read operation for a device having device identifier <device_ID>:
<burst read op_code>; <device_ID>, where <burst read op_code> is an op code specifying burst read operation; for a block erase operation for a device having device identifier <device_ID>:
<block erase op_code>; <device_ID>, where <block erase op_code> is an op code specifying block erase operation; for a read operation for a device having device identifier <device_ID>:
<read status op_code>; <device_ID>, where <read status op_code> is an op code specifying read status operation; for a page program operation for a device having device identifier <device_ID>:
<page program op_code>; <device_ID>, where <page program op_code> is an op code specifying page program operation.
33. The memory device of claim 31 wherein the command is an 8 bit command, of which the command portion is 4 bits and the device identifier portion is 4 bits.
34. The memory device of claim 30 wherein device selection is performed by command with device interleave operations.
35. The memory device of claim 34 wherein the interleave operation comprises one of: page program of the memory device interleaved with page program of a second device;
page program of the memory device interleaved with page read of a second device; page read of the memory device interleaved with page read of a second device.
36. The memory device of claim 30 wherein the plurality of devices comprises a plurality of NAND flash devices that are part of a multi-chip package.
37. The memory device of claim 36 comprising:
a common chip enable for the plurality of NAND flash devices.
38. The memory device of claim 30 wherein the common bus comprises:
a write protect line;
a write enable line;
a read enable line;
an address latch enable line; a command latch enable line;
a chip enable line;
an I/O for command, address and data; and
a ready/busy line.
39. A memory device for use in memory system comprising a memory controller, and a plurality of memory devices inclusive of the memory device connected to the controller via a common bus with a multi-drop connection, the memory device comprising:
a register containing a device identifier;
a device identifier comparator that compares selected bits of a received input address to contents of the register to determine if there is a match, and wherein the memory device is selected if the device identifier comparator determines there is a match.
40. The memory device of claim 39 comprising:
a global buffer in which command, data and input address are initially stored upon receipt
wherein the device identifier comparator obtains the selected bits of the received input address via the global buffer.
41. The memory device of claim 39 further comprising:
a burst data controller that causes the memory device to be selected:
when the device identifier comparator determines there is a match;
while a command input is in progress; and
while an address input is in progress.
42. The memory device of claim 41 wherein the burst data controller comprises an output that indicates whether the memory device is selected or deselected.
43. The memory device of claim 41 wherein the burst data controller comprises:
a logic circuit that receives an output of the device identifier comparator, an address latch enable signal that indicates whether an address input is in progress, and a command latch enable signal that indicates whether a command input is in progress, and wherein the logic circuit generates an output that indicates whether the memory device is selected or deselected.
44. The memory device of claim 39 wherein the memory device further comprises:
a write enable buffer for buffering a received write enable signal, the write buffer having an input for receiving an indication of whether that memory device is selected or deselected, and wherein the write enable buffer is disabled when the memory device is deselected;
a read enable buffer for buffering a received read enable signal, the read buffer having an input for receiving an indication of whether that memory device is selected or deselected, and wherein the read enable buffer is disabled when the memory device is deselected.
45. The memory device of claim 39 wherein device selection is performed by input address with device interleave operations.
46. The memory device of claim 45 wherein the interleave operation comprises one of: page program of the memory device interleaved with page program of a second device;
page program of the memory device interleaved with page read of a second device; page read of the memory device interleaved with page read of a second device.
47. The memory device of claim 39 wherein the plurality of devices comprises a plurality of NAND flash devices that are part of a multi-chip package.
48. The memory device of claim 47 comprising:
a common chip enable for the plurality of NAND flash devices.
49. The memory device of claim 39 wherein the common bus comprises:
a write protect line;
a write enable line;
a read enable line; an address latch enable line;
a command latch enable line;
a chip enable line;
an I/O for command, address and data; and
a ready/busy line.
50. A method in a memory system comprising a memory controller and a plurality of memory devices connected to the controller via a common bus with a multi-drop connection, the method comprising:
performing device selection by command.
51. The method of claim 50, wherein performing device selection by command comprises for each command, transmitting the command comprising a command op code portion and a device identifier portion;
the method further comprising:
each of the plurality of memory devices acting upon the command when the device identifier portion of the command matches a device identifier of the memory device.
52. The method of claim 50 wherein the command is a command selected from the following: for a read status operation for a device having device identifier <device_ID>:
<read op_code>; <device_ID>, where <read op_code> is an op code specifying read operation; for a burst read operation for a device having device identifier <device_ID>:
<burst read op_code>; <device_ID>, where <burst read op_code> is an op code specifying burst read operation; for a block erase operation for a device having device identifier <device_ID>: <block erase op_code>; <device_ID>, where <block erase op_code> is an op code specifying block erase operation; for a read operation for a device having device identifier <device_ID>:
<read status op_code>; <device_ID>, where <read status op_code> is an op code specifying read status operation; for a page program operation for a device having device identifier <device_ID>:
<page program op_code>; <device_ID>, where <page program op_code> is an op code specifying page program operation.
53. The method of claim 51 wherein the command is an 8 bit command, of which the command portion is 4 bits and the device identifier portion is 4 bits.
54. The method of claim 50 wherein performing device selection comprises performing device interleave operations.
55. The method of claim 54 wherein performing device interleave operation comprises one of:
page programming of a first device interleaved with page programming of a second device;
page programming of a first device interleaved with page reading of a second device; page reading of a first device interleaved with page reading of a second device.
56. The method of claim 50 wherein the plurality of devices comprises a plurality of NAND flash devices that are part of a multi-chip package.
57. The method of claim 56 wherein the multi-chip package comprises:
a common chip enable for the plurality of NAND flash devices.
58. The method of claim 50 wherein the common bus comprises:
a write protect line; a write enable line;
a read enable line;
an address latch enable line;
a command latch enable line;
a chip enable line;
an I/O for command, address and data; and
a ready/busy line.
59. A method for use in a memory system comprising a memory controller and a plurality of memory devices connected to the controller via a common bus with a multi-drop connection, the method comprising:
the memory controller performing device selection by input address;
each memory device maintaining a device identifier in a register;
a device identifier comparator in each memory device comparing selected bits of a received input address to contents of the register of the memory device to determine if there is a match, and wherein a given device is selected if the device identifier comparator of the given device determines there is a match.
60. The method of claim 59 comprising:
each memory device Initially storing command, data and input address are initially stored upon receipt in a global buffer
wherein in each memory device the device identifier comparator obtains the selected bits of the received input address via the global buffer.
61. The method of claim 59 further comprising:
a burst data controller in each memory device causing the memory device to be selected:
when the device identifier comparator determines there is a match;
while a command input is in progress; and
while an address input is in progress.
62. The method of claim 61 wherein in each memory device, the burst data controller generating an output that indicates whether the memory device is selected or deselected.
63. The method of claim 61 further comprising, in each memory device:
in the burst data controller of the memory device: a) receiving in a logic circuit an output of the device identifier comparator of the memory device;
b) generating an address latch enable signal that indicates whether an address input is in progress,
c) generating a command latch enable signal that indicates whether a command input is in progress,
the method further comprising the logic circuit generating an output that indicates whether the memory device is selected or deselected.
64. The method of claim 59 further comprising, in each memory device:
buffering a received write enable signal in a write buffer, the write buffer having an input for receiving an indication of whether that memory device is selected or deselected, and wherein the write enable buffer is disabled when the memory device is deselected;
for buffering a received read enable signal in a read buffer, the read buffer having an input for receiving an indication of whether that memory device is selected or deselected, and wherein the read enable buffer is disabled when the memory device is deselected.
65. The method of claim 59 wherein device selection is performed by input address with device interleave operations.
66. The method of claim 65 wherein the interleave operation comprises one of:
page program of a first device interleaved with page program of a second device; page program of a first device interleaved with page read of a second device;
page read of a first device interleaved with page read of a second device.
67. The method of claim 59 wherein the plurality of devices comprises a plurality of NAND flash devices that are part of a multi-chip package.
68. The method of claim 67 further comprising using a common chip enable for the plurality of NAND flash devices.
69. The method of claim 59 further comprising using a common bus comprising:
a write protect line;
a write enable line;
a read enable line;
an address latch enable line;
a command latch enable line;
a chip enable line;
an I/O for command, address and data; and
a ready/busy line.
EP12864164.4A 2012-01-05 2012-11-08 Device selection schemes in multi chip package nand flash memory system Withdrawn EP2801096A4 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201261583408P 2012-01-05 2012-01-05
US13/611,580 US8797799B2 (en) 2012-01-05 2012-09-12 Device selection schemes in multi chip package NAND flash memory system
PCT/CA2012/001035 WO2013102255A1 (en) 2012-01-05 2012-11-08 Device selection schemes in multi chip package nand flash memory system

Publications (2)

Publication Number Publication Date
EP2801096A1 true EP2801096A1 (en) 2014-11-12
EP2801096A4 EP2801096A4 (en) 2015-10-28

Family

ID=48743830

Family Applications (1)

Application Number Title Priority Date Filing Date
EP12864164.4A Withdrawn EP2801096A4 (en) 2012-01-05 2012-11-08 Device selection schemes in multi chip package nand flash memory system

Country Status (7)

Country Link
US (2) US8797799B2 (en)
EP (1) EP2801096A4 (en)
KR (1) KR20140111323A (en)
CN (1) CN104160448A (en)
CA (1) CA2865019A1 (en)
TW (1) TW201337945A (en)
WO (1) WO2013102255A1 (en)

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8797799B2 (en) * 2012-01-05 2014-08-05 Conversant Intellectual Property Management Inc. Device selection schemes in multi chip package NAND flash memory system
US9256502B2 (en) * 2012-06-19 2016-02-09 Oracle International Corporation Method and system for inter-processor communication
US20150039813A1 (en) * 2013-08-05 2015-02-05 Greenliant Llc NAND Interface Capacity Extender Device For Extending Solid State Drives Capacity, Performance, And Reliability
KR101655008B1 (en) 2014-11-27 2016-09-06 숭실대학교산학협력단 Apparatus and method for real-time multi-chip flash storage
JP2016170747A (en) * 2015-03-16 2016-09-23 セイコーエプソン株式会社 Semiconductor integrated circuit device and electronic apparatus using the same
US10146608B2 (en) * 2015-04-06 2018-12-04 Rambus Inc. Memory module register access
KR102291639B1 (en) * 2015-07-13 2021-08-20 에스케이하이닉스 주식회사 Semiconductor memory device outputting ready busy signal and memory system including the same
KR102296740B1 (en) * 2015-09-16 2021-09-01 삼성전자 주식회사 Memory device and memory system including the same
KR102342789B1 (en) * 2015-09-24 2021-12-24 에스케이하이닉스 주식회사 Memory system and operating method thereof
KR102554416B1 (en) * 2016-08-16 2023-07-11 삼성전자주식회사 Internal status output device of memory device and memory system adopting the same
CN109478162B (en) * 2016-09-26 2023-01-03 株式会社日立制作所 Semiconductor memory device with a plurality of memory cells
CN110149459B (en) * 2018-02-11 2024-04-05 杭州海康威视数字技术股份有限公司 Camera control method and camera
CN109101730B (en) * 2018-08-14 2022-02-18 郑州云海信息技术有限公司 Method and system for acquiring chip associated element
JP2021044358A (en) * 2019-09-10 2021-03-18 キオクシア株式会社 Semiconductor device and manufacturing method for semiconductor device
KR20210157749A (en) 2020-06-22 2021-12-29 삼성전자주식회사 Device for interfacing between memory device and memory controller, package and system including the same
WO2022269740A1 (en) * 2021-06-22 2022-12-29 ユニサンティス エレクトロニクス シンガポール プライベート リミテッド Memory device using semiconductor element
US12468446B2 (en) 2021-11-15 2025-11-11 Samsung Electronics Co., Ltd. Memory systems including memory controllers that use status input pins to check memory operation statuses of memory devices
EP4465353A4 (en) * 2022-12-08 2025-10-01 Yangtze Memory Tech Co Ltd Chip, semiconductor package structure, method for configuring an activation pin and memory

Family Cites Families (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3810105A (en) * 1967-10-26 1974-05-07 Xerox Corp Computer input-output system
US5860080A (en) 1996-03-19 1999-01-12 Apple Computer, Inc. Multicasting system for selecting a group of memory devices for operation
JP3189727B2 (en) 1997-04-15 2001-07-16 日本電気株式会社 Packet-type memory LSI with built-in coprocessor, memory system using the same, and control method therefor
JP3003782B2 (en) * 1997-07-31 2000-01-31 日本電気株式会社 Development support equipment
US6223230B1 (en) * 1998-06-15 2001-04-24 Sun Microsystems, Inc. Direct memory access in a bridge for a multi-processor system
US6216178B1 (en) * 1998-11-16 2001-04-10 Infineon Technologies Ag Methods and apparatus for detecting the collision of data on a data bus in case of out-of-order memory accesses of different times of memory access execution
US6535450B1 (en) 2000-08-18 2003-03-18 Micron Technology, Inc. Method for selecting one or a bank of memory devices
JP4358111B2 (en) * 2002-08-29 2009-11-04 パナソニック株式会社 Semiconductor memory device and data writing method to flash memory
US7861007B2 (en) * 2003-12-05 2010-12-28 Ati Technologies Ulc Method and apparatus for multimedia display in a mobile device
US8429326B2 (en) * 2005-09-12 2013-04-23 Mediatek Inc. Method and system for NAND-flash identification without reading device ID table
KR101260632B1 (en) * 2005-09-30 2013-05-03 모사이드 테크놀로지스 인코퍼레이티드 Memory with output control
US20070165457A1 (en) * 2005-09-30 2007-07-19 Jin-Ki Kim Nonvolatile memory system
US7802064B2 (en) * 2006-03-31 2010-09-21 Mosaid Technologies Incorporated Flash memory system control scheme
EP2487794A3 (en) * 2006-08-22 2013-02-13 Mosaid Technologies Incorporated Modular command structure for memory and memory system
US8433874B2 (en) * 2006-12-06 2013-04-30 Mosaid Technologies Incorporated Address assignment and type recognition of serially interconnected memory devices of mixed type
US7796462B2 (en) * 2007-02-22 2010-09-14 Mosaid Technologies Incorporated Data flow control in multiple independent port
US8046527B2 (en) * 2007-02-22 2011-10-25 Mosaid Technologies Incorporated Apparatus and method for using a page buffer of a memory device as a temporary cache
US20080282017A1 (en) * 2007-05-09 2008-11-13 Microsoft Corporation Serial Peripheral Interface Switch
US7831742B2 (en) * 2007-08-10 2010-11-09 Qimonda Ag Method and device for enumeration
US8131913B2 (en) * 2008-02-04 2012-03-06 Mosaid Technologies Incorporated Selective broadcasting of data in series connected devices
US20100115172A1 (en) * 2008-11-04 2010-05-06 Mosaid Technologies Incorporated Bridge device having a virtual page buffer
US8880970B2 (en) * 2008-12-23 2014-11-04 Conversant Intellectual Property Management Inc. Error detection method and a system including one or more memory devices
US8250417B2 (en) * 2009-01-14 2012-08-21 Micron Technology, Inc. Method for detecting flash program failures
US8370718B2 (en) * 2009-04-08 2013-02-05 Stmicroelectronics S.R.L. Method for identifying a flash memory device and related hosting device
US8966208B2 (en) * 2010-02-25 2015-02-24 Conversant Ip Management Inc. Semiconductor memory device with plural memory die and controller die
US8582382B2 (en) * 2010-03-23 2013-11-12 Mosaid Technologies Incorporated Memory system having a plurality of serially connected devices
US8924626B2 (en) * 2010-04-29 2014-12-30 Sandisk Technologies Inc. Phased NAND power-on reset
KR101635446B1 (en) * 2010-05-25 2016-07-04 삼성전자주식회사 Method of merging blocks for a semiconductor memory device
JP2012133416A (en) * 2010-12-17 2012-07-12 Toshiba Corp Memory system
WO2013071399A1 (en) * 2011-11-14 2013-05-23 Mosaid Technologies Incorporated Package having stacked memory dies with serially connected buffer dies
US8825967B2 (en) * 2011-12-08 2014-09-02 Conversant Intellectual Property Management Inc. Independent write and read control in serially-connected devices
US8797799B2 (en) * 2012-01-05 2014-08-05 Conversant Intellectual Property Management Inc. Device selection schemes in multi chip package NAND flash memory system

Also Published As

Publication number Publication date
TW201337945A (en) 2013-09-16
US20130176788A1 (en) 2013-07-11
KR20140111323A (en) 2014-09-18
CA2865019A1 (en) 2013-07-11
WO2013102255A1 (en) 2013-07-11
EP2801096A4 (en) 2015-10-28
US8797799B2 (en) 2014-08-05
CN104160448A (en) 2014-11-19
US20140313831A1 (en) 2014-10-23
US9524778B2 (en) 2016-12-20

Similar Documents

Publication Publication Date Title
US9524778B2 (en) Device selection schemes in multi chip package NAND flash memory system
US10705736B2 (en) Flash memory system
US12079060B2 (en) Memory system
CN107871521B (en) Semiconductor storage device, flash memory and continuous reading method thereof
JP5421127B2 (en) Nonvolatile memory with dynamic multimode operation
EP2332036B1 (en) Solid state storage device controller with expansion mode
US20150134887A1 (en) Data writing method, memory control circuit unit and memory storage apparatus
US20130166825A1 (en) Method Of Controlling Non-Volatile Memory, Non-Volatile Memory Controller Therefor, And Memory System Including The Same
US20080172521A1 (en) Memory System Determining Storage Mode According to Host Provided Data Information
US9021218B2 (en) Data writing method for writing updated data into rewritable non-volatile memory module, and memory controller, and memory storage apparatus using the same
US9846643B2 (en) Methods for maintaining a storage mapping table and apparatuses using the same
JP2015164090A (en) multiple independent serial link memory
WO2012082656A2 (en) Universal timing waveforms sets to improve random access read and write speed of memories
JP2017045391A (en) Memory system
US20140173173A1 (en) Method, device, and system including configurable bit-per-cell capability
US10884668B2 (en) Memory system
JP2020149151A (en) Semiconductor storage device
US20070047308A1 (en) Memory controller, flash memory system and control method for flash memory
US8713242B2 (en) Control method and allocation structure for flash memory device
JP6708762B1 (en) Semiconductor memory device
US20250266839A1 (en) Storage device including pad for determining link startup mode and method of controlling level of pad for determining link startup mode thereof

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20140730

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: CONVERSANT INTELLECTUAL PROPERTY MANAGEMENT INC.

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: CONVERSANT INTELLECTUAL PROPERTY MANAGEMENT INC.

DAX Request for extension of the european patent (deleted)
RA4 Supplementary search report drawn up and despatched (corrected)

Effective date: 20150930

RIC1 Information provided on ipc code assigned before grant

Ipc: G11C 7/10 20060101ALI20150924BHEP

Ipc: G11C 8/12 20060101AFI20150924BHEP

Ipc: G11C 16/06 20060101ALI20150924BHEP

Ipc: G11C 16/10 20060101ALI20150924BHEP

Ipc: G11C 16/04 20060101ALI20150924BHEP

Ipc: G11C 15/04 20060101ALI20150924BHEP

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN

18W Application withdrawn

Effective date: 20160310