US20010048121A1 - Semiconductor memory device with block alignment function - Google Patents

Semiconductor memory device with block alignment function Download PDF

Info

Publication number
US20010048121A1
US20010048121A1 US09/779,610 US77961001A US2001048121A1 US 20010048121 A1 US20010048121 A1 US 20010048121A1 US 77961001 A US77961001 A US 77961001A US 2001048121 A1 US2001048121 A1 US 2001048121A1
Authority
US
United States
Prior art keywords
address
data
memory device
semiconductor memory
logical address
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
US09/779,610
Other versions
US6459644B2 (en
Inventor
Nagamasa Mizushima
Kunihiro Katayama
Kazunori Furusawa
Tomihisa Hatano
Takayuki Tamura
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Renesas Electronics Corp
Original Assignee
Hitachi 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 Hitachi Ltd filed Critical Hitachi Ltd
Publication of US20010048121A1 publication Critical patent/US20010048121A1/en
Assigned to HITACHI, LTD. reassignment HITACHI, LTD. CORRECTIVE ASSIGNMENT TO CORRECT THE SERIAL NUMBER, ERROUNEOUSLY RECORDED AT REEL 012773, FRAME 0944. Assignors: HATANO, TOMIHISA, TAMURA, TAKAYUKI, FURUSAWA, KAZUNORI, KATAYAMA, KUNIHIRO, MIZUSHIMA, NAGAMASA
Application granted granted Critical
Publication of US6459644B2 publication Critical patent/US6459644B2/en
Assigned to RENESAS TECHNOLOGY CORPORATION reassignment RENESAS TECHNOLOGY CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: HITACHI, LTD.
Assigned to RENESAS ELECTRONICS CORPORATION reassignment RENESAS ELECTRONICS CORPORATION MERGER AND CHANGE OF NAME Assignors: RENESAS TECHNOLOGY CORP.
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02Addressing or allocation; Relocation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02Addressing or allocation; Relocation
    • G06F12/0223User address space allocation, e.g. contiguous or non contiguous base addressing
    • G06F12/023Free address space management
    • G06F12/0238Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory
    • G06F12/0246Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory in block erasable memory, e.g. flash memory
    • GPHYSICS
    • G11INFORMATION STORAGE
    • G11CSTATIC STORES
    • G11C16/00Erasable programmable read-only memories
    • G11C16/02Erasable programmable read-only memories electrically programmable
    • G11C16/06Auxiliary circuits, e.g. for writing into memory
    • G11C16/34Determination of programming status, e.g. threshold voltage, overprogramming or underprogramming, retention
    • G11C16/349Arrangements for evaluating degradation, retention or wearout, e.g. by counting erase cycles
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02Addressing or allocation; Relocation
    • G06F12/04Addressing variable-length words or parts of words
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/06Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
    • G06F3/0601Interfaces specially adapted for storage systems
    • G06F3/0628Interfaces specially adapted for storage systems making use of a particular technique
    • G06F3/0662Virtualisation aspects
    • G06F3/0664Virtualisation aspects at device level, e.g. emulation of a storage device or system

Definitions

  • the present invention relates to a semiconductor memory device, more particularly to a semiconductor memory device using a storage medium which requires data erasion for each predetermined block in writing data thereto.
  • a semiconductor memory device mounting a semiconductor memory has been rapidly spread.
  • a flash memory has been used as the semiconductor memory, which is capable of performing simultaneous erasing/rewriting of data electrically, and which is non-volatile, shows low power consumption, and can store a large capacity of data.
  • the flash memory adopting the multi-valued structure can store the two or more bit data in one cell, storage capacity per unit area increases.
  • the flash memory adopting the multi-valued structure shows lowered writing processing performance than the flash memory adopting the binary-valued structure, in the case that the size of a unit block (hereinafter referred to as an erase block) of the flash memory adopting the multi-valued structure, for erasing/writing of batch data is the same as that of the flash memory adopting the binary-valued structure.
  • an erase block a unit block of the flash memory adopting the multi-valued structure
  • a host system when a host system reads out file data from such an external storage device and writes it thereinto, the host system generally uses a sector as a unit of access similarly to a hard disc device, or the like.
  • a size of one sector is, for example, 512 bytes.
  • the size of this sector and the size of the erase block are made to be coincident with each other.
  • the semiconductor memory device which has the flash memory adopting the multi-level structure the size of the erase block is expanded as described above, and the plurality of sectors are collected into one as the erase block.
  • FAT file allocation table
  • a partition in which the FAT file system is constructed (hereinafter referred to as a FAT partition) has a management data area (a partition boot record (hereinafter referred to as a PBR) area, a FAT area and the like), which is for storing management data, and a FAT file area for storing file data.
  • the FAT file area among these areas is managed using each cluster composed of the plurality of sectors amounting to 4, 8, 16, 32 sectors in number and the like as a unit.
  • the number K (K: an integer equal to two or more) of the sectors constituting the erase block is normally set to a number so as to be able to divide the number J of the sectors constituting the cluster.
  • the number J of the sectors constituting the cluster is equal to K ⁇ L pieces (L: a positive integer).
  • the host system allocated a logical address, which is used for the host system to manage a sector number, to a physical address having an equal value of the flash memory.
  • the logical address of a head sector of a cluster and the physical address of a head sector of an eraser block correspond to each other.
  • the logical address of the head sector of the cluster and the physical address so the head sector of the erase block do not correspond to each other.
  • clusters A and B share one erase block (hereinafter referred to as a block M).
  • a sector portion included in the cluster A is set as a sector portion X
  • a sector portion included in the cluster B is set as a sector Y.
  • the data of the sector portion Y is erased as batch data of the block M irrespective of no necessity to rewrite the data of the sector portion Y, and the original data is written thereinto again.
  • the data of the sector portion X is erased as batch data of the block M irrespective of no necessity to rewrite the data of the sector portion X, and the original data is written thereinto again.
  • the number of times of erasing/writing operations performed for each erase block shared by the clusters adjacent to each other such as the block M must be twice the number of times of erasing/writing operations performed for an erase block included in a single cluster (hereinafter referred to as a block N), and hence a life of a memory element in the block M is reduced by half compared to that in the block N in terms of probability.
  • the object of the present invention is to provide a semiconductor memory device capable of reducing the number of times of an erasing operation for each block or the number of blocks erased by one writing operation to the minimum.
  • the semiconductor memory device is accessed by using logical addresses from a host system which divides and manages file data by using clusters each of which is composed of a plurality of sectors and is a unit for dividing and managing and the semiconductor memory device comprises: a memory section composed of the plurality of sectors, which is capable of erasing data for each block; and a control section for transforming a logical address to a physical address so that the logical address of a head sector of the cluster corresponds to the physical address of a head sector of the block, and for accessing the memory section by using the physical address thus transformed.
  • the logical address may be transformed to the physical address by applying an address offset value to the logical address.
  • a computation of the address offset value may be executed by the use of total storage capacity information of the memory section immediately after beginning power supply.
  • the computation of the address offset value may be executed when the information concerning the partition is written.
  • the information concerning the partition is, for example, data written into an address “0” of the logical address.
  • the computation of the address offset value may be executed, by the use of management information used to manage the file data, when the management information is written.
  • the management information is, for example, data written into a logical address range occupied by a management data area of the file system.
  • the management information is data of the PBR.
  • An information processing device has a feature in that this device includes the semiconductor memory device as described above.
  • a host system divides and manages file data by using clusters each of which is composed of a plurality of sectors and is a unit for dividing and managing.
  • the host system accesses a memory section composed of the plurality of sectors which is capable of erasing data for each block, the host system transforms a logical address to a physical address so that the logical address of a head sector of the cluster corresponds to the physical address of a head sector of the block and accesses the memory section by using the physical address thus transformed
  • FIG. 1 is a block diagram showing a semiconductor memory device according to the present invention.
  • FIG. 2 is a constitutional view showing a constitution of a flash memory.
  • FIG. 3 is a constitutional view showing a constitution of a flash memory array.
  • FIG. 4 is a constitutional view showing a constitution of the FAT file system.
  • FIG. 5 is a view illustrating a relation between a cluster and a block in the FAT file area disposed on the flash memory array.
  • FIG. 6 is a flowchart of a first address offset setting processing.
  • FIG. 7 is a table showing an example of a correspondence correlation between a logical address and a physical address.
  • FIG. 8 is a flowchart of a second address offset setting processing.
  • FIG. 9 is a table showing an example of a correspondence correlation between a logical address and a physical address.
  • FIG. 10 is a flowchart of a third address offset setting processing.
  • FIG. 11 is a table showing an example of a correlation between a logical address and a physical address.
  • FIG. 12 is a block diagram showing a semiconductor memory device and a host system.
  • FIG. 1 is a block diagram of a semiconductor memory device to which the present invention is applied.
  • the semiconductor memory device 100 comprises: a host interface 3 ; a central processing unit (hereinafter referred to as a CPU) 6 ; a programmable read only memory (hereinafter referred to as a programmable ROM) 8 ; an address offset storage section 10 ; a buffer memory 12 ; a memory interface 15 ; and a flash memory 17 .
  • the CPU 6 and the address offset storage section 10 constitute a control section.
  • the semiconductor memory device 100 is connected to the host system 1 such as a personal computer via a bus 2 , and receives a command from the host system 1 . Moreover, the semiconductor memory device 100 exchanges data with the host system 1 .
  • the bus 2 is used when the host system 1 accesses to the semiconductor memory device 100 , and is, for example, a local bus of the host system 1 or a standard bus of a personal computer such as an Integrated Drive Electronic (IDE) bus, an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, a Small Computer System Interface (SCSI) bus, a PC card bus, and the like.
  • IDE Integrated Drive Electronic
  • ISA Industry Standard Architecture
  • PCI Peripheral Component Interconnect
  • SCSI Small Computer System Interface
  • the host interface 3 is a hardware which transfers data sent via the bus 2 to the buffer memory 12 and transfers data stored in the buffer memory 12 to the bus 2 .
  • the buffer memory 12 temporarily holds the data read out from the flash memory 17 and the data to be written into the flash memory 17 , and comprises, for example, a static RAM (Random Access Memory).
  • the memory interface 15 is a hardware which transfers the data read out from the flash memory 17 to the buffer memory 12 and writes the data held by the buffer memory 12 into the flash memory 17 .
  • the CPU 6 reads out a program stored in the programmable ROM 8 , and performs a operation according to the program. For example, the CPU interprets a command and status of the host system 1 received via the host interface 3 , and controls functions of the host interface 3 and memory interface 15 according to the result of interpretation. Furthermore, the CPU 6 reads out the data held in the buffer memory 12 , and rewrites the data.
  • the CPU 6 transforms a logical address designated by the host system 1 to a physical address for accessing the flash memory 17 , by the use of an address offset value stored in the address offset storage section 10 .
  • a method of computing the address offset value and a method of transforming the logical address to the physical address will be described later.
  • the address offset storage section 10 stores the address offset value used in transforming the logical address to the physical address, and comprises a non-volatile or volatile memory element. Note that the address offset storage section 10 may be provided as independent storage means or alternatively may be constituted by using a part of other memory such as the flash memory 17 .
  • the flash memory 17 stores file data and the like.
  • FIG. 2 is a constitutional view showing a constitution of the flash memory 17 .
  • the flash memory 17 comprises a flash memory array 18 and a data register 19 .
  • the flash memory array 18 is an area for storing data, and constituted of a plurality of (erase) blocks 20 .
  • the data register 19 temporarily holds data for reading out data from any or the blocks 20 and for storing the data in any of the blocks 20 .
  • writing of sector data for the designated physical address is performed in the following manner. All batch data of a block including sectors to which data is to be written is first transferred to the data register 19 of the flash memory 17 . Thereafter, all data stored in the block of the flash memory array 18 is erased. A bit data of the block falls in an erase state, for example, all bit data becomes “1”. Reference numeral 21 of FIG. 2 illustrates a block in the erase state.
  • FIG. 3 is a constitutional view showing a constitution of a flash memory array 18 .
  • the flash memory array 18 comprises the plurality of blocks 20 , and each of the blocks 20 comprises the four sectors 22 , respectively. Note that each block may be comprised by any number of the sectors as long as the number of the sectors is two or more.
  • the sector 22 functions as a data unit when the host system 1 performs reading-out and writing of data for the semiconductor memory device 100 , and having a data unit size of, for example, 512 bytes.
  • the sectors 22 comprising the flash memory array 18 are numbered in a sequentially ascending order from 0h, respectively, and the sector number is called a physical address.
  • the host system 1 When the host system 1 performs the reading-out and writing of the data from and to the semiconductor memory device 100 , using the sector as a unit, the sector number managed by the host system 1 is called a logical address, which starts from 0h as a starting point. The host system 1 specifies the logical address, and performs reading-out and writing of data from and to the semiconductor memory device 100 .
  • the CPU 6 reads out the address offset value stored in the address offset storage section 10 , and adds the address offset value to the logical address value, thus generating the physical address.
  • the writing data transferred from the host system 1 is held in the buffer memory 12 via the host interface 3 .
  • the CPU 6 controls the memory interface 15 so that the data in the buffer memory 12 is written into the physical address after the address transformation, and writes the data into the specified physical address of the flash memory 17 .
  • a file system prepared in the semiconductor memory device 100 A system in which the host system 1 manages file data on the flash memory array 18 of the flash memory 17 is called a file system.
  • the plurality of file systems can be prepared on the flash memory array 18 , and a logical address range for placing a certain file system is called a partition.
  • FIG. 4 is a constitutional view showing a constitution of the FAT file system.
  • FIG. 4 shows an example in which one FAT partition 25 is prepared on the flash memory 18 .
  • the FAT partition 25 is a partition occupied by the FAT file system.
  • the logical address range of the FAT partition 25 covers from 20h to 1E7Fh.
  • the FAT partition 25 comprises a PBR 26 , a FAT area I 27 , a FAT area II 28 , a route directory area 29 and the FAT file area 30 .
  • the PBR 26 is a data stored in a head logical address of the FAT partition 25 .
  • the logical address of the PBR 26 is 20h.
  • the FAT file area 30 is an area for storing file data.
  • the logical address range of the FAT file area 30 covers from 47h to 1E7Fh.
  • the host system 1 manages the FAT file area 30 using clusters 31 each of which is a unit for managing, and writes file data into the FAT file area 30 using clusters 31 each of which is as a unit for writing.
  • each cluster 31 shall be composed of eight sectors 22 .
  • the number of the sectors 22 constituting the cluster 31 may be any number as long as it is natural number-times of the number of the sectors 22 constituting the block 20 .
  • the FAT area I 27 is an area for storing table data indicating a usage state of each of the clusters 31 .
  • the logical address range of the FAT area I 27 covers from 21h to 23h.
  • the FAT area II 28 is an area for storing a copy of data of the FAT area I 27 .
  • the logical address range thereof covers from 24h to 26h.
  • the route directory area 29 is an area for storing data indicating information pertaining to a file and a sub-directory in a route directory of the FAT partition 25 .
  • the logical address range thereof covers from 27h to 46h.
  • the host system 1 When the host system 1 prepares a file system on the semiconductor memory device 100 , the host system 1 first allocates a partition to an empty logical address range on the flash memory array 18 .
  • the empty logical address range means a logical address range to which another partition is not allocated. Then, the host system 1 formats this partition.
  • the word “format” means that the logical address ranges of the PBR 26 , FAT area I 27 , FAT area II 28 and route directory area 29 are allocated onto the partition and initialization data for managing file data is written into these areas.
  • a master boot record (hereinafter referred to as MBR) 23 is data stored in the logical address 0h.
  • the MBR 23 includes information indicating the logical address range of each of the partitions and sorts of the file systems existing in the logical address range. The host system 1 rewrites the data of the MBR 23 when the host system 1 performs the allocation of the partition to the empty logical address range, the format of the partition, deletion of the existing partition and the like.
  • the CPU 6 computes an address offset value that satisfies the following conditions.
  • the address offset value serves so as to make a head logical address of the FAT file area 30 correspond to a physical address of a head sector of a certain block 20 when the address offset value is added up.
  • the destination of the logical address of the head sector of each cluster 31 which constitutes the FAT file area 30 always agrees with the physical address of the head sector of the corresponding one of the blocks 20 .
  • FIG. 5 is a view illustrating a correlation between a block 20 of the flash memory 17 and a cluster 31 in a FAT file area 30 under the above-described conditions.
  • FIG. 5 shows a case where the block 20 consists of four sectors and the cluster 31 consists of eight sectors. Each of the clusters 31 consists of just two blocks 20 .
  • FIG. 6 is a flowchart of the address offset setting processing.
  • the CPU 6 When power supply to the semiconductor memory device 100 starts (S 32 ), the CPU 6 first checks the number of memory chips constituting the flash memory 17 and a capacity of each of the memory chips (S 33 ). Checking is carried out by reading out, for example, capacity information from each memory chip.
  • the total of the memory capacity capable of preparing the file system in the flash memory 17 is computed (S 34 ).
  • computed is the logical address range occupied by the PBR 26 , the FAT area I 27 , the FAT area II 28 and the route directory area 29 , and a starting logical address value of the FAT area 30 is calculated (S 35 ).
  • a sector having a value, equal to the starting logical address value, as a physical address is a head address of a block. If the sector is not the head address of the block, the starting logical address value is subtracted from a physical address value of a head sector of each block following the block concerned, and an address offset value is computed (S 36 ). The computed address offset value is stored in the address offset storage section 10 (S 37 ).
  • the CPU 6 transforms the logical address specified by the host system 1 to the physical address having a value obtained by adding the address offset value stored in the address offset storage section 10 to this logical address, and accesses the flash memory 17 using the physical address thus transformed.
  • FIG. 7 shows an example of correlation between logical addresses of the head sectors of the MBR 23 , the areas 26 to 30 of the FAT partition and the head sectors of clusters 31 , and physical addresses corresponding to them, when the host system 1 allocates all flash memory areas to one partition and formats this partition by the FAT.
  • a sector having the physical address whose value is a multiple of four is a head sector of the block 20 . Since a sector having the physical address whose value is equal to the head logical address 47h of the FAT file area 30 is not the head sector of the block 20 , for example, “1” obtained by subtracting the physical address value 47h from the physical address value 48h of the head sector of the next block 20 is set as the address offset value.
  • the head logical address of each cluster 31 constituting the FAT file area 30 is transformed so as to correspond to the physical address of the head sector of the block 20 . Accordingly, the above described conditions of the address offset value are satisfied.
  • the address offset value is applied to the whole of the logical address range, the address offset value may be applied to any range as long as the address offset value is applied at least to the logical address range occupied by the FAT file area 30 .
  • FIG. 8 is a flowchart of a second address offset setting processing.
  • the second address offset setting processing computes by the use of data an address offset value when the data is written into the MBR 23 .
  • the host system 1 When a new partition is prepared on the flash memory array 18 (S 38 ), the host system 1 writes data including information pertaining to a logical address range of the partition into the MBR 23 having a logical address 0h. Specifically, the host system 1 sends the CPU 6 a command to write data into the logical address 0h (S 39 ).
  • the CPU 6 When the CPU 6 is instructed to write the data into the logical address 0h, the CPU 6 writes data held in the buffer memory 12 into the physical address 0h of the flash memory 17 , and reads out the data to analyze the data. Thus, the CPU 6 knows the logical address range of the partition newly prepared (S 40 ). Then, the CPU 6 computes the logical address range occupied by the PBR 26 , the FAT area I 27 , the FAT area II 28 and the route directory area 29 when this partition is formatted by the FAT, and computes the starting logical address value of the FAT file area 30 (S 41 ).
  • the CPU 6 subtracts the starting logical address value from physical address value of a head sector of each block following the block concerned, and computes the address offset value (S 42 ).
  • the CPU 6 allows the address offset storage section 10 to store the computed address offset value therein (S 43 ).
  • the CPU 6 transforms the logical address within a range occupied by the FAT partition 25 to a physical address having a value obtained by adding the address offset value stored in the address offset storage section 10 to this logical address, and accesses the flash memory 17 using the physical address thus transformed.
  • FIG. 9 shows an example of correlation between the logical addresses of the head sectors of the MBR 23 , the areas 26 to 30 of the FAT partition and the clusters 31 , and the physical addresses corresponding to them.
  • FIG. 9 is identical to FIG. 7 except that the address offset value is not added to the MBR 23 .
  • the address offset value may be applied to any range as long as the address offset value is applied at least to the logical address range occupied by the FAT file area 30 .
  • data of the MBR 23 may be written into the physical address 1h.
  • FIG. 10 is a flowchart of the third address offset setting processing.
  • the third address offset setting processing computes the address offset value by the use of the data of the PBR in formatting the partition.
  • the CPU 6 checks whether the certain logical address is a head logical address of the partition. As a result of the check, if the certain logical address is the head logical address of the partition, the CPU 6 reads out the data held by the buffer memory 12 and analyzes the read-out data, and checks whether the read-out data is data corresponding to the PBR 26 of the FAT file system (S 46 ).
  • the CPU 6 when the CPU 6 detects that the partition is formatted with the FAT, the CPU 6 writes the PBR data held by the buffer memory 12 into a physical address whose value is equal to the head logical address value of the partition, and calculates, based on the PBR data, the logical address range occupied by the FAT area I 27 , the FAT area II 28 and the route directory area 29 , which constitute the FAT partition 25 , thus computing a starting logical address value of the FAT file area 30 (S 47 ).
  • the CPU 6 transforms the logical address within a range occupied by the FAT partition 30 to a physical address having a value obtained by adding the offset address value stored in the address offset storage section 10 to this logical address, and accesses the flash memory 17 using the physical address thus transformed.
  • FIG. 11 shows an example of correlation between logical addresses of the head sectors of the MBR 23 , the areas 26 to 30 of the FAT partition and the clusters 31 , and physical addresses corresponding to then.
  • the address offset value is applied only to the logical address range occupied by the FAT file area 30 .
  • the address offset value may be applied to other areas, for example, an area ranging from the PBR area 26 , as shown in FIG. 9.
  • the CPU 6 in the semiconductor memory device 100 performs the computation of the address offset value, the address transformation and the like.
  • a CPU outside the semiconductor memory device may perform a part of these functions or all of these functions.
  • FIG. 12 is a block diagram showing constitutions of the semiconductor memory device and the host system in the case where the address transformation is performed in the host system.
  • the host system 1 a comprises a host CPU 50 , the address offset storage section 10 and the buffer memory 12 .
  • a semiconductor memory device 100 a comprises the memory interface 15 and the flash memory 17 .
  • the buffer memory 12 and the like may be provided in the semiconductor memory device 100 a.
  • the CPU 50 of the host system 1 a performs a processing identical to that performed by the foregoing CPU 6 , and accesses the flash memory 17 in the semiconductor memory device 100 a by the use of a physical address that has been undergone the address transformation.
  • the same effects can be achieved also in the semiconductor memory device 100 a as in the foregoing semiconductor memory device 100 .
  • the FAT file system was described as the file data management system
  • the present invention can be applied to other file systems as long as applied is a file data management system in which a case where a head of unit of a file data area such as a cluster does not coincide with a head of a batch erasable/writable block of a flash memory occurs and in which a logical address occupied by a file data area can be computed by the use of management data.
  • the memory section constituting the semiconductor memory device according to the present invention is not limited to a flash memory.
  • the memory section may be the one which performs the erasion for each block constituted by two or more sectors in writing data.

Abstract

In the present invention, disclosed is a semiconductor memory device capable of reducing the number of erasing times of each block allocated to a cluster or the number of blocks to be erased in one writing to the minimum. As an embodiment of the present invention, when a host system 1 performs accessing, for each cluster as a unit, to the FAT partition prepared on a flash memory 17 of the semiconductor memory device 100, a CPU 6 adds an address offset value held by address offset storage section 10 to a logical address specified by the host system 1, whereby a logical address of a head sector of the cluster corresponds to a physical address of a head sector of a unit block for erasing/writing data in the flash memory 17.

Description

  • This application claims a priority based on Japanese Patent Application No. 2000-169289 filed on Jun. 6, 2000, the entire contents of which are incorporated herein by reference for all purposes. [0001]
  • BACKGROUND OF THE INVENTION
  • The present invention relates to a semiconductor memory device, more particularly to a semiconductor memory device using a storage medium which requires data erasion for each predetermined block in writing data thereto. [0002]
  • As an external storage device for such as a portable terminal device, a semiconductor memory device mounting a semiconductor memory has been rapidly spread. In such semiconductor memory device, generally, a flash memory has been used as the semiconductor memory, which is capable of performing simultaneous erasing/rewriting of data electrically, and which is non-volatile, shows low power consumption, and can store a large capacity of data. [0003]
  • With such flash memory, in order to deal with a recent demand for storing a large capacity of data, a flash memory adopting multi-valued structure capable of storing two or more bit data in one cell has been introduced instead of a flash memory adopting a binary-valued structure storing one bit data in one cell. [0004]
  • Since such a flash memory adopting the multi-valued structure can store the two or more bit data in one cell, storage capacity per unit area increases. However, since a cell adopting the multi-valued structure takes more processing time for data erasing/writing than a cell adopting the binary-valued structure, the flash memory adopting the multi-valued structure shows lowered writing processing performance than the flash memory adopting the binary-valued structure, in the case that the size of a unit block (hereinafter referred to as an erase block) of the flash memory adopting the multi-valued structure, for erasing/writing of batch data is the same as that of the flash memory adopting the binary-valued structure. [0005]
  • Accordingly, a countermeasure to expand the size of the erase block has been taken. With this countermeasure, the number of times (the number of erase blocks) of erasing/writing batch data simultaneously can be reduced in writing a certain quantity of data, and hence lowering of data processing performance can be prevented. [0006]
  • Furthermore, when the erase block is subdivided and the erase block increases in number, more peripheral circuits coping with the increase of the number of erase blocks is required, and a chip area is expanded as a whole, resulting in a decrease in a yield rate in manufacturing the flash memory. However, the expansion of the chip area is controlled by expanding the size of the erase blocks and by decreasing the number of the erase blocks, leading to an improvement of the yield rate. [0007]
  • On the other hand, when a host system reads out file data from such an external storage device and writes it thereinto, the host system generally uses a sector as a unit of access similarly to a hard disc device, or the like. A size of one sector is, for example, 512 bytes. [0008]
  • In the semiconductor memory device which has the flash memory adopting the binary-valued structure, generally, the size of this sector and the size of the erase block are made to be coincident with each other. On the other hand, in the semiconductor memory device which has the flash memory adopting the multi-level structure, the size of the erase block is expanded as described above, and the plurality of sectors are collected into one as the erase block. Thus, when the host system sends a command to the semiconductor memory device so as to write batch data into the plurality or sectors thereof simultaneously, it is possible to erase the batch data from the plurality of sectors and write the data thereinto simultaneously. Therefore, the semiconductor memory device which has the flash memory adopting the multi-valued structure can more shorten the processing time compared to the semiconductor memory device which has the flash memory adopting the binary-valued structure. [0009]
  • Furthermore, when the semiconductor memory devices having the flash memory are used, the host system often executes a file data management according to file allocation table (hereinafter referred to as FAT) file system, which is the commonest as a file management system for the hard disc device. [0010]
  • A partition in which the FAT file system is constructed (hereinafter referred to as a FAT partition) has a management data area (a partition boot record (hereinafter referred to as a PBR) area, a FAT area and the like), which is for storing management data, and a FAT file area for storing file data. The FAT file area among these areas is managed using each cluster composed of the plurality of sectors amounting to 4, 8, 16, 32 sectors in number and the like as a unit. [0011]
  • In a situation where the host system stores the file data in the FAT file area, a writing operation using each cluster as a unit is frequently performed. In the flash memory adopting the multi-valued structure, the number K (K: an integer equal to two or more) of the sectors constituting the erase block is normally set to a number so as to be able to divide the number J of the sectors constituting the cluster. Specifically, the number J of the sectors constituting the cluster is equal to K×L pieces (L: a positive integer). [0012]
  • Consideration will be given to the case where the host system allocates FAT partitions onto the flash memory mounted on the semiconductor memory device for managing file data using the FAT file system. [0013]
  • In the semiconductor memory device mounting the conventional flash memory, the host system allocated a logical address, which is used for the host system to manage a sector number, to a physical address having an equal value of the flash memory. [0014]
  • When such an allocation is performed, the following two cases are conceived with respect to a correlation between the cluster and the erase block in the FAT area. [0015]
  • In the [0016] case 1, the logical address of a head sector of a cluster and the physical address of a head sector of an eraser block correspond to each other. In the case 2, the logical address of the head sector of the cluster and the physical address so the head sector of the erase block do not correspond to each other.
  • For example, when the erase block consists of four sectors (K=4) and the cluster consists of eight sectors (J=8, L=2), one cluster consists of eight sectors included in continuous two erase blocks in the [0017] case 1 without any surplus or shortage. However, since the head of the cluster and the head of the erase block disagree with each other, one cluster consists of the middle eight sectors among the twelve sectors included in the three continuous erase blocks
  • To be specific, in the [0018] case 2, the clusters adjacent to each other (hereinafter referred to as clusters A and B) share one erase block (hereinafter referred to as a block M).
  • Here, among the four sectors constituting the block M, a sector portion included in the cluster A is set as a sector portion X, and a sector portion included in the cluster B is set as a sector Y. When the host system writes data into the cluster A, the data of the sector portion Y is erased as batch data of the block M irrespective of no necessity to rewrite the data of the sector portion Y, and the original data is written thereinto again. Furthermore, also when the host system writes data into the cluster B, the data of the sector portion X is erased as batch data of the block M irrespective of no necessity to rewrite the data of the sector portion X, and the original data is written thereinto again. [0019]
  • Accordingly, when the data is written into each cluster of the FAT file area evenly, the number of times of erasing/writing operations performed for each erase block shared by the clusters adjacent to each other such as the block M must be twice the number of times of erasing/writing operations performed for an erase block included in a single cluster (hereinafter referred to as a block N), and hence a life of a memory element in the block M is reduced by half compared to that in the block N in terms of probability. [0020]
  • Furthermore, though erasing and writing operations for the two erase blocks is necessary to write the data into one cluster in the [0021] case 1, erasing and writing operations for the three erase blocks is required to write the data into one cluster in the case 2. Accordingly, the speed of the writing operation is slower compared to that in the case 1.
  • SUMMARY OF THE INVENTION
  • The object of the present invention is to provide a semiconductor memory device capable of reducing the number of times of an erasing operation for each block or the number of blocks erased by one writing operation to the minimum. [0022]
  • The semiconductor memory device according to the present invention is accessed by using logical addresses from a host system which divides and manages file data by using clusters each of which is composed of a plurality of sectors and is a unit for dividing and managing and the semiconductor memory device comprises: a memory section composed of the plurality of sectors, which is capable of erasing data for each block; and a control section for transforming a logical address to a physical address so that the logical address of a head sector of the cluster corresponds to the physical address of a head sector of the block, and for accessing the memory section by using the physical address thus transformed. [0023]
  • In this case, the logical address may be transformed to the physical address by applying an address offset value to the logical address. [0024]
  • A computation of the address offset value may be executed by the use of total storage capacity information of the memory section immediately after beginning power supply. [0025]
  • Furthermore, by the use of information concerning a partition made on the memory section, the computation of the address offset value may be executed when the information concerning the partition is written. The information concerning the partition is, for example, data written into an address “0” of the logical address. [0026]
  • In a file system made on the memory section, the computation of the address offset value may be executed, by the use of management information used to manage the file data, when the management information is written. [0027]
  • The management information is, for example, data written into a logical address range occupied by a management data area of the file system. In a case where a file system is, for example, the FAT file system, the management information is data of the PBR. [0028]
  • An information processing device according to the present invention has a feature in that this device includes the semiconductor memory device as described above. [0029]
  • A host system according to the present invention divides and manages file data by using clusters each of which is composed of a plurality of sectors and is a unit for dividing and managing. When the host system accesses a memory section composed of the plurality of sectors which is capable of erasing data for each block, the host system transforms a logical address to a physical address so that the logical address of a head sector of the cluster corresponds to the physical address of a head sector of the block and accesses the memory section by using the physical address thus transformed[0030]
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a block diagram showing a semiconductor memory device according to the present invention. [0031]
  • FIG. 2 is a constitutional view showing a constitution of a flash memory. [0032]
  • FIG. 3 is a constitutional view showing a constitution of a flash memory array. [0033]
  • FIG. 4 is a constitutional view showing a constitution of the FAT file system. [0034]
  • FIG. 5 is a view illustrating a relation between a cluster and a block in the FAT file area disposed on the flash memory array. [0035]
  • FIG. 6 is a flowchart of a first address offset setting processing. [0036]
  • FIG. 7 is a table showing an example of a correspondence correlation between a logical address and a physical address. [0037]
  • FIG. 8 is a flowchart of a second address offset setting processing. [0038]
  • FIG. 9 is a table showing an example of a correspondence correlation between a logical address and a physical address. [0039]
  • FIG. 10 is a flowchart of a third address offset setting processing. [0040]
  • FIG. 11 is a table showing an example of a correlation between a logical address and a physical address. [0041]
  • FIG. 12 is a block diagram showing a semiconductor memory device and a host system.[0042]
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
  • Embodiments of the present invention will be described with reference to the accompanying drawings below. [0043]
  • FIG. 1 is a block diagram of a semiconductor memory device to which the present invention is applied. [0044]
  • As shown in FIG. 1, the [0045] semiconductor memory device 100 according to the present invention comprises: a host interface 3; a central processing unit (hereinafter referred to as a CPU) 6; a programmable read only memory (hereinafter referred to as a programmable ROM) 8; an address offset storage section 10; a buffer memory 12; a memory interface 15; and a flash memory 17. The CPU 6 and the address offset storage section 10 constitute a control section.
  • Furthermore, the [0046] semiconductor memory device 100 is connected to the host system 1 such as a personal computer via a bus 2, and receives a command from the host system 1. Moreover, the semiconductor memory device 100 exchanges data with the host system 1.
  • The [0047] bus 2 is used when the host system 1 accesses to the semiconductor memory device 100, and is, for example, a local bus of the host system 1 or a standard bus of a personal computer such as an Integrated Drive Electronic (IDE) bus, an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, a Small Computer System Interface (SCSI) bus, a PC card bus, and the like.
  • The [0048] host interface 3 is a hardware which transfers data sent via the bus 2 to the buffer memory 12 and transfers data stored in the buffer memory 12 to the bus 2.
  • The [0049] buffer memory 12 temporarily holds the data read out from the flash memory 17 and the data to be written into the flash memory 17, and comprises, for example, a static RAM (Random Access Memory).
  • The [0050] memory interface 15 is a hardware which transfers the data read out from the flash memory 17 to the buffer memory 12 and writes the data held by the buffer memory 12 into the flash memory 17.
  • The [0051] CPU 6 reads out a program stored in the programmable ROM 8, and performs a operation according to the program. For example, the CPU interprets a command and status of the host system 1 received via the host interface 3, and controls functions of the host interface 3 and memory interface 15 according to the result of interpretation. Furthermore, the CPU 6 reads out the data held in the buffer memory 12, and rewrites the data.
  • Furthermore, the [0052] CPU 6 transforms a logical address designated by the host system 1 to a physical address for accessing the flash memory 17, by the use of an address offset value stored in the address offset storage section 10. A method of computing the address offset value and a method of transforming the logical address to the physical address will be described later.
  • The address offset [0053] storage section 10 stores the address offset value used in transforming the logical address to the physical address, and comprises a non-volatile or volatile memory element. Note that the address offset storage section 10 may be provided as independent storage means or alternatively may be constituted by using a part of other memory such as the flash memory 17.
  • In the [0054] semiconductor memory device 100, the flash memory 17 stores file data and the like.
  • FIG. 2 is a constitutional view showing a constitution of the [0055] flash memory 17.
  • As shown in FIG. 2, the [0056] flash memory 17 comprises a flash memory array 18 and a data register 19.
  • The [0057] flash memory array 18 is an area for storing data, and constituted of a plurality of (erase) blocks 20.
  • The data register [0058] 19 temporarily holds data for reading out data from any or the blocks 20 and for storing the data in any of the blocks 20.
  • In the [0059] flash memory 17 shown in FIG. 2, writing of sector data for the designated physical address is performed in the following manner. All batch data of a block including sectors to which data is to be written is first transferred to the data register 19 of the flash memory 17. Thereafter, all data stored in the block of the flash memory array 18 is erased. A bit data of the block falls in an erase state, for example, all bit data becomes “1”. Reference numeral 21 of FIG. 2 illustrates a block in the erase state.
  • Next, among the data held in the data register [0060] 19, data of the sector to which data is to be written is rewritten in the data register 19, and all data in the data register 19 is written into the block 21. In the example of FIG. 2, writing is performed by inverting the bit data from “1” to “0” of the block 21 corresponding to the bit data “0” in the data register 19
  • FIG. 3 is a constitutional view showing a constitution of a [0061] flash memory array 18. As shown in FIG. 3, the flash memory array 18 comprises the plurality of blocks 20, and each of the blocks 20 comprises the four sectors 22, respectively. Note that each block may be comprised by any number of the sectors as long as the number of the sectors is two or more.
  • The [0062] sector 22 functions as a data unit when the host system 1 performs reading-out and writing of data for the semiconductor memory device 100, and having a data unit size of, for example, 512 bytes.
  • The [0063] sectors 22 comprising the flash memory array 18 are numbered in a sequentially ascending order from 0h, respectively, and the sector number is called a physical address.
  • When the [0064] host system 1 performs the reading-out and writing of the data from and to the semiconductor memory device 100, using the sector as a unit, the sector number managed by the host system 1 is called a logical address, which starts from 0h as a starting point. The host system 1 specifies the logical address, and performs reading-out and writing of data from and to the semiconductor memory device 100.
  • Next, an operation of the [0065] semiconductor memory device 100 will be described when the host system 1 issues an instruction to the semiconductor memory device 100 so as to perform writing of data.
  • When a command for requesting writing of data to the specified logical address is sent from the [0066] host system 1 to the semiconductor memory device 100, the CPU 6 acquires the logical address via the host interface 3, and transforms the logical address to the physical address corresponding thereto.
  • Specifically, the [0067] CPU 6 reads out the address offset value stored in the address offset storage section 10, and adds the address offset value to the logical address value, thus generating the physical address.
  • The writing data transferred from the [0068] host system 1 is held in the buffer memory 12 via the host interface 3. The CPU 6 controls the memory interface 15 so that the data in the buffer memory 12 is written into the physical address after the address transformation, and writes the data into the specified physical address of the flash memory 17.
  • Next, a method of computing the address offset value used for the address transformation will be described. [0069]
  • For the sake of understanding this method in more detail, descriptions for a file system prepared in the [0070] semiconductor memory device 100 will be made. A system in which the host system 1 manages file data on the flash memory array 18 of the flash memory 17 is called a file system. The plurality of file systems can be prepared on the flash memory array 18, and a logical address range for placing a certain file system is called a partition.
  • Here, a case where the FAT file system is adopted as the file system is explained. [0071]
  • FIG. 4 is a constitutional view showing a constitution of the FAT file system. FIG. 4 shows an example in which one [0072] FAT partition 25 is prepared on the flash memory 18. The FAT partition 25 is a partition occupied by the FAT file system.
  • In FIG. 4, the logical address range of the [0073] FAT partition 25 covers from 20h to 1E7Fh. The FAT partition 25 comprises a PBR 26, a FAT area I 27, a FAT area II 28, a route directory area 29 and the FAT file area 30.
  • The [0074] PBR 26 is a data stored in a head logical address of the FAT partition 25. In FIG. 4, the logical address of the PBR 26 is 20h. In the PBR 26, included is information from which the logical address ranges of the FAT area I 27, FAT area II 28, route directory area 29 and FAT file area 30 of the FAT partition 25 can be known, respectively.
  • The [0075] FAT file area 30 is an area for storing file data. In FIG. 4, the logical address range of the FAT file area 30 covers from 47h to 1E7Fh.
  • The [0076] host system 1 manages the FAT file area 30 using clusters 31 each of which is a unit for managing, and writes file data into the FAT file area 30 using clusters 31 each of which is as a unit for writing.
  • Here, each [0077] cluster 31 shall be composed of eight sectors 22. Note that the number of the sectors 22 constituting the cluster 31 may be any number as long as it is natural number-times of the number of the sectors 22 constituting the block 20.
  • The FAT area I [0078] 27 is an area for storing table data indicating a usage state of each of the clusters 31. In FIG. 4, the logical address range of the FAT area I 27 covers from 21h to 23h.
  • The FAT area II [0079] 28 is an area for storing a copy of data of the FAT area I 27. In FIG. 4, the logical address range thereof covers from 24h to 26h.
  • The [0080] route directory area 29 is an area for storing data indicating information pertaining to a file and a sub-directory in a route directory of the FAT partition 25. In FIG. 4, the logical address range thereof covers from 27h to 46h.
  • When the [0081] host system 1 prepares a file system on the semiconductor memory device 100, the host system 1 first allocates a partition to an empty logical address range on the flash memory array 18. In this case, the empty logical address range means a logical address range to which another partition is not allocated. Then, the host system 1 formats this partition. The word “format” means that the logical address ranges of the PBR 26, FAT area I 27, FAT area II 28 and route directory area 29 are allocated onto the partition and initialization data for managing file data is written into these areas.
  • A master boot record (hereinafter referred to as MBR) [0082] 23 is data stored in the logical address 0h. Within a logical address range in which the host system 1 can store file data, the MBR 23 includes information indicating the logical address range of each of the partitions and sorts of the file systems existing in the logical address range. The host system 1 rewrites the data of the MBR 23 when the host system 1 performs the allocation of the partition to the empty logical address range, the format of the partition, deletion of the existing partition and the like.
  • When the FAT file system as described above is prepared in the [0083] semiconductor memory device 100, the CPU 6 computes an address offset value that satisfies the following conditions. To be specific, the address offset value serves so as to make a head logical address of the FAT file area 30 correspond to a physical address of a head sector of a certain block 20 when the address offset value is added up. By computing the address offset value satisfying the above conditions, the destination of the logical address of the head sector of each cluster 31 which constitutes the FAT file area 30 always agrees with the physical address of the head sector of the corresponding one of the blocks 20.
  • FIG. 5 is a view illustrating a correlation between a [0084] block 20 of the flash memory 17 and a cluster 31 in a FAT file area 30 under the above-described conditions. FIG. 5 shows a case where the block 20 consists of four sectors and the cluster 31 consists of eight sectors. Each of the clusters 31 consists of just two blocks 20.
  • With such constitution, the data of the sector which is not included in the cluster to which the data is written is never erased in writing process using a cluster as a unit for writing. Accordingly, effects can be achieved, in which the foregoing problem of reducing the life of the memory element can be solved and the number of the blocks to which the data is written for each cluster becomes minimum, thus shortening the processing time. [0085]
  • Subsequently, the details of an address offset setting processing for computing the address offset value will be described. FIG. 6 is a flowchart of the address offset setting processing. [0086]
  • When power supply to the [0087] semiconductor memory device 100 starts (S32), the CPU 6 first checks the number of memory chips constituting the flash memory 17 and a capacity of each of the memory chips (S33). Checking is carried out by reading out, for example, capacity information from each memory chip.
  • Then, the total of the memory capacity capable of preparing the file system in the [0088] flash memory 17 is computed (S34). Next, when one FAT partition 25 is prepared using the total of the computed memory capacity, computed is the logical address range occupied by the PBR 26, the FAT area I 27, the FAT area II 28 and the route directory area 29, and a starting logical address value of the FAT area 30 is calculated (S35).
  • Subsequently, it is decided whether a sector having a value, equal to the starting logical address value, as a physical address, is a head address of a block. If the sector is not the head address of the block, the starting logical address value is subtracted from a physical address value of a head sector of each block following the block concerned, and an address offset value is computed (S[0089] 36). The computed address offset value is stored in the address offset storage section 10 (S37).
  • Thereafter, the [0090] CPU 6 transforms the logical address specified by the host system 1 to the physical address having a value obtained by adding the address offset value stored in the address offset storage section 10 to this logical address, and accesses the flash memory 17 using the physical address thus transformed.
  • FIG. 7 shows an example of correlation between logical addresses of the head sectors of the [0091] MBR 23, the areas 26 to 30 of the FAT partition and the head sectors of clusters 31, and physical addresses corresponding to them, when the host system 1 allocates all flash memory areas to one partition and formats this partition by the FAT.
  • In this case, since the [0092] block 20 consists of four sectors, a sector having the physical address whose value is a multiple of four is a head sector of the block 20. Since a sector having the physical address whose value is equal to the head logical address 47h of the FAT file area 30 is not the head sector of the block 20, for example, “1” obtained by subtracting the physical address value 47h from the physical address value 48h of the head sector of the next block 20 is set as the address offset value.
  • By adding “1” that is the address offset value to the logical address, the head logical address of each [0093] cluster 31 constituting the FAT file area 30 is transformed so as to correspond to the physical address of the head sector of the block 20. Accordingly, the above described conditions of the address offset value are satisfied. Although, in the embodiment, the address offset value is applied to the whole of the logical address range, the address offset value may be applied to any range as long as the address offset value is applied at least to the logical address range occupied by the FAT file area 30.
  • Next, a second address offset setting processing which can be applied to the present invention similarly to the foregoing address offset setting processing will be described. [0094]
  • FIG. 8 is a flowchart of a second address offset setting processing. The second address offset setting processing computes by the use of data an address offset value when the data is written into the [0095] MBR 23.
  • When a new partition is prepared on the flash memory array [0096] 18 (S38), the host system 1 writes data including information pertaining to a logical address range of the partition into the MBR 23 having a logical address 0h. Specifically, the host system 1 sends the CPU 6 a command to write data into the logical address 0h (S39).
  • When the [0097] CPU 6 is instructed to write the data into the logical address 0h, the CPU 6 writes data held in the buffer memory 12 into the physical address 0h of the flash memory 17, and reads out the data to analyze the data. Thus, the CPU 6 knows the logical address range of the partition newly prepared (S40). Then, the CPU 6 computes the logical address range occupied by the PBR 26, the FAT area I 27, the FAT area II 28 and the route directory area 29 when this partition is formatted by the FAT, and computes the starting logical address value of the FAT file area 30 (S41).
  • Then, when a physical address whose value is equal to the starting logical address value does not correspond to a head sector of the block, the [0098] CPU 6 subtracts the starting logical address value from physical address value of a head sector of each block following the block concerned, and computes the address offset value (S42). The CPU 6 allows the address offset storage section 10 to store the computed address offset value therein (S43).
  • Thereafter, the [0099] CPU 6 transforms the logical address within a range occupied by the FAT partition 25 to a physical address having a value obtained by adding the address offset value stored in the address offset storage section 10 to this logical address, and accesses the flash memory 17 using the physical address thus transformed.
  • FIG. 9 shows an example of correlation between the logical addresses of the head sectors of the [0100] MBR 23, the areas 26 to 30 of the FAT partition and the clusters 31, and the physical addresses corresponding to them.
  • FIG. 9 is identical to FIG. 7 except that the address offset value is not added to the [0101] MBR 23. With respect to the range to which the address offset is applied, the address offset value may be applied to any range as long as the address offset value is applied at least to the logical address range occupied by the FAT file area 30. For example, similarly to FIG. 7, data of the MBR 23 may be written into the physical address 1h.
  • Furthermore, a third address offset setting processing which is applicable to the present invention will be described. FIG. 10 is a flowchart of the third address offset setting processing. The third address offset setting processing computes the address offset value by the use of the data of the PBR in formatting the partition. [0102]
  • When the [0103] host system 1 formats the partition on the flash memory 18 with the FAT (S44), data including information pertaining to the logical address range of each area of the FAT partition is written into the PBR 26 located at the head logical address of the partition (S45).
  • When a command to write data into a certain logical address is sent from the [0104] host system 1 to the semiconductor memory device 100, the CPU 6 checks whether the certain logical address is a head logical address of the partition. As a result of the check, if the certain logical address is the head logical address of the partition, the CPU 6 reads out the data held by the buffer memory 12 and analyzes the read-out data, and checks whether the read-out data is data corresponding to the PBR 26 of the FAT file system (S46).
  • Thus, when the [0105] CPU 6 detects that the partition is formatted with the FAT, the CPU 6 writes the PBR data held by the buffer memory 12 into a physical address whose value is equal to the head logical address value of the partition, and calculates, based on the PBR data, the logical address range occupied by the FAT area I 27, the FAT area II 28 and the route directory area 29, which constitute the FAT partition 25, thus computing a starting logical address value of the FAT file area 30 (S47).
  • Then, if a physical address whose value is equal to the computed starting logical address value is not a head address of a block, the [0106] CPU 6 subtracts the starting logical address value from a physical address value of a head sector of each block following the block concerned, and computes an address offset value (S48), thus allowing the address offset storage section 10 to store the computed address offset value therein (S49).
  • Thereafter, the [0107] CPU 6 transforms the logical address within a range occupied by the FAT partition 30 to a physical address having a value obtained by adding the offset address value stored in the address offset storage section 10 to this logical address, and accesses the flash memory 17 using the physical address thus transformed.
  • FIG. 11 shows an example of correlation between logical addresses of the head sectors of the [0108] MBR 23, the areas 26 to 30 of the FAT partition and the clusters 31, and physical addresses corresponding to then.
  • As shown in FIG. 11, in this case, the address offset value is applied only to the logical address range occupied by the [0109] FAT file area 30. Note that the address offset value may be applied to other areas, for example, an area ranging from the PBR area 26, as shown in FIG. 9.
  • In the above descriptions, the [0110] CPU 6 in the semiconductor memory device 100 performs the computation of the address offset value, the address transformation and the like. However, a CPU outside the semiconductor memory device may perform a part of these functions or all of these functions.
  • FIG. 12 is a block diagram showing constitutions of the semiconductor memory device and the host system in the case where the address transformation is performed in the host system. [0111]
  • As shown in FIG. 12, the [0112] host system 1 a comprises a host CPU 50, the address offset storage section 10 and the buffer memory 12.
  • On the other hand, a [0113] semiconductor memory device 100 a, comprises the memory interface 15 and the flash memory 17. Note that the buffer memory 12 and the like may be provided in the semiconductor memory device 100 a.
  • The [0114] CPU 50 of the host system 1 a performs a processing identical to that performed by the foregoing CPU 6, and accesses the flash memory 17 in the semiconductor memory device 100 a by the use of a physical address that has been undergone the address transformation. Thus, the same effects can be achieved also in the semiconductor memory device 100 a as in the foregoing semiconductor memory device 100.
  • In the above descriptions, though the FAT file system was described as the file data management system, the present invention can be applied to other file systems as long as applied is a file data management system in which a case where a head of unit of a file data area such as a cluster does not coincide with a head of a batch erasable/writable block of a flash memory occurs and in which a logical address occupied by a file data area can be computed by the use of management data. [0115]
  • The memory section constituting the semiconductor memory device according to the present invention is not limited to a flash memory. The memory section may be the one which performs the erasion for each block constituted by two or more sectors in writing data. [0116]
  • As described above, according to the present invention, even when the host system performs writing of file data for each cluster constituted by the plurality of blocks for the semiconductor memory device mounting the memory section in which the erasion/writing is performed for each block constituted by the plurality of sectors, it is possible to reduce the number of erasion times of each block to the minimum, and a reduction of a life of the block can be prevented. In addition, the number of the blocks in which the simultaneous erasion/writing is performed can be reduced to the minimum for one writing, and a processing time required for the writing can be shortened. [0117]

Claims (10)

What we claimed is:
1. A semiconductor memory device accessible by the use of logical addresses from a host system which divides and manages file data by the use of clusters each of which is composed of a plurality of sectors and is a unit for division and management of the file data, comprising:
a memory section composed of the plurality of sectors, and capable of erasing data stored therein for each block; and
a control section for transforming a logical address received by the host system to a physical address so that a logical address of a head sector of said cluster corresponds to a physical address of a head sector of said block, and for accessing the memory section by the use of the physical address thus transformed.
2. The semiconductor memory device in accordance with
claim 1
, wherein said logical address is transformed to said physical address by applying an address offset value to said logical address.
3. The semiconductor memory device in accordance with
claim 2
, wherein a computation of said address offset value is executed by the use of information concerning total storage capacity of said memory section immediately after beginning power supply.
4. The semiconductor memory device in accordance with
claim 2
, wherein a computation of said address offset value is executed by the use of information concerning a partition prepared on said memory section.
5. The semiconductor memory device in accordance with
claim 4
, wherein the computation of said address offset value is executed when the information pertaining to said partition is written.
6. The semiconductor memory device in accordance with
claim 5
, wherein the information pertaining to said partition is data written into an address “0” of said logical address.
7. The semiconductor memory device in accordance with
claim 2
, wherein a computation of said address offset value is executed by the use of managing information used for managing said file data in a file system prepared on said memory section.
8. The semiconductor memory device in accordance with
claim 7
, wherein the computation of said address offset value is executed when said managing information is written.
9. An information processing device comprising:
the semiconductor memory device in accordance with any one of
claims 1
to
8
.
10. A host system which divides and manages file data using clusters each of which is composed of a plurality of sectors and is a unit for division and management of the file data, wherein in accessing a memory device which is composed of a plurality of sectors and is capable of erasing data for each block, a logical address is transformed to a physical address so that a logical address of a head sector of said cluster corresponds to a physical address of a head sector of said block, and then accesses said memory device by the use of the physical address thus transformed.
US09/779,610 2000-06-06 2001-02-09 Semiconductor memory device with block alignment function Expired - Fee Related US6459644B2 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2000-169289 2000-06-06
JP2000169289A JP3942807B2 (en) 2000-06-06 2000-06-06 Semiconductor memory device with block alignment function

Publications (2)

Publication Number Publication Date
US20010048121A1 true US20010048121A1 (en) 2001-12-06
US6459644B2 US6459644B2 (en) 2002-10-01

Family

ID=18672171

Family Applications (1)

Application Number Title Priority Date Filing Date
US09/779,610 Expired - Fee Related US6459644B2 (en) 2000-06-06 2001-02-09 Semiconductor memory device with block alignment function

Country Status (4)

Country Link
US (1) US6459644B2 (en)
JP (1) JP3942807B2 (en)
KR (1) KR100441587B1 (en)
TW (1) TWI221553B (en)

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030101313A1 (en) * 2001-11-27 2003-05-29 Fujitsu Limited Memory system
US20040193781A1 (en) * 2003-03-31 2004-09-30 Samsung Electronics Co., Ltd. Flash memory access apparatus and method
EP1492014A1 (en) * 2002-04-03 2004-12-29 Sony Corporation Recording apparatus and method, recording medium, and program
EP1498817A1 (en) * 2002-04-15 2005-01-19 Sony Corporation Data storage device
US20060253643A1 (en) * 2005-05-04 2006-11-09 Delkin Devices, Inc. Memory with isolated master boot record
US20080201392A1 (en) * 2007-02-19 2008-08-21 Hitachi, Ltd. Storage system having plural flash memory drives and method for controlling data storage
US20120226887A1 (en) * 2011-03-06 2012-09-06 Micron Technology, Inc. Logical address translation
US20130254465A1 (en) * 2009-01-21 2013-09-26 Micron Technology, Inc. Solid state memory formatting
US8683173B2 (en) 2009-01-21 2014-03-25 Micron Technology, Inc. Logical address offset in response to detecting a memory formatting operation
US20230135096A1 (en) * 2021-11-04 2023-05-04 International Business Machines Corporation File Based Virtual Disk Management
CN116798468A (en) * 2016-11-11 2023-09-22 美光科技公司 Apparatus and method for memory alignment

Families Citing this family (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100716576B1 (en) * 1999-02-22 2007-05-11 가부시키가이샤 히타치세이사쿠쇼 Memory card, method for allotting logical address, and method for writing data
US7203729B2 (en) * 2001-04-20 2007-04-10 Motorola Inc. Method and apparatus for a communication network with nodes capable of selective cluster head operation
JP4009840B2 (en) * 2002-06-27 2007-11-21 ソニー株式会社 Information processing apparatus, information processing method, and information processing program
US7173852B2 (en) * 2003-10-03 2007-02-06 Sandisk Corporation Corrected data storage and handling methods
US8001325B2 (en) * 2004-01-09 2011-08-16 Sandisk Corporation Memory card that supports file system interoperability
US7200703B2 (en) * 2004-06-08 2007-04-03 Valmiki Ramanujan K Configurable components for embedded system design
US7315916B2 (en) * 2004-12-16 2008-01-01 Sandisk Corporation Scratch pad block
US7366826B2 (en) * 2004-12-16 2008-04-29 Sandisk Corporation Non-volatile memory and method with multi-stream update tracking
US7386655B2 (en) * 2004-12-16 2008-06-10 Sandisk Corporation Non-volatile memory and method with improved indexing for scratch pad and update blocks
US7395404B2 (en) * 2004-12-16 2008-07-01 Sandisk Corporation Cluster auto-alignment for storing addressable data packets in a non-volatile memory array
US7412560B2 (en) * 2004-12-16 2008-08-12 Sandisk Corporation Non-volatile memory and method with multi-stream updating
KR100684887B1 (en) * 2005-02-04 2007-02-20 삼성전자주식회사 Data storing device including flash memory and merge method of thereof
US8122193B2 (en) 2004-12-21 2012-02-21 Samsung Electronics Co., Ltd. Storage device and user device including the same
WO2007000862A1 (en) * 2005-06-24 2007-01-04 Matsushita Electric Industrial Co., Ltd. Memory controller, nonvolatile storage device, nonvolatile storage system, and data writing method
US7457910B2 (en) * 2005-06-29 2008-11-25 Sandisk Corproation Method and system for managing partitions in a storage device
KR100739722B1 (en) * 2005-08-20 2007-07-13 삼성전자주식회사 A method for managing a flash memory and a flash memory system
US20070174549A1 (en) * 2006-01-24 2007-07-26 Yevgen Gyl Method for utilizing a memory interface to control partitioning of a memory module
JP2007233838A (en) * 2006-03-02 2007-09-13 Toshiba Corp Control method for memory system
JP2008112285A (en) * 2006-10-30 2008-05-15 Toshiba Corp Non-volatile memory system
JP4991320B2 (en) * 2007-01-12 2012-08-01 株式会社東芝 Host device and memory system
KR101449524B1 (en) 2008-03-12 2014-10-14 삼성전자주식회사 Storage device and computing system
TWI415134B (en) * 2008-04-10 2013-11-11 Phison Electronics Corp Data accessing method, controller and system using the same
CN101866269A (en) * 2009-04-16 2010-10-20 鸿富锦精密工业(深圳)有限公司 Storing device, storing system and method for controlling storing device
US8856488B2 (en) 2010-02-11 2014-10-07 Memory Technologies Llc Method for utilizing a memory interface to control partitioning of a memory module
TWI420305B (en) * 2010-10-08 2013-12-21 Phison Electronics Corp Memory storage device, memory controller thereof, and method for creating fill-file automatically thereof
US8626989B2 (en) * 2011-02-02 2014-01-07 Micron Technology, Inc. Control arrangements and methods for accessing block oriented nonvolatile memory
TWI515736B (en) * 2013-07-25 2016-01-01 慧榮科技股份有限公司 Data storage device and flash memory control method
CN108845959B (en) * 2018-06-25 2023-06-23 联想(北京)有限公司 Memory data processing method and device and electronic equipment

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5303198A (en) 1990-09-28 1994-04-12 Fuji Photo Film Co., Ltd. Method of recording data in memory card having EEPROM and memory card system using the same
GB2251323B (en) * 1990-12-31 1994-10-12 Intel Corp Disk emulation for a non-volatile semiconductor memory
JP2856621B2 (en) 1993-02-24 1999-02-10 インターナショナル・ビジネス・マシーンズ・コーポレイション Batch erase nonvolatile memory and semiconductor disk device using the same
JP3078946B2 (en) * 1993-03-11 2000-08-21 インターナショナル・ビジネス・マシーンズ・コーポレ−ション Managing method of batch erase nonvolatile memory and semiconductor disk device
US5799140A (en) * 1995-04-21 1998-08-25 International Business Machines Corporation Disk array system and method for storing data
US5907856A (en) * 1995-07-31 1999-05-25 Lexar Media, Inc. Moving sectors within a block of information in a flash memory mass storage architecture
US5835935A (en) 1995-09-13 1998-11-10 Lexar Media, Inc. Method of and architecture for controlling system data with automatic wear leveling in a semiconductor non-volatile mass storage memory
JPH10124384A (en) * 1996-08-28 1998-05-15 Toshiba Corp Method for controlling non-volatile semiconductor memory
US5937423A (en) * 1996-12-26 1999-08-10 Intel Corporation Register interface for flash EEPROM memory arrays
JP3588231B2 (en) 1997-08-04 2004-11-10 東京エレクトロンデバイス株式会社 Data processing system and block erase type storage medium
JP4079506B2 (en) 1997-08-08 2008-04-23 株式会社東芝 Method for controlling nonvolatile semiconductor memory system
KR100319598B1 (en) * 1998-03-18 2002-04-06 김영환 Flash memory array access method and device
EP0997904B1 (en) * 1998-10-22 2001-12-12 Matsushita Electric Industrial Co., Ltd. Information recording medium, and method and apparatus for managing defect thereof

Cited By (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7046574B2 (en) * 2001-11-27 2006-05-16 Fujitsu Limited Memory system
US20030101313A1 (en) * 2001-11-27 2003-05-29 Fujitsu Limited Memory system
EP1492014A1 (en) * 2002-04-03 2004-12-29 Sony Corporation Recording apparatus and method, recording medium, and program
EP1492014A4 (en) * 2002-04-03 2007-06-06 Sony Corp Recording apparatus and method, recording medium, and program
US7472251B2 (en) 2002-04-15 2008-12-30 Sony Corporation Data storage apparatus detachably mounted to a host apparatus
EP1498817A1 (en) * 2002-04-15 2005-01-19 Sony Corporation Data storage device
US20050080985A1 (en) * 2002-04-15 2005-04-14 Junko Sasaki Data storage device
KR100975178B1 (en) * 2002-04-15 2010-08-10 소니 주식회사 Data storage device
EP1498817A4 (en) * 2002-04-15 2007-07-11 Sony Corp Data storage device
US20040193781A1 (en) * 2003-03-31 2004-09-30 Samsung Electronics Co., Ltd. Flash memory access apparatus and method
US7664906B2 (en) 2003-03-31 2010-02-16 Samsung Electronics Co., Ltd. Flash memory access apparatus and method
WO2006119282A2 (en) * 2005-05-04 2006-11-09 Delkin Devices, Inc. Memory with isolated master boot record
WO2006119282A3 (en) * 2005-05-04 2008-01-31 Delkin Devices Inc Memory with isolated master boot record
US20060253643A1 (en) * 2005-05-04 2006-11-09 Delkin Devices, Inc. Memory with isolated master boot record
US7831764B2 (en) 2007-02-19 2010-11-09 Hitachi, Ltd Storage system having plural flash memory drives and method for controlling data storage
US20080201392A1 (en) * 2007-02-19 2008-08-21 Hitachi, Ltd. Storage system having plural flash memory drives and method for controlling data storage
US8683173B2 (en) 2009-01-21 2014-03-25 Micron Technology, Inc. Logical address offset in response to detecting a memory formatting operation
US9626287B2 (en) * 2009-01-21 2017-04-18 Micron Technology, Inc. Solid state memory formatting
US8930671B2 (en) 2009-01-21 2015-01-06 Micron Technology, Inc. Logical address offset in response to detecting a memory formatting operation
US20130254465A1 (en) * 2009-01-21 2013-09-26 Micron Technology, Inc. Solid state memory formatting
US20120226887A1 (en) * 2011-03-06 2012-09-06 Micron Technology, Inc. Logical address translation
CN103502958A (en) * 2011-03-06 2014-01-08 美光科技公司 Logical address translation
US8732431B2 (en) * 2011-03-06 2014-05-20 Micron Technology, Inc. Logical address translation
TWI459200B (en) * 2011-03-06 2014-11-01 Micron Technology Inc Logical address translation
WO2012121968A3 (en) * 2011-03-06 2012-11-22 Micron Technology, Inc. Logical address translation
US9164701B2 (en) 2011-03-06 2015-10-20 Micron Technology, Inc. Logical address translation
WO2012121968A2 (en) 2011-03-06 2012-09-13 Micron Technology, Inc. Logical address translation
CN116798468A (en) * 2016-11-11 2023-09-22 美光科技公司 Apparatus and method for memory alignment
US20230135096A1 (en) * 2021-11-04 2023-05-04 International Business Machines Corporation File Based Virtual Disk Management
US11816363B2 (en) * 2021-11-04 2023-11-14 International Business Machines Corporation File based virtual disk management

Also Published As

Publication number Publication date
KR20010110073A (en) 2001-12-12
US6459644B2 (en) 2002-10-01
TWI221553B (en) 2004-10-01
JP3942807B2 (en) 2007-07-11
KR100441587B1 (en) 2004-07-23
JP2001350665A (en) 2001-12-21

Similar Documents

Publication Publication Date Title
US6459644B2 (en) Semiconductor memory device with block alignment function
EP0770959B1 (en) Flash translation layer clean-up method
US6262918B1 (en) Space management for managing high capacity nonvolatile memory
US6134151A (en) Space management for managing high capacity nonvolatile memory
US5953737A (en) Method and apparatus for performing erase operations transparent to a solid state storage system
US5812814A (en) Alternative flash EEPROM semiconductor memory system
US7392343B2 (en) Memory card having a storage cell and method of controlling the same
EP1561168B1 (en) Method and apparatus for splitting a logical block
US5598370A (en) Nonvolatile memory with cluster-erase flash capability and solid state file apparatus using the same
US7388792B2 (en) Memory management device and memory device
JP5823875B2 (en) Solid memory formatting
US6202138B1 (en) Increasing the memory performance of flash memory devices by writing sectors simultaneously to multiple flash memory devices
EP0522780B1 (en) Control method for a computer memory device
US8539140B2 (en) Storage device including flash memory and capable of predicting storage device performance based on performance parameters
US9396103B2 (en) Method and system for storage address re-mapping for a memory device
US6477632B1 (en) Storage device and accessing method
US7814264B2 (en) Memory card, semiconductor device, and method of controlling semiconductor memory
US20050172068A1 (en) Memory card and semiconductor device
CN113986773A (en) Write amplification optimization method and device based on solid state disk and computer equipment
JP2000181784A (en) Non-volatile storage device which can be rewritten
JPH05150913A (en) Silicon disk with flash memory as storage medium
US6898680B2 (en) Minimization of overhead of non-volatile memory operation
JPH05250884A (en) Nonvolatile storage device

Legal Events

Date Code Title Description
AS Assignment

Owner name: HITACHI, LTD., JAPAN

Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE SERIAL NUMBER, ERROUNEOUSLY RECORDED AT REEL 012773, FRAME 0944;ASSIGNORS:MIZUSHIMA, NAGAMASA;FURUSAWA, KAZUNORI;TAMURA, TAKAYUKI;AND OTHERS;REEL/FRAME:013016/0288;SIGNING DATES FROM 20010419 TO 20010424

AS Assignment

Owner name: RENESAS TECHNOLOGY CORPORATION, JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HITACHI, LTD.;REEL/FRAME:014569/0186

Effective date: 20030912

FEPP Fee payment procedure

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

FPAY Fee payment

Year of fee payment: 4

FPAY Fee payment

Year of fee payment: 8

AS Assignment

Owner name: RENESAS ELECTRONICS CORPORATION, JAPAN

Free format text: MERGER AND CHANGE OF NAME;ASSIGNOR:RENESAS TECHNOLOGY CORP.;REEL/FRAME:025114/0629

Effective date: 20100401

REMI Maintenance fee reminder mailed
LAPS Lapse for failure to pay maintenance fees
STCH Information on status: patent discontinuation

Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FP Lapsed due to failure to pay maintenance fee

Effective date: 20141001