CN111309361A - Data reading and writing method and device, electronic equipment and storage medium - Google Patents
Data reading and writing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN111309361A CN111309361A CN202010091984.4A CN202010091984A CN111309361A CN 111309361 A CN111309361 A CN 111309361A CN 202010091984 A CN202010091984 A CN 202010091984A CN 111309361 A CN111309361 A CN 111309361A
- Authority
- CN
- China
- Prior art keywords
- data
- burned
- writing
- memory
- reading
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/654—Updates using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/08—Error detection or correction by redundancy in data representation, e.g. by using checking codes
- G06F11/10—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's
- G06F11/1004—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's to protect a block of data words, e.g. CRC or checksum
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Quality & Reliability (AREA)
- Techniques For Improving Reliability Of Storages (AREA)
Abstract
The application provides a data reading and writing method and device, an electronic device and a storage medium, and the scheme comprises the following steps: responding to the received write operation instruction, and writing the data to be burned into a memory; reading the written target data of the memory, and comparing whether the target data is consistent with the data to be burned; and determining whether to write the data to be burned again or not according to the comparison result of the target data and the data to be burned. This scheme ensures the correctness of data written to the memory.
Description
Technical Field
The present disclosure relates to the field of memory technologies, and in particular, to a data reading and writing method and apparatus, an electronic device, and a storage medium.
Background
Otp (one Time programmable) is a type of memory, meaning one-Time programmable: after the program is burned in, it cannot be changed and cleaned again.
However, when writing data to memory, there may be some unforeseen circumstances that result in the data written to memory and the pre-written data being different. In this case, since the OTP memory cannot clear and change written data, the chip cannot implement the preset function, which results in low utilization rate of the chip and incapability of guaranteeing the correctness of the data in the memory. A risk may occur when directly reading data applications in memory.
Disclosure of Invention
The embodiment of the application provides a data reading and writing method, and the correctness of data writing is guaranteed.
The application provides a data reading and writing method, which comprises the following steps:
responding to the received write operation instruction, and writing the data to be burned into a memory;
reading the written target data of the memory, and comparing whether the target data is consistent with the data to be burned;
and determining whether to write the data to be burned again or not according to the comparison result of the target data and the data to be burned.
In one embodiment, writing data to be burned into a memory in response to a received write operation command includes:
responding to the received write operation instruction, and reading the packet body data which is programmed successfully at the last time from the memory;
comparing whether the packet body data is consistent with the data to be burned;
and if the packet body data is inconsistent with the data to be burned, writing the data to be burned into a memory.
In an embodiment, writing the data to be burned into a memory includes:
recording the writing state of the data to be burned at a first zone bit of the packet header of the data to be burned;
and writing the first zone bit of the packet header of the data to be burned into the zone area of the memory.
In an embodiment, writing the data to be burned into a memory includes:
and writing the packet body data of the data to be burned into the parameter area of the memory.
In one embodiment, the reading of the body data that was programmed successfully last time from the memory includes:
reading the data in the mark area of the memory to obtain the writing state and the correct state of each data packet;
and reading the body data of the latest written and correct data packet from the parameter area of the memory according to the writing state and the correct state of each data packet.
In an embodiment, the determining whether to perform the writing of the data to be burned again according to the comparison result between the target data and the data to be burned includes:
if the target data is inconsistent with the data to be burned, recording the correct state of the data to be burned at a second marker bit of the packet header of the data to be burned;
and writing the data to be burned into the memory again.
The application also provides a data reading and writing method, which comprises the following steps:
responding to the received read operation instruction, reading the data in the mark area of the memory, and obtaining the writing state and the correct state of each data packet;
and reading the packet body data of the data packet which is written recently and written correctly from the parameter area of the memory according to the writing state and the correct state of each data packet.
On the other hand, the present application also provides a data read/write apparatus, the apparatus includes:
the data writing module is used for responding to the received writing operation instruction and writing the data to be burned into the memory;
the data comparison module is used for reading the written target data of the memory and comparing whether the target data is consistent with the data to be burned;
and the re-burning module is used for determining whether to re-write the data to be burned according to the comparison result of the target data and the data to be burned.
Further, the present application also provides an electronic device, including:
a processing unit;
a storage unit for storing processing unit executable instructions;
the processing unit is configured to execute the data reading and writing method provided by the application.
Further, the present application also provides a computer storage medium, where the computer storage medium stores a computer program, and the computer program is executable by a processing unit to perform the data reading and writing method provided in the present application.
According to the technical scheme provided by the embodiment of the application, after the data to be burned is written into the memory, the written target data is read, whether the target data is consistent with the data to be burned is compared, whether the data to be burned is written again is determined according to the comparison result, and the correctness of the data written into the memory is ensured.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required to be used in the embodiments of the present application will be briefly described below.
Fig. 1 is a schematic view of an application scenario of a data reading and writing method provided in an embodiment of the present application;
fig. 2 is a schematic flowchart of a data reading and writing method according to an embodiment of the present application;
FIG. 3 is a diagram illustrating a structure of a data packet according to an embodiment of the present application;
FIG. 4 is a schematic diagram illustrating a space allocation of a memory according to an embodiment of the present application;
FIG. 5 is a detailed flowchart of step 210 in the corresponding embodiment of FIG. 2;
FIG. 6 is a detailed flowchart of step 230 in the corresponding embodiment of FIG. 2;
fig. 7 is a schematic flowchart of a data reading/writing method according to another embodiment of the present application;
FIG. 8 is a schematic diagram of a data writing process according to an embodiment of the present application;
fig. 9 is a block diagram of a data read/write apparatus according to another embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
Like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.
Fig. 1 is a schematic view of an application scenario of a data reading and writing method provided in an embodiment of the present application. As shown in fig. 1, the application scenario includes a processing unit 11 and a memory 12. The processing unit 11 may perform read and write operations on the data of the memory 12 by using the method provided in the embodiment of the present application. The memory 12 may be an otp (one Time programmable) memory.
As shown in fig. 1, an embodiment of the present application provides an electronic device 10, which includes a processing unit 11, a memory 12, and a storage unit 13. The storage unit 13 is used for storing executable instructions of the processing unit 11; the processing unit 11 is configured to execute the method provided by the embodiment of the present application, and performs read and write operations on the data of the memory 12.
The storage unit 13 may be implemented by any type of volatile or non-volatile storage device or combination thereof, such as a Static Random Access Memory (SRAM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), an Erasable Programmable Read-Only Memory (EPROM), a Programmable Read-Only Memory (PROM), a Read-Only Memory (ROM), a magnetic Memory, a flash Memory, a magnetic disk or an optical disk.
The embodiment of the present application further provides a computer-readable storage medium, where the storage medium stores a computer program, and the computer program can be executed by the processing unit 11 to complete the data reading and writing method provided in the embodiment of the present application.
The processing unit 11 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; but may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. Which may implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present application.
Fig. 2 is a schematic flowchart of a data reading and writing method of a memory according to an embodiment of the present disclosure. The memory may be the memory 12 shown in fig. 1. As shown in fig. 2, the method may include the following steps S210-S230.
In step S210, a write operation command is received, and the data to be burned is written into the memory.
The writing operation instruction can be triggered by an operator and issued by a computer or other types of processors. The data to be burned may include stored data or programs.
In step S220, the written target data of the memory is read, and whether the target data is consistent with the data to be burned is compared.
The target data is data written in the memory by the data to be burned, and is referred to as target data for distinguishing. Due to the possibility of write errors, the target data and the data to be burned may be different. By comparing whether the target data is consistent with the data to be burned, whether the data to be burned is written correctly can be determined.
In step S230, it is determined whether to perform writing of the data to be burned again according to a comparison result between the target data and the data to be burned.
If the comparison result of the target data and the data to be burned is consistent, the writing operation of the data to be burned is finished; if the comparison result of the target data and the data to be burned is inconsistent, the target data is not eliminated or changed, and the data to be burned is only required to be written into the memory again, and whether the rewritten data is consistent with the data to be burned is judged until the data to be burned is written correctly.
After the data to be burned is written into the memory, the written target data is read and compared whether the target data is consistent with the data to be burned, whether the data to be burned is written again is determined according to the comparison result, and the correctness of the data written into the memory is guaranteed.
In one embodiment, the memory may be an OTP memory, and the data to be burned is written into a different storage space of the memory each time. Thus, the memory can store data written several times.
In an embodiment, the data to be burned may be stored in the form of a data packet. The structure of the data packet may be as shown in fig. 3. The data packet is divided into a header 51 and a body 52. The packet header 51 records the flag information of the data packet, and the packet header 51 is divided into a first flag bit 510 and a second flag bit 511. The first flag bit 510 is used to record a write status, where the write status may be 0 or 1, 0 represents unwritten, and 1 represents written; the second flag 511 is used to record the correct status, which may be 0 or 1, where 0 represents correct and 1 represents error. The body 52 records the specific data content of the data packet.
Fig. 4 is a schematic diagram of space allocation of the memory 40. As shown in fig. 4, the memory 40 includes two address-sequential storage areas, a flag area 41 and a parameter area 42. The flag area 41 is used for storing a header 51 of a data packet, and the parameter area 42 is used for storing a packet body 52 of the data packet. The number of data packets that can be stored in the memory 40 may be determined before the memory is subjected to the first write operation. In this embodiment, the number of the data packets that can be stored in the memory 40 is 8, and the flag area 41 is divided into 8 areas, which are the area 410 and the area 417 respectively. As indicated by the marks in area 410, each area is divided into two parts A, B for storing the writing status and the correct status of the burning data. The initial value of the write state is 0, and the initial value of the correct state is 0. Correspondingly, the parameter area 42 is also divided into 8 storage units, namely storage unit 420 and 427.
In one embodiment, as shown in FIG. 5, the step S210 may include the following steps S211-S213.
In step 211, a write operation command is received, and the last successfully programmed body data is read from the memory.
For example, the data packets may be stored in sequence according to the writing sequence, where the packet body data may be marked to determine whether the packet body data is written correctly. Therefore, the weld data with the highest sequence and correct writing can be regarded as the weld data which is successfully written by the last burning. When the processor receives a write operation instruction, the packet data which is sorted in the top and marked as 'write correct' can be read from the memory.
In one embodiment, reading the packet data that was programmed successfully last time from the memory may include the following steps: reading the data in the mark area of the memory to obtain the writing state and the correct state of each data packet; and reading the body data of the latest written and correct data packet from the parameter area of the memory according to the writing state and the correct state of each data packet.
The writing state and the correct state of the data packet may be stored in the flag area of the memory in sequence according to the writing sequence, for example, the writing state stored in the flag area is 11100000 in sequence, and the data packet written last time is the data packet written for the third time. And reading the correct state of the data packet written for the third time, and if the correct state is 0, determining that the data packet is the data packet which is successfully programmed for the last time.
The bag body data in the parameter area can be stored in sequence according to the burning sequence, so that the bag body data burned for the third time can be determined in the storage area of the parameter area, and the bag body data written for the last time and correct data bags can be read.
In step S212, it is compared whether the packet data is consistent with the data to be burned.
In step S213, if the packet data is inconsistent with the data to be burned, the data to be burned is written into a memory.
If the packet body data is consistent with the data to be burned, the data to be burned is not burned, so that the read-write times are reduced, and the efficiency is improved. And if the packet body data is inconsistent with the data to be burned, writing the data to be burned into a memory.
In an embodiment, the data to be burned can be divided into a packet header and a packet body, and the packet header includes a first flag bit and a second flag bit. The memory is divided into a flag area and a parameter area. Writing the data to be burned into the memory may include: recording the writing state of the data to be burned at a first zone bit of a packet header of the data to be burned, and writing the first zone bit of the packet header of the data to be burned into a zone area of the memory.
In this embodiment, the first flag bit may be set from 0 to 1, which indicates that the writing status of the data to be burned is changed from "unwritten" to "written" status.
The header can be stored in the mark area according to the writing sequence, so that the area of the mark area of the memory where the first mark bit of the data to be burned is written can be determined according to the fact that the data to be burned is written into the memory for the second time.
In an embodiment, writing the data to be burned into the memory may further include: and writing the packet body data of the data to be burned into the parameter area of the memory.
The packet body can also be stored in the mark zone according to the writing sequence, and the writing of the packet body data into which zone of the parameter zone of the memory is determined according to the writing of the data to be burned into the memory for the second time.
In one embodiment, as shown in FIG. 6, the step S230 may include the following steps S231-S232.
In step S231, if the target data is inconsistent with the data to be burned, a correct state of the data to be burned is recorded in a second flag bit of the header of the data to be burned.
In this embodiment, if the target data is inconsistent with the data to be burned and indicates that the data to be burned is burned incorrectly, the second flag bit of the header of the data to be burned may be set from 0 to 1, which is used to indicate that the data to be burned is a data packet, so as to avoid reading a data packet with a wrong write error subsequently.
In step 232, the writing of the data to be burned is performed again in the memory.
In an embodiment, when the data to be burned is wrongly written in one storage space of the memory, the data to be burned can be written in the next storage space of the memory. For example, if the comparison result between the target data to be written for the fourth time (for example, the storage address is 1 to 10) and the data to be burned is incorrect, the fifth writing is performed, that is, the inclusion data of the data to be burned is written into the parameter area of the memory again, and at this time, the inclusion data of the data to be burned can be written into the storage address is 11 to 20.
Fig. 7 is a flowchart illustrating a data reading/writing method according to another embodiment of the present application, including steps S710-S711.
In step S710, in response to the received read operation command, the data in the flag area of the memory is read, and the write status and correct status of each data packet are obtained.
In step S711, the body data of the data packet that is written recently and written correctly is read from the parameter area of the memory according to the writing status and the correct status of each data packet.
The read operation instruction can be triggered by an operator and issued by a computer or other types of processors. As described above, the writing status and the correct status of the data packet may be sequentially stored in the flag area of the memory according to the writing sequence, for example, the writing status stored in the flag area is 11100000 sequentially, and the data packet written last time is the data packet written for the third time. And reading the correct state of the data packet written for the third time, and if the correct state is 0, determining that the data packet is the data packet which is successfully programmed for the last time.
The bag body data in the parameter area can be stored in sequence according to the burning sequence, so that the bag body data burned for the third time can be determined in the storage area of the parameter area, and the bag body data written for the last time and correct data bags can be read.
Fig. 8 is a schematic diagram of a data writing process according to an embodiment of the present application. As shown in fig. 8, the first step: receiving a write operation instruction;
the second step is that: reading bag body data which is programmed successfully at the last time from a memory;
the third step: judging whether the read bag body data is consistent with the pre-written data; if the two are consistent, the writing operation is finished, and if the two are not consistent, the fourth step is executed;
the fourth step: writing the first zone bit of the packet header and the packet body data into a memory;
the fifth step: reading the bag body data written in the last step;
and a sixth step: judging whether the read bag body data is equal to the pre-written data or not; if not, returning to the fourth step to perform the write operation again; if yes, executing the seventh step;
the seventh step: and writing the second zone bit of the packet header into a zone area of the memory, and finishing the writing operation.
The following is an embodiment of the apparatus of the present application, which can be used to implement the above-mentioned embodiments of the data reading and writing method of the present application. For details not disclosed in the embodiments of the apparatus of the present application, please refer to the embodiments of the data reading and writing method of the present application.
Fig. 9 is a block diagram of a data reading and writing apparatus according to another embodiment of the present application. The data read-write device includes: a data writing module 910, a data comparing module 911, and a re-burning module 912.
The data writing module 910 is configured to respond to the received write operation command and write the data to be burned into the memory.
A data comparing module 911, configured to read target data written in the memory, and compare whether the target data is consistent with the data to be burned;
a re-burning module 912, configured to determine whether to re-write the data to be burned according to a comparison result between the target data and the data to be burned.
The implementation process of the functions and actions of each module in the device is specifically described in the implementation process of the data reading and writing method, and is not described herein again.
In the embodiments provided in the present application, the disclosed apparatus and method can be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
Claims (10)
1. A method for reading and writing data, comprising:
responding to the received write operation instruction, and writing the data to be burned into a memory;
reading the written target data of the memory, and comparing whether the target data is consistent with the data to be burned;
and determining whether to write the data to be burned again or not according to the comparison result of the target data and the data to be burned.
2. A method for reading and writing data according to claim 1, wherein writing the data to be burned into the memory in response to the received write operation command comprises:
responding to the received write operation instruction, and reading the packet body data which is programmed successfully at the last time from the memory;
comparing whether the packet body data is consistent with the data to be burned;
and if the packet body data is inconsistent with the data to be burned, writing the data to be burned into a memory.
3. The data reading and writing method according to claim 2, wherein writing the data to be burned into a memory comprises:
recording the writing state of the data to be burned at a first zone bit of the packet header of the data to be burned;
and writing the first zone bit of the packet header of the data to be burned into the zone area of the memory.
4. The data reading and writing method according to claim 2, wherein writing the data to be burned into a memory comprises:
and writing the packet body data of the data to be burned into the parameter area of the memory.
5. The method according to claim 2, wherein the reading of the packet data that was written successfully last time from the memory comprises:
reading the data in the mark area of the memory to obtain the writing state and the correct state of each data packet;
and reading the body data of the latest written and correct data packet from the parameter area of the memory according to the writing state and the correct state of each data packet.
6. The method according to claim 1, wherein determining whether to perform the writing of the data to be burned again according to the comparison result between the target data and the data to be burned includes:
if the target data is inconsistent with the data to be burned, recording the correct state of the data to be burned at a second zone bit of the packet header of the data to be burned;
and writing the data to be burned into the memory again.
7. A method for reading and writing data, comprising:
responding to the received read operation instruction, reading the data in the mark area of the memory, and obtaining the writing state and the correct state of each data packet;
and reading the packet body data of the data packet which is written recently and written correctly from the parameter area of the memory according to the writing state and the correct state of each data packet.
8. A data read/write apparatus, comprising:
the data writing module is used for responding to the received writing operation instruction and writing the data to be burned into the memory;
the data comparison module is used for reading the written target data of the memory and comparing whether the target data is consistent with the data to be burned;
and the re-burning module is used for determining whether to re-write the data to be burned according to the comparison result of the target data and the data to be burned.
9. An electronic device, characterized in that the electronic device comprises:
a processing unit;
a storage unit for storing processing unit executable instructions;
wherein the processing unit is configured to perform the data reading and writing method of any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that the storage medium stores a computer program executable by a processing unit to perform the method of reading and writing data according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010091984.4A CN111309361A (en) | 2020-02-13 | 2020-02-13 | Data reading and writing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010091984.4A CN111309361A (en) | 2020-02-13 | 2020-02-13 | Data reading and writing method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111309361A true CN111309361A (en) | 2020-06-19 |
Family
ID=71150997
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010091984.4A Pending CN111309361A (en) | 2020-02-13 | 2020-02-13 | Data reading and writing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111309361A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115827032A (en) * | 2022-12-12 | 2023-03-21 | 深微光电科技(深圳)有限公司 | Memory burning method and device, electronic equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020039312A1 (en) * | 2000-09-29 | 2002-04-04 | Kabushiki Kaisha Toshiba | Nonvolatile memory and method of writing data thereto |
| CN102508732A (en) * | 2011-10-25 | 2012-06-20 | 深圳芯邦科技股份有限公司 | Method and device for improving one-time programmable memory use performance |
| CN104391727A (en) * | 2014-12-15 | 2015-03-04 | 福州瑞芯微电子有限公司 | Data writing method and system, writing equipment and target equipment |
| CN109614118A (en) * | 2018-11-23 | 2019-04-12 | 信利光电股份有限公司 | A kind of SPI Flash firmware burning method and device |
| CN109710296A (en) * | 2018-12-14 | 2019-05-03 | 上海航天控制技术研究所 | A kind of sky and space plane inertial navigation embedded software on-line updating method |
-
2020
- 2020-02-13 CN CN202010091984.4A patent/CN111309361A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020039312A1 (en) * | 2000-09-29 | 2002-04-04 | Kabushiki Kaisha Toshiba | Nonvolatile memory and method of writing data thereto |
| CN102508732A (en) * | 2011-10-25 | 2012-06-20 | 深圳芯邦科技股份有限公司 | Method and device for improving one-time programmable memory use performance |
| CN104391727A (en) * | 2014-12-15 | 2015-03-04 | 福州瑞芯微电子有限公司 | Data writing method and system, writing equipment and target equipment |
| CN109614118A (en) * | 2018-11-23 | 2019-04-12 | 信利光电股份有限公司 | A kind of SPI Flash firmware burning method and device |
| CN109710296A (en) * | 2018-12-14 | 2019-05-03 | 上海航天控制技术研究所 | A kind of sky and space plane inertial navigation embedded software on-line updating method |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115827032A (en) * | 2022-12-12 | 2023-03-21 | 深微光电科技(深圳)有限公司 | Memory burning method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101613678B1 (en) | Recovery for non-volatile memory after power loss | |
| US9996462B1 (en) | Data storage device and data maintenance method thereof | |
| CN109582216B (en) | Data storage device and data processing method of memory device | |
| TWI486957B (en) | Method, device and operating system for processing, using a nand flash memory burn data | |
| CN116880782B (en) | Embedded memory and testing method thereof | |
| CN114624575A (en) | Chip testing method, device, equipment and storage medium | |
| CN111615688A (en) | Assertion verification code binding method and device | |
| CN115620799A (en) | Firmware simulation-based fault site backtracking method and equipment and readable storage medium | |
| CN111309361A (en) | Data reading and writing method and device, electronic equipment and storage medium | |
| CN111352594A (en) | Method and device for writing data and reading data in eFuse | |
| WO2024103600A1 (en) | Data management method and apparatus, electronic device, and nonvolatile readable storage medium | |
| CN115512757B (en) | Error reproduction and repair method, device, equipment and storage medium | |
| JP3675375B2 (en) | Nonvolatile memory and data rewriting method of nonvolatile memory | |
| CN112083891B (en) | Method for detecting data block in memory and related equipment | |
| US9424176B2 (en) | Robust sector ID scheme for tracking dead sectors to automate search and copydown | |
| CN112463042B (en) | Data volume import data verification method, device, terminal and storage medium | |
| JP2002244932A (en) | Control device | |
| CN115543685A (en) | Database rollback method and device, electronic equipment and storage medium | |
| CN108614664A (en) | Read error treating method and apparatus based on NANDflash | |
| CN114203252A (en) | Bad block detection method, device, equipment and storage medium of nonvolatile memory | |
| US7313648B2 (en) | Corruption tolerant method and system for deploying and modifying data in flash memory | |
| CN111949198A (en) | Bad block management method and device and storage equipment | |
| CN109144409B (en) | Data processing method and device, storage medium and data system | |
| CN113050888A (en) | Method, system, device and storage medium for quickly eliminating Flash unstable blocks | |
| JPS63219045A (en) | Ic card |
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 |