CN106970809A - A kind of method and apparatus of safety upgrade file system - Google Patents
A kind of method and apparatus of safety upgrade file system Download PDFInfo
- Publication number
- CN106970809A CN106970809A CN201710096040.4A CN201710096040A CN106970809A CN 106970809 A CN106970809 A CN 106970809A CN 201710096040 A CN201710096040 A CN 201710096040A CN 106970809 A CN106970809 A CN 106970809A
- Authority
- CN
- China
- Prior art keywords
- file
- upgrading
- area
- upgrade
- file system
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 58
- 238000001514 detection method Methods 0.000 claims abstract description 21
- 230000008569 process Effects 0.000 claims abstract description 16
- 238000010586 diagram Methods 0.000 description 13
- 230000006870 function Effects 0.000 description 11
- 238000004590 computer program Methods 0.000 description 7
- 230000009471 action Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005192 partition Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/11—File system administration, e.g. details of archiving or snapshots
- G06F16/116—Details of conversion of file system types or formats
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/4406—Loading of operating system
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiments of the invention provide a kind of method of safety upgrade file system, methods described includes：During os starting, detected in the BootLoader stages and whether there is the corresponding upgrade file of file system to be upgraded in the upgrade area in storage chip；When there is upgrade file in the upgrade area that detection determines in storage chip, the upgrade file is written to execution file system updating operation in the file system area in storage chip.The method for the safety upgrade file system that the embodiment of the present invention is provided, the escalation process of file system can be completed in the BootLoader stages, it is possible to prevente effectively from after os starting, when carrying out file system upgrading, due to the erasing to storage chip content, lead to not the instrument for finding the file system new for burning, and new file system can not be written into storage chip, the problem of also can not just completing upgrading.
Description
Technical Field
The invention relates to the technical field of data processing, in particular to a method and a device for safely upgrading a file system.
Background
A file system is a method and data structure used by an operating system to specify files on a storage device (usually a disk, but also a NAND Flash based solid state disk) or partition, i.e., a method of organizing files on a storage device. From a system perspective, a file system is a system that organizes and allocates space of a file storage device, is responsible for file storage, and protects and retrieves stored files.
The existing schemes for upgrading a file system are all to upgrade the file system after directly erasing the existing file system on a memory chip in a running state of an operating system, but this method has a risk of system crash. This is because the entire file system source file is not completely imported into system memory after the operating system is booted. Therefore, after the file system in the memory chip is directly erased, the tools for burning the new file system in the original file system are also erased, and if the tools for burning the new file system in the original file system are not imported into the system memory, when the file system is upgraded, the system can report errors because the tools for burning the new file system in the original file system cannot be called. That is, since a tool for burning a new file system cannot be found, the new file system cannot be normally written into the corresponding storage area, and thus the upgrade cannot be normally completed. For the above reasons, the new file system cannot be normally written into the memory chip, so that the file system fails to be upgraded, and further the operating system crashes and the machine cannot be started.
Disclosure of Invention
In order to solve the problems in the prior art, embodiments of the present invention are expected to provide a method and an apparatus for safely upgrading a file system.
The embodiment of the invention provides a method for safely upgrading a file system, which comprises the following steps:
in the process of starting an operating system, detecting whether an upgrade file corresponding to a file system to be upgraded exists in an upgrade area in a memory chip at a BootLoader stage;
and when the upgrade file exists in the upgrade area in the storage chip, writing the upgrade file into a file system area in the storage chip to execute file system upgrade operation.
In the foregoing solution, before detecting whether an upgrade file exists in the memory chip at the BootLoader stage, the method further includes:
and in the state that the equipment is started, after the operating system starts the file system upgrading operation, writing an upgrading file corresponding to the file system to be upgraded into an upgrading area in the storage chip.
In the above scheme, the upgrade area and the file system area are two different storage areas on the same memory chip, or are different storage areas on different memory chips.
In the foregoing solution, the detecting whether an upgrade file exists in an upgrade area in a memory chip includes:
detecting the Magic number of the file in the upgrading area in the storage chip, and if the file type corresponding to the Magic number of the file in the upgrading area is the type of the file system to be upgraded, determining that the upgrading file exists in the upgrading area in the storage chip.
In the foregoing solution, after writing the upgrade file into a file system area in a memory chip, the method further includes:
and erasing the upgrade file stored in the upgrade area, and normally starting the operating system.
The embodiment of the invention provides a device for safely upgrading a file system, which comprises: the system comprises a starting module, a detection module and an upgrading module; wherein,
the starting module is used for starting the operating system;
the detection module is used for detecting whether an upgrade file corresponding to a file system to be upgraded exists in an upgrade area in a memory chip at a BootLoader stage in the process of starting an operating system;
and the upgrading module is used for writing the upgrading file into a file system area in the storage chip to execute file system upgrading operation when the detection module detects that the upgrading file exists in the upgrading area in the storage chip.
In the above scheme, the apparatus further comprises: and the writing module is used for writing the upgrading file corresponding to the file system to be upgraded into the upgrading area in the storage chip after the operating system starts the upgrading operation of the file system in the state that the equipment is started.
In the above scheme, the upgrade area and the file system area are two different storage areas on the same memory chip, or are different storage areas on different memory chips.
In the above solution, the detection module includes:
the detection submodule is used for detecting the type corresponding to the Magic number of the file in the upgrading area in the storage chip;
and the determining submodule is used for determining that the upgrading file exists in the upgrading area in the storage chip when the file type corresponding to the Magic number of the file in the upgrading area is the type of the file system to be upgraded.
In the above scheme, the apparatus further comprises: the erasing module is used for erasing the upgrading file stored in the upgrading area after the upgrading file is written into the file system area in the storage chip;
the starting module is further configured to normally start the operating system after the upgrade file is written into the file system area in the memory chip.
Compared with the prior art, the embodiment of the invention at least has the following advantages:
according to the method for safely upgrading the file system provided by the embodiment of the invention, in the process of starting the operating system, the upgrading operation of the file system is completed in the boot loader stage, and in the stage, when the upgrading file exists in the upgrading area in the storage chip through detection and determination, the upgrading file is obtained and written into the file system area in the storage chip. By the method, the problem that when the file system is upgraded after the operating system is started, due to the fact that the content of the storage chip is erased, a tool for burning a new file system cannot be found, the new file system cannot be written into the storage chip, and the upgrade cannot be completed can be effectively solved.
Drawings
FIG. 1 is a flow diagram of a method for securely upgrading a file system in accordance with one embodiment of the present invention;
FIG. 2 is a flow chart of a method for safely upgrading a file system according to a second embodiment of the invention;
FIG. 3 is a schematic diagram of a basic structure of an apparatus for securely upgrading a file system according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of a basic structure of a second embodiment of the apparatus for securely upgrading a file system according to the present invention;
FIG. 5 is a schematic diagram of a basic structure of a third embodiment of the apparatus for securely upgrading a file system according to the present invention;
FIG. 6 is an exemplary flowchart of a method for securely upgrading a file system according to the present invention.
Detailed Description
The present invention will be described in further detail with reference to the following detailed description and accompanying drawings.
Example one
Referring to fig. 1, a flowchart illustrating steps of a method for securely upgrading a file system according to the present invention is shown, where the method may specifically include:
step 101, in the process of starting an operating system, detecting whether an upgrade file corresponding to a file system to be upgraded exists in an upgrade area in a memory chip at a boot loader (BootLoader) stage;
generally, BootLoader is a first section of code executed by an operating system after power-on, after the BootLoader completes initialization of a CPU and related hardware, an operating system image or a solidified embedded application program is installed in a memory and then jumps to a space where the operating system is located, and the operating system is started to run.
In an optional implementation manner of the present invention, before detecting whether an upgrade file exists in a memory chip at a BootLoader stage, the method further includes:
and in the state that the equipment is started, after the operating system starts the file system upgrading operation, writing an upgrading file corresponding to the file system to be upgraded into an upgrading area in the storage chip.
The device can be any device with data computing and processing capabilities, such as a PC, a server, a notebook computer, a tablet computer and the like. Specifically, in the state that the device is started, when it is determined that the file system upgrading operation is performed, after the file system upgrading operation is started by the operating system, the upgrading file corresponding to the file system to be upgraded is written into the upgrading area in the memory chip.
Specifically, the detecting whether an upgrade file exists in an upgrade area in the memory chip includes:
detecting Magic numbers (Magic numbers) of files in an upgrading area in a storage chip, and if the file type corresponding to the Magic numbers of the files in the upgrading area is the type of a file system to be upgraded, determining that the upgrading files exist in the upgrading area in the storage chip.
In many types of files, the content of the first N bytes is fixed (the fixed bytes may be intentionally padded or may be a byte inherent to the file itself), and the file type can be determined according to the content of the N fixed bytes, and the content of the N bytes is called a magic number, where N is a positive integer whose value is adjusted according to the actual file type.
Therefore, in the above-mentioned scheme of the embodiment of the present invention, BootLoader detects the contents of the first N bytes of the file in the upgrade area, and if the file type corresponding to the contents of the first N bytes is the type of the file system to be upgraded, it may be determined that the upgrade file exists in the upgrade area in the memory chip.
Step 102, when it is determined that the upgrade file exists in the upgrade area in the memory chip, writing the upgrade file into a file system area in the memory chip to execute a file system upgrade operation.
Specifically, the upgrade area and the file system area are two different storage areas on the same memory chip, or different storage areas on different memory chips.
The upgrading area is used for storing upgrading files corresponding to a file system to be upgraded, and the file system area is a storage and installation area of the file system.
In this step, when it is detected that an upgrade file exists in an upgrade area in the memory chip, the BootLoader calls an internal function to write the upgrade file into a file system area, thereby completing the upgrade of the file system. Compared with the prior art, the method and the device have the advantages that the BootLoader internal function is directly utilized to complete the writing operation of the upgrade file, and a tool for burning a new file system in the original file system is not required to be called.
In an optional implementation manner of the present invention, referring to fig. 2, after the writing the upgrade file to the file system area in the memory chip, the method further includes:
and 103, erasing the upgrade file stored in the upgrade area, and normally starting the operating system.
In the above scheme, when it is determined by the detection that the upgrade file does not exist in the upgrade area in the memory chip, the operating system is normally started.
By deleting the upgrade file stored in the upgrade area in step 103, it is possible to prevent the file system upgrade operation from being repeatedly performed again when the device is started next time.
The method according to the first embodiment of the present invention is described in detail below with reference to an application example.
After the device is started, the BootLoader reads the first 4 bytes of the upgrade area through a local nandflash drive function nand _ read _ skip _ bad () function, and identifies the content of the 4 bytes to judge whether the upgrade file exists in the upgrade area. If the upgrade file exists in the upgrade area, erasing original data in the file system area through a nand _ erase _ ops () function, then reading all the data (i.e., the upgrade file) in the upgrade area to a certain continuous address of the memory through a nand _ read _ skip _ band () function, and then writing the upgrade file in the memory area into a nandflash area (i.e., the file system area) where the file system is located through a nand _ write _ skip _ band () function.
Through the process, the upgrading process of the file system is completed once.
To sum up, the method for safely upgrading a file system according to the embodiment of the present invention is performed in a BootLoader phase during a process of starting an operating system, and in this phase, when it is determined that an upgrade file exists in an upgrade area in a memory chip through detection, the upgrade file is obtained and written into a file system area in the memory chip, so as to complete an upgrade operation of the file system. By the method, the problem that when the file system is upgraded after the operating system is started, due to the fact that the content of the storage chip is erased, a tool for burning a new file system cannot be found, the new file system cannot be written into the storage chip, and the upgrade cannot be completed can be effectively solved.
Example two
Referring to fig. 3, a block diagram of an embodiment of an apparatus for securely upgrading a file system according to the present invention is shown, the apparatus including: a starting module 31, a detection module 32 and an upgrading module 33; wherein,
the starting module 31 is used for starting an operating system;
the detection module 32 is configured to detect, in a BootLoader stage, whether an upgrade file corresponding to a file system to be upgraded exists in an upgrade area in a memory chip in a process of starting an operating system;
the upgrade module 33 is configured to, when the detection module 32 determines that the upgrade file exists in the upgrade area in the memory chip through detection, write the upgrade file into the file system area in the memory chip to perform a file system upgrade operation.
In an alternative embodiment of the invention, with reference to fig. 4, the apparatus further comprises: the write-in module 34 is configured to, in a state where the device is turned on, write an upgrade file corresponding to the file system to be upgraded into an upgrade area in the memory chip after the operating system starts a file system upgrade operation.
Specifically, the upgrade area and the file system area are two different storage areas on the same memory chip, or different storage areas on different memory chips.
Specifically, the detection module 32 includes:
the detection submodule is used for detecting the type corresponding to the Magic number of the file in the upgrading area in the storage chip;
and the determining submodule is used for determining that the upgrading file exists in the upgrading area in the storage chip when the file type corresponding to the Magic number of the file in the upgrading area is the type of the file system to be upgraded.
In an alternative embodiment of the invention, with reference to fig. 5, the apparatus further comprises: the erasing module 35 is configured to erase the file stored in the upgrade area after the upgrade file is written into the file system area in the memory chip;
the starting module 31 is further configured to normally start the operating system after the upgrade file is written into the file system area in the memory chip.
In a specific implementation process, the starting module 31, the detecting module 32, the upgrading module 33, the writing module 34, and the erasing module 35 may be implemented by a Central Processing Unit (CPU), a Micro Processing Unit (MPU), a Digital Signal Processor (DSP), or a Programmable logic array (FPGA) in the device with data calculation and Processing capabilities.
Application example
Referring to FIG. 6, a flowchart illustrating exemplary steps of a method for securely upgrading a file system of the present invention is shown, including:
step 601: starting a system;
specifically, the operating system enters a normal running state after being started.
Step 602: judging whether to upgrade the file system;
specifically, the operating system determines whether to upgrade the file system, and if so, proceeds to step 604 to continue execution; if the judgment result is no, go to step 603, and the operating system continues to operate normally;
step 603: operating the system normally;
step 604: writing an upgrade file corresponding to the file system into an upgrade area in the storage chip;
that is, an image of the file system is written to an upgrade area in the memory chip.
Step 605: restarting an operating system;
after step 604 is performed, the operating system reboot action is performed actively by the user, or the operating system is automatically rebooted.
Step 606: the BootLoader performs magic number detection on the upgrading area;
specifically, the contents of the Magic number of the file in the upgrade area in the memory chip are detected.
Step 607: judging whether an upgrade file exists in the upgrade area;
specifically, determining a file type corresponding to the Magic number, determining that an upgrade file exists in an upgrade area in the memory chip when the file type corresponding to the Magic number is the type of the file system to be upgraded, and then turning to step 608 to continue execution; and when the upgrade file does not exist in the upgrade area in the memory chip, turning to the step 601, and starting the system normally.
Step 608: and writing the upgrade file in the upgrade area into the file system area.
Step 609: and erasing the content in the upgrading area.
Specifically, the upgrade file in the upgrade area is erased, so that the file system upgrade operation is not repeatedly executed next time the operating system is restarted.
After step 609 is performed, 601 is continued, i.e., the operating system is normally started.
The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications of these 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 embodiments of the invention.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or terminal that comprises the element.
The method and the device for safely upgrading the file system provided by the invention are described in detail, a specific example is applied in the text to explain the principle and the implementation mode of the invention, and the description of the embodiment is only used for helping to understand the method and the core idea of the invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (10)
1. A method of securely upgrading a file system, the method comprising:
in the process of starting an operating system, detecting whether an upgrade file corresponding to a file system to be upgraded exists in an upgrade area in a memory chip at a BootLoader stage;
and when the upgrade file exists in the upgrade area in the storage chip, writing the upgrade file into a file system area in the storage chip to execute file system upgrade operation.
2. The method according to claim 1, wherein before detecting whether the upgrade file exists in the memory chip in the BootLoader phase, the method further comprises:
and in the state that the equipment is started, after the operating system starts the file system upgrading operation, writing an upgrading file corresponding to the file system to be upgraded into an upgrading area in the storage chip.
3. The method of claim 2, wherein the upgrade area and the file system area are two different storage areas on the same memory chip, or are different storage areas on different memory chips.
4. The method of claim 3, wherein the detecting whether the upgrade file exists in the upgrade area in the memory chip comprises:
detecting the Magic number of the file in the upgrading area in the storage chip, and if the file type corresponding to the Magic number of the file in the upgrading area is the type of the file system to be upgraded, determining that the upgrading file exists in the upgrading area in the storage chip.
5. The method of any of claims 1 to 4, wherein after writing the upgrade file to a file system area in a memory chip, the method further comprises:
and erasing the upgrade file stored in the upgrade area, and normally starting the operating system.
6. An apparatus for securely upgrading a file system, the apparatus comprising: the system comprises a starting module, a detection module and an upgrading module; wherein,
the starting module is used for starting the operating system;
the detection module is used for detecting whether an upgrade file corresponding to a file system to be upgraded exists in an upgrade area in a memory chip at a BootLoader stage in the process of starting an operating system;
and the upgrading module is used for writing the upgrading file into a file system area in the storage chip to execute file system upgrading operation when the detection module detects that the upgrading file exists in the upgrading area in the storage chip.
7. The apparatus of claim 6, further comprising: and the writing module is used for writing the upgrading file corresponding to the file system to be upgraded into the upgrading area in the storage chip after the operating system starts the upgrading operation of the file system in the state that the equipment is started.
8. The apparatus of claim 7, wherein the upgrade area and the file system area are two different storage areas on a same memory chip, or are different storage areas on different memory chips.
9. The apparatus of claim 8, wherein the detection module comprises:
the detection submodule is used for detecting the type corresponding to the Magic number of the file in the upgrading area in the storage chip;
and the determining submodule is used for determining that the upgrading file exists in the upgrading area in the storage chip when the file type corresponding to the Magic number of the file in the upgrading area is the type of the file system to be upgraded.
10. The apparatus of any one of claims 6 to 9, further comprising: the erasing module is used for erasing the upgrading file stored in the upgrading area after the upgrading file is written into the file system area in the storage chip;
the starting module is further configured to normally start the operating system after the upgrade file is written into the file system area in the memory chip.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710096040.4A CN106970809A (en) | 2017-02-22 | 2017-02-22 | A kind of method and apparatus of safety upgrade file system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710096040.4A CN106970809A (en) | 2017-02-22 | 2017-02-22 | A kind of method and apparatus of safety upgrade file system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN106970809A true CN106970809A (en) | 2017-07-21 |
Family
ID=59328363
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710096040.4A Pending CN106970809A (en) | 2017-02-22 | 2017-02-22 | A kind of method and apparatus of safety upgrade file system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106970809A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112291206A (en) * | 2020-10-14 | 2021-01-29 | 北京安石科技有限公司 | Method for improving operating system security through main control chip |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101196822A (en) * | 2007-07-02 | 2008-06-11 | 深圳创维－Rgb电子有限公司 | Code upgrading device, method and system |
| CN102012831A (en) * | 2010-12-08 | 2011-04-13 | 四川金网通电子科技有限公司 | Over-the-air technology (OTA) upgrading method based on Linux platform |
| CN102043652A (en) * | 2010-12-08 | 2011-05-04 | 苏州捷泰科信息技术有限公司 | Processing system and method for embedded device root file system |
| CN202186344U (en) * | 2011-07-18 | 2012-04-11 | 广州汽车集团股份有限公司 | Vehicle-mounted electronic control unit |
| CN102495670A (en) * | 2011-12-09 | 2012-06-13 | 山东大学 | Systematic one-key reset device applicable to embedded Linux operating system |
| CN103092647A (en) * | 2012-12-29 | 2013-05-08 | 聚光科技(杭州)股份有限公司 | Online upgrade method of embedded system |
| CN103136002A (en) * | 2011-11-25 | 2013-06-05 | 航天信息股份有限公司 | Automatic upgrade control method based on UBoot instruction and system |
| CN104750527A (en) * | 2015-03-27 | 2015-07-01 | 广州快飞计算机科技有限公司 | Embedded system upgrading method and system |
| CN105551486A (en) * | 2015-12-02 | 2016-05-04 | 珠海市杰理科技有限公司 | Voice recognition toy and voice interactive device |
-
2017
- 2017-02-22 CN CN201710096040.4A patent/CN106970809A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101196822A (en) * | 2007-07-02 | 2008-06-11 | 深圳创维－Rgb电子有限公司 | Code upgrading device, method and system |
| CN102012831A (en) * | 2010-12-08 | 2011-04-13 | 四川金网通电子科技有限公司 | Over-the-air technology (OTA) upgrading method based on Linux platform |
| CN102043652A (en) * | 2010-12-08 | 2011-05-04 | 苏州捷泰科信息技术有限公司 | Processing system and method for embedded device root file system |
| CN202186344U (en) * | 2011-07-18 | 2012-04-11 | 广州汽车集团股份有限公司 | Vehicle-mounted electronic control unit |
| CN103136002A (en) * | 2011-11-25 | 2013-06-05 | 航天信息股份有限公司 | Automatic upgrade control method based on UBoot instruction and system |
| CN102495670A (en) * | 2011-12-09 | 2012-06-13 | 山东大学 | Systematic one-key reset device applicable to embedded Linux operating system |
| CN103092647A (en) * | 2012-12-29 | 2013-05-08 | 聚光科技(杭州)股份有限公司 | Online upgrade method of embedded system |
| CN104750527A (en) * | 2015-03-27 | 2015-07-01 | 广州快飞计算机科技有限公司 | Embedded system upgrading method and system |
| CN105551486A (en) * | 2015-12-02 | 2016-05-04 | 珠海市杰理科技有限公司 | Voice recognition toy and voice interactive device |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112291206A (en) * | 2020-10-14 | 2021-01-29 | 北京安石科技有限公司 | Method for improving operating system security through main control chip |
| CN112291206B (en) * | 2020-10-14 | 2023-08-15 | 北京安石科技有限公司 | Method for improving operating system safety through main control chip |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9471435B2 (en) | Information processing device, information processing method, and computer program | |
| TWI501253B (en) | Handling errors during device bootup from a non-volatile memory | |
| US7322029B2 (en) | Method and system for recovering program code in a computer system | |
| US9239725B2 (en) | System and method for installing an OS via a network card supporting PXE | |
| US20170220278A1 (en) | Backing up firmware during initialization of device | |
| US7908469B2 (en) | Method for executing power on self test on a computer system and updating SMBIOS information partially | |
| US20080082814A1 (en) | Electronic system with nand flash memory storing boot code and highly reliable boot up method | |
| US11144328B2 (en) | System method to update failover process by running basic input/output (BIOS) system boot code from non-volatile memory express device (NVME) | |
| CN105739961B (en) | Starting method and device of embedded system | |
| CN108829449B (en) | Method, device, equipment and medium for starting operating system by BIOS (basic input output System) | |
| CN103514015A (en) | Method and device for booting operation system from storage medium | |
| CN106909362A (en) | The method and apparatus that the method and apparatus of BMC firmwares generation, BMC systems start | |
| US20060064576A1 (en) | Boot systems and methods | |
| US10664598B1 (en) | Firmware security patch deployment | |
| US8788800B2 (en) | OS processing method, system and non-transitory computer readable storage medium thereof | |
| WO2015184732A1 (en) | Bootstrap storage method, bootstrap fault recovery method and device, and computer storage medium | |
| US20130080751A1 (en) | Method and device for updating bios program for computer system | |
| US10491736B2 (en) | Computer system and method thereof for bluetooth data sharing between UEFI firmware and OS | |
| CN103455750B (en) | The high peace verification method of a kind of embedded device and device | |
| US7849300B2 (en) | Method for changing booting sources of a computer system and a related backup/restore method thereof | |
| CN114265603A (en) | System upgrading method and device based on asymmetric partition and electronic equipment | |
| WO2018014687A1 (en) | Parameter passing method and apparatus, and computer storage medium | |
| CN110286953B (en) | Method and device for starting embedded system, embedded device and storage medium | |
| CN106970809A (en) | A kind of method and apparatus of safety upgrade file system | |
| CN110825421A (en) | Firmware upgrading method and system and readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20170721 |