CN116820824A - Fault processing method and embedded system - Google Patents
Fault processing method and embedded system Download PDFInfo
- Publication number
- CN116820824A CN116820824A CN202310801165.8A CN202310801165A CN116820824A CN 116820824 A CN116820824 A CN 116820824A CN 202310801165 A CN202310801165 A CN 202310801165A CN 116820824 A CN116820824 A CN 116820824A
- Authority
- CN
- China
- Prior art keywords
- cpu
- abnormal
- instruction information
- storage module
- embedded system
- 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
- 238000003672 processing method Methods 0.000 title abstract description 5
- 230000002159 abnormal effect Effects 0.000 claims abstract description 134
- 238000000034 method Methods 0.000 claims abstract description 65
- 230000006399 behavior Effects 0.000 claims abstract description 40
- 230000008569 process Effects 0.000 claims abstract description 30
- 230000004044 response Effects 0.000 claims description 20
- 230000005856 abnormality Effects 0.000 claims description 11
- 238000010586 diagram Methods 0.000 description 7
- 238000004458 analytical method Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000036541 health Effects 0.000 description 2
- 238000011084 recovery Methods 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000003999 initiator Substances 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Classifications
-
- 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/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0736—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in functional embedded systems, i.e. in a data processing system designed as a combination of hardware and software dedicated to performing a certain function
-
- 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/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1438—Restarting or rejuvenating
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Hardware Redundancy (AREA)
Abstract
The invention provides a fault processing method and an embedded system. In the running process of the embedded system, after the CPU triggers the file operation of the data in the storage module, if the CPU receives the error prompt fed back by the driving side of the storage module, the CPU determines the abnormal type of the storage module; the CPU determines the processing strategy corresponding to the abnormal type according to the behavior table, and performs abnormal processing according to the determined processing strategy, wherein the processing strategy corresponding to each abnormal type is recorded in the behavior table. According to the method, the storage module faults are repaired by processing different fault behaviors at the interfaces of the driving layer and the file operation bottom layer, and the upper software operation is not influenced in the repairing process, so that the purpose of improving the reliability of the file system is achieved.
Description
Technical Field
The present invention relates to the field of embedded technologies, and in particular, to a fault handling method and an embedded system.
Background
As the complexity of communication systems continues to increase, embedded devices become more and more complex, and memory module anomalies in each embedded device affect program operations on the device, thereby affecting overall communication system stability. The external appearance of the abnormal memory module may be that the business program is wrong, or the abnormal operating system causes a black disk, which brings great difficulty to the positioning and repairing of the problem.
In order to improve the reliability of the file system, the prior art increases a hardware module through caching, block backup and the like, increases a data backup flow, and solves the problem of reliable file access by using a data backup method when a storage module is abnormal, but the mode increases the hardware cost. Therefore, how to improve the reliability of the file system without increasing the hardware cost is a urgent problem to be solved.
Disclosure of Invention
In order to solve the above technical problems, a main objective of the present invention is to provide a fault handling method and an embedded system.
In a first aspect, the present invention provides a fault handling method, the fault handling method comprising:
in the running process of the embedded system, after the CPU triggers the file operation of the data in the storage module, if the CPU receives the error prompt fed back by the driving side of the storage module, the CPU determines the abnormal type of the storage module;
the CPU determines the processing strategy corresponding to the abnormal type according to the behavior table, and performs abnormal processing according to the determined processing strategy, wherein the processing strategy corresponding to each abnormal type is recorded in the behavior table.
Optionally, in the running process of the embedded system, after the CPU triggers the file operation on the data in the storage module, if the CPU receives the error alert fed back by the driving side of the storage module, before the step of determining the abnormal type of the storage module, the method further includes:
when the embedded system starts, the CPU loads the behavior table from the storage module to the reserved memory;
the CPU judges whether the starting is power-down restarting or not;
if the starting is power-down restarting, the CPU loads an abnormal instruction information table from the storage module to the reserved memory, wherein the abnormal instruction information table is used for recording abnormal instruction information;
the CPU checks whether the abnormal instruction information exists in the abnormal instruction information table;
if the file system checking command is executed, the embedded system is continuously guided to start, the abnormal instruction information in the abnormal instruction information table is recorded into the historical abnormal instruction information table, the abnormal instruction information table is emptied, and the embedded system starts to operate after the embedded system is guided to start.
Optionally, after the step that the CPU receives the error alert fed back by the driving side of the storage module, the method further includes:
the CPU marks the data and then re-triggers the file operation of the data;
after receiving the marked data, the storage module driving side inserts the data into normal data stream preferentially to process and stops triggering new file operation;
resetting the memory module to allow the memory module to enter a ready state;
after the memory module is in a ready state, the CPU determines the exception type of the memory module.
Optionally, the step of determining the abnormality type of the storage module by the CPU includes:
the CPU sends CMD instructions to the storage module;
if the response of the memory module returns an exception or the response is overtime, the CPU determines the exception type of the memory module according to the sent CMD instruction.
Optionally, after the step of determining the abnormality type of the memory module by the CPU according to the sent CMD command if the memory module returns an abnormality in response or the response times out, the method further includes:
and recording the abnormal instruction information corresponding to the abnormal type into an abnormal instruction information table.
In a second aspect, the present invention further provides an embedded system, where the embedded system includes a storage module and a CPU, and in an operation process of the embedded system, after the CPU triggers a file operation on data in the storage module, if the CPU receives an error alert fed back by a driving side of the storage module, the CPU determines an abnormal type of the storage module; the CPU determines the processing strategy corresponding to the abnormal type according to the behavior table, and performs abnormal processing according to the determined processing strategy, wherein the processing strategy corresponding to each abnormal type is recorded in the behavior table.
Optionally, when the embedded system starts, the CPU loads the behavior table from the storage module to the reserved memory; the CPU judges whether the starting is power-down restarting or not; if the starting is power-down restarting, the CPU loads an abnormal instruction information table from the storage module to the reserved memory, wherein the abnormal instruction information table is used for recording abnormal instruction information; the CPU checks whether the abnormal instruction information exists in the abnormal instruction information table; if the file system checking command is executed, the embedded system is continuously guided to start, the abnormal instruction information in the abnormal instruction information table is recorded into the historical abnormal instruction information table, the abnormal instruction information table is emptied, and the embedded system starts to operate after the embedded system is guided to start.
Optionally, the CPU marks the data and then re-triggers the file operation on the data; after receiving the marked data, the storage module driving side inserts the data into normal data stream preferentially to process and stops triggering new file operation; resetting the memory module to allow the memory module to enter a ready state; after the memory module is in a ready state, the CPU determines the exception type of the memory module.
Optionally, the CPU sends a CMD command to the memory module; if the response of the memory module returns an exception or the response is overtime, the CPU determines the exception type of the memory module according to the sent CMD instruction.
Optionally, the abnormal instruction information corresponding to the abnormal type is recorded in an abnormal instruction information table.
In the invention, in the running process of the embedded system, after the CPU triggers the file operation of the data in the storage module, if the CPU receives the error prompt fed back by the driving side of the storage module, the CPU determines the abnormal type of the storage module; the CPU determines the processing strategy corresponding to the abnormal type according to the behavior table, and performs abnormal processing according to the determined processing strategy, wherein the processing strategy corresponding to each abnormal type is recorded in the behavior table. According to the method, the storage module faults are repaired by processing different fault behaviors at the interfaces of the driving layer and the file operation bottom layer, and the upper software operation is not influenced in the repairing process, so that the purpose of improving the reliability of the file system is achieved.
Drawings
FIG. 1 is a flow chart of an embodiment of a fault handling method according to the present invention;
FIG. 2 is a schematic diagram of an overall framework of an embodiment of a fault handling method according to the present invention;
FIG. 3 is a diagram illustrating a behavior table according to an embodiment of the fault handling method of the present invention;
FIG. 4 is a schematic diagram illustrating a behavior of a fault handling method according to an embodiment of the present invention;
FIG. 5 is a system architecture diagram of an embodiment of an embedded system according to the present invention.
The achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.
Detailed Description
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
In a first aspect, an embodiment of the present invention provides a fault handling method.
In an embodiment, referring to fig. 1, fig. 1 is a flow chart of an embodiment of a fault handling method according to the present invention. As shown in fig. 1, the fault handling method includes:
step S10, in the running process of the embedded system, after the CPU triggers the file operation of the data in the storage module, if the CPU receives the error prompt fed back by the driving side of the storage module, the CPU determines the abnormal type of the storage module;
in step S20, the CPU determines a processing policy corresponding to the exception type according to the behavior table, and performs exception handling according to the determined processing policy, where the processing policy corresponding to each exception type is recorded in the behavior table.
In this embodiment, during the running process of the embedded system, file operations such as reading, writing, deleting are performed on the file, and finally an API interface provided by a libc library is used at the file system side, and most of file operation exceptions are related to the operation of a writing (including handle) storage module, and finally the file operation exceptions are adjusted to an adaptation layer bottom layer function new_do_write. If the file operation is performed on the data in the storage module, the written data stream will be transferred to the driving side of the storage module through the middle layer (e.g. the right side of fig. 2, fig. 2 is a schematic diagram of the overall framework of an embodiment of the fault handling method of the present invention). If the emmc driving side IO stream returns an error (emmc is used as a storage module for description herein, but it should be noted that the storage module is not limited to emmc, and the storage module may be an SD card or other types of storage devices, which are not limited herein), the data is marked and then retried. Unless the storage module is physically damaged, the common software side such as a state machine is abnormal, the retrying is successful after the recovery, the accidental phenomenon is shielded, and the high reliability of file operation on the file system side is ensured.
If the CPU receives the error prompt fed back by the driving side of the storage module, the storage module is indicated to be abnormal, and the CPU needs to determine the abnormal type of the storage module. After determining the abnormal type of the storage module, searching a behavior table, determining a processing strategy corresponding to the abnormal type, and performing abnormal processing according to the determined processing strategy, wherein the processing strategy corresponding to each abnormal type is recorded in the behavior table.
In this embodiment, in the running process of the embedded system, after the CPU triggers the file operation on the data in the storage module, if the CPU receives an error alert fed back by the driving side of the storage module, the CPU determines the abnormal type of the storage module; the CPU determines the processing strategy corresponding to the abnormal type according to the behavior table, and performs abnormal processing according to the determined processing strategy, wherein the processing strategy corresponding to each abnormal type is recorded in the behavior table. According to the method, the storage module faults are repaired by processing different fault behaviors at the interfaces of the driving layer and the file operation bottom layer, and the upper software operation is not influenced in the repairing process, so that the purpose of improving the reliability of a file system is achieved.
Further, in an embodiment, before step S10, the method further includes:
when the embedded system starts, the CPU loads the behavior table from the storage module to the reserved memory; the CPU judges whether the starting is power-down restarting or not; if the starting is power-down restarting, the CPU loads an abnormal instruction information table from the storage module to the reserved memory, wherein the abnormal instruction information table is used for recording abnormal instruction information; the CPU checks whether the abnormal instruction information exists in the abnormal instruction information table; if the file system checking command is executed, the embedded system is continuously guided to start, the abnormal instruction information in the abnormal instruction information table is recorded into the historical abnormal instruction information table, the abnormal instruction information table is emptied, and the embedded system starts to operate after the embedded system is guided to start.
In this embodiment, referring to fig. 2, when the embedded system starts to start, the CPU loads the behavior table from the storage module first, and then determines whether the start is a power-down restart. The reserved memory is an initial value after power failure, and if the reserved memory is a regular value (a flag value and a corresponding field value are valid), non-power-failure restarting is proved, otherwise, the reserved memory is power-failure restarting.
If the power is turned off and the power is turned on again, the abnormal instruction information table in the storage module is loaded to the reserved memory. The memory operation data is reserved faster and more reliable than FLASH, and if FLASH is abnormal, the memory record is still effective, and the memory data can be stored without power failure. The memory module is not limited to emmc memory, and other nonvolatile FLASH devices are similar, such as SD card, CFAST card. The information table is still accessible when the reserved memory is for emmc exceptions.
Checking an abnormal instruction information table, if abnormal instruction information exists, which indicates that the last emmc has an abnormality, executing the fsck repairing file system (fsck command comes from abbreviation of English phrase filesystem check, and the function of fsck repairing file system) and then continuing to guide the system, so as to ensure the reliability of the file system, and executing the fsck command without extra. And judging whether the file system needs to be repaired according to the abnormal instruction information table, wherein the reliability is enhanced without influencing the normal starting.
And after the execution of the previous step, clearing the abnormal instruction information table, and storing the last record in the historical instruction information table, wherein the data are stored in the emmc for subsequent examination of the emmc health state, so that the system starting and guiding are completed, and the embedded system starts to operate. The last record is the data of the last start, for example, after a reset key is pressed, the last record (the abnormal record occurring in the last operation) is called before a key is pressed, and the file system abnormality which has occurred last time is dumped in the FLASH file system (namely, a historical abnormal instruction information table) after being repaired this time, so that the historical file is traced back to determine the health degree of the system.
The abnormal instruction information table comprises instruction codes, states, data, block information, the number of starting abnormal times and total abnormal times fields and is used for recording abnormal instructions. The behavior table comprises user state operation, system behavior measurement, instructions, response states, emmc behavior and multiple exception fields in the same block, and is used for a file system side and an emmc driving behavior method when an exception occurs, and referring to fig. 3, fig. 3 is a schematic diagram of the behavior table in an embodiment of the fault processing method of the present invention.
Further, in an embodiment, after the step that the CPU receives the error alert fed back by the driving side of the storage module, the method further includes:
the CPU marks the data and then re-triggers the file operation of the data; after receiving the marked data, the storage module driving side inserts the data into normal data stream preferentially to process and stops triggering new file operation; resetting the memory module to allow the memory module to enter a ready state; after the memory module is in a ready state, the CPU determines the exception type of the memory module.
In this embodiment, if the storage module driving side receives the data stream marked by the file system side, the storage module driving side inserts the data stream preferentially into the normal data stream to process, stops adding a new file operation instruction, resets the storage module to allow the storage module to enter a ready state (reset about 20 ms), and then the CPU determines the abnormal type of the storage module.
Further, in an embodiment, the step of determining the abnormality type of the storage module by the CPU includes:
the CPU sends CMD instructions to the storage module; if the response of the memory module returns an exception or the response is overtime, the CPU determines the exception type of the memory module according to the sent CMD instruction.
Further, in an embodiment, after the step of determining, by the CPU, the type of abnormality of the memory module according to the CMD command sent if the memory module returns an abnormality in response or the response times out, the method further includes:
and recording the abnormal instruction information corresponding to the abnormal type into an abnormal instruction information table.
In this embodiment, the behavior processing refers to fig. 4, and fig. 4 is a schematic flow chart of the behavior processing in an embodiment of the fault processing method of the present invention. In order to accurately control emmc (SD card is similar), the exception handling time is controllable, normal file operation is not affected, and the processing operation of CMD and DATA signal lines of the emmc memory is required to be modified at the bottom layer. CPUHOST sends CMD command to emmc, if response returns exception or overtime does not respond, inquiring and adding information to the exception command information table for fault recovery and analysis. The analysis emmc reads (single block, multi block), erases, writes (single block, multi block) instructions correspond to operations such as open, close, read, write and the like of files on the file system, the abnormal light process processes the abnormal, and the file system side processes confusion when the abnormal light process is heavy, and the file system becomes a read-only state.
If the emmc instruction is abnormal, the instruction can be directly retried due to simple flow and low failure probability. The writing or erasing command can enter a programming state, and the emmc state machine can return an exception when normal, and the emmc state machine exception can not respond when overtime occurs. It is necessary to construct a behavior table for the optimal handling of different anomalies. And if the CPU detects the Ready state of the emmc controller, the CPU sends an instruction, preferentially executes the data in the abnormal instruction information table, updates the result to the abnormal instruction information table, and does not retry if the result still fails. If the block fails a plurality of times, the suspected bad block needs to be actively shielded. When the erasing and writing instructions fail, if the programming state is entered and the overtime is not responded, stopping the new instruction and resetting the emmc controller, and adding information to the abnormal instruction information table to be processed. The emmc is reset for about 20ms during which the emmc controller is busy and the file system data cache can continue to process the new data stream. And (3) erasing and writing other failure states of the instruction, and directly adding information to an abnormal instruction information table to be processed as the instruction reading failure. Failure is returned to the initiator only if the per-table execution fails again.
In a second aspect, the embodiment of the invention further provides an embedded system.
In an embodiment, referring to fig. 5, fig. 5 is a schematic diagram of a system architecture of an embedded system according to an embodiment of the invention. As shown in fig. 5, the embedded system includes a storage module and a CPU, and in the running process of the embedded system, after the CPU triggers a file operation on data in the storage module, if the CPU receives an error alert fed back by a driving side of the storage module, the CPU determines an abnormal type of the storage module; the CPU determines the processing strategy corresponding to the abnormal type according to the behavior table, and performs abnormal processing according to the determined processing strategy, wherein the processing strategy corresponding to each abnormal type is recorded in the behavior table.
Further, in an embodiment, when the embedded system starts, the CPU loads the behavior table from the storage module to the reserved memory; the CPU judges whether the starting is power-down restarting or not; if the starting is power-down restarting, the CPU loads an abnormal instruction information table from the storage module to the reserved memory, wherein the abnormal instruction information table is used for recording abnormal instruction information; the CPU checks whether the abnormal instruction information exists in the abnormal instruction information table; if the file system checking command is executed, the embedded system is continuously guided to start, the abnormal instruction information in the abnormal instruction information table is recorded into the historical abnormal instruction information table, the abnormal instruction information table is emptied, and the embedded system starts to operate after the embedded system is guided to start.
Further, in one embodiment, the CPU marks the data and then re-triggers the file operation on the data; after receiving the marked data, the storage module driving side inserts the data into normal data stream preferentially to process and stops triggering new file operation; resetting the memory module to allow the memory module to enter a ready state; after the memory module is in a ready state, the CPU determines the exception type of the memory module.
Further, in one embodiment, the CPU sends a CMD command to the memory module; if the response of the memory module returns an exception or the response is overtime, the CPU determines the exception type of the memory module according to the sent CMD instruction.
Further, in an embodiment, the abnormal instruction information corresponding to the abnormal type is recorded in an abnormal instruction information table.
The specific embodiments of the embedded system are basically the same as the embodiments of the fault handling method, and are not described herein.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) as described above, comprising several instructions for causing a terminal device to perform the method according to the embodiments of the present invention.
The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.
Claims (10)
1. A fault handling method, the fault handling method comprising:
in the running process of the embedded system, after the CPU triggers the file operation of the data in the storage module, if the CPU receives the error prompt fed back by the driving side of the storage module, the CPU determines the abnormal type of the storage module;
the CPU determines the processing strategy corresponding to the abnormal type according to the behavior table, and performs abnormal processing according to the determined processing strategy, wherein the processing strategy corresponding to each abnormal type is recorded in the behavior table.
2. The method for processing a fault as claimed in claim 1, wherein, during the operation of the embedded system, after the CPU triggers the file operation on the data in the storage module, if the CPU receives an error alert fed back by the driving side of the storage module, the CPU further includes, before the step of determining the type of abnormality of the storage module:
when the embedded system starts, the CPU loads the behavior table from the storage module to the reserved memory;
the CPU judges whether the starting is power-down restarting or not;
if the starting is power-down restarting, the CPU loads an abnormal instruction information table from the storage module to the reserved memory, wherein the abnormal instruction information table is used for recording abnormal instruction information;
the CPU checks whether the abnormal instruction information exists in the abnormal instruction information table;
if the file system checking command is executed, the embedded system is continuously guided to start, the abnormal instruction information in the abnormal instruction information table is recorded into the historical abnormal instruction information table, the abnormal instruction information table is emptied, and the embedded system starts to operate after the embedded system is guided to start.
3. The fault handling method of claim 2, further comprising, after the step of the CPU receiving the error notification fed back from the driving side of the storage module:
the CPU marks the data and then re-triggers the file operation of the data;
after receiving the marked data, the storage module driving side inserts the data into normal data stream preferentially to process and stops triggering new file operation;
resetting the memory module to allow the memory module to enter a ready state;
after the memory module is in a ready state, the CPU determines the exception type of the memory module.
4. The fault handling method of claim 3, wherein the step of the CPU determining the type of exception for the memory module comprises:
the CPU sends CMD instructions to the storage module;
if the response of the memory module returns an exception or the response is overtime, the CPU determines the exception type of the memory module according to the sent CMD instruction.
5. The method for processing a fault as claimed in claim 4, further comprising, after the step of determining the type of abnormality of the memory module by the CPU based on the CMD command transmitted if the memory module returns an abnormality in response or the response times out:
and recording the abnormal instruction information corresponding to the abnormal type into an abnormal instruction information table.
6. The embedded system is characterized by comprising a storage module and a CPU, wherein in the running process of the embedded system, after the CPU triggers the file operation of data in the storage module, if the CPU receives an error prompt fed back by a driving side of the storage module, the CPU determines the abnormal type of the storage module; the CPU determines the processing strategy corresponding to the abnormal type according to the behavior table, and performs abnormal processing according to the determined processing strategy, wherein the processing strategy corresponding to each abnormal type is recorded in the behavior table.
7. The embedded system of claim 6, wherein the CPU loads the behavior table from the storage module to the reserved memory at the start of the startup of the embedded system; the CPU judges whether the starting is power-down restarting or not; if the starting is power-down restarting, the CPU loads an abnormal instruction information table from the storage module to the reserved memory, wherein the abnormal instruction information table is used for recording abnormal instruction information; the CPU checks whether the abnormal instruction information exists in the abnormal instruction information table; if the file system checking command is executed, the embedded system is continuously guided to start, the abnormal instruction information in the abnormal instruction information table is recorded into the historical abnormal instruction information table, the abnormal instruction information table is emptied, and the embedded system starts to operate after the embedded system is guided to start.
8. The embedded system of claim 7, wherein the CPU marks the data and then re-triggers a file operation on the data; after receiving the marked data, the storage module driving side inserts the data into normal data stream preferentially to process and stops triggering new file operation; resetting the memory module to allow the memory module to enter a ready state; after the memory module is in a ready state, the CPU determines the exception type of the memory module.
9. The embedded system of claim 8, wherein the CPU sends CMD commands to the memory module; if the response of the memory module returns an exception or the response is overtime, the CPU determines the exception type of the memory module according to the sent CMD instruction.
10. The embedded system of claim 9, wherein the exception instruction information corresponding to the exception type is recorded to an exception instruction information table.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310801165.8A CN116820824A (en) | 2023-06-30 | 2023-06-30 | Fault processing method and embedded system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310801165.8A CN116820824A (en) | 2023-06-30 | 2023-06-30 | Fault processing method and embedded system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116820824A true CN116820824A (en) | 2023-09-29 |
Family
ID=88123842
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310801165.8A Pending CN116820824A (en) | 2023-06-30 | 2023-06-30 | Fault processing method and embedded system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116820824A (en) |
-
2023
- 2023-06-30 CN CN202310801165.8A patent/CN116820824A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6233108B1 (en) | Storage device with the ability to check for defects in same | |
| US6816984B1 (en) | Method and system for verifying and storing documents during a program failure | |
| US5421003A (en) | Disk storage system with fault tolerant media maintenance | |
| CN102369513A (en) | Method for improving stability of computer system and computer system | |
| CN115620799A (en) | Firmware simulation-based fault site backtracking method and equipment and readable storage medium | |
| CN100395713C (en) | Method of automatic repairing basic input output system element and module | |
| CN114895845A (en) | EMmC data storage control method and embedded mainboard | |
| CN116820824A (en) | Fault processing method and embedded system | |
| CN112579179A (en) | Partition mounting method of embedded system | |
| TW201025309A (en) | Overwrite control method and overwrite control program for data in tape recording apparatus, and tape recording apparatus | |
| JP3675375B2 (en) | Nonvolatile memory and data rewriting method of nonvolatile memory | |
| JPH07182250A (en) | Automatic substituting processing system for magnetic disk | |
| US20100169572A1 (en) | Data storage method, apparatus and system for interrupted write recovery | |
| CN111813748B (en) | File system mounting method and device, electronic equipment and storage medium | |
| CN112908390B (en) | Data storage method, device, electronic equipment and storage medium | |
| US6229743B1 (en) | Method of a reassign block processing time determination test for storage device | |
| CN111897583A (en) | Equipment starting method and embedded equipment | |
| CN111859458A (en) | Data updating recording method, system, medium and equipment | |
| JPH08287207A (en) | Ic card | |
| CN110826114A (en) | User data testing method and device based on SSD after safe erasure | |
| JP2005149291A (en) | Filesystem, program therefor, and information processing system | |
| US8108740B2 (en) | Method for operating a memory device | |
| CN114840360A (en) | Program loading method and device, electronic equipment and storage medium | |
| CN112562774B (en) | Storage device mounting method and device, computer device and storage medium | |
| CN117194110A (en) | Data heterogeneous storage system and abnormal data self-recovery method |
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 |