WO2005010637A2 - Sdram memory device with an embedded nand flash controller - Google Patents

Sdram memory device with an embedded nand flash controller Download PDF

Info

Publication number
WO2005010637A2
WO2005010637A2 PCT/IL2004/000399 IL2004000399W WO2005010637A2 WO 2005010637 A2 WO2005010637 A2 WO 2005010637A2 IL 2004000399 W IL2004000399 W IL 2004000399W WO 2005010637 A2 WO2005010637 A2 WO 2005010637A2
Authority
WO
WIPO (PCT)
Prior art keywords
memory
memory device
controller
host system
sdram
Prior art date
Application number
PCT/IL2004/000399
Other languages
French (fr)
Other versions
WO2005010637A3 (en
Inventor
Meir Avraham
Dan Inbar
Ziv Paz
Original Assignee
M-Systems Flash Disk Pioneers Ltd.
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 M-Systems Flash Disk Pioneers Ltd. filed Critical M-Systems Flash Disk Pioneers Ltd.
Priority to EP04732398A priority Critical patent/EP1649378A4/en
Priority to JP2006521766A priority patent/JP5290516B2/en
Publication of WO2005010637A2 publication Critical patent/WO2005010637A2/en
Publication of WO2005010637A3 publication Critical patent/WO2005010637A3/en

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00—Accessing, addressing or allocating within memory systems or architectures
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C14/00—Digital stores characterised by arrangements of cells having volatile and non-volatile storage properties for back-up when the power is down
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/14—Handling requests for interconnection or transfer
    • G06F13/20—Handling requests for interconnection or transfer for access to input/output bus
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/14—Handling requests for interconnection or transfer
    • G06F13/20—Handling requests for interconnection or transfer for access to input/output bus
    • G06F13/28—Handling requests for interconnection or transfer for access to input/output bus using burst mode transfer, e.g. direct memory access DMA, cycle steal
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping
    • G06F9/4403—Processor initialisation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping
    • G06F9/4406—Loading of operating system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44568—Immediately runnable code
    • G06F9/44573—Execute-in-place [XIP]
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C14/00—Digital stores characterised by arrangements of cells having volatile and non-volatile storage properties for back-up when the power is down
    • G11C14/0009—Digital stores characterised by arrangements of cells having volatile and non-volatile storage properties for back-up when the power is down in which the volatile element is a DRAM cell
    • G11C14/0018—Digital stores characterised by arrangements of cells having volatile and non-volatile storage properties for back-up when the power is down in which the volatile element is a DRAM cell whereby the nonvolatile element is an EEPROM element, e.g. a floating gate or metal-nitride-oxide-silicon [MNOS] transistor

Definitions

  • FIG. 1 is a partial high level block diagram of a generic prior art embedded device 10.
  • Device 10 includes a central processing unit (CPU) 12 and three memory devices 14, 16 and 18.
  • Memory device 14 includes a nonvolatile memory such as a NOR flash memory for storing the operating system and the pre-stored applications of device 10.
  • Memory device 16 includes a nonvolatile memory, such as a NAND flash memory accessed via a NAND controller 17, for storing the user's data and downloaded applications.
  • Memory device 18 is a volatile memory such as a SDRAM for run-time execution.
  • CPU 12 communicates with memory devices 14 and 16 via a bus 20 and with memory device 18 via a bus 22.
  • the communication protocols of NOR flash memories, NAND flash memories and SDRAM are different. This is why device 10 needs NAND controller 17 and two different buses 20 and 22. If not for prior art technology described below, an implementation of device 10 that used NAND flash memory in memory device 16 would need three buses.
  • Typical signals for communicating on bus 20 with a synchronous/asynchronous external memory such as a NOR flash memory or a static random access memory (SRAM) include the following: A[0:x] - Address D[0:x] - Data CE# - Chip Select OE# - Output Enable WE# - Write Enable BUSY# - indicates the status of the memory device Reset# - Reset Signal CLK - system clock
  • Typical signals for communicating with SDRAM 18 on bus 22 include the following: CLK - System Clock CS - Chip Select CKE - Clock Enable BA[0:x] - Bank Address DMQ[0:x] - Data Input/Output A[0:x] - Row Address, Column Address DQ[0:x] - Data Input/Output RAS - Row Address Strobe CAS - Column Address Strobe WE - Write Enable
  • a NAND flash memory intrinsically requires a multiplexed interface for Address and
  • I/O [0:x] The I/O pins are used to input command, address and data, and to output data during read operations.
  • CLE - controls the activating path for commands sent to the command register.
  • ALE - controls the activating path for address to the internal address registers.
  • CS - Chip Select (or, equivalently, CE - Chip Enable) RE - serial data-out control. When active, drives the data onto the I/O bus.
  • reading is random access and fast, similar to RAM (tens of nanoseconds). Writing also is random access but is slow (a few microseconds). Erasing must be done in large chunks called "blocks" and is very slow (a few hundred milliseconds).
  • blocks In a NAND flash device, reading is serial rather than random access and is somewhat slow (typically 10 to 15 microseconds). Writing must be done in medium-size chunks called
  • NAND flash memory has become an attractive option for data storage in embedded devices such as device 10. This is because of NAND flash's smaller size, lower cost and faster write speed relative to NOR flash.
  • One of the factors that inhibits the migration from NOR flash to NAND flash in embedded devices is the non-standard interface of NAND flash.
  • M-Systems Flash Disk Pioneers, Ltd. of Kfar Saba, Israel introduced technology that enables a NAND flash memory device to use the same memory interface as a NOR flash memory device.
  • FIG. 1 is implemented in Figure 1 by NAND flash controller 17.
  • This technology is described in the DiskOnChip® Millennium Plus Data Sheet, which is available on request from M-Systems Flash Disk Pioneers, Ltd., and which is incorporated by reference for all purposes as if fully set forth herein.
  • Figure 2 is a simplified block diagram of a prior art NAND flash memory device 30, specifically M-Systems' DiskOnChip® Millennium Plus.
  • Device 30 includes a NAND flash memory 34 and a controller 32 of NAND flash memory 34, both fabricated on a common die 36.
  • the functional blocks of controller 32 include: A system interface 38 for interfacing with the rest of a host system such as device 10
  • a configuration interface 58 for configuring device 30 to operate in 8 bit vs. 16 bit mode, cascaded configuration and hardware write protection
  • a protection and security-enabling block 52 including Write/Read protection and One-
  • An error detection and error correction code block 54 for on-the-fly error handling A data pipeline 44 through which data flows from the host system to NAND flash memory 34
  • a control and status block 50 that contains registers responsible for transferring the address, data and control information between the software driver and the NAND flash memory 34
  • a flash interface 56 A bus control block 48 for translating the host system bus address, data and control signals into valid NAND flash signals
  • An address decoder 46 to enable the relevant unit inside controller 32, according to the address range received from system interface 38. More details of these functional blocks are given in the DiskOnChip® Millennium
  • NAND flash does not support execution-in-place, such as is needed to boot the host system.
  • the inclusion of boot block 40 in controller 32 gives device 30 a boot capability that would otherwise be available only in a device such as a NOR flash memory device.
  • device 30 or a similar device can provide the functionality of both memory device 14 and memory device 16 in device 10.
  • Such a device 30 could be conveniently packaged inside a common MCP package with SDRAM 18. Because of the need to use two buses 20 and 22, however, such an MCP would have to have a correspondingly large number of pins. There is thus a widely recognized need for, and it would be highly advantageous to have, a memory device including both a NAND flash memory and a SDRAM that can communicate with a host system via a single external bus.
  • a memory device including: (a) a first die on which is fabricated a first memory; and (b) a second die on which are fabricated: (i) a controller for the first memory, and (ii) at least one additional component.
  • a first memory device of the present invention includes two dies. A first memory is fabricated on the first die. A controller for the first memory, and also at least one additional component, are fabricated on the second die. Preferably, both dies are packaged together in a common package.
  • the first device includes a plurality of pins for operationally connecting the first device to a host system.
  • the term "pin” refers to any kind of lead for establishing an electrical connection between the first device of the present invention and a host system. So, for example the balls of a ball grid array are examples of “pins” as the term “pin” is used herein.
  • the first memory is a nonvolatile memory. More preferably, the first memory is a flash memory. Most preferably, the first memory is a NAND flash memory.
  • one of the additional components is a second memory. Most preferably, the second memory is a volatile memory such as a SDRAM.
  • the first device of the present invention includes (for example as part of the controller) a single interface, to a host system, that is appropriate to the SDRAM.
  • the first memory and the additional component(s) communicate with a host system using different respective pluralities of signals.
  • the first device of the present invention includes (for example as part of the controller) a single interface to the host system for communicating with the host system only using the respective signals of the additional component(s), and not the respective signals of the first memory.
  • the controller includes a XIP boot block.
  • the controller also is operative to manage one of the additional component(s).
  • the additional component managed by the controller is a second memory, and the controller provides paging and/or hardware decompression for the second memory.
  • the scope of the present invention also includes a system that includes the first memory device of the present invention, a CPU and a single bus for communication between the CPU and the first memory device of the present invention.
  • the communication via the bus are via signals that are appropriate only to the additional component(s) and not to the first memory.
  • a memory device including: (a) a first die on which is fabricated a first memory and a controller for a second memory.
  • a second memory device of the present invention includes a first die on which is fabricated a first memory and a controller for a second memory.
  • the second memory is a nonvolatile memory. More preferably, the second memory is a flash memory. Most preferably, the second memory is a NAND flash memory.
  • the first memory is a volatile memory such as a SDRAM. If the first memory is an SDRAM, then preferably the second device of the present invention includes (for example as part of the controller) a single interface, to a host system, that is appropriate to the SDRAM.
  • the second device of the present invention also includes a second die on which is fabricated the second memory. More preferably, both dies are packaged together in a common package. Most preferably, the second device includes a plurality of pins for operationally connecting the second device to a host system.
  • the two memories communicate with a host system using different respective pluralities of signals.
  • the second device of the present invention includes (for example as part of the controller) a single interface to the host system for communicating with the host system only using the respective signals of the first memory, and not the respective signals of the second memory.
  • the controller includes a XIP boot block.
  • the controller also is operative to manage the first memory, for example by providing paging and/or hardware decompression for the first memory.
  • the scope of the present invention also includes a system that includes the basic second memory device of the present invention, a CPU and a single bus for commumcating between the CPU and the second memory device of the present invention. Normally, the system also includes the second memory.
  • the communication via the bus are via signals that are appropriate only to the first memory and not to the second memory.
  • SDRAM synchronous dynamic RAM
  • DDR SDRAM DDR SDRAM
  • QDR SDRAM derivatives thereof
  • FIG. 1 is a partial high-level block diagram of a generic prior art embedded device
  • FIG. 2 is a simplified block diagram of a DiskOnChip® Millennium Plus NAND flash memory device
  • FIG. 3 is a high-level block diagram of a memory device of the present invention
  • FIG. 4 is a partial high-level block diagram of a generic embedded device of the present invention.
  • FIG. 3 is a high-level block diagram of a memory device 70 of the present invention.
  • Device 70 includes two dies 72 and 74. Fabricated on die 74 is a NAND flash memory 76. Fabricated on die 72 are a controller 78 for NAND flash memory 76 and a SDRAM 80.
  • Controller 78 is similar to prior art controller 32. There are three principal differences between controller 78 and controller 32. The first difference is that in addition to communicating with NAND flash memory 76 (via an internal bus 84), controller 78 also communicates directly with SDRAM 80, for example in a direct memory access (DMA) mode. The second difference is that controller 78 can act as a "short" that passes signals directly between the CPU 112 of a host system 110 that includes memory device 70 (see Figure 4 as described below) and SDRAM 80, with no change to the signals. The third difference is that the signals that controller 78 uses to communicate with an external host system are the signals appropriate to SDRAM 80. Some of these signals are illustrated to the left of device 70.
  • DMA direct memory access
  • controller 78 In terms of the functional blocks of controller 78, the only functional block of controller 78 that differs substantially from the corresponding functional block of controller 32 is the system interface block. Unlike system interface block 38 of controller 32, which supports communication according to a protocol appropriate to a synchronous/asynchronous memory such as a NOR flash memory, system interface block 82 of controller 78 supports conimunication according to a protocol appropriate to SDRAM 80. Therefore, the only functional block of controller 78 that is illustrated in Figure 3 is system interface block 82. It will be clear to those skilled in the art what additional functionality is required in controller 78 to support direct access such as DMA to SDRAM 80. Therefore, this direct access support functionality is not detailed herein. Dies 72 and 74 are packaged together in a common package 86, so that device 70 is a
  • FIG. 1 illustrates a basic memory device 70 of the present invention.
  • a more sophisticated memory device 70 of the present invention includes optional features that take advantage of the presence of NAND flash memory 76 and SDRAM 80 in the same device, for example a decompression engine in controller 78 for compressing data to be stored in NAND flash memory 76 and decompressing that data when that data is loaded from NAND flash memory 76 to SDRAM 80.
  • FIG. 4 is a partial high level block diagram of a generic embedded device 110 of the present invention.
  • CPU 112 of device 110 is similar to CPU 12 of device 10.
  • the principal difference between device 10 and device 110 is that in device 110 the functionality of memory devices 14, 16 and 18 is combined into memory device 70 of the present invention.
  • NAND flash memory 76 is used for storing the operating system and the pre- stored applications of device 110 and also for storing the user's data and downloaded applications; and SDRAM 80 is used for run-time execution. Consequently, device 110 needs only one bus 116 for communicating with its single memory device 70, using only signals appropriate for SDRAM 70.
  • the present invention offers the following advantages over the prior art: 1.
  • SDRAM 80 is large enough both to hold a shadowed image of the operating system of device 110 and also to provide the memory space required for run time execution, then, because controller 78 includes a boot block and a download engine similar to boot block 40 and download engine 42 of controller 32, device 70 is a chipset that can boot directly from SDRAM 80. Because execution from a SDRAM is substantially faster than execution from a NOR flash memory, device 110, if so configured, operates significantly faster than device 10. 2. Because device 110 does not need bus 20 to support communication with a NOR flash memory device, CPU chipset vendors are free to eliminate NOR/SRAM signals and the associated pins from their chips. This results in reduced die size, reduced cost of the chipsets and physically smaller package sizes. 3.
  • the transfer of data from NAND flash memory 76 to SDRAM 80 is a fast, direct transfer at low power and without loading an external bus, unlike the transfer of data from NAND flash memory device 16 to SDRAM memory device 18 via external buses 20 and 22. 4.
  • memory management functionality such as paging and hardware decompression, for managing SDRAM 80 may be included in controller 78. In device 10, bus 22 and CPU 12 would have to participate in such functionality. While the invention has been described with respect to a limited number of embodiments, it will be appreciated that many variations, modifications and other applications of the invention may be made.

Abstract

A memory device (86) includes two dies. A first memory (76) is fabricated on one die (74). A controller (78) of the first memory (76) is fabricated on the other die (72) Also fabricated on the other die (72) is another component, such as a second memory (80), that communicates with a host system using a plurality of signals different from the signals used by the first memory. The device includes a single interface for communicating with the host system using only the respective signals of the second component. In a most preferred embodiment, the first memory (76) is a NAND flash memory and the second memory (80) is a SDRAM.

Description

SDRAM MEMORY DEVICE WITH AN EMBEDDED NAND FLASH CONTROLLER
FIELD AND BACKGROUND OF THE INVENTION The present invention relates to memory devices and, more particularly, to a MCP (multi-chip package) memory device with a NAND flash memory on one die and a SDRAM (synchronous dynamic random access memory) together with a controller for the NAND flash memory on another die. Figure 1 is a partial high level block diagram of a generic prior art embedded device 10. Device 10 includes a central processing unit (CPU) 12 and three memory devices 14, 16 and 18. Memory device 14 includes a nonvolatile memory such as a NOR flash memory for storing the operating system and the pre-stored applications of device 10. Memory device 16 includes a nonvolatile memory, such as a NAND flash memory accessed via a NAND controller 17, for storing the user's data and downloaded applications. Memory device 18 is a volatile memory such as a SDRAM for run-time execution. CPU 12 communicates with memory devices 14 and 16 via a bus 20 and with memory device 18 via a bus 22. The communication protocols of NOR flash memories, NAND flash memories and SDRAM are different. This is why device 10 needs NAND controller 17 and two different buses 20 and 22. If not for prior art technology described below, an implementation of device 10 that used NAND flash memory in memory device 16 would need three buses. Typical signals for communicating on bus 20 with a synchronous/asynchronous external memory such as a NOR flash memory or a static random access memory (SRAM) include the following: A[0:x] - Address D[0:x] - Data CE# - Chip Select OE# - Output Enable WE# - Write Enable BUSY# - indicates the status of the memory device Reset# - Reset Signal CLK - system clock Typical signals for communicating with SDRAM 18 on bus 22 include the following: CLK - System Clock CS - Chip Select CKE - Clock Enable BA[0:x] - Bank Address DMQ[0:x] - Data Input/Output A[0:x] - Row Address, Column Address DQ[0:x] - Data Input/Output RAS - Row Address Strobe CAS - Column Address Strobe WE - Write Enable A NAND flash memory intrinsically requires a multiplexed interface for Address and
Data and control signals which are not included in the signals defined for buses 20 and 22. If a NAND flash memory device were to have its own bus, the associated signals would include: I/O [0:x] - The I/O pins are used to input command, address and data, and to output data during read operations. CLE - controls the activating path for commands sent to the command register. ALE - controls the activating path for address to the internal address registers. CS - Chip Select (or, equivalently, CE - Chip Enable) RE - serial data-out control. When active, drives the data onto the I/O bus. WE - controls writes to the I/O port RJB - indicates device status In a NOR flash device, reading is random access and fast, similar to RAM (tens of nanoseconds). Writing also is random access but is slow (a few microseconds). Erasing must be done in large chunks called "blocks" and is very slow (a few hundred milliseconds). In a NAND flash device, reading is serial rather than random access and is somewhat slow (typically 10 to 15 microseconds). Writing must be done in medium-size chunks called
"pages" and is slow (a few hundred microseconds). As in the case of a NOR flash device, erasing must be done in blocks, but is much faster (a few milliseconds) than in a NOR flash device. Recently, NAND flash memory has become an attractive option for data storage in embedded devices such as device 10. This is because of NAND flash's smaller size, lower cost and faster write speed relative to NOR flash. One of the factors that inhibits the migration from NOR flash to NAND flash in embedded devices is the non-standard interface of NAND flash. To overcome this and other limitations of NAND flash, M-Systems Flash Disk Pioneers, Ltd. of Kfar Saba, Israel introduced technology that enables a NAND flash memory device to use the same memory interface as a NOR flash memory device. This technology is implemented in Figure 1 by NAND flash controller 17. This technology is described in the DiskOnChip® Millennium Plus Data Sheet, which is available on request from M-Systems Flash Disk Pioneers, Ltd., and which is incorporated by reference for all purposes as if fully set forth herein. Figure 2 is a simplified block diagram of a prior art NAND flash memory device 30, specifically M-Systems' DiskOnChip® Millennium Plus. Device 30 includes a NAND flash memory 34 and a controller 32 of NAND flash memory 34, both fabricated on a common die 36. The functional blocks of controller 32 include: A system interface 38 for interfacing with the rest of a host system such as device 10 A configuration interface 58 for configuring device 30 to operate in 8 bit vs. 16 bit mode, cascaded configuration and hardware write protection A protection and security-enabling block 52 including Write/Read protection and One-
Time Programming (OTP), for advanced data/code security and protection A programmable boot block 40 with execute-in-place (XIP) capability, enhanced with a download engine 42, for host system initialization capability An error detection and error correction code block 54 for on-the-fly error handling A data pipeline 44 through which data flows from the host system to NAND flash memory 34 A control and status block 50 that contains registers responsible for transferring the address, data and control information between the software driver and the NAND flash memory 34 A flash interface 56 A bus control block 48 for translating the host system bus address, data and control signals into valid NAND flash signals An address decoder 46 to enable the relevant unit inside controller 32, according to the address range received from system interface 38. More details of these functional blocks are given in the DiskOnChip® Millennium
Plus Data Sheet. To the left of device 30 in Figure 2 are shown some of the signals that device 30 exchanges with the host system. Unlike NOR flash, in which reading is random access, NAND flash does not support execution-in-place, such as is needed to boot the host system. The inclusion of boot block 40 in controller 32 gives device 30 a boot capability that would otherwise be available only in a device such as a NOR flash memory device. Hence, device 30 or a similar device can provide the functionality of both memory device 14 and memory device 16 in device 10. Such a device 30 could be conveniently packaged inside a common MCP package with SDRAM 18. Because of the need to use two buses 20 and 22, however, such an MCP would have to have a correspondingly large number of pins. There is thus a widely recognized need for, and it would be highly advantageous to have, a memory device including both a NAND flash memory and a SDRAM that can communicate with a host system via a single external bus.
SUMMARY OF THE INVENTION According to the present invention there is provided a memory device including: (a) a first die on which is fabricated a first memory; and (b) a second die on which are fabricated: (i) a controller for the first memory, and (ii) at least one additional component. In its most basic form, a first memory device of the present invention includes two dies. A first memory is fabricated on the first die. A controller for the first memory, and also at least one additional component, are fabricated on the second die. Preferably, both dies are packaged together in a common package. Most preferably, the first device includes a plurality of pins for operationally connecting the first device to a host system. As understood herein, the term "pin" refers to any kind of lead for establishing an electrical connection between the first device of the present invention and a host system. So, for example the balls of a ball grid array are examples of "pins" as the term "pin" is used herein. Preferably, the first memory is a nonvolatile memory. More preferably, the first memory is a flash memory. Most preferably, the first memory is a NAND flash memory. Preferably, one of the additional components is a second memory. Most preferably, the second memory is a volatile memory such as a SDRAM. If the second memory is a SDRAM, then preferably the first device of the present invention includes (for example as part of the controller) a single interface, to a host system, that is appropriate to the SDRAM. Preferably, the first memory and the additional component(s) communicate with a host system using different respective pluralities of signals. Most preferably, the first device of the present invention includes (for example as part of the controller) a single interface to the host system for communicating with the host system only using the respective signals of the additional component(s), and not the respective signals of the first memory. Preferably, the controller includes a XIP boot block. Preferably, the controller also is operative to manage one of the additional component(s). Most preferably, the additional component managed by the controller is a second memory, and the controller provides paging and/or hardware decompression for the second memory. The scope of the present invention also includes a system that includes the first memory device of the present invention, a CPU and a single bus for communication between the CPU and the first memory device of the present invention. Preferably, the communication via the bus are via signals that are appropriate only to the additional component(s) and not to the first memory. Also according to the present invention, there is provided a memory device including: (a) a first die on which is fabricated a first memory and a controller for a second memory. In its most basic form, a second memory device of the present invention includes a first die on which is fabricated a first memory and a controller for a second memory. Preferably, the second memory is a nonvolatile memory. More preferably, the second memory is a flash memory. Most preferably, the second memory is a NAND flash memory. Preferably, the first memory is a volatile memory such as a SDRAM. If the first memory is an SDRAM, then preferably the second device of the present invention includes (for example as part of the controller) a single interface, to a host system, that is appropriate to the SDRAM. Preferably, the second device of the present invention also includes a second die on which is fabricated the second memory. More preferably, both dies are packaged together in a common package. Most preferably, the second device includes a plurality of pins for operationally connecting the second device to a host system. Preferably, the two memories communicate with a host system using different respective pluralities of signals. Most preferably, the second device of the present invention includes (for example as part of the controller) a single interface to the host system for communicating with the host system only using the respective signals of the first memory, and not the respective signals of the second memory. Preferably, the controller includes a XIP boot block. Preferably, the controller also is operative to manage the first memory, for example by providing paging and/or hardware decompression for the first memory. The scope of the present invention also includes a system that includes the basic second memory device of the present invention, a CPU and a single bus for commumcating between the CPU and the second memory device of the present invention. Normally, the system also includes the second memory. Preferably, the communication via the bus are via signals that are appropriate only to the first memory and not to the second memory.
DEFINITIONS The scope of the term "SDRAM" as used herein includes any type of synchronous dynamic RAM, including but not limited to DDR SDRAM, QDR SDRAM and derivatives thereof.
BRIEF DESCRIPTION OF THE DRAWINGS The invention is herein described, by way of example only, with reference to the accompanying drawings, wherein: FIG. 1 is a partial high-level block diagram of a generic prior art embedded device; FIG. 2 is a simplified block diagram of a DiskOnChip® Millennium Plus NAND flash memory device; FIG. 3 is a high-level block diagram of a memory device of the present invention; FIG. 4 is a partial high-level block diagram of a generic embedded device of the present invention.
DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention is of a memory device that includes two kinds of memories but communicates with a host device or system using the protocol and signals of only one of the memories. The present invention thereby enables the host device or system to include only one bus for communicating with the two memories. The principles and operation of a memory device according to the present invention may be better understood with reference to the drawings and the accompanying description. Returning now to the drawings, Figure 3 is a high-level block diagram of a memory device 70 of the present invention. Device 70 includes two dies 72 and 74. Fabricated on die 74 is a NAND flash memory 76. Fabricated on die 72 are a controller 78 for NAND flash memory 76 and a SDRAM 80. Controller 78 is similar to prior art controller 32. There are three principal differences between controller 78 and controller 32. The first difference is that in addition to communicating with NAND flash memory 76 (via an internal bus 84), controller 78 also communicates directly with SDRAM 80, for example in a direct memory access (DMA) mode. The second difference is that controller 78 can act as a "short" that passes signals directly between the CPU 112 of a host system 110 that includes memory device 70 (see Figure 4 as described below) and SDRAM 80, with no change to the signals. The third difference is that the signals that controller 78 uses to communicate with an external host system are the signals appropriate to SDRAM 80. Some of these signals are illustrated to the left of device 70. In terms of the functional blocks of controller 78, the only functional block of controller 78 that differs substantially from the corresponding functional block of controller 32 is the system interface block. Unlike system interface block 38 of controller 32, which supports communication according to a protocol appropriate to a synchronous/asynchronous memory such as a NOR flash memory, system interface block 82 of controller 78 supports conimunication according to a protocol appropriate to SDRAM 80. Therefore, the only functional block of controller 78 that is illustrated in Figure 3 is system interface block 82. It will be clear to those skilled in the art what additional functionality is required in controller 78 to support direct access such as DMA to SDRAM 80. Therefore, this direct access support functionality is not detailed herein. Dies 72 and 74 are packaged together in a common package 86, so that device 70 is a
MCP device. Protruding from package 86 is a plurality of pins 88. Device 70 typically includes significantly fewer pins than the number of pins that device 70 would need to support two separate communication protocols for NAND flash memory 76 and SDRAM 80. For illustrational simplicity, only four pins 88 are shown in Figure 3. Figure 3 illustrates a basic memory device 70 of the present invention. A more sophisticated memory device 70 of the present invention includes optional features that take advantage of the presence of NAND flash memory 76 and SDRAM 80 in the same device, for example a decompression engine in controller 78 for compressing data to be stored in NAND flash memory 76 and decompressing that data when that data is loaded from NAND flash memory 76 to SDRAM 80. Figure 4 is a partial high level block diagram of a generic embedded device 110 of the present invention. CPU 112 of device 110 is similar to CPU 12 of device 10. The principal difference between device 10 and device 110 is that in device 110 the functionality of memory devices 14, 16 and 18 is combined into memory device 70 of the present invention. Specifically, NAND flash memory 76 is used for storing the operating system and the pre- stored applications of device 110 and also for storing the user's data and downloaded applications; and SDRAM 80 is used for run-time execution. Consequently, device 110 needs only one bus 116 for communicating with its single memory device 70, using only signals appropriate for SDRAM 70. In addition to the reduced number of buses in device 110 vs. device 10, the present invention offers the following advantages over the prior art: 1. If (as is preferable) SDRAM 80 is large enough both to hold a shadowed image of the operating system of device 110 and also to provide the memory space required for run time execution, then, because controller 78 includes a boot block and a download engine similar to boot block 40 and download engine 42 of controller 32, device 70 is a chipset that can boot directly from SDRAM 80. Because execution from a SDRAM is substantially faster than execution from a NOR flash memory, device 110, if so configured, operates significantly faster than device 10. 2. Because device 110 does not need bus 20 to support communication with a NOR flash memory device, CPU chipset vendors are free to eliminate NOR/SRAM signals and the associated pins from their chips. This results in reduced die size, reduced cost of the chipsets and physically smaller package sizes. 3. The transfer of data from NAND flash memory 76 to SDRAM 80 is a fast, direct transfer at low power and without loading an external bus, unlike the transfer of data from NAND flash memory device 16 to SDRAM memory device 18 via external buses 20 and 22. 4. Optionally, memory management functionality, such as paging and hardware decompression, for managing SDRAM 80 may be included in controller 78. In device 10, bus 22 and CPU 12 would have to participate in such functionality. While the invention has been described with respect to a limited number of embodiments, it will be appreciated that many variations, modifications and other applications of the invention may be made.

Claims

WHAT IS CLAIMED IS:
1. A memory device comprising: (a) a first die on which is fabricated a first memory; and (b) a second die on which are fabricated: (i) a controller for said first memory, and (ii) at least one additional component.
2. The memory device of claim 1, wherein said first and second dies are packaged in a common package.
3. The memory device of claim 2, further comprising: (c) a plurality of pins for operationally connecting said first and second dies to a host system.
4. The memory device of claim 1, wherein said first memory is a nonvolatile memory.
5. The memory device of claim 4, wherein said nonvolatile memory is a flash memory.
6. The memory device of claim 5, wherein said flash memory is a NAND flash memory.
7. The memory device of claim 1, wherein said at least one additional component includes a second memory.
8. The memory device of claim 7, wherein said second memory is a volatile memory.
9. The memory device of claim 8, wherein said volatile memory is a SDRAM.
10. The memory device of claim 9, wherein said controller includes an interface, to a host system, appropriate to said SDRAM.
11. The memory device of claim 9, further comprising: (c) a single interface to a host system, said interface being appropriate to said SDRAM.
12. The memory device of claim 1, wherein said first memory and said at least one additional component communicate with a host system using different respective pluralities of signals.
13. The memory device of claim 12, wherein said controller includes an interface for communicating with said host system only using said respective signals of said at least one additional component.
14. The memory device of claim 12, further comprising: (c) a single interface for communicating with said host system only using said respective signals of said at least one additional component.
15. The memory device of claim 1, wherein said controller includes a XIP boot block.
16. The memory device of claim 1, wherein said controller is operative to also manage one of said at least one additional component.
17. The memory device of claim 1 , wherein said one of said at least one additional component is a second memory, and wherein said controller provides paging for said second memory.
18. The memory device of claim 1, wherein said one of said at least one additional component is a second memory, and wherein said controller provides hardware decompression for said second memory.
19. A system comprising: (a) the memory device of claim 1 ; (b) a CPU; and (c) a single bus for communication between said CPU and said memory device.
20. The system of claim 19, wherein said communication is via signals appropriate only to at least one of said at least one additional component.
21. A memory device comprising: (a) a first die on which is fabricated a first memory and a controller for a second memory.
22. The memory device of claim 21, wherein said second memory is a nonvolatile memory.
23. The memory device of claim 22, wherein said nonvolatile memory is a flash memory.
24. The memory device of claim 23, wherein said flash memory is a NAND flash memory.
25. The memory device of claim 21, wherein said first memory is a volatile memory.
26. The memory device of claim 25, wherein said volatile memory is a SDRAM.
27. The memory device of claim 26, wherein said controller includes an interface, to a host system, appropriate to said SDRAM.
28. The memory device of claim 26, further comprising: (b) a single interface to a host system, said interface being appropriate to said SDRAM.
29. The memory device of claim 21 , further comprising: (b) a second die on which is fabricated said second memory.
30. The memory device of claim 29, wherein said first and second dies are packaged in a common package.
31. The memory device of claim 30, further comprising: (c) a plurality of pins for operationally connecting said first and second dies to a host system.
32. The memory device of claim 29, wherein said first and second memories communicate with a host system using different respective pluralities of signals.
33. The memory device of claim 32, wherein said controller includes an interface for communicating with said host system only using said respective signals of said first memory.
34. The memory device of claim 33, further comprising: (c) a single interface for communicating with said host system only using said respective signals of said first memory.
35. The memory device of claim 21, wherein said controller includes a XIP boot block.
36. The memory device of claim 21, wherein said controller is operative to also manage said first memory.
37. The memory device of claim 21, wherein said controller provides paging for said first memory.
38. The memory device of claim 21, wherein said controller provides decompression for said first memory.
39. A system comprising: (a) the memory device of claim 21 ; (b) a CPU; and (c) a single bus for communication between said CPU and said memory device.
40. The system of claim 39, wherein said communication is via signals appropriate only to said first memory.
41. The system of claim 39, further comprising: (d) said second memory.
PCT/IL2004/000399 2003-07-31 2004-05-12 Sdram memory device with an embedded nand flash controller WO2005010637A2 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP04732398A EP1649378A4 (en) 2003-07-31 2004-05-12 Sdram memory device with an embedded nand flash controller
JP2006521766A JP5290516B2 (en) 2003-07-31 2004-05-12 Memory device, system having memory device, and method of operating embedded device

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US49221703P 2003-07-31 2003-07-31
US60/492,217 2003-07-31
US10/704,613 US7752380B2 (en) 2003-07-31 2003-11-12 SDRAM memory device with an embedded NAND flash controller
US10/704,613 2003-11-12

Publications (2)

Publication Number Publication Date
WO2005010637A2 true WO2005010637A2 (en) 2005-02-03
WO2005010637A3 WO2005010637A3 (en) 2005-06-30

Family

ID=34108105

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IL2004/000399 WO2005010637A2 (en) 2003-07-31 2004-05-12 Sdram memory device with an embedded nand flash controller

Country Status (5)

Country Link
US (1) US7752380B2 (en)
EP (1) EP1649378A4 (en)
JP (2) JP5290516B2 (en)
KR (1) KR100867900B1 (en)
WO (1) WO2005010637A2 (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007183962A (en) * 2005-12-28 2007-07-19 Silicon Storage Technology Inc Integrated memory and controller
JP2007183961A (en) * 2005-12-28 2007-07-19 Silicon Storage Technology Inc Hard disk drive cache memory and playback device
JP2009506390A (en) * 2005-03-24 2009-02-12 サンディスク アイエル リミテッド Loading internal applications on a smart card
JP2012027929A (en) * 2011-08-31 2012-02-09 Sandisk Il Ltd Loading of internal application on smart card
WO2012106806A1 (en) * 2011-02-08 2012-08-16 Diablo Technologies Inc. System and method of interfacing co-processors and input/output devices via a main memory system
US9429623B2 (en) 2010-05-28 2016-08-30 Advantest Corporation Solution for full speed, parallel DUT testing

Families Citing this family (91)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7800932B2 (en) * 2005-09-28 2010-09-21 Sandisk 3D Llc Memory cell comprising switchable semiconductor memory element with trimmable resistance
KR20050022798A (en) * 2003-08-30 2005-03-08 주식회사 이즈텍 A system for analyzing bio chips using gene ontology, and a method thereof
US7424659B2 (en) * 2003-10-31 2008-09-09 Sandisk Il Ltd. System-in-package and method of testing thereof
KR100598097B1 (en) * 2003-12-29 2006-07-07 삼성전자주식회사 Dual chip package
TWI279718B (en) * 2004-07-01 2007-04-21 Winity Technology Inc Architecture and method of a cellular phone embedded system
US20060143371A1 (en) * 2004-12-28 2006-06-29 Rudelic John C Integrated memory management apparatus, systems, and methods
WO2006085324A2 (en) * 2005-02-11 2006-08-17 Sandisk Il Ltd. Nand flash memory system architecture
US7590796B2 (en) * 2006-07-31 2009-09-15 Metaram, Inc. System and method for power management in memory systems
US9171585B2 (en) 2005-06-24 2015-10-27 Google Inc. Configurable memory circuit system and method
US8060774B2 (en) 2005-06-24 2011-11-15 Google Inc. Memory systems and memory modules
US8327104B2 (en) 2006-07-31 2012-12-04 Google Inc. Adjusting the timing of signals associated with a memory system
US8055833B2 (en) 2006-10-05 2011-11-08 Google Inc. System and method for increasing capacity, performance, and flexibility of flash storage
US8111566B1 (en) 2007-11-16 2012-02-07 Google, Inc. Optimal channel design for memory devices for providing a high-speed memory interface
US8397013B1 (en) 2006-10-05 2013-03-12 Google Inc. Hybrid memory module
US9507739B2 (en) 2005-06-24 2016-11-29 Google Inc. Configurable memory circuit system and method
US20080082763A1 (en) 2006-10-02 2008-04-03 Metaram, Inc. Apparatus and method for power management of memory circuits by a system or component thereof
US20060294295A1 (en) * 2005-06-24 2006-12-28 Yukio Fukuzo DRAM chip device well-communicated with flash memory chip and multi-chip package comprising such a device
US9542352B2 (en) * 2006-02-09 2017-01-10 Google Inc. System and method for reducing command scheduling constraints of memory circuits
US8359187B2 (en) 2005-06-24 2013-01-22 Google Inc. Simulating a different number of memory circuit devices
US8089795B2 (en) 2006-02-09 2012-01-03 Google Inc. Memory module with memory stack and interface with enhanced capabilities
US8438328B2 (en) 2008-02-21 2013-05-07 Google Inc. Emulation of abstracted DIMMs using abstracted DRAMs
US8244971B2 (en) 2006-07-31 2012-08-14 Google Inc. Memory circuit system and method
US8796830B1 (en) 2006-09-01 2014-08-05 Google Inc. Stackable low-profile lead frame package
US7386656B2 (en) * 2006-07-31 2008-06-10 Metaram, Inc. Interface circuit system and method for performing power management operations in conjunction with only a portion of a memory circuit
US8090897B2 (en) 2006-07-31 2012-01-03 Google Inc. System and method for simulating an aspect of a memory circuit
US20080028136A1 (en) * 2006-07-31 2008-01-31 Schakel Keith R Method and apparatus for refresh management of memory modules
US8081474B1 (en) 2007-12-18 2011-12-20 Google Inc. Embossed heat spreader
US8077535B2 (en) 2006-07-31 2011-12-13 Google Inc. Memory refresh apparatus and method
US7609567B2 (en) * 2005-06-24 2009-10-27 Metaram, Inc. System and method for simulating an aspect of a memory circuit
US7392338B2 (en) 2006-07-31 2008-06-24 Metaram, Inc. Interface circuit system and method for autonomously performing power management operations in conjunction with a plurality of memory circuits
US8041881B2 (en) * 2006-07-31 2011-10-18 Google Inc. Memory device with emulated characteristics
US8335894B1 (en) 2008-07-25 2012-12-18 Google Inc. Configurable memory system with interface circuit
US8130560B1 (en) 2006-11-13 2012-03-06 Google Inc. Multi-rank partial width memory modules
US8386722B1 (en) 2008-06-23 2013-02-26 Google Inc. Stacked DIMM memory interface
US10013371B2 (en) 2005-06-24 2018-07-03 Google Llc Configurable memory circuit system and method
US7509594B2 (en) * 2005-07-06 2009-03-24 Sandisk Il Ltd. Method of selling integrated circuit dies for multi-chip packages
US7317630B2 (en) * 2005-07-15 2008-01-08 Atmel Corporation Nonvolatile semiconductor memory apparatus
KR20080025761A (en) * 2005-07-29 2008-03-21 더 제너럴 하스피탈 코포레이션 Methods and compositions for reducing skin damage
DE112006002300B4 (en) 2005-09-02 2013-12-19 Google, Inc. Device for stacking DRAMs
US7490177B2 (en) * 2006-01-23 2009-02-10 Infineon Technologies Ag System method for performing a direct memory access for automatically copying initialization boot code in a new memory architecture
US7451263B2 (en) * 2006-02-08 2008-11-11 Infineon Technologies Ag Shared interface for components in an embedded system
US9632929B2 (en) 2006-02-09 2017-04-25 Google Inc. Translating an address associated with a command communicated between a system and memory circuits
US20070245061A1 (en) * 2006-04-13 2007-10-18 Intel Corporation Multiplexing a parallel bus interface and a flash memory interface
US8000134B2 (en) * 2006-05-15 2011-08-16 Apple Inc. Off-die charge pump that supplies multiple flash devices
US7852690B2 (en) * 2006-05-15 2010-12-14 Apple Inc. Multi-chip package for a flash memory
US7568135B2 (en) * 2006-05-15 2009-07-28 Apple Inc. Use of alternative value in cell detection
US7701797B2 (en) * 2006-05-15 2010-04-20 Apple Inc. Two levels of voltage regulation supplied for logic and data programming voltage of a memory device
US7551486B2 (en) * 2006-05-15 2009-06-23 Apple Inc. Iterative memory cell charging based on reference cell value
US7911834B2 (en) * 2006-05-15 2011-03-22 Apple Inc. Analog interface for a flash memory die
US7511646B2 (en) * 2006-05-15 2009-03-31 Apple Inc. Use of 8-bit or higher A/D for NAND cell value
US7613043B2 (en) * 2006-05-15 2009-11-03 Apple Inc. Shifting reference values to account for voltage sag
US7639542B2 (en) * 2006-05-15 2009-12-29 Apple Inc. Maintenance operations for multi-level data storage cells
US7639531B2 (en) * 2006-05-15 2009-12-29 Apple Inc. Dynamic cell bit resolution
US7716411B2 (en) * 2006-06-07 2010-05-11 Microsoft Corporation Hybrid memory device with single interface
US20080010419A1 (en) * 2006-07-06 2008-01-10 Rom-Shen Kao System and Method for Issuing Commands
US7441070B2 (en) * 2006-07-06 2008-10-21 Qimonda North America Corp. Method for accessing a non-volatile memory via a volatile memory interface
US20080007569A1 (en) * 2006-07-06 2008-01-10 Rom-Shen Kao Control protocol and signaling in a new memory architecture
US20080010420A1 (en) * 2006-07-06 2008-01-10 Rom-Shen Kao Method for Accessing Control Registers via a Memory Device
US7450414B2 (en) * 2006-07-31 2008-11-11 Sandisk 3D Llc Method for using a mixed-use memory array
US7724589B2 (en) * 2006-07-31 2010-05-25 Google Inc. System and method for delaying a signal communicated from a system to at least one of a plurality of memory circuits
US20080023790A1 (en) * 2006-07-31 2008-01-31 Scheuerlein Roy E Mixed-use memory array
US7486537B2 (en) * 2006-07-31 2009-02-03 Sandisk 3D Llc Method for using a mixed-use memory array with different data states
US7827346B2 (en) * 2006-08-14 2010-11-02 Plankton Technologies, Llc Data storage device
US7730268B2 (en) * 2006-08-18 2010-06-01 Cypress Semiconductor Corporation Multiprocessor system having an input/output (I/O) bridge circuit for transferring data between volatile and non-volatile memory
US8209479B2 (en) 2007-07-18 2012-06-26 Google Inc. Memory circuit system and method
US8080874B1 (en) 2007-09-14 2011-12-20 Google Inc. Providing additional space between an integrated circuit and a circuit board for positioning a component therebetween
US8667224B1 (en) * 2007-12-20 2014-03-04 Emc Corporation Techniques for data prefetching
US8082384B2 (en) 2008-03-26 2011-12-20 Microsoft Corporation Booting an electronic device using flash memory and a limited function memory controller
US20090254705A1 (en) * 2008-04-07 2009-10-08 International Business Machines Corporation Bus attached compressed random access memory
WO2010002943A1 (en) * 2008-07-01 2010-01-07 Lsi Corporation Methods and apparatus for interfacing between a flash memory controller and a flash memory array
US8250285B2 (en) * 2008-09-10 2012-08-21 Infinte Mormories Ltd. Non-volatile dual memory die for data storage devices
US8090692B2 (en) * 2008-09-10 2012-01-03 Infinite Memory Ltd Method for using an OTP storage device
WO2010144624A1 (en) 2009-06-09 2010-12-16 Google Inc. Programming of dimm termination resistance values
US9342445B2 (en) 2009-07-23 2016-05-17 Hgst Technologies Santa Ana, Inc. System and method for performing a direct memory access at a predetermined address in a flash storage
US9164679B2 (en) 2011-04-06 2015-10-20 Patents1, Llc System, method and computer program product for multi-thread operation involving first memory of a first memory class and second memory of a second memory class
US9170744B1 (en) 2011-04-06 2015-10-27 P4tents1, LLC Computer program product for controlling a flash/DRAM/embedded DRAM-equipped system
US8930647B1 (en) 2011-04-06 2015-01-06 P4tents1, LLC Multiple class memory systems
US9176671B1 (en) 2011-04-06 2015-11-03 P4tents1, LLC Fetching data between thread execution in a flash/DRAM/embedded DRAM-equipped system
US9158546B1 (en) 2011-04-06 2015-10-13 P4tents1, LLC Computer program product for fetching from a first physical memory between an execution of a plurality of threads associated with a second physical memory
US9417754B2 (en) 2011-08-05 2016-08-16 P4tents1, LLC User interface system, method, and computer program product
JP5801158B2 (en) * 2011-10-21 2015-10-28 ラピスセミコンダクタ株式会社 RAM storage device
KR20140027859A (en) 2012-08-27 2014-03-07 삼성전자주식회사 Host device and system including the same
US8812744B1 (en) 2013-03-14 2014-08-19 Microsoft Corporation Assigning priorities to data for hybrid drives
US9626126B2 (en) 2013-04-24 2017-04-18 Microsoft Technology Licensing, Llc Power saving mode hybrid drive access management
US9946495B2 (en) 2013-04-25 2018-04-17 Microsoft Technology Licensing, Llc Dirty data management for hybrid drives
US20150347151A1 (en) * 2014-05-28 2015-12-03 Diablo Technologies Inc. System and method for booting from a non-volatile memory
US10691838B2 (en) * 2014-06-20 2020-06-23 Cypress Semiconductor Corporation Encryption for XIP and MMIO external memories
CN104850516B (en) * 2015-05-25 2017-09-26 福州瑞芯微电子股份有限公司 A kind of DDR Frequency Conversion Designs method and apparatus
US10331586B2 (en) 2015-10-30 2019-06-25 Samsung Electronics Co., Ltd. Nonvolatile memory device for providing fast booting and system including the same
US10732866B2 (en) * 2016-10-27 2020-08-04 Samsung Electronics Co., Ltd. Scaling out architecture for DRAM-based processing unit (DPU)
US10845866B2 (en) * 2017-06-22 2020-11-24 Micron Technology, Inc. Non-volatile memory system or sub-system

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH05299616A (en) * 1992-04-16 1993-11-12 Hitachi Ltd Semiconductor storage device
JPH08129509A (en) * 1994-11-01 1996-05-21 Canon Inc Unit and method for memory control
KR960039006A (en) * 1995-04-26 1996-11-21 김광호 Nonvolatile semiconductor memory device connectable to DRAM bus
US6145069A (en) * 1999-01-29 2000-11-07 Interactive Silicon, Inc. Parallel decompression and compression system and method for improving storage density and access speed for non-volatile memory and embedded memory devices
GB9903490D0 (en) * 1999-02-17 1999-04-07 Memory Corp Plc Memory system
US6526462B1 (en) * 1999-11-19 2003-02-25 Hammam Elabd Programmable multi-tasking memory management system
JP4616960B2 (en) * 2000-03-28 2011-01-19 インターナショナル・ビジネス・マシーンズ・コーポレーション Semiconductor device having external ROM terminal
JP2002251884A (en) 2001-02-21 2002-09-06 Toshiba Corp Semiconductor memory and system device therefor
JP2002312232A (en) * 2001-04-10 2002-10-25 Mitsubishi Electric Corp Semiconductor memory device
US20020188337A1 (en) * 2001-04-17 2002-12-12 Bischoff Thomas C. Apparatus for transferring traction forces exerted on an implantable medical lead
JP4049297B2 (en) 2001-06-11 2008-02-20 株式会社ルネサステクノロジ Semiconductor memory device
TWI240864B (en) * 2001-06-13 2005-10-01 Hitachi Ltd Memory device
JP4059002B2 (en) * 2001-06-13 2008-03-12 株式会社日立製作所 Memory device
JP3816788B2 (en) * 2001-11-22 2006-08-30 株式会社東芝 Nonvolatile semiconductor memory device
DE60210416T2 (en) 2002-02-28 2006-09-07 Matsushita Electric Industrial Co., Ltd., Kadoma memory card
US7234052B2 (en) * 2002-03-08 2007-06-19 Samsung Electronics Co., Ltd System boot using NAND flash memory and method thereof
US20030206442A1 (en) * 2002-05-02 2003-11-06 Jerry Tang Flash memory bridiging device, method and application system
JP4499982B2 (en) * 2002-09-11 2010-07-14 株式会社日立製作所 Memory system
US7110934B2 (en) * 2002-10-29 2006-09-19 Arm Limited. Analysis of the performance of a portion of a data processing system
US20040179016A1 (en) * 2003-03-11 2004-09-16 Chris Kiser DRAM controller with fast page mode optimization
TW591389B (en) * 2003-03-20 2004-06-11 Icp Electronics Inc Execute-in-place system and method of serial memory

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of EP1649378A4 *

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2009506390A (en) * 2005-03-24 2009-02-12 サンディスク アイエル リミテッド Loading internal applications on a smart card
JP2007183962A (en) * 2005-12-28 2007-07-19 Silicon Storage Technology Inc Integrated memory and controller
JP2007183961A (en) * 2005-12-28 2007-07-19 Silicon Storage Technology Inc Hard disk drive cache memory and playback device
US9429623B2 (en) 2010-05-28 2016-08-30 Advantest Corporation Solution for full speed, parallel DUT testing
WO2012106806A1 (en) * 2011-02-08 2012-08-16 Diablo Technologies Inc. System and method of interfacing co-processors and input/output devices via a main memory system
US10168954B2 (en) 2011-02-08 2019-01-01 Rambus Inc. System and method of interfacing co-processors and input/output devices via a main memory system
US10725704B2 (en) 2011-02-08 2020-07-28 Rambus Inc. System and method of interfacing co-processors and input/output devices via a main memory system
US10942682B2 (en) 2011-02-08 2021-03-09 Rambus Inc. System and method of interfacing co-processors and input/output devices via a main memory system
US11422749B2 (en) 2011-02-08 2022-08-23 Rambus Inc. System and method of interfacing co-processors and input/output devices via a main memory system
US11789662B2 (en) 2011-02-08 2023-10-17 Rambus Inc. System and method of interfacing co-processors and input/output devices via a main memory system
JP2012027929A (en) * 2011-08-31 2012-02-09 Sandisk Il Ltd Loading of internal application on smart card

Also Published As

Publication number Publication date
US7752380B2 (en) 2010-07-06
WO2005010637A3 (en) 2005-06-30
JP5290516B2 (en) 2013-09-18
KR20060041153A (en) 2006-05-11
US20050027928A1 (en) 2005-02-03
JP5588536B2 (en) 2014-09-10
EP1649378A4 (en) 2006-08-23
KR100867900B1 (en) 2008-11-10
JP2013168169A (en) 2013-08-29
JP2007500916A (en) 2007-01-18
EP1649378A2 (en) 2006-04-26

Similar Documents

Publication Publication Date Title
US7752380B2 (en) SDRAM memory device with an embedded NAND flash controller
US8185728B2 (en) System boot using NAND flash memory and method thereof
US7782683B2 (en) Multi-port memory device for buffering between hosts and non-volatile memory devices
EP1537483B1 (en) A memory circuit comprising a non-volatile ram and a ram
US8650388B2 (en) Multi-processor systems and booting methods thereof
US20060206701A1 (en) Booting From Non-Linear Memory
US8041885B2 (en) Memory system and method with flash memory device
US7533253B2 (en) System and method for fetching a boot code
US7426607B2 (en) Memory system and method of operating memory system
EP1343082A2 (en) System boot using nand flash memory and method thereof
CN213691455U (en) Memory, electronic device and test system thereof
US7249253B2 (en) Booting from a re-programmable memory on an unconfigured bus
WO2005086007A1 (en) Data copy device
US6549975B2 (en) Tri-stating output buffer during initialization of synchronous memory
US20050018524A1 (en) Synchronous flash memory command sequence
EP1796100A2 (en) SDRAM memory device with an embedded NAND flash controller
US11550740B2 (en) Data storage device with an exclusive channel for flag checking of read data, and non-volatile memory control method
JP2005190312A (en) Multi-chip package type memory system and computer system

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 1020057009826

Country of ref document: KR

WWE Wipo information: entry into national phase

Ref document number: 2004732398

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2006521766

Country of ref document: JP

WWP Wipo information: published in national office

Ref document number: 2004732398

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 1020057009826

Country of ref document: KR

WWW Wipo information: withdrawn in national office

Ref document number: 2004732398

Country of ref document: EP