CN113805967A - MPU (micro processing Unit) safe starting method and MPU safe starting system - Google Patents

MPU (micro processing Unit) safe starting method and MPU safe starting system Download PDF

Info

Publication number
CN113805967A
CN113805967A CN202111093105.2A CN202111093105A CN113805967A CN 113805967 A CN113805967 A CN 113805967A CN 202111093105 A CN202111093105 A CN 202111093105A CN 113805967 A CN113805967 A CN 113805967A
Authority
CN
China
Prior art keywords
partition
backup
mpu
boot
main
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
Application number
CN202111093105.2A
Other languages
Chinese (zh)
Inventor
梁群
张萍
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Yuanfeng Technology Co Ltd
Original Assignee
Yuanfeng Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Yuanfeng Technology Co Ltd filed Critical Yuanfeng Technology Co Ltd
Priority to CN202111093105.2A priority Critical patent/CN113805967A/en
Publication of CN113805967A publication Critical patent/CN113805967A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • G06F9/44505Configuring for program initiating, e.g. using registry, configuration files
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error 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/0706Error 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/0736Error 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
    • G06F11/0739Error 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 in a data processing system embedded in automotive or aircraft systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1415Saving, restoring, recovering or retrying at system level
    • G06F11/1417Boot up procedures

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Quality & Reliability (AREA)
  • Stored Programmes (AREA)

Abstract

The invention discloses an MPU safe starting method and an MPU safe starting system, wherein the method comprises the following steps: detecting whether a main partition in the FLASH memory is damaged or not in response to a starting operation; if not, running the starting content in the main partition; if yes, copying the starting content stored in the backup partition to the main partition from the backup partition in the FLASH memory, and running the starting content in the main partition. According to the MPU safe starting method and the MPU safe starting system, the starting content is copied to the main partition from the backup partition and operated after the main partition in the FLASH memory is detected to be damaged, so that the probability of starting failure of the MPU is reduced, the starting success rate is improved, and the operation stability of the MPU is ensured.

Description

MPU (micro processing Unit) safe starting method and MPU safe starting system
Technical Field
The invention relates to the technical field of computers, in particular to an MPU (micro processing unit) safe starting method and an MPU safe starting system.
Background
With the continuous development of science and technology and society, the appearance of various intelligent and automatic vehicles greatly facilitates the work and life of people.
A vehicle-mounted T-Box (also called a car Box) is a very important component in a current car networking system, and its main function is to realize interconnection between a car and a car remote Service Provider (TSP).
Currently, the start content for starting an MPU (Microprocessor Unit) in the on-board T-Box is stored in a Flash memory. When the vehicle-mounted T-Box is triggered to start, the starting content in the Flash memory runs, and if the starting content is found to be damaged, the T-Box starts unsuccessfully, and the starting success rate of the vehicle-mounted T-Box cannot be ensured.
Therefore, there is a need for improvements in the art.
The above information is given as background information only to aid in understanding the present disclosure, and no determination or admission is made as to whether any of the above is available as prior art against the present disclosure.
Disclosure of Invention
The invention provides an MPU (micro processing Unit) safe starting method and an MPU safe starting system, which aim to solve the defects of the prior art.
In order to achieve the above purpose, the present invention provides the following technical solutions:
in a first aspect, an embodiment of the present invention provides a method for safely starting an MPU, where the method includes:
detecting whether a main partition in the FLASH memory is damaged or not in response to a starting operation;
if not, running the starting content in the main partition;
if yes, copying the starting content stored in the backup partition to the main partition from the backup partition in the FLASH memory, and running the starting content in the main partition.
Further, in the MPU secure boot method, the step of copying boot contents stored in the backup partition from the backup partition in the FLASH memory to the main partition, and executing the boot contents in the main partition includes:
formatting the primary partition;
copying boot contents stored in the backup partition from the backup partition in the FLASH memory into the primary partition;
executing the boot content in the main partition.
Further, in the MPU secure boot method, before the step of detecting whether the main partition in the FLASH memory is damaged in response to the boot operation, the method further includes:
setting a main partition and a backup partition in the FLASH memory in advance;
boot contents for booting the MPU are stored in the main partition and the backup partition, respectively.
Further, in the MPU secure boot method, after the step of executing boot contents in the main partition, the method further includes:
detecting whether the main partition in operation is abnormal or not;
and if so, switching from the main partition to the backup partition, and running the starting content in the backup partition.
Further, in the MPU secure boot method, after the step of switching from the main partition to the backup partition and executing boot contents in the backup partition, the method further includes:
formatting the primary partition;
copying boot contents stored in the backup partition from the backup partition in the FLASH memory into the primary partition;
switching from the backup partition to the primary partition and running boot content in the primary partition.
In a second aspect, an embodiment of the present invention provides an MPU secure boot system, where the system includes:
a damage detection module for detecting whether a main partition in the FLASH memory is damaged in response to a start operation;
the first starting module is used for running the starting content in the main partition if the main partition is damaged;
and the second starting module is used for copying the starting content stored in the backup partition from the backup partition in the FLASH memory to the main partition and running the starting content in the main partition if the main partition is not damaged.
Further, in the MPU secure boot system, the second boot module is specifically configured to:
formatting the primary partition;
copying boot contents stored in the backup partition from the backup partition in the FLASH memory into the primary partition;
executing the boot content in the main partition.
Further, in the MPU secure boot system, the system further includes a partition establishment module configured to:
before the step of responding to the starting operation and detecting whether the main partition in the FLASH memory is damaged, the main partition and the backup partition are arranged in the FLASH memory in advance;
boot contents for booting the MPU are stored in the main partition and the backup partition, respectively.
Further, in the MPU secure boot system, the system further includes an anomaly detection module configured to:
after the step of running the boot contents in the main partition, detecting whether the running main partition is abnormal;
and if so, switching from the main partition to the backup partition, and running the starting content in the backup partition.
Further, in the MPU secure boot system, the system further includes a recovery switching module configured to:
formatting the primary partition after the step of switching from the primary partition to the backup partition and running boot contents in the backup partition;
copying boot contents stored in the backup partition from the backup partition in the FLASH memory into the primary partition;
switching from the backup partition to the primary partition and running boot content in the primary partition.
Compared with the prior art, the embodiment of the invention has the following beneficial effects:
according to the MPU safe starting method and the MPU safe starting system provided by the embodiment of the invention, after the damage of the main partition in the FLASH memory is detected, the starting content is copied into the main partition from the backup partition and operated, so that the probability of starting failure of the MPU is reduced, the starting success rate is improved, and the operation stability of the MPU is ensured.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without inventive exercise.
FIG. 1 is a flowchart illustrating a secure booting method for an MPU according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a secure booting method for an MPU according to a second embodiment of the present invention;
FIG. 3 is a flowchart illustrating a secure booting method for an MPU according to a third embodiment of the present invention;
fig. 4 is a functional module schematic diagram of an MPU secure boot system according to a fourth embodiment of the present invention.
Detailed Description
In order to make the objects, features and advantages of the present invention more obvious and understandable, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the embodiments described below are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In the description of the present invention, it is to be understood that when an element is referred to as being "connected" to another element, it can be directly connected to the other element or intervening elements may also be present. When a component is referred to as being "disposed on" another component, it can be directly on the other component or intervening components may also be present.
Furthermore, the terms "long", "short", "inner", "outer", and the like indicate orientations or positional relationships based on those shown in the drawings, and are only for convenience of describing the present invention, but do not indicate or imply that the referred devices or elements must have the specific orientations, be configured to operate in the specific orientations, and thus are not to be construed as limitations of the present invention.
The technical scheme of the invention is further explained by the specific implementation mode in combination with the attached drawings.
Example one
In view of the defects of the prior art, the inventor of the invention actively researches and innovates based on abundant practical experience and professional knowledge in many years of the industry and by matching with the application of the theory, so as to create a feasible safe starting technology of the MPU, thereby ensuring that the MPU has higher practicability. After continuous research, design and repeated trial and improvement, the invention with practical value is finally created.
Referring to fig. 1, fig. 1 is a schematic flowchart of a secure MPU startup method, which is applicable to a scenario of starting an MPU in a vehicle-mounted T-Box and is implemented by an MPU secure startup system, which may be implemented by software and/or hardware and integrated inside the vehicle-mounted T-Box. As shown in fig. 1, the MPU secure boot method may include the steps of:
s101, responding to the starting operation, and detecting whether a main partition in the FLASH memory is damaged; if not, step S102 is executed, and if yes, step S103 is executed.
The start operation refers to an operation of starting the in-vehicle T-Box issued by the user, and in general, the start operation may be issued by manually operating a physical key or a virtual key. When a boot operation is received, the embodiment responds by detecting whether the main partition in the FLASH memory is damaged. The self-checking step exists in each starting, and the event that the MPU fails to start is reduced.
And S102, running the starting content in the main partition.
It should be noted that when it is determined that the main partition in the FLASH memory is not damaged, the main partition as the default boot partition is necessarily required to be executed, specifically, the boot contents for booting the MPU stored in the main partition are executed. The starting content is pre-stored in the main partition, and can be modified, added and deleted according to the needs.
S103, copying the starting content stored in the backup partition to the main partition from the backup partition in the FLASH memory, and running the starting content in the main partition.
It should be noted that, in this embodiment, the starting contents in the main partition and the backup partition are the same, and the backup partition may be regarded as a backup of the main partition, and provides a backup function when necessary.
Specifically, when it is determined that the main partition in the FLASH memory is damaged, it is necessary to also preferably run the main partition as the default boot partition, but since the main partition is damaged at this time, that is, the boot contents stored in the main partition have errors, before the main partition is run, repair needs to be performed, specifically, the boot contents stored in the backup partition are copied into the main partition from the backup partition in the FLASH memory, so that the successfully copied boot contents in the main partition can be run.
In this embodiment, preferably, the step S103 may further include the steps of:
formatting the primary partition;
copying boot contents stored in the backup partition from the backup partition in the FLASH memory into the primary partition;
executing the boot content in the main partition.
It should be noted that before copying the startup content stored in the backup partition from the backup partition in the FLASH memory to the main partition, the startup content with an error in the main partition needs to be deleted, specifically, a formatting operation needs to be performed, and then the main partition can be restored to a normal state, so that the startup content in the backup partition can be copied.
According to the MPU safe starting method provided by the embodiment of the invention, after the damage of the main partition in the FLASH memory is detected, the starting content is copied into the main partition from the backup partition and operated, so that the probability of starting failure of the MPU is reduced, the starting success rate is improved, and the operation stability of the MPU is ensured.
Example two
Fig. 2 is a flowchart illustrating a secure MPU booting method according to a second embodiment of the present invention, where in the first embodiment, before "detecting whether a main partition in a FLASH memory is damaged in response to a booting operation" in step S101, the present embodiment is further optimized. Explanations of the same or corresponding terms as those of the above embodiments are omitted. Namely:
setting a main partition and a backup partition in the FLASH memory in advance;
boot contents for booting the MPU are stored in the main partition and the backup partition, respectively.
Based on the above optimization, as shown in fig. 2, the MPU secure boot method provided in this embodiment may include the following steps:
s201, setting a main partition and a backup partition in the FLASH memory in advance.
It should be noted that, the purpose of the present embodiment of setting the main partition and the backup partition in the FLASH memory is to provide a fault-tolerant mechanism for the startup of the MPU, that is, when the main partition is damaged, the main partition is repaired by the backup partition, so that the main partition can be started normally.
S202, storing the starting content for starting the MPU in the main partition and the backup partition respectively.
It should be noted that, the startup content stored in the primary partition and the backup partition may be added, deleted and modified according to different needs.
S203, responding to the starting operation, and detecting whether the main partition in the FLASH memory is damaged; if not, step S204 is executed, and if yes, step S205 is executed.
And S204, running the starting content in the main partition.
S205, copying the starting content stored in the backup partition to the main partition from the backup partition in the FLASH memory, and running the starting content in the main partition.
According to the MPU safe starting method provided by the embodiment of the invention, after the damage of the main partition in the FLASH memory is detected, the starting content is copied into the main partition from the backup partition and operated, so that the probability of starting failure of the MPU is reduced, the starting success rate is improved, and the operation stability of the MPU is ensured.
EXAMPLE III
Fig. 3 is a flowchart of a secure MPU startup method according to a third embodiment of the present invention, which is further optimized after "run the startup content in the main partition" in step S102 and step S103 based on the first embodiment. Explanations of the same or corresponding terms as those of the above embodiments are omitted. Namely:
detecting whether the main partition in operation is abnormal or not;
and if so, switching from the main partition to the backup partition, and running the starting content in the backup partition.
Based on the above optimization, as shown in fig. 3, the MPU secure boot method provided in this embodiment may include the following steps:
s301, responding to the starting operation, and detecting whether a main partition in the FLASH memory is damaged; if not, step S302 is executed, and if yes, step S303 is executed.
And S302, operating the starting content in the main partition.
S303, copying the starting content stored in the backup partition to the main partition from the backup partition in the FLASH memory, and running the starting content in the main partition.
S304, detecting whether the main partition in operation is abnormal or not; if so, step S305 is executed, otherwise, step S304 is continued.
It should be noted that, in this embodiment, in addition to detecting the startup state of the main partition during startup, the real-time running state of the main partition is also monitored during running, and it is intended that when the main partition is abnormal, measures can be timely found and taken to ensure the running stability of the MPU.
S305, switching from the main partition to the backup partition, and running the starting content in the backup partition.
It should be noted that, when detecting that the running main partition is abnormal, the present embodiment may switch from the main partition to the backup partition, and then run the start content in the backup partition. Since the startup content stored in the primary partition is consistent with the startup content stored in the backup partition, the MPU can normally operate after the switch. At this point the backup partition will act as a temporary boot partition, typically set to restore on the next boot. Of course, depending on the repair condition of the primary partition, if the primary partition is not repaired, the backup partition will be used as a temporary boot partition in the next boot.
In this embodiment, preferably, after the step S305, the method may further include the steps of:
formatting the primary partition;
copying boot contents stored in the backup partition from the backup partition in the FLASH memory into the primary partition;
switching from the backup partition to the primary partition and running boot content in the primary partition.
It should be noted that, in this embodiment, after it is confirmed that the main partition is successfully repaired, the main partition needs to be switched back to operate. The time of switching may be switching immediately after the main partition is repaired, or switching may be switching at the next time of starting, which is not limited in this embodiment.
According to the MPU safe starting method provided by the embodiment of the invention, after the damage of the main partition in the FLASH memory is detected, the starting content is copied into the main partition from the backup partition and operated, so that the probability of starting failure of the MPU is reduced, the starting success rate is improved, and the operation stability of the MPU is ensured.
Example four
Referring to fig. 4, fig. 4 is a functional block diagram of an MPU secure boot system according to a fourth embodiment of the present invention, which is suitable for executing the MPU secure boot method according to the fourth embodiment of the present invention. The system specifically comprises the following modules:
a damage detection module 401, configured to detect whether a main partition in the FLASH memory is damaged in response to the start operation;
a first starting module 402, configured to run starting content in the main partition if the main partition is damaged;
a second starting module 403, configured to copy, from the backup partition in the FLASH memory, the starting content stored in the backup partition to the main partition, and execute the starting content in the main partition, if the main partition is not damaged.
Preferably, the second starting module 403 is specifically configured to:
formatting the primary partition;
copying boot contents stored in the backup partition from the backup partition in the FLASH memory into the primary partition;
executing the boot content in the main partition.
Preferably, the system further comprises a partition establishing module, configured to:
before the step of responding to the starting operation and detecting whether the main partition in the FLASH memory is damaged, the main partition and the backup partition are arranged in the FLASH memory in advance;
boot contents for booting the MPU are stored in the main partition and the backup partition, respectively.
Preferably, the system further comprises an anomaly detection module for:
after the step of running the boot contents in the main partition, detecting whether the running main partition is abnormal;
and if so, switching from the main partition to the backup partition, and running the starting content in the backup partition.
Preferably, the system further comprises a recovery switching module, configured to:
formatting the primary partition after the step of switching from the primary partition to the backup partition and running boot contents in the backup partition;
copying boot contents stored in the backup partition from the backup partition in the FLASH memory into the primary partition;
switching from the backup partition to the primary partition and running boot content in the primary partition.
According to the MPU safe starting system provided by the embodiment of the invention, after the damage of the main partition in the FLASH memory is detected, the starting content is copied into the main partition from the backup partition and operated, so that the probability of starting failure of the MPU is reduced, the starting success rate is improved, and the operation stability of the MPU is ensured.
The system can execute the method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.
The foregoing description of the embodiments has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the disclosure. Individual elements or features of a particular embodiment are generally not limited to that particular embodiment, but, where applicable, are interchangeable and can be used in a selected embodiment, even if not specifically shown or described. The same elements or features may also vary in many respects. Such variations are not to be regarded as a departure from the disclosure, and all such modifications are intended to be included within the scope of the disclosure.
Example embodiments are provided so that this disclosure will be thorough and will fully convey the scope to those skilled in the art. Numerous details are set forth, such as examples of specific parts, devices, and methods, in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent to those skilled in the art that specific details need not be employed, that example embodiments may be embodied in many different forms and that neither should be construed to limit the scope of the disclosure. In certain example embodiments, well-known processes, well-known device structures, and well-known technologies are not described in detail.
The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The terms "comprises" and "comprising" are intended to be inclusive and therefore specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. The method steps, processes, and operations described herein are not to be construed as necessarily requiring their performance in the particular order discussed and illustrated, unless explicitly indicated as an order of performance. It should also be understood that additional or alternative steps may be employed.
When an element or layer is referred to as being "on" … … "," engaged with "… …", "connected to" or "coupled to" another element or layer, it can be directly on, engaged with, connected to or coupled to the other element or layer, or intervening elements or layers may also be present. In contrast, when an element or layer is referred to as being "directly on … …," "directly engaged with … …," "directly connected to" or "directly coupled to" another element or layer, there may be no intervening elements or layers present. Other words used to describe the relationship of elements should be interpreted in a similar manner (e.g., "between … …" and "directly between … …", "adjacent" and "directly adjacent", etc.). As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items. Although the terms first, second, third, etc. may be used herein to describe various elements, components, regions, layers and/or sections, these elements, components, regions, layers and/or sections should not be limited by these terms. These terms may be only used to distinguish one element, component, region or section from another element, component, region or section. Unless clearly indicated by the context, use of terms such as the terms "first," "second," and other numerical values herein does not imply a sequence or order. Thus, a first element, component, region, layer or section discussed below could be termed a second element, component, region, layer or section without departing from the teachings of the example embodiments.
Spatially relative terms, such as "inner," "outer," "below," "… …," "lower," "above," "upper," and the like, may be used herein for ease of description to describe a relationship between one element or feature and one or more other elements or features as illustrated in the figures. Spatially relative terms may be intended to encompass different orientations of the device in addition to the orientation depicted in the figures. For example, if the device in the figures is turned over, elements described as "below" or "beneath" other elements or features would then be oriented "above" the other elements or features. Thus, the example term "below … …" can encompass both an orientation of facing upward and downward. The device may be otherwise oriented (rotated 90 degrees or at other orientations) and the spatially relative descriptors used herein interpreted.

Claims (10)

1. An MPU secure boot method, the method comprising:
detecting whether a main partition in the FLASH memory is damaged or not in response to a starting operation;
if not, running the starting content in the main partition;
if yes, copying the starting content stored in the backup partition to the main partition from the backup partition in the FLASH memory, and running the starting content in the main partition.
2. An MPU secure boot method according to claim 1, wherein said step of copying boot contents stored in said backup partition from said backup partition in said FLASH memory into said main partition, and running boot contents in said main partition comprises:
formatting the primary partition;
copying boot contents stored in the backup partition from the backup partition in the FLASH memory into the primary partition;
executing the boot content in the main partition.
3. An MPU secure boot method according to claim 1, characterized in that before said step of detecting whether a main partition in a FLASH memory is damaged in response to a boot operation, said method further comprises:
setting a main partition and a backup partition in the FLASH memory in advance;
boot contents for booting the MPU are stored in the main partition and the backup partition, respectively.
4. An MPU secure boot method according to claim 1, characterized in that after said step of executing boot contents in said main partition, said method further comprises:
detecting whether the main partition in operation is abnormal or not;
and if so, switching from the main partition to the backup partition, and running the starting content in the backup partition.
5. An MPU secure boot method according to claim 4, wherein after the step of switching from the main partition to the backup partition and running boot contents in the backup partition, the method further comprises:
formatting the primary partition;
copying boot contents stored in the backup partition from the backup partition in the FLASH memory into the primary partition;
switching from the backup partition to the primary partition and running boot content in the primary partition.
6. An MPU secure boot system, the system comprising:
a damage detection module for detecting whether a main partition in the FLASH memory is damaged in response to a start operation;
the first starting module is used for running the starting content in the main partition if the main partition is damaged;
and the second starting module is used for copying the starting content stored in the backup partition from the backup partition in the FLASH memory to the main partition and running the starting content in the main partition if the main partition is not damaged.
7. An MPU secure boot system according to claim 6, wherein said second boot module is specifically configured to:
formatting the primary partition;
copying boot contents stored in the backup partition from the backup partition in the FLASH memory into the primary partition;
executing the boot content in the main partition.
8. An MPU secure boot system as defined in claim 6, wherein the system further comprises a partition establishment module to:
before the step of responding to the starting operation and detecting whether the main partition in the FLASH memory is damaged, the main partition and the backup partition are arranged in the FLASH memory in advance;
boot contents for booting the MPU are stored in the main partition and the backup partition, respectively.
9. An MPU secure boot system according to claim 6, further comprising an anomaly detection module for:
after the step of running the boot contents in the main partition, detecting whether the running main partition is abnormal;
and if so, switching from the main partition to the backup partition, and running the starting content in the backup partition.
10. An MPU secure boot system according to claim 9, further comprising a resume switch module for:
formatting the primary partition after the step of switching from the primary partition to the backup partition and running boot contents in the backup partition;
copying boot contents stored in the backup partition from the backup partition in the FLASH memory into the primary partition;
switching from the backup partition to the primary partition and running boot content in the primary partition.
CN202111093105.2A 2021-09-17 2021-09-17 MPU (micro processing Unit) safe starting method and MPU safe starting system Pending CN113805967A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111093105.2A CN113805967A (en) 2021-09-17 2021-09-17 MPU (micro processing Unit) safe starting method and MPU safe starting system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111093105.2A CN113805967A (en) 2021-09-17 2021-09-17 MPU (micro processing Unit) safe starting method and MPU safe starting system

Publications (1)

Publication Number Publication Date
CN113805967A true CN113805967A (en) 2021-12-17

Family

ID=78895776

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111093105.2A Pending CN113805967A (en) 2021-09-17 2021-09-17 MPU (micro processing Unit) safe starting method and MPU safe starting system

Country Status (1)

Country Link
CN (1) CN113805967A (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040044886A1 (en) * 2000-07-12 2004-03-04 Ng Weiloon Partition recovery method
CN102799499A (en) * 2012-06-15 2012-11-28 深圳乐投卡尔科技有限公司 Vehicular Android equipment system recovery method and vehicular Android equipment
CN106776122A (en) * 2016-11-23 2017-05-31 武汉光迅科技股份有限公司 A kind of method of main-apparatus protection in start-up course based on Flash
CN108874582A (en) * 2017-05-15 2018-11-23 上海宽翼通信科技有限公司 A kind of system recovery method, device and terminal
CN113296850A (en) * 2021-07-26 2021-08-24 湖南博匠信息科技有限公司 Backup starting method for embedded board card operating system and embedded system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040044886A1 (en) * 2000-07-12 2004-03-04 Ng Weiloon Partition recovery method
CN102799499A (en) * 2012-06-15 2012-11-28 深圳乐投卡尔科技有限公司 Vehicular Android equipment system recovery method and vehicular Android equipment
CN106776122A (en) * 2016-11-23 2017-05-31 武汉光迅科技股份有限公司 A kind of method of main-apparatus protection in start-up course based on Flash
CN108874582A (en) * 2017-05-15 2018-11-23 上海宽翼通信科技有限公司 A kind of system recovery method, device and terminal
CN113296850A (en) * 2021-07-26 2021-08-24 湖南博匠信息科技有限公司 Backup starting method for embedded board card operating system and embedded system

Similar Documents

Publication Publication Date Title
US8762782B2 (en) Basic input-output system circuit and method for using the same
CN106775610B (en) Electronic equipment starting method and electronic equipment
JP2009067298A (en) Vehicular memory management apparatus
CN103176875A (en) Embedded system power on self test method
CN102455954A (en) Power-failure-preventing upgrading method of Linux system
CN108920301B (en) Data backup method and system, and data recovery method and system
CN111552592A (en) Double-backup starting method and system
CN103092724A (en) System self-recovery method for embedded electric power terminal
CN108737153B (en) Block chain disaster recovery system, method, server and computer-readable storage medium
CN104572352B (en) A kind of POS terminal critical data back-up restoring method
CN106095474A (en) For the method and apparatus updating the software in means of transport
JP2011198205A (en) Redundant system control system
CN110871897B (en) Unmanned aerial vehicle self-checking method and system
CN110147090A (en) Controller Area Network BUS closing fault processing method and system
CN113805967A (en) MPU (micro processing Unit) safe starting method and MPU safe starting system
CN113742165A (en) Double-master control equipment and master-slave control method
CN110766890A (en) Anti-shell-dismantling method and system for T-BOX controller, controller and vehicle
CN113127883B (en) Locking method, device, equipment and medium for platform firmware protection recovery
JP2003345620A (en) Process monitoring method for multi-node cluster system
US6721882B1 (en) Method and apparatus for warm starting a system where the system includes region(s) of software code incapable of warm starting
CN110427280B (en) Cache management method, system, computer equipment and storage medium
JP3022768B2 (en) Virtual computer system
KR102410515B1 (en) Control apparatus and control method of the same
CN111061255A (en) Control method and device of electric vehicle
JP2006323494A (en) Failure recovery method and microcomputer

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