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
- embedded
- starting failure
- subregion
- starting
- 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
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 present invention relates to embedded system technology fields more particularly to a kind of embedded system to start anti-brick method and dress
It sets.
Background technique
Embedded system during startup, it is possible that become brick phenomenon.So-called change brick phenomenon refers to when embedded system
When something goes wrong, embedded system starts unresponsive phenomenon to the firmware for the various hardware drivings that system includes.
In practical applications, the stable starting of system is most important for embedded system, if embedded system is opening
Occur becoming brick phenomenon during dynamic, it is likely that lead to embedded system starting failure, to reduce the stabilization of embedded system
Property.
Summary of the invention
The embodiment of the invention provides a kind of embedded systems to start anti-brick method and device, specifically, the present invention is implemented
The technical solution that example provides is as follows:
In a first aspect, the embodiment of the invention provides a kind of embedded systems to start anti-brick method, comprising:
In embedded system start-up course, to be configured as in embedded system the system boot partition of monitoring node into
Row monitoring；
When according to embedded system starting failure is determined to the monitoring result of monitoring node, embedded system is answered
Position simultaneously enters minimum system mode；
Obtain the system repair data packet of embedded system, wherein system repair data packet is including at least embedded system
The data packet of the configuration data of system；
Under minimum system mode, multiple embedded system is guaranteed the repair free of charge according to system repair data, and in embedded system reparation
Embedded system when completion, after starting reparation.
Second aspect, the embodiment of the invention provides a kind of embedded systems to start anti-brick device, comprising:
Monitoring unit, in embedded system start-up course, to being configured as monitoring node in embedded system
System boot partition is monitored；
Reset unit, for determining embedded system starting failure according to the monitoring result to monitoring node when monitoring unit
When, embedded system reset and enters minimum system mode；
Acquiring unit, for obtaining the system repair data packet of embedded system, wherein system repair data packet is at least
The data packet of configuration data comprising embedded system；
Unit is repaired, for guaranteeing the repair free of charge again according to the system repair data that acquiring unit obtains embedding under minimum system mode
Embedded system, and the embedded system when embedded system reparation is completed, after starting reparation.
The third aspect, the embodiment of the invention also provides a kind of embedded systems to start anti-brick equipment, comprising: memory and
Processor, wherein memory, for storing computer instruction；Processor is realized of the invention real for computer instructions
The embedded system for applying example offer starts anti-brick method.
Fourth aspect, the embodiment of the invention also provides a kind of computer readable storage medium, the computer-readable storages
Media storage has computer instruction, which realizes embedded system provided in an embodiment of the present invention when being executed by processor
System starts anti-brick method.
The embodiment of the present invention has the beneficial effect that:
In the embodiment of the present invention, by opening the system for being configured as monitoring node in embedded system start-up course
Dynamic subregion is monitored, and can know embedded system starting failure in time, in turn, is being resetted embedded system and is being entered most
, can be according to the system repair data packet of embedded system after mini system mode, repairing built-in system in time, to realize
Embedded system is automatically repaired, efficiently solves and is led since embedded system occurs becoming brick phenomenon during startup
The problem of causing embedded system starting failure.
Other features and advantages of the present invention will be illustrated in the following description, also, partly becomes from specification
It obtains it is clear that understand through the implementation of the invention.The objectives and other advantages of the invention can be by written explanation
Specifically noted structure is achieved and obtained in book, claims and attached drawing.
Detailed description of the invention
The drawings described herein are used to provide a further understanding of the present invention, constitutes a part of the invention, this hair
Bright illustrative embodiments and their description are used to explain the present invention, and are not constituted improper limitations of the present invention.In the accompanying drawings:
Fig. 1 is the embedded system start-up course schematic diagram in the embodiment of the present invention；
Fig. 2 starts the flow diagram of anti-brick method for the embedded system in the embodiment of the present invention；
Fig. 3 starts the illustrative view of functional configuration of anti-brick device for the embedded system in the embodiment of the present invention；
Fig. 4 starts the hardware structural diagram of anti-brick equipment for the embedded system in the embodiment of the present invention.
Specific embodiment
Following will be combined with the drawings in the embodiments of the present invention, and technical solution in the embodiment of the present invention carries out clear, complete
Site preparation description, it is clear that described embodiments are only a part of the embodiments of the present invention, is not whole embodiments.It is based on
Embodiment in the present invention, it is obtained by those of ordinary skill in the art without making creative efforts every other
Embodiment shall fall within the protection scope of the present invention.
Currently, the start-up course of embedded system is broadly divided into four-stage, as shown in fig.1, embedded system starts
Process includes: the stage that is booted up, file system startup stage, initial phase and starting up's stage four-stage.Wherein,
The stage of being booted up is that starting is guided by bootload (boot) subregion, and file system startup stage is by load text
Part system (rootfs) subregion carries out file system starting, and initial phase is carried out just by loading system (system) subregion
Beginningization starting, starting up are to execute starting up by load data (data) subregion in the stages.Started in embedded system
Cheng Zhong can cause to be embedded in if the either partition in boot subregion, rootfs subregion, system subregion and data subregion damages
Formula system occurs becoming brick phenomenon, to cause embedded system starting failure.
For this purpose, the embodiment of the present invention is directed to embedded system, such as based on general purpose microprocessor (Advanced RISC
Machines, ARM) architecture embedded Linux system etc., provide a kind of embedded system and start anti-brick method, should
Method can be executed by the anti-brick device of starting in embedded system, be opened specifically, starting anti-brick device in embedded system
During dynamic, the system boot partition that monitoring node is configured as in embedded system can be monitored, when according to prison
When the monitoring result of survey node determines embedded system starting failure, embedded system reset and enters minimum system mould
Formula, according to the system repair data packet of embedded system, repairs embedded system, when embedding under minimum system mode
When embedded system reparation is completed, start the embedded system after repairing, in this way, by embedded system start-up course, it is right
The system boot partition for being configured as monitoring node is monitored, and can know embedded system starting failure in time, in turn,
It, can be according to the system repair data packet of embedded system, in time after resetting embedded system and entering minimum system mode
Ground repairing built-in system, is automatically repaired embedded system to realize, efficiently solves due to embedded system
Occur becoming the problem of brick phenomenon leads to embedded system starting failure during startup.
Start anti-brick method to embedded system provided in an embodiment of the present invention with reference to the accompanying drawing to be described in detail, when
So, the present invention is not limited to following embodiments.
Start in anti-brick method in embedded system provided in an embodiment of the present invention, starting anti-brick device can be in advance embedding
Monitoring node is configured in embedded system, i.e., configures monitoring section for the system boot partition loaded in embedded system start-up course
Point.Specifically, the system boot partition for being configured as monitoring node may include: boot subregion, rootfs subregion and system
Subregion.
Further, in one embodiment, the system boot partition for being configured as monitoring node can also include: boot
(bootb) subregion, file system backup (rootfsb) subregion of rootfs subregion and system subregion are backed up in the guidance of subregion
System backup (systemb) subregion.In another embodiment, the system boot partition for being configured as monitoring node can also wrap
Include data subregion.
As shown in fig.2, the process that embedded system provided in an embodiment of the present invention starts anti-brick method is as follows:
Step 201: in embedded system start-up course, the system that monitoring node is configured as in embedded system being opened
Dynamic subregion is monitored.
In practical applications, starting anti-brick device can be using house dog (watchdog) mechanism to quilt in embedded system
The system boot partition for being configured to monitoring node is monitored.
Step 202: when according to embedded system starting failure is determined to the monitoring result of monitoring node, to embedded system
System reset and enters minimum system mode.
In one embodiment, if the system boot partition for being configured as monitoring node includes boot subregion, rootfs points
Area and system subregion, then starting anti-brick device can be when determining the following either case of appearance, it is believed that embedded system starting
Failure:
The first situation: failure is booted up according to the execution of the boot subregion of load.
Second situation: after being booted up successfully, file system starting failure is executed according to the rootfs subregion of load.
The third situation: be booted up with file system starting it is successful after, executed according to the system subregion of load
Initialization starting failure.
In another embodiment, if the system boot partition for being configured as monitoring node includes boot subregion, bootb points
Area, rootfs subregion, rootfsb subregion, system subregion and systemb subregion, then starting anti-brick device can determine
Now when following either case, it is believed that embedded system starting failure:
The first situation: after being booted up unsuccessfully according to the execution of the boot subregion of load, again according to the bootb subregion of load
Secondary execution is booted up failure.
Second situation: fail being booted up successfully and executing file system starting according to the rootfs subregion of load
Afterwards, file system starting failure is executed according to the rootfsb subregion of load again.
The third situation: start successfully in file system and initialization starting is executed according to the system subregion of load and lose
After losing, initialization starting failure is executed again according to the systemb subregion of load.
Further, start anti-brick device after determining embedded system starting failure, watchdog mechanism can be triggered
Overtime reset is carried out to embedded system, and runs minimum system, embedded system is made to enter minimum system mode.
In addition, starting anti-brick device after determining embedded system starting failure, embedded system can also be started and be lost
Specific field is written in identification information corresponding to the system boot partition loaded when losing, when so as to subsequent repairing built-in system,
The system boot partition damaged in embedded system can be determined according to the identification information recorded in specific field.
Specifically, in one embodiment, if the system boot partition for being configured as monitoring node include boot subregion,
Rootfs subregion and system subregion, then boot can be set for specific field when being booted up unsuccessfully by starting anti-brick device
The corresponding identification information 1-1 of subregion sets specific field to when being booted up successfully and file system starting fails
The corresponding identification information 2-1 of rootfs subregion, when file system starts successfully and initializes starting failure, by specific field
It is set as the corresponding identification information 3-1 of system subregion.
In another embodiment, if the system boot partition for being configured as monitoring node includes boot subregion, bootb points
Area, rootfs subregion, rootfsb subregion, system subregion and systemb subregion, then starting anti-brick device can add in basis
The bootb subregion of load executes again when being booted up unsuccessfully, sets the corresponding identification information 1- of bootb subregion for specific field
2, when the rootfsb subregion according to load executes file system starting failure again, rootfsb points are set by specific field
The corresponding identification information 2-2 in area, when executing initialization starting failure again according to the systemb subregion of load, by designated word
Section is set as the corresponding identification information 3-2 of systemb subregion.
Step 203: obtaining the system repair data packet of embedded system, wherein system repair data packet be including at least
The data packet of the configuration data of embedded system.
In the specific implementation, system repair data packet can be obtained from locally specified storage region by starting anti-brick device,
It can also initiate system and repair prompt information, and when having detected USB flash disk insertion, system repair data packet, tool are obtained from USB flash disk
Body implementation is not specifically limited herein.
Step 204: under minimum system mode, multiple embedded system being guaranteed the repair free of charge according to system repair data, and embedded
Embedded system when system reparation is completed, after starting reparation.
In the specific implementation, starting anti-brick device can determine embedded according to the identification information recorded in specific field
The damage subregion of system, and multiple damage subregion is guaranteed the repair free of charge according to system repair data, to realize repairing automatically to embedded system
It is multiple, in turn, the embedded system after repairing can be started when embedded system reparation is completed, be avoided as much as due to embedding
Embedded system occurs becoming the problem of brick phenomenon leads to embedded system starting failure during startup.
It is tellable to be, start in anti-brick method in embedded system provided in an embodiment of the present invention, if being configured as supervising
Survey node system boot partition further include data subregion, then be booted up, file system starting and initialization starting at
After function, when executing starting up's failure according to the data subregion of load, data subregion can be formatted and restart insertion
Formula system, to complete being restarted automatically for embedded system.
Based on the above embodiment, the embodiment of the invention provides a kind of embedded systems to start anti-brick device, refering to Fig. 3 institute
Show, embedded system provided in an embodiment of the present invention starts anti-brick device 300 and includes at least:
Monitoring unit 301, in embedded system start-up course, to being configured as monitoring node in embedded system
System boot partition be monitored；
Reset unit 302, for determining that embedded system opens according to the monitoring result to monitoring node when monitoring unit 301
When dynamic failure, embedded system reset and enters minimum system mode；
Acquiring unit 303, for obtaining the system repair data packet of embedded system, wherein system repair data packet is
Including at least the data packet of the configuration data of embedded system；
Unit 304 is repaired, the system repair data packet for being obtained under minimum system mode according to acquiring unit 303
Repairing built-in system, and the embedded system when embedded system reparation is completed, after starting reparation.
In a kind of possible embodiment, the system boot partition for being configured as monitoring node includes at least guidance point
Area, file partition and system partitioning.
In a kind of possible embodiment, determining that embedded system starting is lost according to the monitoring result of monitoring node
When losing, monitoring unit 301 is specifically used for:
If being booted up failure according to the execution of the boot partition of load, then it is assumed that embedded system starting failure；Alternatively,
After being booted up successfully, if executing file system starting failure according to the file partition of load, then it is assumed that embedded system
Starting failure；Alternatively, be booted up with file system starting it is successful after, if the system partitioning according to load executes initialization
Starting failure, then it is assumed that embedded system starting failure.
In a kind of possible embodiment, the system partitioning for being configured as monitoring node further includes the guidance of boot partition
The system backup subregion of backup subregion, the file system backup subregion of file partition and system partitioning.
In a kind of possible embodiment, determining that embedded system starting is lost according to the monitoring result of monitoring node
When losing, monitoring unit 301 is specifically used for:
After being booted up unsuccessfully according to the execution of the boot partition of load, if the guidance backup subregion according to load executes again
It is booted up failure, then it is assumed that embedded system starting failure；Alternatively, being booted up successfully and according to the file system of load
After subregion of uniting executes file system starting failure, if executing file system starting again according to the file system backup subregion of load
Failure, then it is assumed that embedded system starting failure；It holds alternatively, starting in file system successfully and according to the system partitioning of load
After row initialization starting failure, if executing initialization starting failure again according to the system backup subregion of load, then it is assumed that insertion
The starting failure of formula system.
In a kind of possible embodiment, embedded system provided in an embodiment of the present invention starts anti-brick device 300 also
Include:
Unit 305 is identified, for determining that embedded system opens according to the monitoring result to monitoring node when monitoring unit 301
When dynamic failure, when determining the system boot partition loaded when embedded system starting failure, and embedded system being started failure
Specific field is written in identification information corresponding to the system boot partition of load.
In a kind of possible embodiment, when obtaining the system repair data packet of embedded system, acquiring unit 303
It is specifically used for:
System repair data packet is obtained from locally specified storage region；Alternatively, display system reparation prompt information, and
When having detected USB flash disk insertion, system repair data packet is obtained from USB flash disk.
In a kind of possible embodiment, multiple insertion is guaranteed the repair free of charge in the system repair data obtained according to acquiring unit 303
When formula system, repairs unit 304 and is specifically used for:
According to the identification information recorded in specific field, the damage subregion of embedded system is determined, and according to system reparation
Data packet reparation damages subregion.
In a kind of possible embodiment, the system boot partition for being configured as monitoring node further includes data subregion.
In a kind of possible embodiment, embedded system provided in an embodiment of the present invention starts anti-brick device 300 also
Include:
Formatting unit 306, for after being booted up, file system starting and initialization starting be successful, if according to
The data subregion of load executes starting up's failure, then format data subregion and restarts.
Tellable to be, embedded system provided in an embodiment of the present invention starts each unit pair in anti-brick device 300
Should the anti-brick system of above-mentioned starting in the embodiment of the present invention, start in anti-brick device 300 in embedded system and above-mentioned open be installed
Moving anti-brick system can be realized the anti-brick function of embedded system starting.
Tellable to be, embedded system provided in an embodiment of the present invention starts each unit pair in anti-brick device 300
Should the anti-brick device of above-mentioned starting in the embodiment of the present invention, so as to realize managing embedded system memory function.
After the embedded system for describing exemplary embodiment of the invention starts anti-brick method and apparatus, connect down
Come, anti-brick equipment is started to embedded system provided in an embodiment of the present invention and is simply introduced.
It is included at least as shown in fig.4, embedded system provided in an embodiment of the present invention starts anti-brick equipment 400: processing
Device 41 and memory 42, wherein memory 42, for storing computer instruction；Processor 41, for computer instructions with
Realize that embedded system provided in an embodiment of the present invention starts anti-brick method.
It should be noted that it is only an example that embedded system shown in Fig. 4, which starts anti-brick equipment 400, it should not be right
The function and use scope of the embodiment of the present invention bring any restrictions.
It can also include connecting different component (packets that embedded system provided in an embodiment of the present invention, which starts anti-brick equipment 400,
Include processor 41 and memory 42) bus 43.Wherein, bus 43 indicates one of a few class bus structures or a variety of, including
Memory bus, peripheral bus, local bus etc..
Memory 42 may include the readable medium of form of volatile memory, such as random access memory (Random
Access Memory, RAM) 421 and/or cache memory 422, it can further include read-only memory (Read
Only Memory, ROM) 423.
Memory 42 can also include the program means 424 with one group of (at least one) program module 424, program module
424 include but is not limited to: operational subsystems, one or more application program, other program modules and program data, these
It may include the realization of network environment in each of example or certain combination.
Embedded system starts anti-brick equipment 400 can also be with one or more external equipments 44 (such as keyboard, remote controler
Deng) communication, it can also enable a user to start equipment that anti-brick equipment 400 interact with embedded system with one or more and lead to
Believe (such as mobile phone, computer etc.), and/or, with enable embedded system start anti-brick equipment 400 with it is one or more of the other embedding
Embedded system starts any equipment (such as router, modem etc.) communication that anti-brick equipment 400 is communicated.It is this logical
Letter can be carried out by input/output (Input/Output, I/O) interface 45.Also, embedded system starts anti-brick equipment
400 can also by network adapter 46 and one or more network (such as local area network (Local Area Network,
LAN), wide area network (Wide Area Network, WAN) and/or public network, such as internet) communication.As shown in figure 4, net
Network adapter 46 is communicated by bus 43 with other modules that embedded system starts anti-brick equipment 400.It will be appreciated that though figure
It is not shown in 4, anti-brick equipment 400 can be started in conjunction with embedded system and use other hardware and/or software module, including but not
It is limited to: microcode, device driver, redundant processor, external disk drive array, disk array (Redundant Arrays
Of Independent Disks, RAID) subsystem, tape drive and data backup storage subsystem etc..
Computer readable storage medium provided in an embodiment of the present invention is introduced below.The embodiment of the invention provides
A kind of computer readable storage medium, the computer-readable recording medium storage have computer instruction, which is located
Reason device realizes that embedded system provided in an embodiment of the present invention starts anti-brick method when executing.Specifically, which can
Started in anti-brick equipment 400 with being built in embedded system, in this way, embedded system, which starts anti-brick equipment 400, to be passed through
It executes built-in executable program and realizes that embedded system provided in an embodiment of the present invention starts anti-brick method.
In addition, embedded system provided in an embodiment of the present invention, which starts anti-brick method, is also implemented as a kind of program production
Product, the program product include program code, are run in anti-brick equipment 400 when the program product can start in embedded system
When, which executes embedded system provided in an embodiment of the present invention for making embedded system start anti-brick equipment 400
Start anti-brick method.
Program product provided in an embodiment of the present invention can be using any combination of one or more readable mediums, wherein
Readable medium can be readable signal medium or readable storage medium storing program for executing, and readable storage medium storing program for executing can be but it is electric to be not limited to,
Magnetic, optical, electromagnetic, infrared ray or semiconductor system, device or device, or any above combination is specifically, readable to deposit
The more specific example (non exhaustive list) of storage media includes: electrical connection with one or more conducting wires, portable disc, hard
Disk, RAM, ROM, erasable programmable read only memory (Erasable Programmable Read Only Memory,
EPROM), optical fiber, portable compact disc read only memory (Compact Disc Read-Only Memory, CD-ROM), light are deposited
Memory device, magnetic memory device or above-mentioned any appropriate combination.
Program product provided in an embodiment of the present invention can also be set using CD-ROM and including program code in calculating
Standby upper operation.However, program product provided in an embodiment of the present invention is without being limited thereto, and in embodiments of the present invention, readable storage medium
Matter can be any tangible medium for including or store program, which, which can be commanded execution system, device or device, makes
With or it is in connection.
It should be noted that although being referred to several unit or sub-units of device in the above detailed description, this stroke
It point is only exemplary not enforceable.In fact, embodiment according to the present invention, it is above-described two or more
The feature and function of unit can embody in a unit.Conversely, the feature and function of an above-described unit can
It is to be embodied by multiple units with further division.
In addition, although describing the operation of the method for the present invention in the accompanying drawings with particular order, this do not require that or
Hint must execute these operations in this particular order, or have to carry out shown in whole operation be just able to achieve it is desired
As a result.Additionally or alternatively, it is convenient to omit multiple steps are merged into a step and executed by certain steps, and/or by one
Step is decomposed into execution of multiple steps.
It should be understood by those skilled in the art that, the embodiment of the present invention can provide as method, system or computer program
Product.Therefore, complete hardware embodiment, complete software embodiment or reality combining software and hardware aspects can be used in the present invention
Apply the form of example.
Although preferred embodiments of the present invention have been described, it is created once a person skilled in the art knows basic
Property concept, then additional changes and modifications may be made to these embodiments.So it includes excellent that the following claims are intended to be interpreted as
It selects embodiment and falls into all change and modification of the scope of the invention.
Obviously, those skilled in the art can carry out various modification and variations without departing from this hair to the embodiment of the present invention
The spirit and scope of bright embodiment.In this way, if these modifications and variations of the embodiment of the present invention belong to the claims in the present invention
And its within the scope of equivalent technologies, then the present invention is also intended to include these modifications and variations.
Claims (22)
1. a kind of embedded system starts anti-brick method characterized by comprising
In embedded system start-up course, to be configured as in the embedded system system boot partition of monitoring node into
Row monitoring；
When according to the embedded system starting failure is determined to the monitoring result of the monitoring node, to the embedded system
System reset and enters minimum system mode；
Obtain the system repair data packet of the embedded system, wherein the system repair data packet is including at least described
The data packet of the configuration data of embedded system；
Under the minimum system mode, the embedded system is guaranteed the repair free of charge again according to the system repair data, and described embedding
Embedded system when embedded system reparation is completed, after starting reparation.
2. embedded system as described in claim 1 starts anti-brick method, which is characterized in that be configured as monitoring node is
Boot partition of uniting includes at least boot partition, file partition and system partitioning.
3. embedded system as claimed in claim 2 starts anti-brick method, which is characterized in that according to the monitoring node
Monitoring result determines the embedded system starting failure, comprising:
If being booted up failure according to the execution of the boot partition of load, then it is assumed that the embedded system starting failure；Alternatively,
After being booted up successfully, if executing file system starting failure according to the file partition of load, then it is assumed that described
Embedded system starting failure；Alternatively,
Be booted up with file system starting it is successful after, if executing initialization starting failure according to the system partitioning of load,
Then think the embedded system starting failure.
4. embedded system as claimed in claim 2 starts anti-brick method, which is characterized in that be configured as monitoring node is
System subregion further includes the file system backup subregion and system partitioning of the guidance backup subregion of boot partition, file partition
System backup subregion.
5. embedded system as claimed in claim 4 starts anti-brick method, which is characterized in that according to the monitoring node
Monitoring result determines the embedded system starting failure, comprising:
After being booted up unsuccessfully according to the execution of the boot partition of load, if the guidance backup subregion according to load executes guidance again
Starting failure, then it is assumed that the embedded system starting failure；Alternatively,
Be booted up successfully and according to the file partition of load execute file system starting failure after, if according to load
File system backup subregion execute file system starting failure again, then it is assumed that embedded system starting failure；Alternatively,
File system start successfully and according to the system partitioning of load execute initialization starting failure after, if according to load
System backup subregion executes initialization starting failure again, then it is assumed that the embedded system starting failure.
6. embedded system as described in any one in claim 1-5 starts anti-brick method, which is characterized in that when according to described
When the monitoring result of monitoring node determines the embedded system starting failure, further includes:
Determine the system boot partition loaded when the embedded system starting failure；
The embedded system is started to identification information write-in specific field corresponding to the system boot partition loaded when failure.
7. embedded system as claimed in claim 6 starts anti-brick method, which is characterized in that obtain the embedded system
System repair data packet, comprising:
The system repair data packet is obtained from locally specified storage region；Alternatively,
Display system repairs prompt information, and when having detected USB flash disk insertion, and the system is obtained from the USB flash disk and repairs number
According to packet.
8. embedded system as claimed in claim 7 starts anti-brick method, which is characterized in that according to the system repair data
Guarantee the repair free of charge again the embedded system, comprising:
According to the identification information recorded in specific field, the damage subregion of the embedded system is determined, and according to the system
Repair data guarantees the repair free of charge again the damage subregion.
9. embedded system as described in any one in claim 1-5 starts anti-brick method, which is characterized in that be configured as monitoring
The system boot partition of node further includes data subregion.
10. embedded system as claimed in claim 9 starts anti-brick method, which is characterized in that further include:
After being booted up, file system starts and initialization starting succeeds, if the data subregion according to load executes booting
Starting failure, then format the data subregion and restarted.
11. a kind of embedded system starts anti-brick device characterized by comprising
Monitoring unit, in embedded system start-up course, to being configured as monitoring node in the embedded system
System boot partition is monitored；
Reset unit, for determining the embedded system according to the monitoring result to the monitoring node when the monitoring unit
When starting failure, the embedded system reset and enters minimum system mode；
Acquiring unit, for obtaining the system repair data packet of the embedded system, wherein the system repair data packet is
Including at least the data packet of the configuration data of the embedded system；
Unit is repaired, the system repair data for being obtained under the minimum system mode according to the acquiring unit
Guarantee the repair free of charge again the embedded system, and the embedded system when the embedded system reparation is completed, after starting reparation.
12. embedded system as claimed in claim 11 starts anti-brick device, which is characterized in that be configured as monitoring node
System boot partition includes at least boot partition, file partition and system partitioning.
13. embedded system as claimed in claim 12 starts anti-brick device, which is characterized in that saved according to the monitoring
When the monitoring result of point determines the embedded system starting failure, the monitoring unit is specifically used for:
If being booted up failure according to the execution of the boot partition of load, then it is assumed that the embedded system starting failure；Alternatively,
After being booted up successfully, if executing file system starting failure according to the file partition of load, then it is assumed that described
Embedded system starting failure；Alternatively,
Be booted up with file system starting it is successful after, if executing initialization starting failure according to the system partitioning of load,
Then think the embedded system starting failure.
14. embedded system as claimed in claim 12 starts anti-brick device, which is characterized in that be configured as monitoring node
System partitioning further includes the file system backup subregion and system partitioning of the guidance backup subregion of boot partition, file partition
System backup subregion.
15. embedded system as claimed in claim 14 starts anti-brick device, which is characterized in that saved according to the monitoring
When the monitoring result of point determines the embedded system starting failure, the monitoring unit is specifically used for:
After being booted up unsuccessfully according to the execution of the boot partition of load, if the guidance backup subregion according to load executes guidance again
Starting failure, then it is assumed that the embedded system starting failure；Alternatively,
Be booted up successfully and according to the file partition of load execute file system starting failure after, if according to load
File system backup subregion execute file system starting failure again, then it is assumed that embedded system starting failure；Alternatively,
File system start successfully and according to the system partitioning of load execute initialization starting failure after, if according to load
System backup subregion executes initialization starting failure again, then it is assumed that the embedded system starting failure.
16. as the described in any item embedded systems of claim 11-15 start anti-brick device, which is characterized in that further include:
Unit is identified, for determining the embedded system according to the monitoring result to the monitoring node when the monitoring unit
When starting failure, the system boot partition loaded when embedded system starting failure is determined, and by the embedded system
Identification information write-in specific field corresponding to the system boot partition loaded when starting failure.
17. embedded system as claimed in claim 16 starts anti-brick device, which is characterized in that obtaining the embedded system
When the system repair data packet of system, the acquiring unit is specifically used for:
The system repair data packet is obtained from locally specified storage region；Alternatively,
Display system repairs prompt information, and when having detected USB flash disk insertion, and the system is obtained from the USB flash disk and repairs number
According to packet.
18. embedded system as claimed in claim 17 starts anti-brick device, which is characterized in that according to the acquiring unit
When the system repair data obtained guarantees the repair free of charge the embedded system again, the reparation unit is specifically used for:
According to the identification information recorded in specific field, the damage subregion of the embedded system is determined, and according to the system
Repair data guarantees the repair free of charge again the damage subregion.
19. as the described in any item embedded systems of claim 11-15 start anti-brick device, which is characterized in that be configured as
The system boot partition of monitoring node further includes data subregion.
20. embedded system as claimed in claim 19 starts anti-brick device, which is characterized in that further include:
Formatting unit, for after being booted up, file system starting and initialization starting are successful, if according to the number of load
Starting up's failure is executed according to subregion, then formats the data subregion and restarts.
21. a kind of embedded system starts anti-brick equipment characterized by comprising memory and processor, wherein
The memory, for storing computer instruction；
The processor, for executing the computer instruction to realize such as the described in any item embedded systems of claim 1-10
System starts anti-brick method.
22. a kind of computer readable storage medium, which is characterized in that the computer-readable recording medium storage has computer to refer to
It enables, is realized when the computer instruction is executed by processor as the described in any item embedded system startings of claim 1-10 are anti-
Brick method.
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 (1)
| 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 |
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 (1)
| 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 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9286164B2 (en) | Electronic device to restore MBR, method thereof, and computer-readable medium | |
| US10303459B2 (en) | Electronic system with update control mechanism and method of operation thereof | |
| TWI576764B (en) | A computer system | |
| US9239725B2 (en) | System and method for installing an OS via a network card supporting PXE | |
| US7694165B2 (en) | Automation of bare metal recoveries | |
| KR101931007B1 (en) | Initialization trace of a computing device | |
| CN102855174A (en) | Automatic-recovery target program run control method and device in automated testing | |
| CN103198122A (en) | Method and device for restarting in-memory database | |
| CN103677947A (en) | Equipment dual-system protection method and equipment dual-system upgrading method on basis of linux | |
| CN103970557A (en) | Storage device and system starting method thereof | |
| CN110502281A (en) | A kind of method of embedded device starting linux kernel and file system | |
| TW202030602A (en) | The method and system of bios recovery and update | |
| US11023153B2 (en) | Installation of operating system | |
| CN112882734A (en) | Upgrading method and device, computer equipment and medium | |
| CN111338698A (en) | Method and system for accurately booting server by BIOS (basic input output System) | |
| CN102902550B (en) | Computer system and operating system loading method thereof | |
| CN109783150A (en) | A kind of anti-brick method and device of embedded system starting | |
| CN111090546A (en) | Method, device and equipment for restarting operating system and readable storage medium | |
| US10296218B2 (en) | Update control method, update control apparatus, and storage medium | |
| CN111651304B (en) | Software recovery method and device based on double-core intelligent ammeter and computer equipment | |
| US10635560B2 (en) | Techniques for accurately apprising a user of progress in booting a virtual appliance | |
| US20150212866A1 (en) | Management system for service of multiple operating environments, and methods thereof | |
| CN104750579B (en) | The method and apparatus for making memory mirror | |
| CN115951949A (en) | Recovery method and device for configuration parameters of BIOS (basic input output System) and computing equipment | |
| CN113778485A (en) | System operation method and device of electronic chip, electronic chip and storage medium |
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 |