WO2017162049A1

WO2017162049A1 - Method and device for monitoring memory data of drive module

Info

Publication number: WO2017162049A1
Application number: PCT/CN2017/076290
Authority: WO
Inventors: 罗忠明; 熊飞; 吴胜楠; 陈明宇; 梁建明; 张雲瑞
Original assignee: 广州广电运通金融电子股份有限公司
Priority date: 2016-03-24
Filing date: 2017-03-10
Publication date: 2017-09-28
Also published as: CN105869309A

Abstract

A method for monitoring memory data of a drive module. In the method, memory data of a drive module is pre-stored in a memory space with a pre-set structure; and each time a processing request regarding the memory space is received, a current checksum of the memory space is calculated (S101), and an original checksum of the memory space is acquired (S102); if the two checksums are the same, a processing operation can be executed on the memory data (S103); and if the two checksums are different, it indicates that the memory data of the memory space is broken, and a pre-set error processing operation needs to be executed (S104). In the method, memory data of a drive module can be monitored in real time, and an erroneous drive module can also be accurately positioned, thus being able to accurately process a fault in time. Furthermore, a device for monitoring memory data of a drive module is provided, so as to ensure the application and realization of the method in practice.

Description

Drive module memory data monitoring method and device

The present application claims priority to Chinese Patent Application No. 201610180088.9, entitled "Driving Module Memory Data Monitoring Method and Apparatus", filed on March 24, 2016, the entire contents of which is hereby incorporated by reference. in.

Technical field

The present application relates to the field of memory data protection technologies, and more particularly, to a technique for monitoring memory data of a driver module.

Background technique

Generally, an automatic teller machine (hereinafter referred to as an ATM machine) is associated with a plurality of input and output devices, such as a card reader, a printer, and a PIN pad. These input and output devices each have a drive module, and each drive module has its own private data.

When each driver module is running, it needs to share the memory of the ATM machine. There is a possibility that the memory data of a certain driver module is damaged by other driver modules of the error. For example, a driver module itself has a pointer running away, an array is out of bounds, and the like. The driver module that has made a mistake overwrites the memory data of other driver modules. As a result, the ATM machine may eventually fail to function or even crash. For example, the ATM machine is provided with three drive modules A, B, and C. In the normal working state, the memory areas of the drive module A, the drive module B, and the drive module C are independent, if the drive module B is Overwriting or rewriting the memory area of drive module A in the memory area will cause the ATM machine program to be abnormal.

Therefore, a technical solution is needed to implement monitoring of the memory data of the drive module.

Summary of the invention

In view of this, the present application provides a method for monitoring memory data of a driving module for monitoring whether memory data of a driving module is destroyed. In addition, the present application also provides a drive module memory data monitoring device for ensuring the application and implementation of the method in practice.

To achieve the stated object, the technical solution provided by the present application is as follows:

A first aspect of the present application provides a method for monitoring a memory data of a driver module, where the memory data of the driver module is monitored, and the memory data is stored in a memory space of a preset structure, and the method includes:

Determining a current checksum of the memory space if a processing request for the memory data is received; wherein the current checksum is used to indicate a current memory usage of the memory space;

Obtaining an original checksum of the memory space; wherein the original checksum is used to record a memory usage of the memory space after a last write operation;

And if the current checksum is the same as the original checksum, performing a processing operation corresponding to the processing request on the memory data;

If the current checksum is different from the original checksum, a preset error processing operation is performed.

The second aspect of the present application provides a drive module memory data monitoring device for monitoring memory data of a drive module, where the memory data is stored in a memory space of a preset structure, the device includes:

a current checksum determining module, configured to determine a current checksum of the memory space if a processing request for the memory data is received, wherein the current checksum is used to represent a current memory of the memory space Occupation situation;

An original checksum obtaining module, configured to obtain an original checksum of the memory space, where the original checksum is used to record a memory occupation situation of the memory space after a last write operation;

a checksum processing module, configured to perform a processing operation corresponding to the processing request on the memory data if the current checksum is the same as the original checksum;

The checksum different processing module is configured to perform a preset error processing operation if the current checksum is different from the original checksum.

It can be seen from the above technical solution that the present application provides a method for monitoring memory data of a driving module, which pre-stores the memory data of the driving module in a memory space of a preset structure, and receives the memory space each time. When the request is processed, the current checksum of the memory space is calculated and the original checksum of the memory space is obtained. If the two are the same, the memory data may be processed. If the two are not the same, the memory space is represented. The memory data is destroyed, and the preset error handling operation needs to be performed. This application can not only monitor the memory data of the driver module in real time, but also can accurately locate The faulty drive module allows the fault to be processed in a timely and accurate manner.

DRAWINGS

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings to be used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are only It is an embodiment of the present application, and those skilled in the art can obtain other drawings according to the provided drawings without any creative work.

1 is a flowchart of Embodiment 1 of a method for monitoring memory data of a driving module provided by the present application;

2 is a diagram showing an example of a state of a memory data of a driver module provided by the present application;

FIG. 3 is a code example of requesting allocation of a memory space to a system according to the present application; FIG.

4a, 4b are flowcharts of the process of reading the memory data of the monitoring driver module provided by the present application;

5a, 5b are flow charts of the process of writing memory data of the monitoring driver module provided by the present application;

FIG. 6 is a schematic structural diagram of Embodiment 1 of a memory module data monitoring device of a driving module provided by the present application.

detailed description

The technical solutions in the embodiments of the present application are clearly and completely described in the following with reference to the drawings in the embodiments of the present application. It is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

A specific application scenario of the present application is to monitor the memory data related to the driver module of the ATM machine. It can be known that the input and output devices of the ATM machine have their own drive modules, and the drive modules have their own private data. According to the actual needs, which private data needs to be protected, the private data can be stored in the memory space of the preset structure in advance. It should be noted that each driver module of the ATM machine has its own corresponding memory space, and the memory space corresponding to different driver modules is different.

Of course, the application is not limited to protecting the memory data of the ATM machine driver module, and the monitoring of the memory data of the driver module of other devices may also use the method provided by the present application without departing from the protection of the present application. Range of protection.

The following is an example of a drive module of an ATM machine.

Referring to FIG. 1 , a flow of Embodiment 1 of a method for monitoring memory data of a driving module provided by the present application is shown. As shown in FIG. 1 , this embodiment may specifically include steps S101 to S104.

Step S101: Determine a current checksum of the memory space if a processing request for the memory data is received, where the current checksum is used to indicate the current memory usage of the memory space.

As above, the private data of the driver module of the ATM machine is stored in a memory space of a preset structure. Therefore, other modules of the ATM machine, such as a central processing unit, cannot directly directly access the memory when processing the private data of the driver module. The data is processed, but a processing request needs to be sent to the execution module of the present embodiment. It should be noted that the normal processing request for the driver module triggers the execution of the present application, that is, the normal processing request for the driver module is sent to the execution module of the embodiment to trigger the execution of the embodiment.

After receiving the processing request, the execution module of the embodiment first calculates a checksum of the memory space. In order to distinguish from the original checksum of the memory space, the checksum calculated in this step may be referred to as a current checksum. . It can be understood that the memory space is a memory space for storing the memory data corresponding to the processing request.

Step S102: Acquire an original checksum of the memory space; wherein the original checksum is used to record the memory usage of the memory space after the last write operation.

The original checksum can be saved in the memory space, and the original checksum can be obtained directly in the memory space. The original checksum records the memory footprint of the memory space after the most recent write operation.

It should be noted that the last write operation may be a write operation performed at the time of initialization, or may be a write operation to the memory space at any time after initialization. The write operation may directly write data that does not exist in the memory space, or modify the original data in the memory space.

In addition, the execution order of this step and step S101 does not affect the implementation of the present application. Therefore, this step may be performed simultaneously with the above step S102, or step S102 may be performed first and then step S101 may be performed.

It can be understood that if the data in the memory space is illegally processed, the memory space of the memory space is occupied. The situation may change. Referring to a memory data error situation shown in Figure 2, as shown in Figure 2, the ATM machine is provided with three drive modules A, B, and C. Under normal working conditions, the ATM machine drives the module A and the drive module B. The memory area of the driver module C is independent. If the memory area of the driver module B overwrites or rewrites the memory area of the driver module A, the ATM program is abnormal.

Therefore, the present application can determine whether the data in the memory space is modified according to the memory occupancy. Specifically, the current checksum of the memory space is compared with the original checksum of the memory space, and the following step S103 or step S104 is performed according to the comparison result.

Step S103: If the current checksum is the same as the original checksum, the processing operation corresponding to the processing request is performed on the memory data.

The current checksum is the same as the original checksum, indicating that the memory space is not in error after the last write operation, and the processing operation corresponding to the processing request may be performed on the memory data normally, and the processing operation is performed, such as reading or Write and so on.

Step S104: If the current checksum is different from the original checksum, the preset error processing operation is performed.

If the current checksum is different from the original checksum, it means that the memory space has been wrong after the last write operation, and the preset error processing operation needs to be performed. The error processing operation may be storing the memory data of the memory space that is in error and the visitor to the memory space for subsequent error analysis.

According to the above technical solution, the method for monitoring memory data of a driving module provided by the present application, the method pre-stores the memory data of the driving module in a memory space of a preset structure, and receives a processing request for the memory space each time. The current checksum of the memory space is calculated and the original checksum of the memory space is obtained. If the two are the same, the memory data may be processed. If the two are not the same, the memory of the memory space is represented. The data is corrupted and the preset error handling operations need to be performed. The application not only can monitor the memory data of the driving module in real time, but also can accurately locate the faulty driving module, so that the fault can be processed in time and accurately.

Specifically, in the existing ATM machine fault processing mode, the log only records the faulty drive module. As shown in FIG. 2, the memory data of the drive module B is incorrectly changed, and the drive module A is abnormally changed. The log records that the driver module A has an abnormality. However, if the abnormal code is not found in the driver module A, the drive module B that is actually faulty cannot be located, and the fault cannot be processed in time.

However, the application can store the memory data of the driver module B in the memory space of the preset structure, and monitor the memory occupancy of the memory space. If the memory usage of the memory space changes, the driver module can be determined. B is an error module, and a preset error processing operation can be performed on the drive module B.

Specifically, in the example shown in FIG. 2, it is assumed that the driving module B abnormally rewrites or overwrites the memory data of the driving module A due to its own error, and the driving is monitored during the memory data monitoring process of the driving module A. The current checksum of module A is different from the original checksum, and the memory data of the drive module A error and the visitor drive module B can be written to the file. Through the analysis of the file, it can be known that the driver module B has abnormal access to the driver module A.

Of course, the drive module B itself is also monitored. Once the drive module B is in error, the error state of the drive module B can be found, and the error processing operation can be performed on the drive module B.

As above, the memory data of the drive module B is stored in the memory space of the preset structure. The address of the memory space is continuous, and the end address indicates the checksum variable. The address of the checksum variable is immediately after the address of the memory data, and the checksum variable is used to store the original checksum.

Specifically, the following allocates a memory space by allocating a memory example of memory space for memory data.

As shown in FIG. 3, codes M1 to M4 are used to allocate a memory space to the system request. Wherein, the code M1 declares the type name of the memory space to be protected, and the code M2 declares the memory variable to be protected (the memory variable is used to store the private data of the driver module, the private data is the memory data), and the code M3 declares the checksum variable, the code M4 requests to allocate a memory space instance. The compiler of the ATM system can generate a memory space for storing private data according to the codes M1 to M4.

Of course, the code shown in Figure 3 is just an example. The name of the memory space, the name of the memory variable, the type of the memory variable, the number of memory variables, the type of the checksum variable, the name of the checksum variable, etc. It is the other, not limited to the one shown in Figure 3. In addition, the code shown in FIG. 3 is described using the C language, and programming codes written in other programming languages that are consistent with the implementation ideas of the present application are within the scope of the present application.

After initializing the above memory space, you need to calculate the checksum of the memory space and store the checksum in the checksum variable. Of course, every time you normally write to the memory space, you need to recalculate the The checksum of the memory space and the recalculated checksum is stored in the checksum variable. The checksum stored in the checksum variable is called the original checksum.

Specifically, the steps of calculating the checksum include:

The difference between the memory address of the checksum variable and the first address of the memory space is determined as the length of the memory space, and the memory space is located according to the first address of the memory space and the length of the memory space; the checksum algorithm is used to calculate the The checksum of the current memory data in the memory space and the calculated checksum as the current checksum.

Among them, when the system allocates memory space, it is dynamically allocated according to the compile instruction and execution status, and the first address of the memory space is random. Although the first address of the memory space is random, the memory address of the checksum variable minus the first address of the memory space can determine the length of the memory space. After determining the length of the memory space, the memory is located according to the first address and the length, and the memory data currently stored in the memory space is obtained, and the checksum of the memory data is calculated by using a checksum algorithm. In order to distinguish from the checksum stored in the checksum variable, the currently calculated checksum is referred to as the current checksum. .

It should be noted that the checksum algorithm used in this application may be, but not limited to, CRC (Cyclical Redundancy Check), MD5 (Message-Digest Algorithm 5), SHA ( Algorithms such as Secure Hash Algorithm.

The above step of calculating the checksum may calculate the original checksum of the memory data, and may also determine the current checksum of the memory data after receiving the processing request for the drive module memory data.

If the read request for the memory data of the drive module is received, the reading of the memory data can be monitored. The monitoring process will be described in detail below with reference to FIG. 4a and FIG. 4b.

As shown in FIG. 4a, in one example, the monitoring process may include steps S401 to S404.

Step S401: Determine a current checksum of the memory space if a read request for the memory data is received; wherein the current checksum is used to indicate the current memory usage of the memory space.

Step S402: Acquire an original checksum of the memory space; wherein the original checksum is used to record the memory usage of the memory space after the last execution of the write operation.

Step S403: If the current checksum is the same as the original checksum, the memory data is read from the memory space.

Step S404: If the current checksum is different from the original checksum, the preset error processing operation is performed.

The preset error processing operation may include: writing memory data of the memory space into the file, and triggering the error handler to perform system maintenance operations. At the same time, visitors to the memory space can also be written to the file. This file is similar to an error report that saves illegally changed memory data to facilitate subsequent analysis of the source of illegally changed memory data. In another example, the system API interface can also be invoked to perform a dump dump operation to save the running site of the process for subsequent analysis.

It should be noted that the method for determining the original checksum and the current checksum in this embodiment can be referred to the calculation steps of the above checksum, and details are not described herein.

As shown in FIG. 4b, in a more specific example, the monitoring process for reading the memory data may specifically include steps S411 to S414.

Step S411: After receiving the read request for the memory data, calculate the current checksum of the memory space.

Step S412: Compare the current checksum with the original checksum. If the comparison result is equal, step S413 is performed to read the memory data; if the comparison results are not equal, step S414 is performed to perform error processing.

The original checksum is obtained from the original checksum variable and compared with the current checksum, and different processing actions are performed according to the comparison result.

If a write request for the drive module memory data is received, the process of writing the memory data into the memory space of the drive module can be monitored. The monitoring process will be described in detail below with reference to FIGS. 5a and 5b.

As shown in FIG. 5a, in an example, the monitoring process may specifically include steps S501 to S504.

Step S501: Determine a current checksum of the memory space if a write request for the memory data is received; wherein the current checksum is used to indicate the current memory usage of the memory space.

Step S502: Acquire an original checksum of the memory space; wherein the original checksum is used to record the memory usage of the memory space after the last execution of the write operation.

Step S503: If the current checksum is the same as the original checksum, write new memory data into the memory space, and determine a new checksum of the memory space, and update the original checksum to a new checksum.

The original checksum is stored in the checksum variable of the storage space, and the new checksum is stored in the checksum variable, so that the original checksum can be updated to a new checksum.

Step S504: If the current checksum is different from the original checksum, the preset error processing operation is performed.

See the above description of the monitoring process of the drive module memory data reading, the default error handling operation The method may include: writing the memory data of the memory space to the file, and triggering the error handler to perform system maintenance operations.

For the determination of the original checksum, the current checksum, and the new checksum in this embodiment, refer to the calculation steps of the checksum above, and details are not described herein.

As shown in FIG. 5b, in a more specific example, the monitoring process for writing the memory data may specifically include steps S511 to S516.

Step S511: If a write request for the memory data is received, the current checksum of the memory space is calculated.

Step S512: Compare whether the current checksum and the original checksum are equal. If they are equal, step S513 is performed, and if not, step S516 is performed.

Step S513: Write the memory data into the memory space.

Step S514: Calculate a new checksum of the memory space after writing the memory data, that is, calculate a new checksum of the written memory data.

Step S515: Write the new checksum to the checksum variable to update the original checksum in the checksum variable.

Step S516: Perform error processing. For specific error handling, refer to the above description, which is not described here.

The following describes the drive module memory data monitoring device provided by the present application. It should be noted that the following description of the drive module memory data monitoring device can be referred to the above-mentioned drive module memory data monitoring method, which is not described below.

Corresponding to Embodiment 1 of the above-mentioned driving module memory data monitoring method, the present application provides a driving module memory data monitoring device Embodiment 1. This embodiment is used to monitor the memory data of the driver module, and the memory data is stored in the memory space of the preset structure.

As shown in FIG. 6, the embodiment may specifically include: a current checksum determining module 601, an original checksum obtaining module 602, a checksum identical processing module 603, and a checksum different processing module 604. among them:

The current checksum determining module 601 is configured to determine a current checksum of the memory space if the processing request for the memory data is received, where the current checksum is used to indicate the current memory usage of the memory space;

The original checksum obtaining module 602 is configured to obtain an original checksum of the memory space; wherein, the original The checksum is used to record the memory usage of the memory space after the last write operation;

a checksum identical processing module 603, configured to perform a processing operation corresponding to the processing request on the memory data if the current checksum is the same as the original checksum;

The checksum different processing module 604 is configured to perform a preset error processing operation if the current checksum is different from the original checksum.

It can be seen from the above technical solution that the monitoring device for the memory data of the driving module provided by the present application stores the memory data of the driving module in a preset memory space in advance, and the current checksum determining module 601 receives the memory space each time. When the request is processed, the current checksum of the memory space is calculated, and the original checksum obtaining module 602 obtains the original checksum of the memory space. If the two are the same, the checksum same processing module 603 can access the memory data. The processing operation is performed. If the two are not the same, it indicates that the memory data of the memory space is destroyed, and the checksum different processing module 604 needs to perform a preset error processing operation. The application not only can monitor the memory data of the driving module in real time, but also can accurately locate the faulty driving module, so that the fault can be processed in time and accurately.

In a specific example, the memory space preset by the driver module memory data monitoring device has the following characteristics, that is, the address is continuous, and the end address indicates the checksum variable, and the address of the checksum variable is immediately after the address of the memory data. The checksum variable is used to store the original checksum.

In a specific example, the current checksum determining module 601 may specifically include: a memory space length determining submodule and a current checksum calculating submodule. among them:

The memory space locating submodule is configured to determine the difference between the memory address of the checksum variable and the first address of the memory space when receiving the processing request for the memory data, and determine the length of the memory space according to the first address of the memory space and The length of the memory space, and the memory space is located;

The current checksum calculation sub-module is configured to calculate a checksum of the current memory data in the memory space using the checksum algorithm, and use the calculated checksum as the current checksum.

In a specific example, the checksum same processing module 603 may specifically include: an in-memory data reading sub-module and an in-memory data writing sub-module. among them:

The memory data reading submodule is configured to: if the current checksum is the same as the original checksum, and the processing request is Read the request, then read the memory data from the memory space;

The memory data is written into the submodule, and if the current checksum is the same as the original checksum and the processing request is a write request, the new memory data is written into the memory space, and a new checksum of the memory space is determined. Update the original checksum to a new checksum.

In one specific example, the checksum different processing module 604 can specifically include: a checksum different processing sub-module. among them:

The checksum different processing submodule is used to write the memory data in the memory space to the file if the current checksum is different from the original checksum, and trigger the error handler to perform system maintenance operations.

It should be noted that each embodiment in the specification is described in a progressive manner, and each embodiment focuses on differences from other embodiments, and the same similar parts between the embodiments are referred to each other. can.

It should also be noted that, in this context, relational terms such as first and second, etc. are used merely to distinguish one entity or operation from another entity or operation, without necessarily requiring or implying such entities or operations. There is any such actual relationship or order between them. Furthermore, the term "comprises" or "comprises" or "comprises" or any other variations thereof is intended to encompass a non-exclusive inclusion, such that a process, method, article, or device that comprises a plurality of elements includes not only those elements but also Other elements, or elements that are inherent to such a process, method, item, or device. An element that is defined by the phrase "comprising a ..." does not exclude the presence of additional elements in the process, method, article, or device that comprises the above described elements.

The above description of the disclosed embodiments enables those skilled in the art to make or use the application. Various modifications to these embodiments are obvious to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the application. Therefore, the application is not limited to the embodiments shown herein, but is to be accorded the broadest scope of the principles and novel features disclosed herein.

Claims

A method for monitoring a memory data of a driving module, configured to monitor memory data of a driving module, where the memory data is stored in a memory space of a preset structure, the method comprising:

Determining a current checksum of the memory space if a processing request for the memory data is received; wherein the current checksum is used to indicate a current memory usage of the memory space;

Obtaining an original checksum of the memory space; wherein the original checksum is used to record a memory usage of the memory space after a last write operation;

And if the current checksum is the same as the original checksum, performing a processing operation corresponding to the processing request on the memory data;

If the current checksum is different from the original checksum, a preset error processing operation is performed.
The method for monitoring memory data of a driving module according to claim 1, wherein the address of the memory space is continuous, and the end address indicates a checksum variable, and the address of the checksum variable is immediately adjacent to the memory data. After the address, the checksum variable is used to store the original checksum.
The method for monitoring a memory data of a driving module according to claim 2, wherein the determining a current checksum of the memory space comprises:

Determining a difference between a memory address of the checksum variable and a first address of the memory space as a length of the memory space, and positioning the location according to a first address of the memory space and a length of the memory space Memory space

Using the checksum algorithm, a checksum of the current memory data in the memory space is calculated, and the calculated checksum is used as the current checksum.
The method for monitoring the memory data of the driving module according to claim 1, wherein the performing the processing operation corresponding to the processing request on the memory data comprises:

If the processing request is a read request, reading the memory data from the memory space;

If the processing request is a write request, write new memory data into the memory space, and determine a new checksum of the memory space, and update the original checksum to the new school Check and.
The method for monitoring a memory data of a driving module according to claim 1, wherein the performing a preset error processing operation comprises:

Writes the memory data in the memory space to a file and triggers an error handler to perform system maintenance operations.
A driving module memory data monitoring device is configured to monitor memory data of a driving module, where the memory data is stored in a memory space of a preset structure, the device includes:

a current checksum determining module, configured to determine a current checksum of the memory space if a processing request for the memory data is received, wherein the current checksum is used to represent a current memory of the memory space Occupation situation;

An original checksum obtaining module, configured to obtain an original checksum of the memory space, where the original checksum is used to record a memory occupation situation of the memory space after a last write operation;

a checksum processing module, configured to perform a processing operation corresponding to the processing request on the memory data if the current checksum is the same as the original checksum;

The checksum different processing module is configured to perform a preset error processing operation if the current checksum is different from the original checksum.
The drive module memory data monitoring apparatus according to claim 6, wherein the address of the memory space is continuous, and the end address indicates a checksum variable, and the address of the checksum variable is immediately adjacent to the memory data. After the address, the checksum variable is used to store the original checksum.
The device for monitoring the memory data of the driving module according to claim 7, wherein the current checksum determining module comprises:

a memory space locating submodule, configured to determine, as a processing request for the memory data, a difference between a memory address of the checksum variable and a first address of the memory space as a length of the memory space, And positioning the memory space according to the first address of the memory space and the length of the memory space;

The current checksum calculation submodule is configured to calculate a checksum of the current memory data in the memory space by using a checksum algorithm, and use the calculated checksum as the current checksum.
The device for monitoring memory data of a driving module according to claim 6, wherein the same processing module of the checksum comprises:

a memory data reading submodule, configured to read the memory data from the memory space if the current checksum is the same as the original checksum and the processing request is a read request;

a memory data writing submodule, configured to: when the current checksum is the same as the original checksum, and the processing request is a write request, write new memory data into the memory space, and determine Said A new checksum of the memory space, updating the original checksum to the new checksum.
The device for monitoring memory data of a driving module according to claim 6, wherein the different processing modules of the checksum comprise:

The checksum different processing submodule is configured to write the memory data in the memory space to the file if the current checksum is different from the original checksum, and trigger the error handler to perform a system maintenance operation.