CN104572229A - Firmware upgrade method and firmware upgrade device for embedded system - Google Patents
Firmware upgrade method and firmware upgrade device for embedded system Download PDFInfo
- Publication number
- CN104572229A CN104572229A CN201510074784.7A CN201510074784A CN104572229A CN 104572229 A CN104572229 A CN 104572229A CN 201510074784 A CN201510074784 A CN 201510074784A CN 104572229 A CN104572229 A CN 104572229A
- Authority
- CN
- China
- Prior art keywords
- subregion
- embedded system
- image file
- upgrade
- nonvolatile memory
- 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.)
- Granted
Links
Landscapes
- Stored Programmes (AREA)
- Techniques For Improving Reliability Of Storages (AREA)
Abstract
The invention relates to a firmware upgrade method and a firmware upgrade device for an embedded system. The method comprises the following steps: (a) acquiring and storing an upgrade mirror file to a first partition area of a nonvolatile memory of the embedded system, and generating the storage path information of the upgrade mirror file; (b) performing bad block detection on a second partition area of the nonvolatile memory; (c) copying the upgrade mirror file from the first partition area to the good block of the second partition according to the storage path information and modifying the start position of the operating system to be the position of the second partition; (d) performing bad block detection on a third partition of the nonvolatile memory after the operating system is restarted from the second partition in the embedded system; (e) copying the upgrade mirror file to a good block of the third partition area, and modifying the start position of the operating system to be position of the third partition area; and (f) restarting the operating system from the third partition area in the embedded system. Therefore, the upgrade failure problem brought by the bad block generated in the nonvolatile memory such as NAND FLASH in the operating system upgrading process can be solved.
Description
Technical field
The present invention relates to embedded system technology field, particularly a kind of firmware upgrade method of embedded system and a kind of device for upgrading firmware of embedded system.
Background technology
Embedded OS is a kind of broad-spectrum system software, generally includes hardware-related bottom layer driving software, system kernel, device drives interface, communication protocol, graphical interfaces, standardization browser etc.Embedded OS is responsible for distribution, the task scheduling of whole soft and hardware resources of embedded device, and control, coordinate concurrent activities, it must embody the feature of its place system, can reach function required by system by handling certain module.Have in the widely used operating system of built-in field at present: built-in Linux, Windows Embedded (as: Wince6.0), VxWorks etc., and be applied in Android, iOS etc. of smart mobile phone and panel computer.
The feature of embedded OS mainly contains: system kernel is little, specificity is strong, system is simplified, high real-time, multitask, need developing instrument and environment etc.
Operating system (Operating system, OS) is the core of embedded development, and therefore the upgrading renewal work of operating system also becomes particularly important.The method major part of existing embedded OS upgrading leaves new system file in some fixing storage area, and then copied the region be stored into system file and fixed; Can first delete original operating system file before each copy, copy successfully at new operating system file, restart embedded device and complete primary system firmware upgrade renewal rewards theory (being also operating system update).Another kind of upgrading mode uploads onto the server after being encrypted by new operating system file, then local to embedded system by software download, delete original old operating system file again, be finally copied to the specific region of system, restart system and complete OS upgrading renewal.
But, in existing various operating system update process, following problem can be there is: the problem that (1) dies due to system when NAND Flash produces the operating system update that bad block causes; (2) the escalation process file store path information dropout caused because driving design is unreasonable and the not high problem of the system run all right brought.
Summary of the invention
For overcoming the one or more problems existed in prior art, the invention provides a kind of firmware upgrade method of embedded system and a kind of device for upgrading firmware of embedded system.
Particularly, the firmware upgrade method of a kind of embedded system that the embodiment of the present invention provides, wherein said embedded system comprises nonvolatile memory.Described firmware upgrade method comprises step: (a) obtains and store upgrade image file to one first subregion of the described nonvolatile memory of described embedded system and the store path information generating described upgrade image file; B () one second subregion to described nonvolatile memory carries out bad block detection and in described second subregion, determines a good block; C () copies described upgrade image file to the described good block of described second subregion and the position of retouching operation system startup according to described store path information from described first subregion is start from described second subregion; D () in described embedded system, carries out bad block detection to one the 3rd subregion of described nonvolatile memory and determine a good block in described 3rd subregion after described second partition Reboot operation system; (e) copy described upgrade image file to the described good block of described 3rd subregion and the position that starts of retouching operation system for starting from described 3rd subregion; F () makes described embedded system from described 3rd partition Reboot operation system.
In one embodiment of the invention, above-mentioned steps (a) comprising: an application program of described embedded system receives the described upgrade image file of host computer transmission and is stored to described first subregion; The described store path information of described upgrade image file is sent to bottom upgrading driver by described application program; And after the described store path information of transmission, make the thread of described application program be in blocked state.
In one embodiment of the invention, above-mentioned steps (a) comprising: an application program of described embedded system receives the described upgrade image file of host computer transmission and is stored to described first subregion; The described store path information of described upgrade image file is sent to bottom upgrading driver by described application program; And described bottom upgrading driver is preserved described store path information and creates bottom upgrading thread and return the thread of a thread creation Success Flag for the described application program of end creating successfully.
In one embodiment of the invention, above-mentioned firmware upgrade method also comprised step before step (c): carry out file write-protect operation to the application program to be protected in described embedded system, rewritten to prevent application file data.
In one embodiment of the invention, above-mentioned firmware upgrade method also comprised step before step (c): by the fixed area of the application file backup to be protected of described embedded system at described first subregion.
In one embodiment of the invention, above-mentioned steps (e) comprising: copy the described good block of described upgrade image file to described 3rd subregion from described first subregion; Or copy the described good block of described upgrade image file to described 3rd subregion from described second subregion.
In one embodiment of the invention, above-mentioned nonvolatile memory has also divided one the 4th subregion; Described 4th subregion is that boot section is using the storage area of the boot mirror image as os starting, described 3rd subregion is that the first MIRROR SITE is using the main storage area of the kernel mirror image as operating system, described second subregion be the second MIRROR SITE using the backup area of the kernel mirror image as operating system, described first subregion is user area.
In one embodiment of the invention, above-mentioned nonvolatile memory is NAND flash memory.
In addition, the device for upgrading firmware of a kind of embedded system that the embodiment of the present invention provides, wherein said embedded system comprises nonvolatile memory.Described device for upgrading firmware comprises: data reception module, for obtaining and storing upgrade image file to one first subregion of the described nonvolatile memory of described embedded system and the store path information generating described upgrade image file, Bad Block Management module, for carrying out bad block detection to one second subregion of described nonvolatile memory and one the 3rd subregion and determine a good block respectively in described second subregion and described 3rd subregion, upgrading driver module, for according to the described store path information of described upgrade image file from described first subregion copy described upgrade image file to the described good block of described second subregion and the position that starts of retouching operation system for starting from described second subregion, make described embedded system from copy after described second partition Reboot operation system described upgrade image file to the described good block of described 3rd subregion and the position that starts of retouching operation system for starting from described 3rd subregion, and make described embedded system from described 3rd partition Reboot operation system.
In one embodiment of the invention, above-mentioned nonvolatile memory is NAND flash memory, and described nonvolatile memory has also divided one the 4th subregion; Described 4th subregion is that boot section is using the storage area of the boot mirror image as os starting, described 3rd subregion is that the first MIRROR SITE is using the main storage area of the kernel mirror image as operating system, described second subregion be the second MIRROR SITE using the backup area of the kernel mirror image as operating system, described first subregion is user area.
Therefore, the above embodiment of the present invention can reach following one or more beneficial effect: (1) effectively solves operating system update process, nonvolatile memory such as NAND FLASH produces the upgrading failure that bad block brings, and finally causes the catastrophic problem that system is died; (2) problem that the routing information effectively solving escalation process kernel mirror image file is lost; (3) problem that in operating system update process, stability is not high is solved; And (4) solve the problem of the user file damage brought in escalation process.
By the detailed description below with reference to accompanying drawing, other side of the present invention and feature become obvious.But it should be known that this accompanying drawing is only the object design of explanation, instead of as the restriction of scope of the present invention, this is because it should with reference to additional claim.Should also be appreciated that, unless otherwise noted, unnecessaryly draw accompanying drawing to scale, they only try hard to structure described herein and flow process are described conceptually.
Accompanying drawing explanation
Below in conjunction with accompanying drawing, the specific embodiment of the present invention is described in detail.
Fig. 1 is the process flow diagram of the firmware upgrade method of a kind of embedded system of the embodiment of the present invention.
Fig. 2 is the subregion schematic diagram of a kind of nonvolatile memory of the embodiment of the present invention.
Fig. 3 is the high-level schematic functional block diagram of the device for upgrading firmware of a kind of embedded system of the embodiment of the present invention.
Embodiment
For enabling above-mentioned purpose of the present invention, feature and advantage become apparent more, are described in detail the specific embodiment of the present invention below in conjunction with accompanying drawing.
Refer to Fig. 1 and Fig. 2, wherein Fig. 1 is the process flow diagram of the firmware upgrade method of a kind of embedded system of the embodiment of the present invention, and Fig. 2 is the subregion schematic diagram of a kind of nonvolatile memory of the embodiment of the present invention.Particularly, in the firmware upgrade method of the embedded system of the present embodiment:
By the application software of host computer (such as PC), upgrade image file is sent to embedded system, be responsible for receiving the OS (OperatingSystem from host computer by the application program in embedded system, operating system) upgrade image file be stored in the user area (see Fig. 2) of the nonvolatile memory of embedded system, follow-up updating operation process is just completed by the driver of upgrading of the bottom in embedded system.Perform in the process of firmware upgrade (or claiming OS upgrading) at bottom upgrading driver, the store path information of upgrade image file during upgrading in the user area of nonvolatile memory can not error of transmission to have two kinds of preferred methods to ensure: (a) a kind of is after store path information is sent to bottom upgrading driver by the upper level applications of embedded system, the thread of this application program is in blocked state, so just can ensure that the process intermediate value that bottom upgrading driver calls this store path information variable can not be lost because the thread of application program exits, thus the correctness of guarantee information transmission and accuracy, (b) another mode be upper level applications by the store path information transmission of image upgrade file to bottom upgrading driver time, bottom upgrading driver is first preserved, then the upgrading thread of bottom is created, create successfully, a successfully mark is returned to upper level applications, upper level applications receives and returns successful mark, just exits current thread, performs next step, and now, the thread that bottom upgrading driver creates also can be placed on the process of the complete upgrading of poll in the current process of operating system, this method can solve file path information dropout too and cause failed problem of upgrading.
Hold above-mentioned, after bottom upgrading driver receives the store path information of upgrade image file, the operation of first quiescing system boot self-starting software, the problem of the upgrading failure brought to prevent software self-starting in escalation process.After forbidding start self-starting software, start the copy work of upgrade image file, before copies data, bad block check processing is carried out to nonvolatile memory, when detection has bad block, be labeled as bad block, and select next good block for storage upgrade image file data.In first time copy procedure, be that upgrade image file data is copied to mirror image 2 district (see Fig. 2) from the user area of nonvolatile memory, cover the data in original mirror image 2 district; After having copied, the position started by retouching operation system is for start from mirror image 2 district.After mirror image 2 district restarting operating systems, recover start self-starting item, then mirror image 1 district (see Fig. 2) of upgrade image file data to nonvolatile memory in mirror image 2 district is copied, also Bad Block Management will be done equally before copy, after having copied, changed into the position of os starting and starting from mirror image 1 district, then exit the thread of whole upgrading, embedded system is from mirror image 1 district restarting operating systems.Restarting later operating system is specifically exactly new operating system after current upgrading, and the process of whole upgrading also just leaves it at that.
In addition, owing to being the process copied the data in nonvolatile memory subregion in upgrading operation system process, the application file that user can be caused to store in this process has the possibility damaged, for this problem, the means of following two aspects can be adopted to solve: one is treat protection application program to carry out the write-protected operation of file, is rewritten to prevent user file data; Another one be before OS upgrading first in the user area of nonvolatile memory by application file data backup to be protected in a fixing region, if application file is damaged, just the file copy of backup is out replaced.This addresses the problem the problem of the user application file corruption that may cause in escalation process.
Please again see Fig. 2, nonvolatile memory in the present embodiment divides multiple subregion, the wherein boot mirror image of boot district (or title boot section) mainly deposit operation system startup, mirror image 1 district and mirror image 2 district are all the regions of the kernel mirror image of deposit operation system, mirror image 2 district is normally as the backup area of kernel mirror image, when the kernel mirror image only started in mirror image 1 district goes wrong, system can be switched to and such as automatically switch to mirror image 2 district and start; The stability of os starting can be ensured like this.The file system of user area mainly operating system is used for depositing user file, and when practical application, the software associated documents of application program all can exist this region.In addition, the nonvolatile memory of the present embodiment can be NAND flash memory, or other have the storer of non-volatile nature.
Refer to Fig. 3, it is the high-level schematic functional block diagram of the device for upgrading firmware of a kind of embedded system of the embodiment of the present invention.As shown in Figure 3, the device for upgrading firmware 10 of the present embodiment is applied in the embedded system comprising nonvolatile memory 30, be understandable that, this embedded system also can comprise flush bonding processor, such as arm processor etc., and device for upgrading firmware 10 can be realized by the software being executed in flush bonding processor.
In figure 3, device for upgrading firmware 10 comprises data reception module 11, Bad Block Management module 13 and upgrading driver module 15.Wherein,
Data reception module 11 is for obtaining and storing upgrade image file to one first subregion (shown in Fig. 2 user area) of the nonvolatile memory 30 of embedded system and the store path information generating described upgrade image file.
Bad Block Management module 13 is carried out bad block detection for one second subregion (district of mirror image 2 shown in Fig. 2) to nonvolatile memory 30 and one the 3rd subregion (district of mirror image 1 shown in Fig. 2) and determine a good block respectively in described second subregion and described 3rd subregion.For the nonvolatile memory of embedded system for NAND flash memory (Flash), generally speaking, NAND flash memory produces bad block than being easier in escalation process, therefore before the process copied files of bottom upgrading, add a Bad Block Management module 13, effectively can prevent the problem of copied files failure like this.The concrete function of Bad Block Management module 13 is exactly before upgrade image file starts copy, first whether the subregion detected in NAND flash memory has bad block, if there is bad block, just be labeled as bad block, follow-uply not re-use, file storage data can continue to find next good block and store, and doing so avoids the problem of the upgrade image file data damage that bad block brings.
Upgrading driver module 15 for according to the store path information of described upgrade image file from described first subregion copy described upgrade image file to the described good block of described second subregion and the position that starts of retouching operation system for starting from described second subregion, make described embedded system from copy after described second partition Reboot operation system described upgrade image file to the described good block of described 3rd subregion and the position that starts of retouching operation system for starting from described 3rd subregion, and make described embedded system from described 3rd partition Reboot operation system.
The firmware upgrade that above-mentioned modules 11,13 and 15 realizes jointly or title OS escalation process with reference to aforesaid firmware upgrade method, can not repeat them here.
In addition, it is worth mentioning that, the driving design scheme of the embedded OS upgrading of the above embodiment of the present invention is applicable to Wince, Linux, iOS, Android etc.; Aforementioned mention also can make into from mirror image 2 (the second subregion) district copy upgrade image file to the process being mirrored to 1st district (the 3rd subregion): after system starts from mirror image 2 district, copy upgrade image file to mirror image 1 district from user area (the first subregion), so just can prevent the error in data phenomenon that the upgrade image file data copying mirror image 2 district after mirror image 2 district starts in system operation may occur to mirror image 1 district.
In sum, the above embodiment of the present invention can bring following one or more beneficial effect: (i) effectively solves operating system update process, nonvolatile memory such as NAND flash memory produces the upgrading failure that bad block brings, and finally causes the catastrophic problem that system is died; (ii) problem that the routing information effectively solving escalation process kernel mirror image file is lost; (iii) problem that in operating system update process, stability is not high is solved; And (iv) solves the problem of the user file damage brought in escalation process.
Apply specific case herein to set forth the firmware upgrade method of embedded system of the present invention and the principle of device for upgrading firmware and embodiment, the explanation of above embodiment just understands method of the present invention and core concept thereof for helping; Meanwhile, for one of ordinary skill in the art, according to thought of the present invention; all will change in specific embodiments and applications; in sum, this description should not be construed as limitation of the present invention, and protection scope of the present invention should be as the criterion with appended claim.
Claims (10)
1. a firmware upgrade method for embedded system, described embedded system comprises nonvolatile memory; It is characterized in that, described firmware upgrade method comprises step:
A () obtains and stores upgrade image file to one first subregion of the described nonvolatile memory of described embedded system and the store path information generating described upgrade image file;
B () one second subregion to described nonvolatile memory carries out bad block detection and in described second subregion, determines a good block;
C () copies described upgrade image file to the described good block of described second subregion and the position of retouching operation system startup according to described store path information from described first subregion is start from described second subregion;
D () in described embedded system, carries out bad block detection to one the 3rd subregion of described nonvolatile memory and determine a good block in described 3rd subregion after described second partition Reboot operation system;
(e) copy described upgrade image file to the described good block of described 3rd subregion and the position that starts of retouching operation system for starting from described 3rd subregion;
F () makes described embedded system from described 3rd partition Reboot operation system.
2. firmware upgrade method as claimed in claim 1, it is characterized in that, described step (a) comprising:
One application program of described embedded system receives the described upgrade image file of host computer transmission and is stored to described first subregion;
The described store path information of described upgrade image file is sent to bottom upgrading driver by described application program; And
After the described store path information of transmission, the thread of described application program is made to be in blocked state.
3. firmware upgrade method as claimed in claim 1, it is characterized in that, described step (a) comprising:
One application program of described embedded system receives the described upgrade image file of host computer transmission and is stored to described first subregion;
The described store path information of described upgrade image file is sent to bottom upgrading driver by described application program; And
Described bottom upgrading driver is preserved described store path information and is created bottom upgrading thread and return the thread of a thread creation Success Flag for the described application program of end creating successfully.
4. firmware upgrade method as claimed in claim 1, is characterized in that, before described step (c), also comprise step:
File write-protect operation is carried out to the application program to be protected in described embedded system, is rewritten to prevent application file data.
5. firmware upgrade method as claimed in claim 1, is characterized in that, before described step (c), also comprise step:
By the fixed area of the application file backup to be protected of described embedded system at described first subregion.
6. firmware upgrade method as claimed in claim 1, it is characterized in that, described step (e) comprising:
The described good block of described upgrade image file to described 3rd subregion is copied from described first subregion; Or
The described good block of described upgrade image file to described 3rd subregion is copied from described second subregion.
7. the firmware upgrade method as described in claim 1 to 6 any one, is characterized in that, described nonvolatile memory has also divided one the 4th subregion; Described 4th subregion is that boot section is using the storage area of the boot mirror image as os starting, described 3rd subregion is that the first MIRROR SITE is using the main storage area of the kernel mirror image as operating system, described second subregion be the second MIRROR SITE using the backup area of the kernel mirror image as operating system, described first subregion is user area.
8. firmware upgrade method as claimed in claim 7, it is characterized in that, described nonvolatile memory is NAND flash memory.
9. a device for upgrading firmware for embedded system, described embedded system comprises nonvolatile memory; It is characterized in that, described device for upgrading firmware comprises:
Data reception module, for obtaining and storing upgrade image file to one first subregion of the described nonvolatile memory of described embedded system and the store path information generating described upgrade image file;
Bad Block Management module, for carrying out bad block detection to one second subregion of described nonvolatile memory and one the 3rd subregion and determine a good block respectively in described second subregion and described 3rd subregion;
Upgrading driver module, for according to the described store path information of described upgrade image file from described first subregion copy described upgrade image file to the described good block of described second subregion and the position that starts of retouching operation system for starting from described second subregion, make described embedded system from copy after described second partition Reboot operation system described upgrade image file to the described good block of described 3rd subregion and the position that starts of retouching operation system for starting from described 3rd subregion, and make described embedded system from described 3rd partition Reboot operation system.
10. device for upgrading firmware as claimed in claim 9, it is characterized in that, described nonvolatile memory is NAND flash memory, and described nonvolatile memory has also divided one the 4th subregion; Described 4th subregion is that boot section is using the storage area of the boot mirror image as os starting, described 3rd subregion is that the first MIRROR SITE is using the main storage area of the kernel mirror image as operating system, described second subregion be the second MIRROR SITE using the backup area of the kernel mirror image as operating system, described first subregion is user area.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510074784.7A CN104572229B (en) | 2015-02-12 | 2015-02-12 | The firmware upgrade method and device for upgrading firmware of embedded system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510074784.7A CN104572229B (en) | 2015-02-12 | 2015-02-12 | The firmware upgrade method and device for upgrading firmware of embedded system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104572229A true CN104572229A (en) | 2015-04-29 |
| CN104572229B CN104572229B (en) | 2018-07-20 |
Family
ID=53088387
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510074784.7A Active CN104572229B (en) | 2015-02-12 | 2015-02-12 | The firmware upgrade method and device for upgrading firmware of embedded system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104572229B (en) |
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105225696A (en) * | 2015-10-15 | 2016-01-06 | 广东九联科技股份有限公司 | A kind of bad block detection method of Set Top Box nandflash chip |
| CN105389187A (en) * | 2015-11-26 | 2016-03-09 | 普华基础软件股份有限公司 | System update method |
| CN105808292A (en) * | 2016-03-07 | 2016-07-27 | 西安诺瓦电子科技有限公司 | Firmware upgrade method of embedded terminal device |
| CN105912356A (en) * | 2016-03-31 | 2016-08-31 | 武汉光迅科技股份有限公司 | Optical module firmware program online upgrade method supporting version fallback |
| CN106020875A (en) * | 2016-05-16 | 2016-10-12 | 北京奇虎科技有限公司 | Firmware updating management method and device of embedded terminal |
| CN106874032A (en) * | 2017-01-04 | 2017-06-20 | 青岛海信宽带多媒体技术有限公司 | Method, device and optical module that optical module firmware is upgraded |
| CN106873990A (en) * | 2017-01-23 | 2017-06-20 | 北京空间飞行器总体设计部 | Multi partition bootstrap technique under embedded system RAM defective patterns |
| CN109240720A (en) * | 2018-08-23 | 2019-01-18 | 福州瑞芯微电子股份有限公司 | A kind of firmware upgrade method of Android system and a kind of storage equipment |
| CN109426511A (en) * | 2017-08-18 | 2019-03-05 | 西安诺瓦电子科技有限公司 | Soft core update method and system |
| CN111045709A (en) * | 2019-12-26 | 2020-04-21 | 联想(北京)有限公司 | Firmware upgrading method and firmware upgrading device |
| CN111083001A (en) * | 2018-10-18 | 2020-04-28 | 杭州海康威视数字技术股份有限公司 | Firmware abnormity detection method and device |
| CN111638890A (en) * | 2019-03-01 | 2020-09-08 | Abb瑞士股份有限公司 | Online firmware upgrade of nodes in a process control system |
| CN111857784A (en) * | 2019-04-24 | 2020-10-30 | 西安诺瓦电子科技有限公司 | Firmware upgrading method and firmware upgrading system |
| CN112130778A (en) * | 2020-09-14 | 2020-12-25 | 珠海奔图电子有限公司 | Image forming apparatus, control system and control method thereof |
| CN112416411A (en) * | 2019-08-23 | 2021-02-26 | 百度在线网络技术（北京）有限公司 | Upgrading method and device, equipment terminal, server and computer readable medium |
| CN113485947A (en) * | 2021-06-15 | 2021-10-08 | 翱捷科技股份有限公司 | Automatic division method and device for storage domain of embedded system |
| CN113626060A (en) * | 2021-08-06 | 2021-11-09 | 天津津航计算技术研究所 | Online upgrade method based on separated storage under vxworks system |
| CN115328563A (en) * | 2022-10-09 | 2022-11-11 | 荣耀终端有限公司 | System starting method and electronic equipment |
| CN116501357A (en) * | 2023-06-28 | 2023-07-28 | 广东高斯宝电气技术有限公司 | Online upgrade method of singlechip |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101216772A (en) * | 2008-01-15 | 2008-07-09 | 中兴通讯股份有限公司 | Embedded equipment startup method and software upgrading method |
| CN103092662A (en) * | 2013-02-04 | 2013-05-08 | 烽火通信科技股份有限公司 | Software module upgrading method for terminal device based on embedded operating system |
| CN103678030A (en) * | 2012-09-04 | 2014-03-26 | 杭州海康威视数字技术股份有限公司 | Multi-system equipment start system and method thereof |
| CN104252369A (en) * | 2013-06-27 | 2014-12-31 | 上海博泰悦臻电子设备制造有限公司 | On-board equipment and dual-system backup method and device of on-board equipment |
-
2015
- 2015-02-12 CN CN201510074784.7A patent/CN104572229B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101216772A (en) * | 2008-01-15 | 2008-07-09 | 中兴通讯股份有限公司 | Embedded equipment startup method and software upgrading method |
| CN103678030A (en) * | 2012-09-04 | 2014-03-26 | 杭州海康威视数字技术股份有限公司 | Multi-system equipment start system and method thereof |
| CN103092662A (en) * | 2013-02-04 | 2013-05-08 | 烽火通信科技股份有限公司 | Software module upgrading method for terminal device based on embedded operating system |
| CN104252369A (en) * | 2013-06-27 | 2014-12-31 | 上海博泰悦臻电子设备制造有限公司 | On-board equipment and dual-system backup method and device of on-board equipment |
Cited By (27)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105225696A (en) * | 2015-10-15 | 2016-01-06 | 广东九联科技股份有限公司 | A kind of bad block detection method of Set Top Box nandflash chip |
| CN105389187A (en) * | 2015-11-26 | 2016-03-09 | 普华基础软件股份有限公司 | System update method |
| CN105389187B (en) * | 2015-11-26 | 2021-10-26 | 普华基础软件股份有限公司 | System updating method |
| CN105808292A (en) * | 2016-03-07 | 2016-07-27 | 西安诺瓦电子科技有限公司 | Firmware upgrade method of embedded terminal device |
| CN105912356B (en) * | 2016-03-31 | 2019-04-09 | 武汉光迅科技股份有限公司 | A kind of optical module firmware program on-line upgrading method for supporting version rollback |
| CN105912356A (en) * | 2016-03-31 | 2016-08-31 | 武汉光迅科技股份有限公司 | Optical module firmware program online upgrade method supporting version fallback |
| CN106020875A (en) * | 2016-05-16 | 2016-10-12 | 北京奇虎科技有限公司 | Firmware updating management method and device of embedded terminal |
| CN106874032A (en) * | 2017-01-04 | 2017-06-20 | 青岛海信宽带多媒体技术有限公司 | Method, device and optical module that optical module firmware is upgraded |
| CN106873990A (en) * | 2017-01-23 | 2017-06-20 | 北京空间飞行器总体设计部 | Multi partition bootstrap technique under embedded system RAM defective patterns |
| CN106873990B (en) * | 2017-01-23 | 2020-07-10 | 北京空间飞行器总体设计部 | Multi-partition guiding method under embedded system RAM damage mode |
| CN109426511B (en) * | 2017-08-18 | 2022-03-22 | 西安诺瓦星云科技股份有限公司 | Soft core updating method and system |
| CN109426511A (en) * | 2017-08-18 | 2019-03-05 | 西安诺瓦电子科技有限公司 | Soft core update method and system |
| CN109240720A (en) * | 2018-08-23 | 2019-01-18 | 福州瑞芯微电子股份有限公司 | A kind of firmware upgrade method of Android system and a kind of storage equipment |
| CN109240720B (en) * | 2018-08-23 | 2021-11-26 | 瑞芯微电子股份有限公司 | Firmware upgrading method of android system and storage device |
| CN111083001A (en) * | 2018-10-18 | 2020-04-28 | 杭州海康威视数字技术股份有限公司 | Firmware abnormity detection method and device |
| CN111638890A (en) * | 2019-03-01 | 2020-09-08 | Abb瑞士股份有限公司 | Online firmware upgrade of nodes in a process control system |
| CN111857784A (en) * | 2019-04-24 | 2020-10-30 | 西安诺瓦电子科技有限公司 | Firmware upgrading method and firmware upgrading system |
| CN112416411A (en) * | 2019-08-23 | 2021-02-26 | 百度在线网络技术（北京）有限公司 | Upgrading method and device, equipment terminal, server and computer readable medium |
| CN112416411B (en) * | 2019-08-23 | 2023-08-18 | 百度在线网络技术（北京）有限公司 | Upgrading method and device, equipment end, server and computer readable medium |
| CN111045709A (en) * | 2019-12-26 | 2020-04-21 | 联想(北京)有限公司 | Firmware upgrading method and firmware upgrading device |
| CN112130778A (en) * | 2020-09-14 | 2020-12-25 | 珠海奔图电子有限公司 | Image forming apparatus, control system and control method thereof |
| CN113485947A (en) * | 2021-06-15 | 2021-10-08 | 翱捷科技股份有限公司 | Automatic division method and device for storage domain of embedded system |
| CN113626060A (en) * | 2021-08-06 | 2021-11-09 | 天津津航计算技术研究所 | Online upgrade method based on separated storage under vxworks system |
| CN113626060B (en) * | 2021-08-06 | 2023-08-01 | 天津津航计算技术研究所 | Online upgrade method based on separate storage under vxworks system |
| CN115328563A (en) * | 2022-10-09 | 2022-11-11 | 荣耀终端有限公司 | System starting method and electronic equipment |
| CN115328563B (en) * | 2022-10-09 | 2023-04-14 | 荣耀终端有限公司 | System starting method and electronic equipment |
| CN116501357A (en) * | 2023-06-28 | 2023-07-28 | 广东高斯宝电气技术有限公司 | Online upgrade method of singlechip |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104572229B (en) | 2018-07-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104572229A (en) | Firmware upgrade method and firmware upgrade device for embedded system | |
| JP5113700B2 (en) | Firmware update apparatus and method | |
| US10067835B2 (en) | System reset | |
| US8429639B2 (en) | Image-based software update | |
| CN102270144B (en) | Embedded network equipment and method for upgrading firmware by using same | |
| CN103164342B (en) | Coordinate during the carry of availability of data | |
| CN106775610B (en) | Electronic equipment starting method and electronic equipment | |
| CN105808292A (en) | Firmware upgrade method of embedded terminal device | |
| CN103299276A (en) | Software updating process for an embedded device | |
| CN102141921A (en) | Method for upgrading system of terminal equipment and terminal equipment | |
| EP2329368B1 (en) | Updating content without using a mini operating system | |
| CN111651304B (en) | Software recovery method and device based on double-core intelligent ammeter and computer equipment | |
| CN111045712A (en) | Single system upgrading method and system with backup function | |
| CN113157303A (en) | Upgrading method, embedded system, terminal and computer storage medium | |
| US9910747B2 (en) | Parallel mirrored copying with write consistency | |
| US9619340B1 (en) | Disaster recovery on dissimilar hardware | |
| CN111913753A (en) | Method and system for changing starting mode in cloud migration of windows system | |
| CN116880877A (en) | Virtual machine enhancement tool upgrading method and device, computer equipment and storage medium | |
| US20100146188A1 (en) | Replicated file system for electronic devices | |
| CN115617488A (en) | Operating system migration method and device, computing equipment and storage medium | |
| CN111045709B (en) | Firmware upgrading method and firmware upgrading device | |
| KR102423056B1 (en) | Method and system for swapping booting disk | |
| CN117687663B (en) | OTA-based partition dynamic adjustment method, device, equipment and storage medium | |
| EP4113288B1 (en) | Systems and method for bootup activation of firmware images | |
| CN107656747B (en) | Data upgrading method and mobile terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: 710075 DEF101, Zero One Square, Xi'an Software Park, No. 72 Zhangbajie Science and Technology Second Road, Xi'an High-tech Zone, Shaanxi Province Patentee after: Xi'an Nova Nebula Technology Co., Ltd. Address before: 710075 Qinfengge D District 401, Xi'an Software Park, 68 Science and Technology Second Road, Xi'an High-tech Zone, Shaanxi Province Patentee before: Xian Novastar Electronic Technology Co., Ltd. |