CN107908364B - Embedded file system based on norflash - Google Patents

Embedded file system based on norflash Download PDF

Info

Publication number
CN107908364B
CN107908364B CN201711115807.XA CN201711115807A CN107908364B CN 107908364 B CN107908364 B CN 107908364B CN 201711115807 A CN201711115807 A CN 201711115807A CN 107908364 B CN107908364 B CN 107908364B
Authority
CN
China
Prior art keywords
file
sector
directory
files
information
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.)
Active
Application number
CN201711115807.XA
Other languages
Chinese (zh)
Other versions
CN107908364A (en
Inventor
周悟强
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.)
CETC 30 Research Institute
Original Assignee
CETC 30 Research Institute
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 CETC 30 Research Institute filed Critical CETC 30 Research Institute
Priority to CN201711115807.XA priority Critical patent/CN107908364B/en
Publication of CN107908364A publication Critical patent/CN107908364A/en
Application granted granted Critical
Publication of CN107908364B publication Critical patent/CN107908364B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • 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/0602Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0614Improving the reliability of storage systems
    • 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/0602Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0614Improving the reliability of storage systems
    • G06F3/0616Improving the reliability of storage systems in relation to life time, e.g. increasing Mean Time Between Failures [MTBF]
    • 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/0602Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/062Securing storage systems
    • 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/0629Configuration or reconfiguration of storage systems
    • G06F3/0631Configuration or reconfiguration of storage systems by allocating resources to storage systems
    • 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/0629Configuration or reconfiguration of storage systems
    • G06F3/0637Permissions
    • 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/0638Organizing or formatting or addressing of data
    • G06F3/0643Management of files
    • 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/0638Organizing or formatting or addressing of data
    • G06F3/0644Management of space entities, e.g. partitions, extents, pools
    • 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/0646Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
    • G06F3/0652Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket
    • 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/0668Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/0671In-line storage system
    • G06F3/0673Single storage device
    • G06F3/0679Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]

Abstract

The invention discloses an embedded file system based on norflash, which comprises the following contents: firstly, sector management: each sector comprises sector head information, and the sector head information comprises a sector state, a sector number id, erasing times, a backup sector id, backup sector erasing times and head structure verification information; secondly, file management: all files and folders are numbered and the file directory and files are stored contiguously after the sector header information. The invention can easily realize embedded application and meet the basic requirement of a user on the file storage management in the large-sector norflash memory. The sector damage can be immediately discovered during file operation, and the sector is dynamically replaced; the memory occupies small space and does not need to buffer a sector, the sector erasing is balanced, and the requirement on a file system in a small system can be well met.

Description

Embedded file system based on norflash
Technical Field
The invention relates to an embedded file system based on norflash.
Background
Embedded microprocessors typically have a small memory (KB level), and norflash is widely used as a memory device for embedded systems. Generally, in a small embedded system, since a norflash sector block is too large (64 KB is common), and the total number of storage sectors is not large, it is not good to port a commercial file system such as fat in practical application, and such a file system often uses the whole sector as a storage unit, the RAM occupies too large for a microprocessor, and the utilization of the norflash small file is not sufficient. It is therefore common practice in embedded systems for such applications to: when there is a norflash to store application data, the use function of each sector is generally fixed and defined by a program, and the position of the sector is determined in advance for the storage of files. Such storage has no flexibility, operates frequently on the same sector, is difficult to work normally when a selected sector is damaged, and is very disadvantageous to storage management such as modification of files.
Disclosure of Invention
In order to overcome the defects in the prior art, the invention provides an embedded file system based on norflash, which can easily realize embedded application and meet the basic requirements of a user on file storage management in a large-sector norflash memory. The sector damage can be immediately discovered during file operation, and the sector is dynamically replaced; the memory occupies small space and does not need to buffer a sector, the sector erasing is balanced, and the requirement on a file system in a small system can be well met.
The technical scheme adopted by the invention for solving the technical problems is as follows: an embedded file system based on norflash comprises the following contents:
firstly, sector management: each sector comprises sector head information, and the sector head information comprises a sector state, a sector number id, erasing times, a backup sector id, backup sector erasing times and head structure verification information;
secondly, file management: all files and folders are numbered, a file directory and the files are continuously stored in sector header information, the files are divided into a file header information part and a file fragmentation part, the file header information part comprises total file length information, and the file fragmentation part comprises file fragmentation header information.
Compared with the prior art, the invention has the following positive effects: the invention establishes a file system for the norflash in the embedded system, the file system has simple format and is easy to understand, the sector and the file system are managed uniformly, the sector resources are fully utilized, and the erasing balance is realized. And only modifying the mark for deleting the file, redistributing the sectors to erase the original sectors when the file is modified, and managing the bad areas of the sectors which fail in write operation. The file system can easily construct directory structure and locate search through specially designed files or file cartridge information. The concrete expression is as follows:
(1) one sector can store a plurality of files or directories, and the space of the large sector is fully utilized. The use condition of each sector can be easily obtained by analyzing the length of each information head of each sector, and files and file head information only need to be written in the blank area of the sector when the files are established.
(2) When the file is modified, the memory occupation is small, and the sector data is not required to be buffered. When the file is deleted, the file state is only marked, when the sector needs to be copied to a new sector, the file with the deletion identifier is not copied, and the file is really deleted after the sector is erased. When the file is modified, a new sector is allocated, and the ID and the erasing times of the sector where the original file is located are written into the backup information head of the newly allocated sector. Copying all effective files except the file in the sector where the original file is located to a newly allocated sector, copying the part of the original file which does not need to be modified to a new sector, writing the newly modified part file into the new sector, and constructing the header information of the newly written file. The original sector is deleted and put into the free sector management list. The technology does not need to buffer the content of a sector for modification after erasure, so that the RAM occupation is small, and the sector can not be used repeatedly.
(3) Each sector stores the serial number and the erasing times of the sector, the management of the idle sectors is sequenced, the sector with less erasing times is placed at the head of a queue and is firstly used during distribution, and the erasing balance is realized. And the sector with the error in the sector writing operation is subjected to bad area management and is not used next time.
(4) The file directory stores pin codes and access authority control attributes, authority management can be achieved when all files in the directory are accessed, and the pin codes store conversion data of passwords.
The operation interface of the file system is simple and easy to understand, common function interfaces such as directory and file traversal are provided, and the file system is convenient to use, flexible and cuttable. The size of the file system, the characteristics of the norflash and the access interface are set during the initialization of the file system in a registration mode, so that the transplantation of various norflash on an embedded system can be realized, and the norflash can also be easily transplanted into other memories.
The invention provides a good file system solution for managing the memory on the embedded system, and can be popularized and applied in a small embedded system.
Detailed Description
The design principle of the invention is as follows:
the file system design includes two core services, sector management and file management. For the sector operation of the norflash, information such as the space size occupied by the file system, the size of a sector block and the like is registered in the file system through a structural body when the file system is formatted or initialized.
The file system obtains chip characteristics and an operation function interface of the norflash through the registered norflash operation structure body, and the norflash device can be conveniently transplanted and replaced through the registered interface to manage norflash sectors.
(1) Sector management design in file system
Each sector contains a sector header structure information, including sector status (normal use, damage, etc.), sector number id, erase count, backup sector id (from which the main data is copied), backup sector erase count, header structure verification, etc. The file system establishes sector management information in the memory at initialization (or formatting), including information such as active, free, corrupted, size of use, etc. The idle sectors are sorted by the erasing times, and only the sector with the least erasing times is ensured to be always allocated when the sectors are allocated, so that the erasing balance is ensured. When erasing the sector, only the sector number in the head information is reserved and 1 is added to the erasing times.
(2) File system storage format design
All files or folders are numbered with uniform and unique id in the file system, and after file directories and files are continuously stored in sector header information in sectors, the directory folder storage cannot span the sectors. When the file is too large, the file can span sectors, the file is divided into a file header information part and other file fragmentation parts, the file header information part comprises file total length information, and the file fragmentation part comprises file fragmentation header information (file id, file offset, file fragmentation length, check and the like). Specifically, there are 4 kinds of header information, each kind of header information is stored after the sector header information, and all header information and stored data are designed as check information. When a sector scans all header information, the sector use space condition can be obtained in addition to the information stored in the sector, and the sector use space condition is used for allocating space when a file or a folder is newly created.
1) Root directory folder
The file created during formatting has no difference from the common folder except that the file number is fixed and the attribute of the folder storage format is the root directory, and the parent directory id of the file is equal to the file id of the file.
2) Plain document
The method comprises the information of structure of head and file data information such as id, father directory file id, name, total length of file, occupied length of current sector (when the occupied length is not equal to the total length, the file is divided into fragments), attribute of deletion or modification, file attribute (directory, file or file fragment), authority attribute, verification, creation time, modification time and the like;
3) directory file
The structure of the directory file is similar to that of the file, the directory file also comprises directory access authentication information (pin code), password verification times and the like relative to the file, and meanwhile, the directory file does not have a data storage part of the file.
4) File fragmentation
When a file is too large and cannot be stored in the current sector, fragment storage is needed, and each file fragment information contains information such as the file id of the current fragment, the file id of a parent directory, the offset of stored file data in the file, the occupied space and the storage size of the current fragment in the sector, and the verification of the current file data and the fragment head structure.
(3) File system operation design
The file system erases all sectors when formatted. A free sector is allocated to create a root directory file. After the file system is initialized, the file system establishes a management linked list of all sectors, obtains an operation norflash control structure, and obtains information such as the use condition of the whole sector and the space use condition of the current file system. The design of several key operations in a file system is as follows:
1) creation of files and directory files
When a new directory is created, the file system searches sectors which have enough space and can store a directory structure in the current available sectors, establishes the directory structure until the current sectors have used the space, and maintains and updates the use condition of the current sectors. The same is true for file establishment, operation is performed only after whether the file system has enough space is judged, and a new sector space storage fragment part is reapplied when fragmentation is needed.
2) File reading operation
The file reading requires to open the directory file corresponding to the file first and acquire the corresponding operation authority. When the file is read, the file is firstly opened, when the file is opened, the file system locates the sector where the file is located in the parent directory, and simultaneously obtains the file header information, the file length and the storage offset of the file in the sector, and for the fragment file system, the storage positions, the lengths, the offsets and the like of all the fragment header information are obtained. When the file is read, the position of the sector can be conveniently positioned according to the reading position, and the reading registration function of the norflash is directly called to finish data reading.
3) File and directory file modification operations
File and directory file modification requires that its parent directory file be opened first and the corresponding operation permissions be obtained. And then opens the corresponding file.
When files and directory files need to be modified (mainly correcting a pin password and updating the error times of the pin password verification), an idle sector is allocated firstly, all files except the modified files and the deleted files in the current sector are copied into the new sector, then the part which does not need to be modified in the current file is copied into the new sector, finally the modified part and verification information are updated into the new sector, and after the operation is completed, the original sector is subjected to erasure management (sector erasure, sector header information is updated, the sector is recycled, and the sector is placed into an idle queue according to the erasure times). If the write operation fails, the sector is marked as damaged when multiple attempts still fail, and the sector is reallocated for processing.
4) Deletion of files and directory files
When the file is deleted, the current file state is modified into a deleted state only by positioning the file header and the file fragmentation header information in the file system. When a directory file is deleted (a root directory cannot be deleted, and is automatically re-created during formatting), all files and directory files under the directory file and the state of the directory file need to be modified into a deleted state. When all files in a sector are deleted, the file system performs erasure management on the sector.
5) File and directory file permissions
The file and the directory file are designed with authority, and when the directory file has read-write authority and needs pin codes, all files below the folder inherit the attribute. And when the pin code of the directory file passes the verification, the file under the directory file can be accessed. For a file, besides the requirement of checking the directory authority, a read-write mode is attached when the file is opened, and the file opened in a read-only mode cannot be written. Only when the write mode is on and the write permission attribute is available for writing.
Secondly, the key points of the invention are as follows:
the technology is an embedded file system implementation method based on norflash, and mainly relates to the combination of two key technologies of norflash sector management and file system management.
(1) Managing norflash sectors: the current sector number, the number of times of erasure, the use status, the backup sector number (from which the main data is copied), and the number of times of erasure of the backup sector are stored in each sector header. The file system, upon initialization (or formatting), establishes management information for all sectors.
(2) File system management: basic file system functions are provided, specifically formatting, initialization, directory operations (create, open, password authentication (optional), password modification (optional), close, delete, traverse, etc.), file operations (create, open, read, modify, delete, etc.).
(3) Designing a file system:
1) the whole file system creates a root directory during formatting, manages and maintains all sectors during initialization, and registers an operating interface of a norflash, the size of the sectors, the size of the file system and other attributes to the file system;
2) after the file directories and files are continuously stored in the sector header information in the sector, each file directory and file comprises header information and file data information such as occupied length, deletion or modification attribute, file attribute (directory, file or file fragment), authority attribute, unique number id, name, check, parent directory file id and the like;
3) the file directory can not occupy two sectors, the file can occupy two or more sectors, but the header information of the file must be put in one sector, and the fragments of other sectors all have file fragment information headers;
4) the file system scans the length of each file or file directory from the information head of each sector to obtain the starting position of the next file or file directory, and the space use condition of each sector is obtained. The file system information is initialized until all sectors are scanned, and a root directory is found, so that the effective management of the file system on each sector is realized;
5) the file system realizes the aim of searching files and file directories by starting scanning from the root directory and constructing a complete file system directory structure by the id of each file and the file id of a parent directory.

Claims (5)

1. An embedded file system based on norflash is characterized in that: the method comprises the following steps:
firstly, sector management: each sector comprises sector head information, and the sector head information comprises a sector state, a sector number id, erasing times, a backup sector id, backup sector erasing times and head structure verification information;
when the file system is initialized or formatted, establishing sector management information in a memory, sequencing idle sectors by the erasing times, and only allocating the sector with the least erasing times when allocating the sectors; only keeping the sector number in the header information when the sector is erased and adding 1 to the erasing times;
secondly, file management: numbering all files and folders, continuously storing file directories and files in sector header information, and dividing the files into a file header information part and a file fragmentation part, wherein the file header information part comprises total file length information, and the file fragmentation part comprises file fragmentation header information; wherein:
(1) when a new file directory is created, the file system searches sectors which have enough space and can store a directory structure in the current available sectors, establishes the directory structure behind the used space of the current sectors, and maintains and updates the use condition of the current sectors; when a new file is created, a new sector space needs to be applied for storing the fragmented part again for the file needing fragmented storage;
(2) when reading a file, firstly opening a directory file corresponding to the file, acquiring a corresponding operation authority, then positioning a sector where the file is located in a parent directory, acquiring file header information, file length and storage offset of the file in the sector, and directly calling a read registration function of a norflash to finish data reading;
(3) when modifying the files and the directory files, firstly opening the father directory file of the file and acquiring the corresponding operation authority, after opening the corresponding file, firstly allocating an idle sector, copying all the files in the current sector except the modified files and the deleted files into a new sector, then updating the part of the current file which does not need to be updated to the new sector, then updating the modified part and the verification information to the new sector, and erasing and managing the original sector after finishing the operation;
(4) when deleting a file, only the file header and the file fragmentation header information in the file system need to be positioned, and the current file state is modified into a deletion state; when deleting the directory file, all files and directory files under the directory file and the state of the directory file per se need to be modified into a deleted state; when all files in a sector are deleted, the file system performs erasure management on the sector.
2. The norflash-based embedded file system according to claim 1, wherein: the sector management information includes active, idle, defective, usage size information.
3. The norflash-based embedded file system according to claim 1, wherein: the file fragment header information comprises a file id, a file offset, a file fragment length and verification information.
4. The norflash-based embedded file system according to claim 1, wherein: when reading the file, the storage position, length and offset of all the fragment header information are also required to be acquired for the fragment file.
5. The norflash-based embedded file system according to claim 1, wherein: the erasing management of the sector comprises erasing the sector, updating the head information of the sector, recycling the sector and putting the sector into an idle queue according to the erasing times.
CN201711115807.XA 2017-11-13 2017-11-13 Embedded file system based on norflash Active CN107908364B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201711115807.XA CN107908364B (en) 2017-11-13 2017-11-13 Embedded file system based on norflash

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201711115807.XA CN107908364B (en) 2017-11-13 2017-11-13 Embedded file system based on norflash

Publications (2)

Publication Number Publication Date
CN107908364A CN107908364A (en) 2018-04-13
CN107908364B true CN107908364B (en) 2020-10-23

Family

ID=61843841

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201711115807.XA Active CN107908364B (en) 2017-11-13 2017-11-13 Embedded file system based on norflash

Country Status (1)

Country Link
CN (1) CN107908364B (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111290716A (en) * 2020-03-05 2020-06-16 莆田学院 Abrasion balance processing method based on Norflash
CN112799591A (en) * 2021-01-21 2021-05-14 北京鼎普科技股份有限公司 File erasing method and device and electronic equipment
CN114610230B (en) * 2022-01-27 2023-02-07 福建时代星云科技有限公司 Flash memory data exchange method and terminal based on single chip microcomputer
CN114816581B (en) * 2022-05-20 2023-06-02 中国电子科技集团公司第三十研究所 ARM processor-based non-operating system algorithm dynamic loading method

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1632765A (en) * 2004-12-31 2005-06-29 大唐微电子技术有限公司 A flash memory file system management method
CN101241469A (en) * 2007-02-05 2008-08-13 力博特公司 Method and device for storing and reading data in embedded system
CN101441634A (en) * 2007-11-19 2009-05-27 凤凰微电子(中国)有限公司 Embedded type file system suitable for smart card application environment
CN101529395A (en) * 2006-08-31 2009-09-09 夏普株式会社 File system
CN101609464A (en) * 2009-06-22 2009-12-23 浙江大学 The balanced erase implementation method that is fit to embedded Flash file system
CN102789425A (en) * 2012-07-17 2012-11-21 上海晟东电力科技有限公司 File read-write method on basis of FLASH storage medium
CN103425546A (en) * 2013-08-14 2013-12-04 江苏林洋电子股份有限公司 General high-efficient reliable Nor Flash data memory management method
CN104007939A (en) * 2014-06-23 2014-08-27 深圳供电局有限公司 Embedded type FAT file system and method for frequent write-in of small files
EP2239665B1 (en) * 2009-04-07 2016-07-13 Marvell World Trade Ltd. Distributed flash memory storage manager systems
CN106844583A (en) * 2017-01-10 2017-06-13 厦门雅迅网络股份有限公司 A kind of optimization method that FAT file system is set up on NOR Flash

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1632765A (en) * 2004-12-31 2005-06-29 大唐微电子技术有限公司 A flash memory file system management method
CN101529395A (en) * 2006-08-31 2009-09-09 夏普株式会社 File system
CN101241469A (en) * 2007-02-05 2008-08-13 力博特公司 Method and device for storing and reading data in embedded system
CN101441634A (en) * 2007-11-19 2009-05-27 凤凰微电子(中国)有限公司 Embedded type file system suitable for smart card application environment
EP2239665B1 (en) * 2009-04-07 2016-07-13 Marvell World Trade Ltd. Distributed flash memory storage manager systems
CN101609464A (en) * 2009-06-22 2009-12-23 浙江大学 The balanced erase implementation method that is fit to embedded Flash file system
CN102789425A (en) * 2012-07-17 2012-11-21 上海晟东电力科技有限公司 File read-write method on basis of FLASH storage medium
CN103425546A (en) * 2013-08-14 2013-12-04 江苏林洋电子股份有限公司 General high-efficient reliable Nor Flash data memory management method
CN104007939A (en) * 2014-06-23 2014-08-27 深圳供电局有限公司 Embedded type FAT file system and method for frequent write-in of small files
CN106844583A (en) * 2017-01-10 2017-06-13 厦门雅迅网络股份有限公司 A kind of optimization method that FAT file system is set up on NOR Flash

Also Published As

Publication number Publication date
CN107908364A (en) 2018-04-13

Similar Documents

Publication Publication Date Title
CN107908364B (en) Embedded file system based on norflash
US7831783B2 (en) Effective wear-leveling and concurrent reclamation method for embedded linear flash file systems
JP4685038B2 (en) Hidden area management apparatus and method
US6606628B1 (en) File system for nonvolatile memory
US8140746B2 (en) Intelligent memory data management
US7840617B2 (en) Host device and memory system
US20080109589A1 (en) Nonvolatile Storage Device And Data Write Method
JP2004013895A (en) File system for flash memory
US20060224818A1 (en) Method for fast access to flash-memory media
US20080005531A1 (en) Data Storage Device
JP2008242503A (en) Memory management apparatus and method, and program
KR20080063466A (en) Flash memory management
JP2000305839A (en) Storage device, storage system, memory managing method, and recording medium
EP3752905B1 (en) Append only streams for storing data on a solid state device
US7702845B2 (en) Method and apparatus for managing blocks according to update type of data in block-type memory
US6928456B2 (en) Method of tracking objects for application modifications
US20150052292A1 (en) Method for erasing data entity in memory module
CN105069002A (en) Flash memory file system and method using different types of storage media
US20090125668A1 (en) Management of erased blocks in flash memories
US20100180072A1 (en) Memory controller, nonvolatile memory device, file system, nonvolatile memory system, data writing method and data writing program
US20070005929A1 (en) Method, system, and article of manufacture for sector mapping in a flash device
KR100954603B1 (en) A log file of file system and method for recovering file system
US7451279B2 (en) Storage system comprising a shared memory to access exclusively managed data
JP4419415B2 (en) Recording method
KR100638638B1 (en) Method for controling flash memory device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant