CN109783150A - A kind of anti-brick method and device of embedded system starting - Google Patents
A kind of anti-brick method and device of embedded system starting Download PDFInfo
- Publication number
- CN109783150A CN109783150A CN201910100336.8A CN201910100336A CN109783150A CN 109783150 A CN109783150 A CN 109783150A CN 201910100336 A CN201910100336 A CN 201910100336A CN 109783150 A CN109783150 A CN 109783150A
- Authority
- CN
- China
- Prior art keywords
- embedded system
- partition
- boot
- embedded
- brick
- 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
- 239000011449 brick Substances 0.000 title claims abstract description 54
- 238000000034 method Methods 0.000 title claims abstract description 54
- 238000005192 partition Methods 0.000 claims abstract description 164
- 238000012544 monitoring process Methods 0.000 claims abstract description 64
- 230000008439 repair process Effects 0.000 claims abstract description 49
- 230000008569 process Effects 0.000 claims description 18
- 230000002265 prevention Effects 0.000 claims description 15
- 238000012545 processing Methods 0.000 claims description 6
- 230000008859 change Effects 0.000 abstract description 3
- 230000006870 function Effects 0.000 description 6
- 238000012986 modification Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 5
- 230000000903 blocking effect Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Landscapes
- Stored Programmes (AREA)
Abstract
The invention discloses a kind of embedded systems to start anti-brick method and device, is applied to embedded system technology field, existing in the prior art since appearance change brick phenomenon leads to starting failure on startup for embedded system to solve the problems, such as.Specifically: in embedded system start-up course, system boot partition is monitored, when determining embedded system starting failure according to monitoring result, embedded system and under minimum system mode is resetted, multiple embedded system is guaranteed the repair free of charge according to system repair data and starts the embedded system after repairing.In this way, by being monitored in embedded system start-up course to system boot partition, embedded system starting failure can be known in time, in turn, it being capable of repairing built-in system in time after resetting embedded system and entering minimum system mode, to realize being automatically repaired for embedded system, solve the problems, such as that occurring change brick phenomenon during startup due to embedded system leads to starting failure.
Description
Technical Field
The invention relates to the technical field of embedded systems, in particular to a method and a device for preventing bricks during starting of an embedded system.
Background
The embedded system may have a brick-changing phenomenon during the starting process. The phenomenon of brick change refers to the phenomenon that when the firmware of various hardware drivers included in the embedded system has problems, the embedded system starts up without reaction.
In practical application, the stable starting of the system is very important for the embedded system, and if the brick-changing phenomenon occurs in the starting process of the embedded system, the starting of the embedded system is likely to fail, so that the stability of the embedded system is reduced.
Disclosure of Invention
The embodiment of the invention provides a method and a device for starting an embedded system to prevent bricks, and particularly provides the following technical scheme:
in a first aspect, an embodiment of the present invention provides a method for preventing a brick from being started by an embedded system, including:
monitoring a system starting partition configured as a monitoring node in the embedded system in the starting process of the embedded system;
when the embedded system is determined to be failed to start according to the monitoring result of the monitoring node, resetting the embedded system and entering a minimum system mode;
acquiring a system repair data packet of the embedded system, wherein the system repair data packet at least comprises configuration data of the embedded system;
and under the minimum system mode, repairing the embedded system according to the system repair data packet, and starting the repaired embedded system when the embedded system is repaired.
In a second aspect, an embodiment of the present invention provides an embedded system start-up brick-proof device, including:
the monitoring unit is used for monitoring a system starting partition which is configured as a monitoring node in the embedded system in the starting process of the embedded system;
the reset unit is used for resetting the embedded system and entering a minimum system mode when the monitoring unit determines that the embedded system fails to start according to the monitoring result of the monitoring node;
the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring a system repair data packet of the embedded system, and the system repair data packet at least comprises configuration data of the embedded system;
and the repairing unit is used for repairing the embedded system according to the system repairing data packet obtained by the obtaining unit in the minimum system mode and starting the repaired embedded system when the embedded system is repaired.
In a third aspect, an embodiment of the present invention further provides an embedded system startup brick-proof device, including: a memory and a processor, wherein the memory is configured to store computer instructions; and the processor is used for executing the computer instructions to realize the embedded system starting anti-brick method provided by the embodiment of the invention.
In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, where computer instructions are stored, and when executed by a processor, the computer instructions implement the embedded system boot anti-brick method provided in the embodiment of the present invention.
The embodiment of the invention has the following beneficial effects:
in the embodiment of the invention, the system starting subarea configured as the monitoring node is monitored in the starting process of the embedded system, so that the starting failure of the embedded system can be timely known, and further, after the embedded system is reset and enters the minimum system mode, the embedded system can be timely repaired according to the system repair data packet of the embedded system, thereby realizing the automatic repair of the embedded system and effectively solving the problem of the starting failure of the embedded system caused by the brick-changing phenomenon of the embedded system in the starting process.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the invention and not to limit the invention. In the drawings:
FIG. 1 is a diagram illustrating a boot process of an embedded system according to an embodiment of the present invention;
FIG. 2 is a schematic flow chart of a method for starting a brick prevention by an embedded system according to an embodiment of the present invention;
FIG. 3 is a functional structure diagram of an embedded system startup anti-brick device in the embodiment of the present invention;
fig. 4 is a schematic diagram of a hardware structure of the embedded system start-up brick-prevention device in the embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments 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.
At present, the start-up process of the embedded system is mainly divided into four stages, and referring to fig. 1, the start-up process of the embedded system includes: the method comprises four stages of a boot starting stage, a file system starting stage, an initialization stage and a startup starting stage. The boot startup phase is boot startup through a boot (boot) loading partition, the file system startup phase is file system startup through a file system (rootfs) loading partition, the initialization phase is initialization startup through a system (system) loading partition, and the boot startup phase is boot startup executed through a data (data) loading partition. In the starting process of the embedded system, if any one of the boot partition, the rootfs partition, the system partition and the data partition is damaged, the brick changing phenomenon of the embedded system can be caused, and the starting failure of the embedded system is caused.
To this end, an embodiment of the present invention provides a method for starting and blocking an embedded system, such as an embedded Linux system based on an ARM (Advanced risc machines) architecture, the method being executable by a start blocking apparatus in the embedded system, specifically, the start blocking apparatus may monitor a system start partition configured as a monitoring node in the embedded system during the start of the embedded system, reset the embedded system and enter a minimum system mode when it is determined that the start of the embedded system fails according to a monitoring result of the monitoring node, repair the embedded system according to a system repair packet of the embedded system in the minimum system mode, and start the repaired embedded system when the repair of the embedded system is completed, so that, during the start of the embedded system, the system startup subareas configured as the monitoring nodes are monitored, the startup failure of the embedded system can be timely known, and then, after the embedded system is reset and enters a minimum system mode, the embedded system can be timely repaired according to the system repair data packet of the embedded system, so that the automatic repair of the embedded system is realized, and the problem of startup failure of the embedded system caused by the brick-changing phenomenon of the embedded system in the startup process is effectively solved.
The following describes in detail an embedded system start-up anti-blocking method provided by the embodiment of the present invention with reference to the accompanying drawings, but of course, the present invention is not limited to the following embodiments.
In the method for starting and preventing the brick of the embedded system provided by the embodiment of the invention, the brick starting prevention device can be used for configuring the monitoring node in the embedded system in advance, namely configuring the system starting partition loaded in the starting process of the embedded system as the monitoring node. Specifically, the system booting partition configured to monitor the node may include: boot partitions, rootfs partitions, and system partitions.
Further, in one embodiment, the system booting partition configured to monitor the nodes may further include: a boot backup (boot) partition for boot partitions, a file system backup (rootfsb) partition for rootfs partitions, and a system backup (system) partition for system partitions. In another embodiment, the system boot partition configured to monitor the nodes may also include a data partition.
Referring to fig. 2, a flow of the method for starting the anti-brick function of the embedded system according to the embodiment of the present invention is as follows:
step 201: and monitoring a system starting partition configured as a monitoring node in the embedded system in the starting process of the embedded system.
In practical applications, the start-up anti-blocking device may employ a watchdog (watchdog) mechanism to monitor a system start-up partition configured as a monitoring node within the embedded system.
Step 202: and when the embedded system is determined to fail to start according to the monitoring result of the monitoring node, resetting the embedded system and entering a minimum system mode.
In one embodiment, if the system boot partition configured as the monitor node includes a boot partition, a rootfs partition, and a system partition, the boot-up prevention device may consider the embedded system boot-up to fail when determining that either of the following occurs:
in the first case: the boot execution fails according to the loaded boot partition.
In the second case: and after the boot is successfully started, executing the file system starting failure according to the loaded rootfs partition.
In the third case: and after the boot startup and the file system startup are both successful, executing initialization startup failure according to the loaded system partition.
In another embodiment, if the system boot partitions configured as monitor nodes include a boot partition, a rootfs partition, a rootfsb partition, a system partition, and a system partition, the boot-up debottle device may consider the embedded system boot-up to fail when determining that either of the following occurs:
in the first case: and after the boot starting is failed to be executed according to the loaded boot partition, the boot starting is failed to be executed again according to the loaded boot partition.
In the second case: and after the boot is successfully started and the file system is failed to be started according to the loaded rootfs partition, the file system is failed to be started again according to the loaded rootfsb partition.
In the third case: after the file system successfully starts and the initialization start-up is failed to be executed according to the loaded system partition, the initialization start-up is failed to be executed again according to the loaded system partition.
Furthermore, after the start-up of the anti-brick device is determined to fail, the watchdog mechanism can be triggered to perform timeout reset on the embedded system, and the minimum system is operated, so that the embedded system enters the minimum system mode.
In addition, after the start-up anti-brick device determines that the start-up of the embedded system fails, the identification information corresponding to the system start-up partition loaded when the start-up of the embedded system fails can be written into the designated field, so that when the embedded system is repaired in the following process, the damaged system start-up partition in the embedded system can be determined according to the identification information recorded in the designated field.
Specifically, in one embodiment, if the system boot partition configured as the monitor node includes a boot partition, a rootfs partition, and a system partition, the start-up brick prevention device may set the specified field to the identification information 1-1 corresponding to the boot partition when boot start fails, set the specified field to the identification information 2-1 corresponding to the rootfs partition when boot start succeeds and file system start fails, and set the specified field to the identification information 3-1 corresponding to the system partition when file system start succeeds and initialization start fails.
In another embodiment, if the system boot partition configured as the monitor node includes a boot partition, a bootb partition, a rootfs partition, a rootfsb partition, a system partition, and a system partition, the boot brickwork device may set the designated field to identification information 1-2 corresponding to the bootb partition when a boot failure is performed again according to the loaded bootb partition, set the designated field to identification information 2-2 corresponding to the rootfsb partition when a file system boot failure is performed again according to the loaded rootfsb partition, and set the designated field to identification information 3-2 corresponding to the system partition when an initialization boot failure is performed again according to the loaded system partition.
Step 203: and acquiring a system repair data packet of the embedded system, wherein the system repair data packet at least comprises configuration data of the embedded system.
In specific implementation, the start-up brick-prevention device may obtain the system repair data packet from the local designated storage area, may also initiate system repair prompt information, and obtain the system repair data packet from the usb disk when detecting that the usb disk is inserted, and a specific implementation manner is not specifically limited herein.
Step 204: and under the minimum system mode, repairing the embedded system according to the system repair data packet, and starting the repaired embedded system when the embedded system is repaired.
During specific implementation, the starting brick-proof device can determine the damaged partition of the embedded system according to the identification information recorded in the designated field, and repair the damaged partition according to the system repair data packet, so that the embedded system can be automatically repaired, and further, the repaired embedded system can be started when the embedded system is repaired, so that the problem that the embedded system fails to be started due to the brick-changing phenomenon in the starting process of the embedded system is avoided as much as possible.
It is worth mentioning that in the method for preventing the embedded system from being started and started according to the embodiment of the present invention, if the system start partition configured as the monitoring node further includes the data partition, the data partition may be formatted and the embedded system may be restarted when the startup executed according to the loaded data partition fails after the boot start, the file system start and the initialization start are all successful, so as to complete the automatic restart of the embedded system.
Based on the above embodiments, an embodiment of the present invention provides an embedded system start-up brick-proof device, and referring to fig. 3, an embedded system start-up brick-proof device 300 provided by an embodiment of the present invention at least includes:
the monitoring unit 301 is configured to monitor a system boot partition configured as a monitoring node in the embedded system during a boot process of the embedded system;
the resetting unit 302 is used for resetting the embedded system and entering a minimum system mode when the monitoring unit 301 determines that the embedded system fails to start according to the monitoring result of the monitoring node;
an obtaining unit 303, configured to obtain a system repair data packet of the embedded system, where the system repair data packet is a data packet that at least includes configuration data of the embedded system;
a repairing unit 304, configured to repair the embedded system according to the system repair data packet obtained by the obtaining unit 303 in the minimum system mode, and start the repaired embedded system when the embedded system is repaired.
In one possible implementation, a system boot partition configured to monitor nodes includes at least a boot partition, a file system partition, and a system partition.
In a possible implementation manner, when determining that the embedded system fails to start according to the monitoring result of the monitoring node, the monitoring unit 301 is specifically configured to:
if the boot execution according to the loaded boot partition fails, the embedded system is considered to fail to be started; or after the boot is successfully started, if the execution of the file system according to the loaded file system partition fails to start, the embedded system is considered to fail to start; or after the boot startup and the file system startup are both successful, if the initialization startup executed according to the loaded system partition fails, the embedded system is considered to be failed to start.
In one possible implementation, the system partition configured to monitor nodes further includes a boot backup partition of the boot partition, a file system backup partition of the file system partition, and a system backup partition of the system partition.
In a possible implementation manner, when determining that the embedded system fails to start according to the monitoring result of the monitoring node, the monitoring unit 301 is specifically configured to:
after the boot startup is executed according to the loaded boot partition, if the boot startup is executed again according to the loaded boot backup partition, the embedded system is considered to be failed to start; or after the boot is successfully started and the file system is unsuccessfully started according to the loaded file system partition, if the file system is unsuccessfully started again according to the loaded file system backup partition, the embedded system is considered to be unsuccessfully started; or, after the file system is successfully started and the initialization start is failed to be executed according to the loaded system partition, if the initialization start is failed to be executed again according to the loaded system backup partition, the embedded system is considered to be failed to be started.
In a possible implementation manner, the embedded system start-up brick-prevention device 300 provided by the embodiment of the present invention further includes:
an identification unit 305, configured to determine, when the monitoring unit 301 determines that the embedded system fails to start according to the monitoring result of the monitoring node, a system start partition loaded when the embedded system fails to start, and write identification information corresponding to the system start partition loaded when the embedded system fails to start into the specified field.
In a possible implementation manner, when acquiring a system repair packet of an embedded system, the acquiring unit 303 is specifically configured to:
acquiring a system repair data packet from a local specified storage area; or displaying system repair prompt information, and acquiring a system repair data packet from the USB flash disk when detecting that the USB flash disk is inserted.
In a possible implementation manner, when the embedded system is repaired according to the system repair packet obtained by the obtaining unit 303, the repairing unit 304 is specifically configured to:
and determining the damaged partition of the embedded system according to the identification information recorded in the designated field, and repairing the damaged partition according to the system repair data packet.
In one possible embodiment, the system boot partition configured to monitor the nodes further comprises a data partition.
In a possible implementation manner, the embedded system start-up brick-prevention device 300 provided by the embodiment of the present invention further includes:
and a formatting unit 306, configured to format and restart the data partition if the boot start is failed to be executed according to the loaded data partition after the boot start, the file system start, and the initialization start are all successful.
It should be noted that each unit in the embedded system start-up brick-prevention device 300 provided in the embodiment of the present invention corresponds to the above start-up brick-prevention system in the embodiment of the present invention, and the start-up brick-prevention function of the embedded system can be realized by installing the above start-up brick-prevention system in the embedded system start-up brick-prevention device 300.
It should be noted that each unit in the embedded system start-up anti-brick device 300 provided in the embodiment of the present invention corresponds to the above start-up anti-brick device in the embodiment of the present invention, so that a memory management function of the embedded system can be realized.
After the embedded system start-up brick-proof method and the embedded system start-up brick-proof device according to the exemplary embodiment of the present invention are introduced, a brief description will be given to the embedded system start-up brick-proof device according to the embodiment of the present invention.
Referring to fig. 4, an embedded system start-up brick-proof device 400 according to an embodiment of the present invention at least includes: a processor 41 and a memory 42, wherein the memory 42 is configured to store computer instructions; and the processor 41 is used for executing computer instructions to implement the embedded system start-up anti-brick method provided by the embodiment of the invention.
It should be noted that the embedded system startup brick-proof device 400 shown in fig. 4 is only an example, and should not bring any limitation to the functions and the scope of the embodiments of the present invention.
The embedded system boot brick-prevention apparatus 400 provided by the embodiment of the present invention may further include a bus 43 connecting different components (including the processor 41 and the memory 42). Bus 43 represents one or more of any of several types of bus structures, including a memory bus, a peripheral bus, a local bus, and so forth.
The Memory 42 may include readable media in the form of volatile Memory, such as Random Access Memory (RAM) 421 and/or cache Memory 422, and may further include Read Only Memory (ROM) 423.
The memory 42 may also include a program tool 424 having a set (at least one) of program modules 424, the program modules 424 including, but not limited to: an operating subsystem, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.
The embedded system start-up anti-brick device 400 may also communicate with one or more external devices 44 (e.g., a keyboard, a remote control, etc.), with one or more devices (e.g., a cell phone, a computer, etc.) that enable a user to interact with the embedded system start-up anti-brick device 400, and/or with any device (e.g., a router, a modem, etc.) that enables the embedded system start-up anti-brick device 400 to communicate with one or more other embedded system start-up anti-brick devices 400. This communication may be via an Input/Output (I/O) interface 45. Also, the embedded system boot-up prevention device 400 may also communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public Network, such as the internet) via the Network adapter 46. As shown in fig. 4, the network adapter 46 communicates with the other modules of the embedded system boot anti-brick device 400 over the bus 43. It should be understood that although not shown in FIG. 4, other hardware and/or software modules may be used in conjunction with the embedded system boot brick prevention device 400, including but not limited to: microcode, device drivers, Redundant processors, external disk drive arrays, disk array (RAID) subsystems, tape drives, and data backup storage subsystems, to name a few.
The following describes a computer-readable storage medium provided by an embodiment of the present invention. The embodiment of the invention provides a computer-readable storage medium, which stores computer instructions, and when the computer instructions are executed by a processor, the computer instructions implement the embedded system starting anti-brick method provided by the embodiment of the invention. Specifically, the executable program may be embedded in the embedded system start-up anti-brick device 400, so that the embedded system start-up anti-brick device 400 may implement the embedded system start-up anti-brick method provided by the embodiment of the present invention by executing the embedded executable program.
In addition, the embedded system start-up anti-brick method provided by the embodiment of the present invention can also be implemented as a program product, where the program product includes program code, and when the program product can run on the embedded system start-up anti-brick device 400, the program code is configured to enable the embedded system start-up anti-brick device 400 to execute the embedded system start-up anti-brick method provided by the embodiment of the present invention.
The program product provided by the embodiment of the present invention may adopt any combination of one or more readable media, wherein the readable media may be readable signal media or readable storage media, and the readable storage media may be but not limited to systems, apparatuses or devices of electric, magnetic, optical, electromagnetic, infrared or semiconductor, or any combination thereof, and specifically, more specific examples (non-exhaustive list) of the readable storage media include: an electrical connection having one or more wires, a portable disk, a hard disk, a RAM, a ROM, an Erasable Programmable Read-Only Memory (EPROM), an optical fiber, a portable Compact disk Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The program product provided by the embodiment of the invention can adopt a CD-ROM and comprises program codes, and can run on a computing device. However, the program product provided by the embodiments of the present invention is not limited thereto, and in the embodiments of the present invention, the readable storage medium may be any tangible medium that can contain or store the program, which can be used by or in connection with an instruction execution system, apparatus, or device.
It should be noted that although several units or sub-units of the apparatus are mentioned in the above detailed description, such division is merely exemplary and not mandatory. Indeed, the features and functions of two or more of the units described above may be embodied in one unit, according to embodiments of the invention. Conversely, the features and functions of one unit described above may be further divided into embodiments by a plurality of units.
Moreover, while the operations of the method of the invention are depicted in the drawings in a particular order, this does not require or imply that the operations must be performed in this particular order, or that all of the illustrated operations must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various modifications and variations can be made in the embodiments of the present invention without departing from the spirit or scope of the embodiments of the invention. Thus, if such modifications and variations of the embodiments of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to encompass such modifications and variations.
Claims (22)
1. A method for preventing bricks in the starting of an embedded system is characterized by comprising the following steps:
monitoring a system starting partition configured as a monitoring node in an embedded system in the starting process of the embedded system;
when the embedded system is determined to be failed to start according to the monitoring result of the monitoring node, resetting the embedded system and entering a minimum system mode;
acquiring a system repair data packet of the embedded system, wherein the system repair data packet at least comprises configuration data of the embedded system;
and under the minimum system mode, repairing the embedded system according to the system repair data packet, and starting the repaired embedded system when the embedded system is repaired.
2. The embedded system boot anti-brick method of claim 1 wherein the system boot partition configured to monitor nodes comprises at least a boot partition, a file system partition, and a system partition.
3. The embedded system startup anti-brick method according to claim 2, wherein determining that the embedded system has failed to start up based on the monitoring result of the monitoring node comprises:
if the execution of the boot start according to the loaded boot partition fails, the embedded system is considered to fail to start; or,
after the booting is successfully started, if the file system is unsuccessfully started according to the loaded file system partition, the embedded system is considered to be unsuccessfully started; or,
and after the boot startup and the file system startup are both successful, if the initialization startup executed according to the loaded system partition fails, the embedded system is considered to be failed to start.
4. The embedded system boot brickmaking method of claim 2, wherein the system partition configured to monitor nodes further comprises a boot backup partition of the boot partition, a file system backup partition of the file system partition, and a system backup partition of the system partition.
5. The embedded system startup anti-brick method according to claim 4, wherein determining that the embedded system has failed to start up based on the monitoring result of the monitoring node comprises:
after the boot startup is executed according to the loaded boot partition, if the boot startup is executed again according to the loaded boot backup partition, the embedded system is considered to be failed to start; or,
after the booting is successfully started and the file system is unsuccessfully started according to the loaded file system partition, if the file system is unsuccessfully started according to the loaded file system backup partition, the embedded system is considered to be unsuccessfully started; or,
and after the file system is successfully started and the initialization start is failed to be executed according to the loaded system partition, if the initialization start is failed to be executed again according to the loaded system backup partition, the embedded system is considered to be failed to be started.
6. The embedded system startup anti-brick method according to any one of claims 1-5, further comprising, when it is determined that the embedded system has failed to start up based on the monitoring result for the monitoring node:
determining a system starting partition loaded when the embedded system fails to start;
and writing the identification information corresponding to the system starting partition loaded when the embedded system fails to start into the specified field.
7. The embedded system boot anti-brick method of claim 6 wherein obtaining a system repair data packet for the embedded system comprises:
acquiring the system repair data packet from a local specified storage area; or,
and displaying system repair prompt information, and acquiring the system repair data packet from the USB flash disk when detecting that the USB flash disk is inserted.
8. The embedded system boot brick prevention method of claim 7 wherein repairing the embedded system according to the system repair data packet comprises:
and determining the damaged partition of the embedded system according to the identification information recorded in the designated field, and repairing the damaged partition according to the system repair data packet.
9. The embedded system boot-block prevention method of any one of claims 1-5, wherein the system boot partition configured to monitor nodes further comprises a data partition.
10. The embedded system boot brick prevention method of claim 9, further comprising:
after the boot startup, the file system startup and the initialization startup are successful, if the startup execution fails according to the loaded data partition, formatting the data partition and restarting.
11. An embedded system starts and prevents brick device which characterized in that includes:
the system comprises a monitoring unit, a processing unit and a processing unit, wherein the monitoring unit is used for monitoring a system starting partition which is configured as a monitoring node in an embedded system in the starting process of the embedded system;
the reset unit is used for resetting the embedded system and entering a minimum system mode when the monitoring unit determines that the embedded system fails to start according to the monitoring result of the monitoring node;
the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring a system repair data packet of the embedded system, and the system repair data packet at least comprises configuration data of the embedded system;
and the repairing unit is used for repairing the embedded system according to the system repairing data packet obtained by the obtaining unit in the minimum system mode and starting the repaired embedded system when the embedded system is repaired.
12. The embedded system boot brick prevention apparatus of claim 11 wherein the system boot partition configured to monitor nodes comprises at least a boot partition, a file system partition, and a system partition.
13. The embedded system start-up brick-prevention device according to claim 12, wherein when it is determined that the embedded system fails to start up according to the monitoring result of the monitoring node, the monitoring unit is specifically configured to:
if the execution of the boot start according to the loaded boot partition fails, the embedded system is considered to fail to start; or,
after the booting is successfully started, if the file system is unsuccessfully started according to the loaded file system partition, the embedded system is considered to be unsuccessfully started; or,
and after the boot startup and the file system startup are both successful, if the initialization startup executed according to the loaded system partition fails, the embedded system is considered to be failed to start.
14. The embedded system boot brick prevention apparatus of claim 12 wherein the system partition configured to monitor nodes further comprises a boot backup partition of the boot partition, a file system backup partition of the file system partition, and a system backup partition of the system partition.
15. The embedded system start-up brick prevention apparatus of claim 14, wherein when it is determined that the embedded system fails to start up according to the monitoring result of the monitoring node, the monitoring unit is specifically configured to:
after the boot startup is executed according to the loaded boot partition, if the boot startup is executed again according to the loaded boot backup partition, the embedded system is considered to be failed to start; or,
after the booting is successfully started and the file system is unsuccessfully started according to the loaded file system partition, if the file system is unsuccessfully started according to the loaded file system backup partition, the embedded system is considered to be unsuccessfully started; or,
and after the file system is successfully started and the initialization start is failed to be executed according to the loaded system partition, if the initialization start is failed to be executed again according to the loaded system backup partition, the embedded system is considered to be failed to be started.
16. The embedded system boot brick prevention apparatus of any one of claims 11-15, further comprising:
and the identification unit is used for determining the system starting partition loaded when the embedded system fails to start and writing the identification information corresponding to the system starting partition loaded when the embedded system fails to start into the specified field when the monitoring unit determines that the embedded system fails to start according to the monitoring result of the monitoring node.
17. The embedded system startup anti-brick device of claim 16, wherein when acquiring the system repair data packet of the embedded system, the acquiring unit is specifically configured to:
acquiring the system repair data packet from a local specified storage area; or,
and displaying system repair prompt information, and acquiring the system repair data packet from the USB flash disk when detecting that the USB flash disk is inserted.
18. The embedded system startup brick-proof device of claim 17, wherein when the embedded system is repaired according to the system repair data packet obtained by the obtaining unit, the repairing unit is specifically configured to:
and determining the damaged partition of the embedded system according to the identification information recorded in the designated field, and repairing the damaged partition according to the system repair data packet.
19. The embedded system boot brick prevention apparatus of any one of claims 11-15 wherein the system boot partition configured to monitor nodes further comprises a data partition.
20. The embedded system boot brick prevention apparatus of claim 19, further comprising:
and the formatting unit is used for formatting the data partitions and restarting the data partitions if the startup execution fails according to the loaded data partitions after the boot startup, the file system startup and the initialization startup are successful.
21. An embedded system start-up brick-proof device, comprising: a memory and a processor, wherein,
the memory to store computer instructions;
the processor for executing the computer instructions to implement the embedded system initiated anti-brick method of any of claims 1-10.
22. A computer-readable storage medium storing computer instructions which, when executed by a processor, implement the embedded system enabled anti-brick method of any of claims 1-10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910100336.8A CN109783150A (en) | 2019-01-31 | 2019-01-31 | A kind of anti-brick method and device of embedded system starting |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910100336.8A CN109783150A (en) | 2019-01-31 | 2019-01-31 | A kind of anti-brick method and device of embedded system starting |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109783150A true CN109783150A (en) | 2019-05-21 |
Family
ID=66504042
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910100336.8A Pending CN109783150A (en) | 2019-01-31 | 2019-01-31 | A kind of anti-brick method and device of embedded system starting |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109783150A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112698985A (en) * | 2020-12-21 | 2021-04-23 | 厦门锐骐物联技术股份有限公司 | System starting method and system based on multi-partition technology firmware protection |
| CN115202928A (en) * | 2022-06-09 | 2022-10-18 | 联想(北京)有限公司 | Method and device for processing boot configuration data of operating system |
| CN120510904A (en) * | 2025-07-21 | 2025-08-19 | 合肥康芯威存储技术有限公司 | Memory testing method, device, equipment and medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102214106A (en) * | 2010-04-08 | 2011-10-12 | 三星电子（中国）研发中心 | Automatic dual-system guide method of embedded device |
| CN103761124A (en) * | 2014-01-06 | 2014-04-30 | 武汉烽火富华电气有限责任公司 | Method for starting embedded-type Linux system used for protection measuring and controlling device |
| CN105138430A (en) * | 2015-08-24 | 2015-12-09 | 浪潮集团有限公司 | Embedded operating system backup and restoration method and device |
| CN108205446A (en) * | 2017-10-24 | 2018-06-26 | 中兴通讯股份有限公司 | Firmware restorative procedure and device |
| CN108874582A (en) * | 2017-05-15 | 2018-11-23 | 上海宽翼通信科技有限公司 | A kind of system recovery method, device and terminal |
-
2019
- 2019-01-31 CN CN201910100336.8A patent/CN109783150A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102214106A (en) * | 2010-04-08 | 2011-10-12 | 三星电子（中国）研发中心 | Automatic dual-system guide method of embedded device |
| CN103761124A (en) * | 2014-01-06 | 2014-04-30 | 武汉烽火富华电气有限责任公司 | Method for starting embedded-type Linux system used for protection measuring and controlling device |
| CN105138430A (en) * | 2015-08-24 | 2015-12-09 | 浪潮集团有限公司 | Embedded operating system backup and restoration method and device |
| CN108874582A (en) * | 2017-05-15 | 2018-11-23 | 上海宽翼通信科技有限公司 | A kind of system recovery method, device and terminal |
| CN108205446A (en) * | 2017-10-24 | 2018-06-26 | 中兴通讯股份有限公司 | Firmware restorative procedure and device |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112698985A (en) * | 2020-12-21 | 2021-04-23 | 厦门锐骐物联技术股份有限公司 | System starting method and system based on multi-partition technology firmware protection |
| CN112698985B (en) * | 2020-12-21 | 2024-10-18 | 厦门锐骐物联技术股份有限公司 | System starting method and system based on multi-partition technology firmware protection |
| CN115202928A (en) * | 2022-06-09 | 2022-10-18 | 联想(北京)有限公司 | Method and device for processing boot configuration data of operating system |
| CN120510904A (en) * | 2025-07-21 | 2025-08-19 | 合肥康芯威存储技术有限公司 | Memory testing method, device, equipment and medium |
| CN120510904B (en) * | 2025-07-21 | 2025-11-04 | 合肥康芯威存储技术有限公司 | A method, apparatus, device, and medium for testing a memory. |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP5575338B2 (en) | Information processing apparatus, information processing method, and computer program | |
| US10303459B2 (en) | Electronic system with update control mechanism and method of operation thereof | |
| US8806265B2 (en) | LPAR creation and repair for automated error recovery | |
| US20200394144A1 (en) | Information processing system, information processing device, bios updating method for information processing device, and bios updating program for information processing device | |
| CN106775610B (en) | Electronic equipment starting method and electronic equipment | |
| JP2014522070A (en) | Secure recovery apparatus and method | |
| WO2021057795A1 (en) | System starting method and apparatus, node device and computer-readable storage medium | |
| CN108345464A (en) | A kind of the startup method and Android vehicle device of Android system | |
| CN102184111A (en) | Online upgrade method for operating system and device with operating system | |
| CN109783150A (en) | A kind of anti-brick method and device of embedded system starting | |
| TW202131170A (en) | Firmware corruption recovery | |
| CN111090546B (en) | Method, device and equipment for restarting operating system and readable storage medium | |
| CN111651304B (en) | Software recovery method and device based on double-core intelligent ammeter and computer equipment | |
| CN120179321B (en) | Firmware loading method, device, electronic device and storage medium | |
| US10296218B2 (en) | Update control method, update control apparatus, and storage medium | |
| CN117234544B (en) | Method and device for system recovery of server equipment | |
| CN119025336A (en) | Operating system recovery method, server, storage medium and program product | |
| CN111736908A (en) | A control method for staged startup in an embedded dual system | |
| US11354109B1 (en) | Firmware updates using updated firmware files in a dedicated firmware volume | |
| CN113377425B (en) | Method and device for generating BMC firmware, method and device for starting BMC, and storage medium | |
| CN107368315A (en) | A kind of startup method and device of double hard disk dual systems | |
| CN112817642A (en) | Method and device for starting EFI operating system by X86 platform through automatic firmware switching | |
| US12164929B2 (en) | Information processing method and electronic apparatus | |
| CN119377015B (en) | Method, device, equipment and storage medium for configuring mirror image memory | |
| CN119557009B (en) | Method and device for starting embedded Linux main and standby operating systems based on ping-pong mechanism |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20190521 |
|
| RJ01 | Rejection of invention patent application after publication |