Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.

Patents

  1. Advanced Patent Search
Publication numberUS20080052448 A1
Publication typeApplication
Application numberUS 11/780,441
Publication dateFeb 28, 2008
Filing dateJul 19, 2007
Priority dateJul 20, 2006
Also published asUS8140738
Publication number11780441, 780441, US 2008/0052448 A1, US 2008/052448 A1, US 20080052448 A1, US 20080052448A1, US 2008052448 A1, US 2008052448A1, US-A1-20080052448, US-A1-2008052448, US2008/0052448A1, US2008/052448A1, US20080052448 A1, US20080052448A1, US2008052448 A1, US2008052448A1
InventorsDeboleena Minz, Sanjeev Varshney
Original AssigneeStmicroelectronics Pvt. Ltd.
Export CitationBiBTeX, EndNote, RefMan
External Links: USPTO, USPTO Assignment, Espacenet
Flash memory interface device
US 20080052448 A1
Abstract
A memory interface module provides interfacing between a host processor with multiple flash memories and parallel interfaces of varying protocols. The interface module includes multiple register files, multiple operation information registers, an internal memory, a flash interface portion, and a finite state machine (FSM). The register files receive a command from the host processor for controlling an operation of multiple flash memories. The operation information registers execute and store the command and operation information. The internal memory receives and stores host data from the host processor. The internal memory further stores flash data extracted from multiple flash memories. The flash interface portion interacts with the memory devices connected to the controller. The FSM extracts the command and the operation information from the register files, which are programmed by the user and controls the control signals of the memory devices connected to the controller through the flash interface.
Images(9)
Previous page
Next page
Claims(17)
1. A memory interface module interfacing between a host processor and a plurality of flash memories, the plurality of flash memories obeying a plurality of protocols, said memory interface module comprising:
a plurality of register files receiving a command from the host processor to control an operation of the plurality of flash memories and a plurality of parallel interfaces;
a plurality of operation information registers for executing and storing the command and an operation information;
an internal memory receiving and storing host data from the host processor and storing flash data extracted from the plurality of flash memories to transmit to the host processor;
a flash interface portion performing a plurality of tasks, said tasks comprising: controlling a control signal to operate the plurality of flash memories; outputting one or more of the command, the operation information, and the host data; and controlling a data bus for enabling data transfer to the plurality of flash memories; and
a finite state machine (FSM) extracting the command and the operation information and controlling the internal memory and the flash interface portion to execute the command,
said memory interface module provides a flexibility to control the control signal through a plurality of pre-defined states, and
said finite state machine (FSM) generating the control signal, such that the plurality of pre-defined states and their transitions being controlled by an user.
2. The memory interface module as claimed in claim 1, wherein the plurality of flash memories is selected from a group consisting of flash memories, SDRAMs, and parallel interfaces.
3. The memory interface module as claimed in claim 1, wherein the operation information comprises a starting address to be assigned to a location of said flash memory in which an operation according to the command is performed.
4. The memory interface module as claimed in claim 1, wherein the internal memory comprises:
a booting memory for storing a booting code to boot a system;
one of a buffer, and a register file for storing the host data and the flash data; and
an ECC checker.
5. The memory interface module as claimed in claim 1, wherein the plurality of register files comprises:
an address register for storing an address of a memory read/write location;
a command register for storing device commands for a particular memory being interfaced; and
a timing register for storing one or more of a setup time information, a hold time information, and a memory device timing information.
6. The memory interface module as claimed in claim 5, wherein the plurality of register files further comprising a status register for storing an operation status information of the command, and an execution result of the command.
7. A method of interfacing between a host processor and a plurality of flash memories through a memory interface module, the plurality of flash memories obeying a plurality of protocols, said method comprising:
receiving a command from the host processor to control an operation of the plurality of flash memories through a plurality of register files;
executing and storing the command and an operation information through an operation information register;
decoding the command and the operation information through a flash interface portion; and
executing an operation according to the decoded command, said memory interface module provides a flexibility to control the control signal through a plurality of pre-defined states, wherein the plurality of pre-defined states and their transitions are controlled by a user.
8. An interface between a host processor and a plurality of different types of flash memory, comprising:
a plurality of input/output pins connected through a glue logic to the plurality of different types of flash memory; and
a finite state machine having a plurality of states, the identification of the states and the transition among and between those states being specified by a user of the interface; the finite state machine transitioning between the states to control the operation of the plurality of input/output pins so as to interface with the plurality of different types of flash memory for data exchange.
9. The interface of claim 8 wherein transition among and between the states of the finite state machine is controlled through execution of software comprising a plurality of instruction-operand pairs, certain ones of the instruction-operand pairs controlling the generation of one or more signals at the plurality of input/output pins for interfacing with a certain one of the plurality of different types of flash memory.
10. The interface of claim 9 wherein the finite state machine executes sequences of the instruction-operand pairs in controlling operation of the plurality of input/output pins.
11. The interface of claim 8 wherein the plurality of input/output pins includes a first input/output pin connected through the glue logic to both a first type flash memory and a second type flash memory, the finite state machine controlling the first input/output pin to operate in a first mode for interfacing with first type flash memory and a second mode for interfacing with second type flash memory.
12. The interface of claim 11 wherein the plurality of memories comprise a first type flash memory and a second type flash memory, and wherein the first type flash memory utilizes a first protocol and the second type flash memory utilizes a second protocol, the finite state machine controlling the first input/output pin to operate in accordance with the first protocol for interfacing with first type flash memory and in accordance with the second protocol for interfacing with second type flash memory.
13. The interface of claim 8 wherein the plurality of memories comprise a first type flash memory and a second type flash memory, and wherein the first type flash memory utilizes a first control signal sequence and the second type flash memory utilizes a second control signal sequence, the finite state machine controlling the input/output pins to effectuate the first control signal sequence for interfacing with first type flash memory and the second control signal sequence for interfacing with second type flash memory.
14. The interface of claim 8 wherein the plurality of memories comprise a first type flash memory and a second type flash memory, and wherein the first type flash memory is controlled in accordance with a first protocol and the second type flash memory is controlled in accordance with a second protocol, the finite state machine controlling the input/output pins in accordance with the first protocol for interfacing with first type flash memory and in accordance with the second protocol for interfacing with second type flash memory.
15. The interface of claim 8 wherein the plurality of memories comprise a first type flash memory and a second type flash memory, and wherein the first type flash memory is controlled by a first combination and sequencing of states in the finite state machine and the second type flash memory is controlled in accordance with a second combination and sequencing of states in the finite state machine, the finite state machine responding to a host processor request for access to one of the first and second types of flash memory by executing the corresponding combination and sequencing of states so as to control the input/output pins to interface with the requested flash memory.
16. The interface of claim 8 wherein the finite state machine transitions between the states to control generation of valid control signal sequences at the plurality of input/output pins so as to interface with the plurality of different types of flash memory for data exchange.
17. The interface of claim 16 wherein the plurality of memories comprise a first type flash memory and a second type flash memory, and wherein the first type flash memory is controlled by a first control signal sequence and the second type flash memory is controlled by a second control signal sequence, the finite state machine responding to a host processor request for access to one of the first and second types of flash memory by generating the corresponding control signal sequence at the input/output pins to interface with the requested flash memory.
Description
    PRIORITY CLAIM
  • [0001]
    The present application claims priority from Indian Patent Application No. 1670/Del/2006 of the same title filed Jul. 20, 2006, the disclosure of which is hereby incorporated by reference.
  • BACKGROUND
  • [0002]
    1. Technical Field
  • [0003]
    The present application relates to interface devices, and more specifically, to a flexible and programmable flash memory interface device capable of interfacing with various kinds of flash memory devices with varying protocols.
  • [0004]
    2. Description of Related Art
  • [0005]
    Flash memory is a form of EEPROM (Electrically-Erasable Programmable Read-Only Memory) that allows multiple memory locations to be erased or written in one programming operation. It is a Non-Volatile Read Write Memory (NVRWM) commonly used in memory cards, USB flash drives, MP3 players, digital cameras, mobile phones, etc. There are different kinds of flash memory devices available in the market today. The flash memory stores a correctable control program, which is used instead of an auxiliary memory.
  • [0006]
    NOR-based flash has long erase and write times, but has a full address/data (memory) interface that allows random access to any location, which makes it suitable for storage of program code that needs to be infrequently updated, such as a computer's BIOS or the firmware of a set-top box. The endurance of NOR-based flash is 10,000 to 1,000,000 erase cycles. NOR-based flash was the basis of early flash-based removable media; Compact Flash was originally based on this technology, although later cards moved to the cheaper NAND flash.
  • [0007]
    NAND flash has faster erase and write times, higher density, and lower cost per bit than NOR flash, and ten times the endurance. However its I/O interface allows only sequential access to data. This makes it suitable for mass-storage devices such as PC cards and various memory cards, and it is somewhat less useful for computer memory.
  • [0008]
    Serial Flash is a small, low-power flash memory that uses a serial interface for sequential data access. Serial flash uses fewer wires than parallel flash memories to transfer data to and from a system. A reduction in board space, power consumption and system cost are some of the benefits of the lower pin count interface for serial flash memories.
  • [0009]
    The flash memory is divided into a NAND flash memory and a NOR type flash memory. The NOR type flash memory uses an interface method as an SRAM or as a ROM to easily construct a circuit with a processor. Further, the NAND flash memory is more sophisticated using the interface method than the NOR type flash memory and has an advantage of lower economic costs. However, the NAND flash memory has a higher degree of integration than the NOR flash memory.
  • [0010]
    These days, a number of vendors are providing NOR, NAND and SERIAL flashes having varying protocols and interfacing programs, and hence no common protocol is being followed by these vendors. The result of these flashes is that every new flash that is brought out in the market has its own set of commands, modes and operations that can be performed on them. This becomes a problem when the memory interface modules interacting with these devices have to be modified for every different device. The IPs (Intellectual Property) in the subsystem is not configurable, thus requiring manual changes depending upon nuances of different chips. Many SOCs (System on Chip) have more than one type of flash memory devices in the subsystem. This entails having more than one memory interface module to interact with them. In order to reduce the pin count of the SOC, the output pins of these multiple modules have to be multiplexed leading to an increase in glue logic, and thus area.
  • [0011]
    FIG. 1 represents a conventional structure for a flash memory interface system interacting with NAND, NOR and SERIAL flash memories. The interface has three different modules, one for each type of flash memory device. The output pins of these modules are multiplexed at the output of the subsystem, which drives a shared bus. The shared bus in turn drives the pins of the memory blocks. These modules interact with the external world through a decoder or a router that decodes the incoming address bits and routes it to the required module.
  • [0012]
    The modules offer little or no flexibility to accommodate new protocols, or even new modes. Multiplexing the pins of these three modules adds to the glue logic, and therefore increases a usage area and a delay. Even when the memory devices come up with optimizations in the protocol which offer more efficient access times (for example, removing dummy cycles), incorporating them in the interface subsystem means changing the RTL and going through the entire design cycle which is both time and money consuming.
  • [0013]
    There is a need of a versatile/flexible solution through a proposed flexible and programmable flash memory interface device, which can overcome the above mentioned problems. Moreover, the proposed memory interface device allows support for maximum features of different memories available in the market for easy integration.
  • SUMMARY OF THE INVENTION
  • [0014]
    An embodiment provides a memory interface module having a minimal area due to one set of HW state machines serving for all types of memories with varying protocols.
  • [0015]
    An embodiment provides a memory interface module, which supports newly designed flash memory types due to highly flexible approach with minor changes in software (SW).
  • [0016]
    An embodiment provides a memory interface module, which utilizes reduced pin counts for different memory devices.
  • [0017]
    An embodiment provides a memory interface module, which results in reduced glue, as there would be no need to multiplex the pins for different types of flashes.
  • [0018]
    In an embodiment, a memory interface module provides interfacing between a host processor and multiple flash memories with varying protocols. The memory interface module comprises: a plurality of register files receiving a command from the host processor to control an operation of the plurality of flash memories and a plurality of parallel interfaces; a plurality of operation information registers for executing and storing the command and an operation information; an internal memory receiving and storing host data from the host processor and storing flash data extracted from the plurality of flash memories to transmit to the host processor; a flash interface portion performing a plurality of tasks. The tasks comprises: controlling a control signal to operate the plurality of flash memories; outputting one or more of the command, the operation information, and the host data; and controlling a data bus for enabling data transfer to the plurality of flash memories. The module further includes a finite state machine (FSM) extracting the command and the operation information and controlling the internal memory and the flash interface portion to execute the command. The memory interface module provides a flexibility to control the control signal through a plurality of pre-defined states. The finite state machine (FSM) generates the control signal, such that the plurality of pre-defined states and their transitions being controlled by an user.
  • [0019]
    Further, an embodiment is a method of interfacing between a host processor and multiple flash memories having varying protocols. The method comprises: receiving a command from the host processor to control an operation of the plurality of flash memories through a plurality of register files; executing and storing the command and an operation information through an operation information register; decoding the command and the operation information through a flash interface portion; and executing an operation according to the decoded command, said memory interface module provides a flexibility to control the control signal through a plurality of pre-defined states. A finite state machine (FSM) is designed to generate the control signal, such that the plurality of pre-defined states and their transitions are controlled by an user.
  • [0020]
    In an embodiment, an interface between a host processor and a plurality of different types of flash memory comprises: a plurality of input/output pins connected through a glue logic to the plurality of different types of flash memory; and a finite state machine having a plurality of states, the identification of the states and the transition among and between those states being specified by a user of the interface; the finite state machine transitioning between the states to control the operation of the plurality of input/output pins so as to interface with the plurality of different types of flash memory for data exchange.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • [0021]
    A more complete understanding of the method and apparatus of the present invention may be acquired by reference to the following Detailed Description when taken in conjunction with the accompanying Drawings wherein:
  • [0022]
    FIG. 1 illustrates a conventional structure for a flash memory interface system interacting with NAND, NOR and SERIAL flash memories;
  • [0023]
    FIG. 2 illustrates a proposed structure of flash memory interface according to an embodiment;
  • [0024]
    FIG. 3 shows a table depicting the input/output signals for different devices from various vendors;
  • [0025]
    FIG. 4 shows various states of a finite state machine (FSM) according to an embodiment;
  • [0026]
    FIG. 5 illustrates a timing diagram to show how the NOR controller can be programmed for an asynchronous read operation for a flash memory;
  • [0027]
    FIG. 6 illustrates a timing diagram of an example of read data bytes from a SERIAL flash;
  • [0028]
    FIG. 7 illustrates a timing diagram of an example of a command cycle with its waveform in a NAND flash; and
  • [0029]
    FIG. 8 shows pin diagrams of the controller module connected to a NOR flash, a SERIAL flash, and a NAND flash.
  • DETAILED DESCRIPTION OF THE DRAWINGS
  • [0030]
    A flash memory interface device is provides which is capable of interfacing with various kinds of flash memory devices of varying protocols.
  • [0031]
    The technique presented herein offers many advantages such as: (1) Area saving due to one set of HW state machines serving for all types of memories against configuration existing today where there are different IPs for serving NOR, Serial and NAND flashes and SDRAMS or other parallel interfaces; (2) New memory types support could be added due to highly flexible approach with minor changes in SW only thereby saving lots of design/verify development time; (3) Reduced pin count as many pins get shared for different memory devices. This can prove to be a great advantage in shrinking technologies where the pad sizes do not reduce in the same proportion as the core; (4) Unique subsystem serving all types of products, the changes would be in SW to enable/disable support of given type of memory, this therefore would reduce complexity of development, integration, verification and STA for different SOC's flash memory interface subsystem; and (5) Reduction in glue would result as there would be no need to multiplex the pins for different types of memories.
  • [0032]
    FIG. 2 illustrates a proposed structure of flash memory interface according to an embodiment. In the proposed structure the three modules, as present in the conventional structure, are replaced by one flexible memory module. This arrangement obviates the need for multiplexing the pins at the output, thereby reducing the glue logic and improving timing. This single module also offers more flexibility as compared to conventional structures, which have three individual modules.
  • [0033]
    The memory interface module implemented through the controller shown in FIG. 2 includes a plurality of register files which receive commands from the host processor to control an operation of the plurality of flash memories and a plurality of parallel interfaces. A plurality of operation information registers are included in the controller for executing and storing the command and an operation information. An internal memory receives and stores host data from the host processor and stores flash data extracted from the plurality of flash memories to transmit to the host processor. A flash interface portion of the controller performs a plurality of tasks. These tasks comprise: controlling a control signal to operate the plurality of flash memories; outputting one or more of commands, operation information, and host data; and controlling a data bus for enabling data transfer to the plurality of flash memories. Operation of the controller is controlled via a finite state machine (FSM) which extracts the command and the operation information and controls the internal memory and the flash interface portion to execute the command. The memory interface module provides a flexibility to control the control signal through a plurality of pre-defined states. The finite state machine (FSM) generates the control signal, such that the plurality of pre-defined states and their transitions are being controlled by a user.
  • [0034]
    The internal memory comprises a booting memory for storing a booting code to boot a system, one of a buffer, and a register file for storing the host data and the flash data, and an ECC checker.
  • [0035]
    The plurality of register files comprise: an address register for storing an address of a memory read/write location, a command register for storing device commands for a particular memory being interfaced, and a timing register for storing one or more of a setup time information, a hold time information, and a memory device timing information. The plurality of register files further comprise a status register for storing an operation status information of the command, and an execution result of the command.
  • [0036]
    In operation, the controller functions as follows to interface between a host processor and a plurality of flash memories through a memory interface module. Again, it will be noted that the plurality of flash memories obey a plurality of different protocols. A command is received from the host processor to control an operation of the plurality of flash memories through the plurality of register files. The process executes and stores the command and an operation information through the operation information register. The command and the operation information are decoded through a flash interface portion. An operation is then executed according to the decoded command. In this context, the memory interface module provides a flexibility to control the control signal through a plurality of pre-defined states, wherein the plurality of pre-defined states and their transitions are controlled by a user. The FSM functions to generate the necessary control signal(s).
  • [0037]
    FIG. 3 shows a table depicting the input/output signals for three devices from three vendors.
  • [0038]
    Most of the devices from these vendors have the same basic control pins to control various memory operations. For example, chip enable, output enable, latch enable (synch), write enable, clock (synch) to control the device bus operations.
  • [0039]
    The following example explains the proposed embodiment in the context of NOR flashes. Different embodiments for other types of memory devices can also be proposed.
  • [0040]
    Without loss of generality let us consider the NOR flashes available from three vendors: INTEL, AMD and ST. Each vendor memory provides ASYNCH and SYNCH modes. There are a number of commands available for each one of them for READ, PROGRAM, ERASE, PROGRAM SUSPEND, BLOCK PROTECT etc. The numbers of bus cycles required for these various operations as well as the commands are different for different vendor devices.
  • [0041]
    However, the (dynamic) input/output signals for all three of them are very similar.
  • [0042]
    The proposed idea is to provide the user (software) the flexibility to control these control signals through some pre-defined states.
  • [0043]
    These control signals will be generated from the controller through a state machine. The states of this state machine and the transitions between them could be controlled by the user.
  • [0044]
    The section below explains the idea in detail.
  • [0045]
    A NOR-controller that drives the control signals of the flash device usually consists of a finite state machine (FSM). Let us say that the FSM is made up of the following states as shown in FIG. 4.
  • [0046]
    These states drive the device control signals. The state STATE 7 (start write), for example, prepares the device for a write operation by carrying out the following operations: 1. Provides a valid address at the address pins; 2. Asserts the chip enable signal; 3. Deasserts the output enable signal; 4. Provides a valid command/data at the data pins.
  • [0047]
    The rest of the states also carry out such basic operations as is evident from their names. When the transitions between these states are defined, the FSM (Moore machine) would be complete.
  • [0048]
    Now, let us say that we have a collection of n such states. Some of these states are as basic as the ones mentioned above and few others are made from the combination of one or more of these basic states. If we ensure that any device with these control signals can be controlled by a proper combination and sequencing of these states, then we can provide unlimited flexibility to the user by giving him power to control the transition between these states.
  • [0049]
    The transition between these states can be controlled by the user (software SW) via a set of instruction-operand pair provided. Each of these instruction-operand pair may be used to control one or more control signals of the memory devices. The operand might contain added information required to complete the command for example the address for reads/writes, or information about the register which contains this information. Similarly the information about data, timing values, device commands etc. might be contained in the operand or register file(s). The sequences of such instruction-operand pairs are executed by the FSM, thereby implementing the desired protocol required by the memory device being interfaced. Different sequences of these instructions along with a variety of data/address/device command will provide valid control signal sequences for different memory devices.
  • [0050]
    FIG. 5 illustrates a timing diagram to show how the NOR controller can be programmed for an asynchronous read operation for a flash memory in an embodiment.
  • [0051]
    A set of example states and their transitions and the resulting waveform would be as shown in the FIG. 5.
  • [0052]
    FIG. 6 illustrates a timing diagram of an example of read data bytes from a SERIAL flash.
  • [0053]
    A similar scheme would work for serial flashes as well. In order to interface with a variety of memory devices, a set of generic states will have to be defined. Each of these states will be valid for one or more of these memory devices.
  • [0054]
    Since most of the memory operations require repetition of certain control signal sequences, an instruction-operand pair to repeat a particular sequence of states might ease the task of repeating certain instructions a number of times in the sequence. The information about the sequence of states to be repeated and the number of times it is to be repeated may be contained in the operand or register files(s).
  • [0055]
    FIG. 6 shows the read waveform.
  • [0056]
    FIG. 7 illustrates a timing diagram of an example of a command cycle with its waveform in a NAND flash.
  • [0057]
    The set of instructions shown in FIGS. 5, 6 and 7 are explained in three different embodiments for NAND, NOR, SERIAL. Different embodiments can also exist for different devices and protocols.
  • [0058]
    NAND flashes have similar pins as compared to NOR flashes. The CE (chip enable) pin and the WE (write enable) pin are same in both the flashes (with same/similar functionality). The NAND flashes have only one input output bus for all data and address I/Os. The pin OE-bar (output enable) can function as the ALE (address latch enable) pin and the Lbar pin can function as the CLE (command latch enable) pin. We would, however need an extra port for the R-bar (read enable) pin of the NAND flash.
  • [0059]
    FIG. 8 shows pin diagrams of the controller module (FIG. 2) connected to a NOR flash, a SERIAL flash, and a NAND flash.
  • [0060]
    As shown in FIG. 8 the same set of states as well as I/O pins of the controller might be used to interface with a variety of memory devices. This scheme may be applied to SDRAMs or other parallel interfaces by bringing about a few modifications/additions to the states/instructions defined as might be obvious to those skilled in the art
  • [0061]
    Other Possible Enhancements
  • [0062]
    Another enhancement that can be done to improve the throughput requirements is to have a “PING-PONG” structure for the register file(s). This means that we have two sets of register file(s) instead of one. And while the controller is executing states from one set of register files, the user (software SW) can program the other set of register, thereby having smooth uninterrupted transactions at the flash memory end. This would increase the throughput of the memory especially for transactions requiring large number of state changes.
  • [0063]
    Although preferred embodiments of the method and apparatus of the present invention have been illustrated in the accompanying Drawings and described in the foregoing Detailed Description, it will be understood that the invention is not limited to the embodiments disclosed, but is capable of numerous rearrangements, modifications and substitutions without departing from the spirit of the invention as set forth and defined by the following claims.
Patent Citations
Cited PatentFiling datePublication dateApplicantTitle
US5907700 *Jun 19, 1997May 25, 1999Intel CorporationControlling flash memory program and erase pulses
US6795906 *Jun 15, 2001Sep 21, 2004Nec CorporationMemory controller, interface device and method using a mode selection signal to support different types of memories
US20030131185 *Jan 4, 2002Jul 10, 2003Lance DoverFlash memory command abstraction
US20040003168 *May 28, 2003Jan 1, 2004Samsung Electronics Co., Ltd.NAND flash memory interface device
US20040054864 *Sep 13, 2002Mar 18, 2004Jameson Neil AndrewMemory controller
US20040098549 *Oct 4, 2001May 20, 2004Dorst Jeffrey R.Apparatus and methods for programmable interfaces in memory controllers
US20060282608 *Aug 18, 2006Dec 14, 2006Fujitsu LimitedMemory system
Referenced by
Citing PatentFiling datePublication dateApplicantTitle
US8205037Jun 19, 2012Google Inc.Data storage device capable of recognizing and controlling multiple types of memory chips operating at different voltages
US8239713Aug 7, 2012Google Inc.Data storage device with bad block scan command
US8239724Aug 7, 2012Google Inc.Error correction for a data storage device
US8239729Oct 7, 2011Aug 7, 2012Google Inc.Data storage device with copy command
US8244962Aug 14, 2012Google Inc.Command processor for a data storage device
US8250271Aug 21, 2012Google Inc.Command and interrupt grouping for a data storage device
US8327220Dec 4, 2012Google Inc.Data storage device with verify on write command
US8341334 *Dec 25, 2012Silicon Motion, Inc.Flash memory apparatus and method for operating the same and data storage system
US8380909Feb 19, 2013Google Inc.Multiple command queues having separate interrupts
US8433845Apr 30, 2013Google Inc.Data storage device which serializes memory device ready/busy signals
US8447918Apr 7, 2010May 21, 2013Google Inc.Garbage collection for failure prediction and repartitioning
US8566507Aug 7, 2009Oct 22, 2013Google Inc.Data storage device capable of recognizing and controlling multiple types of memory chips
US8566508Aug 7, 2009Oct 22, 2013Google Inc.RAID configuration in a flash memory data storage device
US8578084Aug 7, 2009Nov 5, 2013Google Inc.Data storage device having multiple removable memory boards
US8595572Apr 7, 2010Nov 26, 2013Google Inc.Data storage device with metadata command
US8639871Aug 7, 2009Jan 28, 2014Google Inc.Partitioning a flash memory data storage device
US8806136Jul 7, 2011Aug 12, 2014Shanghai Actions Semiconductor Co., Ltd.Nandflash controller and data transmission method with Nandflash controller
US9053066 *Mar 30, 2012Jun 9, 2015Sandisk Technologies Inc.NAND flash memory interface
US9152496 *Dec 21, 2007Oct 6, 2015Cypress Semiconductor CorporationHigh performance flash channel interface
US9244842Nov 22, 2013Jan 26, 2016Google Inc.Data storage device with copy command
US20090164704 *Dec 21, 2007Jun 25, 2009Spansion LlcHigh performance flash channel interface
US20090198858 *Jan 29, 2009Aug 6, 2009Sony CorporationSemiconductor memory device and operation method therefor
US20100262738 *Oct 14, 2010Google Inc.Command and interrupt grouping for a data storage device
US20100262740 *Oct 14, 2010Google Inc.Multiple command queues having separate interrupts
US20100262758 *Oct 14, 2010Google Inc.Data storage device
US20100262760 *Oct 14, 2010Google Inc.Command processor for a data storage device
US20100262761 *Aug 7, 2009Oct 14, 2010Google Inc.Partitioning a flash memory data storage device
US20100262762 *Oct 14, 2010Google Inc.Raid configuration in a flash memory data storage device
US20100262766 *Apr 7, 2010Oct 14, 2010Google Inc.Garbage collection for failure prediction and repartitioning
US20100262767 *Oct 14, 2010Google Inc.Data storage device
US20100262773 *Oct 14, 2010Google Inc.Data striping in a flash memory data storage device
US20100262894 *Aug 7, 2009Oct 14, 2010Google Inc.Error correction for a data storage device
US20100262979 *Apr 8, 2010Oct 14, 2010Google Inc.Circular command queues for communication between a host and a data storage device
US20100287217 *Apr 7, 2010Nov 11, 2010Google Inc.Host control of background garbage collection in a data storage device
US20100332731 *Oct 10, 2009Dec 30, 2010Silicon Motion, Inc.Flash memory apparatus and method for operating the same and data storage system
US20110138158 *Jul 24, 2009Jun 9, 2011Masatomo MitsuhashiIntegrated circuit
US20140122777 *Mar 15, 2013May 1, 2014Mosaid Technologies IncorporatedFlash memory controller having multi mode pin-out
US20140297925 *Dec 31, 2013Oct 2, 2014SK Hynix Inc.Storage device with self-contained information storage space
CN101882119BMay 8, 2009May 14, 2014上海炬力集成电路设计有限公司NAND flash memory controller and data transmission method thereof
WO2010127636A1 *May 7, 2010Nov 11, 2010Actions Semiconductor Co., Ltd.Nandflash controller and data transmission method thereof
Classifications
U.S. Classification711/103, 711/E12.002
International ClassificationG06F12/02
Cooperative ClassificationG06F13/1694, G11C16/32, G11C2216/30
European ClassificationG06F13/16D9
Legal Events
DateCodeEventDescription
Nov 5, 2007ASAssignment
Owner name: STMICROELECTRONICS PVT. LTD., INDIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MINZ, DEBOLEENA;VARSHNEY, SANJEEV;REEL/FRAME:020110/0257
Effective date: 20070920
Dec 20, 2013ASAssignment
Owner name: STMICROELECTRONICS INTERNATIONAL N.V., NETHERLANDS
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:STMICROELECTRONICS PVT. LTD.;REEL/FRAME:031826/0530
Effective date: 20131216
Mar 14, 2014ASAssignment
Owner name: SK HYNIX INC., KOREA, REPUBLIC OF
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:STMICROELECTRONICS INTERNATIONAL N.V.;REEL/FRAME:032445/0056
Effective date: 20140307
Jul 28, 2015FPAYFee payment
Year of fee payment: 4