CN1581101A - Embedded system upgrading method - Google Patents
Embedded system upgrading method Download PDFInfo
- Publication number
- CN1581101A CN1581101A CN 03153386 CN03153386A CN1581101A CN 1581101 A CN1581101 A CN 1581101A CN 03153386 CN03153386 CN 03153386 CN 03153386 A CN03153386 A CN 03153386A CN 1581101 A CN1581101 A CN 1581101A
- Authority
- CN
- China
- Prior art keywords
- upgrading
- upgrade
- nonvolatile memory
- upgraded
- data
- 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
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The present invention provides an embedded system upgrading method. Said method includes the following steps: making the nonvolatile memory be divided into logic zone, duplicating original data to be upgraded on the non-volatile memory into the designated zone of the non-volatile memory, then making some portion of said non-volatile memory undergo the process of upgrading operation, under the condition of that if said system produces sudder interruption can make the data in the designated zone of the non-volatile memory be restored to original correspondent position, then can restart or automatically again make upgrade, so that said invention can make the embedded system have a certain self-recovery function, and can implement flexible management in the upgrading process.
Description
Technical field
The present invention relates to the embedded system technology field, be meant a kind of method of embedded system upgrading especially.
Background technology
In embedded system, determined the operational mode of the non-open type of embedded system by the characteristics such as function of the running environment of system and product.In this case, embedded system is carried out auto-update not only make the product life-saving, and protected user's investment, promptly under the situation that does not increase new input, increased the new function of product or repaired the defective that existing product exists.So, for a product that contains embedded system, design good and powerful upgrading scheme and can bring stronger competitive power for this product.
The upgrading scheme of existing embedded system is generally makes image file with upgrade file, and with after original data are all wiped on the nonvolatile memory in the embedded system, again image file is write on the nonvolatile memory, to reach the purpose of refreshing and upgrading.
The defective of such scheme is: for being for the embedded system of permanent storage media with the nonvolatile memory, in the escalation process in case when meeting accident abnormal conditions such as outage, it is unavailable that system will become, after can only using this moment special equipment that the nonvolatile memory of this system is carried out complete refreshing, just can make this system continue to use.This scheme is dangerously the work of recovery system again to be become waste time and energy, even can't realize the recovery of system under certain conditions at all.And above-mentioned upgrading scheme must be to whole refreshing and upgradings that carry out of nonvolatile memory, and can not carry out the refreshing and upgrading operation to the data of the some or several sections of appointment in the nonvolatile memory, are not easy to management.
Summary of the invention
In view of this, the object of the present invention is to provide a kind of method of embedded system upgrading, even system's unexpected interruption in escalation process also can start this system very easily once more.
For achieving the above object, technical scheme of the present invention is achieved in that
A kind of method of embedded system upgrading, this method may further comprise the steps:
A, be dividing logic regions on the nonvolatile memory of embedded system, and specify the partial data to be upgraded before a zone is used to preserve updating operation;
B, when this system need upgrade, download required upgrade file, and with after original part to be upgraded copies to the appointed area of nonvolatile memory on the nonvolatile memory, use institute's data downloaded file this part to be upgraded carried out updating operation;
C, when this system starts next time, judge the whether normal termination of escalation process last time, if then normally start this embedded system, otherwise after the appointed area data that copy to nonvolatile memory before will upgrading last time return to original position, start this embedded system.
Preferably, the described logic region of step a comprises: start-up code district, operating system district, file system area, the fault-tolerant district and the system upgrade process logo area that are used to preserve the preceding partial data to be upgraded of updating operation.
Preferably, comprise upgrading successfully indicate, upgrade Notation Of Content and upgrade data length parameter in the described system upgrade process logo area at least.
Preferably, described step b further comprises: application institute data downloaded file judges whether also have the zone to need upgrading in the nonvolatile memory logic region after this part upgrading to be upgraded is finished again, if, repeated execution of steps b then, otherwise, this embedded system normally started.
Preferably, described step b further comprises: embedded system bootstrap program is connected with upgrade server by outside connected mode, and whether needs are upgraded to judge this system according to the upgrading configuration of downloading from upgrade server.
Preferably, described outside connected mode comprises that network connects, and serial ports connects, the parallel port connects and is connected with USB.
Preferably, described step b further comprises:
After original part to be upgraded copies to the appointed area of nonvolatile memory on the nonvolatile memory, the upgrading in the system upgrade process logo area successfully indicated be not changed to not;
After updating operation finishes, the upgrading in the system upgrade process logo area is successfully indicated to be changed to successfully again;
Whether normal termination is successfully to indicate according to the upgrading in the system upgrade process logo area to judge to step c described last time of escalation process.
Preferably, described step c is: if last time, escalation process was non-normal termination, this system is connected with upgrade server once more, and judge whether successful connection, if, then carry out updating operation, otherwise, after the appointed area data that copy to nonvolatile memory before will upgrading last time return to original position, start this embedded system.
Preferably, described step c further comprises: after the appointed area data that copy to nonvolatile memory before will upgrading last time return to original position, re-execute updating operation.
Preferably, described step b further comprises: after original part to be upgraded copies to the appointed area of nonvolatile memory on the nonvolatile memory, according to the content and the big or small upgrading Notation Of Content and the upgrade data length parameter that is provided with in the system upgrade process logo area of institute's copy data; Described step c is according to the upgrading Notation Of Content in the system upgrade process logo area, obtain to upgrade last time and carry out the object of updating operation before the improper end at last, according to the upgrade data length parameter in the system upgrade process logo area, obtain to upgrade last time carry out the data length of updating operation at last before the improper end after, the data of the respective length of duplicating from the appointed area of nonvolatile memory are written to original position again.
Preferably, the upgrading in the described system upgrade process logo area successfully is masked as a shared zone bit of different logic regions to be upgraded in the nonvolatile memory, or different logic region to be upgraded is used different zone bits respectively.
Preferably, original part to be upgraded is the partial data of the total data or the part to be upgraded of part to be upgraded on the described nonvolatile memory.
Use the present invention, by being the nonvolatile memory dividing logic regions, and with after original data to be upgraded copy to the appointed area of nonvolatile memory on the nonvolatile memory, again certain part of this nonvolatile memory is carried out updating operation, even the situation of accidental interruption appears in the system of making in escalation process, after also the data of nonvolatile memory appointed area being returned to original relevant position, start this system very easily once more.Therefore, the invention enables embedded system to occur having certain self-repairing capability under the situation of accidental interruption at escalation process, the system that promptly can guarantee normally starts once more or upgrades again automatically.Simultaneously, upgraded in the subregion of nonvolatile memory, therefore, realized flexible management escalation process owing to use the present invention.Use the present invention, do not need to increase any control hardware, also do not rely on specific operating system, for requiring system high-available and existing application that a kind of low price reliable solution is provided again to the system upgrade demand.
Description of drawings
Fig. 1 of the present inventionly carries out synoptic diagram after the logical partitioning to nonvolatile memory for using;
Fig. 2 is the process flow diagram of upgrade method one preferred embodiment of the present invention.
Embodiment
For making purpose of the present invention, technical scheme and advantage clearer, below with reference to the accompanying drawing embodiment that develops simultaneously, the present invention is described in further details.
Thinking of the present invention is: be dividing logic regions on the nonvolatile memory of embedded system, and specify a zone to be used to preserve the preceding partial data to be upgraded of updating operation; When this system need upgrade, download required upgrade file, and after part to be upgraded being copied to the appointed area of nonvolatile memory, use institute's data downloaded file this part to be upgraded is carried out updating operation; When this system starts next time, judge the whether normal termination of escalation process last time, if, then normally start this embedded system, the situation such as outage if system met accident in the escalation process in last time and cause escalation process to interrupt, after the appointed area data that copy to nonvolatile memory before then will upgrading last time return to original position, start this embedded system.Like this, guarantee that embedded system is always available.
Figure 1 shows that to use and of the present invention nonvolatile memory is carried out synoptic diagram after the logical partitioning.Because generally, the nonvolatile memory of system can be all not occupied, always leaves some remaining spaces, therefore, the space of remainder is used for fault-tolerant district and system upgrade process logo area.Like this, the nonvolatile memory with system logically is divided into start-up code district 101, operating system district 102, file system area 103, fault- tolerant district 104 and 105 5 zones of system upgrade process logo area.Wherein, start-up code district 101 preserves basic initialization and the guidance code that is used for system start-up, be the bootloader on the ordinary meaning, because the major function of bootloader is to realize the basic initialization of hardware system and the loading of operating system, therefore, under any circumstance all available for the assurance system, do not allow the operation that bootlaoder is write with a brush dipped in Chinese ink again; Operating system district 102 preserves the kernel code of this embedded OS; File system area 103 is preserved the file system of this embedded system; Fault-tolerant district 104 is used for the partial data to be upgraded before the saved system upgrading, used data when promptly being used for System Fault Tolerance and recovering, to prevent because the escalation process accidental interruption, and the situation that causes system can't normally start next time; System upgrade process logo area 105 is used for the state of saved system escalation process, and it comprises upgrading successfully indicate, upgrade Notation Of Content, upgrade data length parameter and manufacturer's sign or the like.The size in each zone is carried out different divisions according to different realization systems.
Figure 2 shows that the process flow diagram of upgrade method one preferred embodiment of the present invention.By revising the flow process of bootlaoder, made Implementation of Embedded System and had an auto-update of fault tolerant mechanism.
Step 201, during system start-up, bootloader is connected with upgrade server by the connected mode of outside, and judges that this connects whether successful connection, if then execution in step 207, otherwise execution in step 202; Wherein, outside connected mode comprises that network connects, serial ports connects, the parallel port connects and is connected with USB etc., and bootloader will attempt respectively being connected with server by above outside connected mode according to predetermined order;
Step 202, the upgrading in the escalation process logo area of check system successfully indicates;
Step 203 successfully indicates the whether normal termination of escalation process of judging last time according to the upgrading in the system upgrade process logo area, if then execution in step 212, otherwise execution in step 204;
Step 204, can bootloader attempt once more and being connected with upgrade server, and judge whether successful connection, if then execution in step 207, otherwise execution in step 205;
Step 205, the upgrading Notation Of Content that bootloader reads in the escalation process logo area is determined to carry out the object of updating operation at last before improper end last time, and reads the data length that upgrade data length parameter in the escalation process logo area determines to carry out at last before the improper end last time updating operation;
Step 206, according to the data length of updating operation, from fault-tolerant district, duplicate the data of respective length, and after these data are returned to relevant position original in the nonvolatile memory, with the upgrading in the system upgrade process logo area successfully indicate be changed to successfully after, execution in step 212;
Step 207 is downloaded upgrading configuration from server, and whether needs are upgraded to judge this system according to the identification field in the upgrading configuration, if then execution in step 208, otherwise direct execution in step 212; This upgrading configuration is required to generate and be placed under definite catalogue by the upgrading of server updating supervisory routine according to the user, and form with agreement, bootloader is by analyzing this configuration file, obtain the user and wish the zone of upgrading, it is the operating system district, or file system area, or operating system district and file system area;
Step 208, bootlaoder is to server application down operation system region or the required upgrade file of file system area, download finish after, execution in step 209; The upgrade file in operating system district represented by different filenames respectively with the upgrade file of file system area, and filename specified by upgrading configuration, and can only download one type file at every turn;
Step 209 arrives fault-tolerant district according to the current file copy to be upgraded of the big young pathbreaker in fault-tolerant district, and in the upgrade data length parameter of length records in system upgrade process logo area with institute's copy data;
Step 210, upgrading in the system upgrade process logo area successfully indicated be not changed to not, and after the upgrading Notation Of Content in the system upgrade process logo area being labeled as the sign of current upgrading part soon, utilize the upgrade file of downloading to respective regions, be operating system district or file system area, upgrade;
Step 211 judges in the embedded system whether to also have other parts to need upgrading, if, then return step 208, otherwise with the upgrading in the system upgrade process logo area successfully indicate be changed to successfully after, execution in step 212;
Step 212 is carried out system initialization and load operation, normal start-up system.Upgrading in the such scheme in the system upgrade process logo area successfully indicates it can is the shared zone bit of operating system district and file system area, also can be that the operating system district uses different zone bits respectively with file system area.
Be example with an embedded Linux system below, specify implementation procedure of the present invention.
Suppose that the flash memory (flash) in this embedded Linux system is 4M, this flash is carried out the logic region division result is: bootloader is deposited in the start-up code district, and take the preceding 32K of flash, the operating system after the compression is deposited in the operating system district, and take thereafter 700K, file system area is deposited the file system after the compression, and take subsequently 1500K, escalation process logo area storage configuration sign, and take the last 32K of flash, be fault-tolerant district before the system upgrade logo area after the file system area, this fault-tolerant district size is 4000-32-700-1500-32, promptly is about 1700K.
During system start-up, bootlaoder is connected with server by network, and obtain the upgrading configuration that server end generates, this configuration file requires embedded Linux system with the os.bin file under the server end c dish operating system on the flash to be upgraded, and with the myfs.bin file in the filesystem catalogue under the server end c dish file system on the flash is upgraded.
Bootlaoder at first downloads the os.bin file by network, and flash is gone up the operating system data of having compressed in original operating system district copy in the fault-tolerant district on the flash, afterwards, in the upgrade data length parameter of length records in system upgrade process logo area with institute's copy data, upgrading in the system upgrade process logo area successfully indicated be not changed to not, upgrading Notation Of Content in the system upgrade process logo area is changed to 1 (supposes that 1 represents upgrading operation system, 2 represent the upgrade file system), with the os.bin file of having downloaded the operating system data in the operating system district on the flash are refreshed then.After the upgrading of operating system finished, the upgrading in the system upgrade process logo area successfully indicated be changed to successfully.At this moment, bootloader is again from downloaded myfs.bin file, and flash is gone up the file system data that has compressed in original file system area copy to fault-tolerant district on the flash, after covering the existing file in the fault-tolerant district, and in the upgrade data length parameter of length records in system upgrade process logo area with institute's copy data, upgrading in the system upgrade process logo area successfully indicated be not changed to not, upgrading Notation Of Content in the system upgrade process logo area is changed to 2, with the myfs.bin file of having downloaded the file system data in the file system area on the flash is refreshed then.
If fortuitous events such as system's power down have taken place in the process that file system is upgraded, and escalation process is interrupted, then after this embedded system re-powered, because bootloader does not damage, therefore, bootloader still can normally move.Its detailed process is as follows:
After this embedded Linux system re-powered, bootloader at first attempted being connected with upgrade server, if successful connection, then download configuration file and carry out updating operation according to its requirement again; Otherwise, upgrading in the bootlaoder check system escalation process logo area successfully indicates, if this is masked as success, then carry out normal system initialization and load operation, start this system, but accident power-off appearred when upgrading last time owing to this system, therefore the upgrading of system successfully indicates to be that at this moment, bootloader does not attempt being connected with upgrade server once more certainly, if successful connection, then download configuration file and carry out updating operation again according to its requirement; Otherwise, upgrading Notation Of Content in the bootlaoder check system escalation process logo area, because the updating operation when interrupting last time is at file system area, therefore, this is masked as 2, so upgrade data length parameter in the bootloader reading system escalation process logo area, obtain the preceding file system size of upgrading last time and be 1500K, bootloader duplicates the data of 1500K to cover the data the present file system area from fault-tolerant district then, and with the upgrading in the system upgrade process logo area successfully indicate be changed to successfully after, carry out normal system initialization and load operation, to start this system.This shows that even the situation that system meets accident and interrupts, system can start, and is available when upgrading.
The size in fault-tolerant district decides according to the size of the non-volatile memory medium of system and to taking all factors into consideration of security of system and cost.If system is higher to security requirement, then advise the non-volatile memory medium that the employing capacity is bigger, identical or big slightly with the operating system after the size that guarantees fault-tolerant district and the compression with the maximal value that file system was taken up space after the compression, the system after fault-tolerant recovery is normally started.If system is not high to security requirement, also can adopt the less non-volatile memory medium of capacity, to save cost.If the size in fault-tolerant district is littler than operating system after compressing and the maximal value that file system took up space after the compression, then when refreshing corresponding zone, it is much that fault-tolerant district has, and puts into fault-tolerant district with regard to the data of duplicating respective length.In this case, after the data in the fault-tolerant district were resumed back, the system that can not guarantee can enter serviceable condition.But because the bootloader of system is always available, even the disabled situation of data of going back recovered has taken place to make owing to fault-tolerant district is too little, system at least can by bootloader and upgrade server carry out once new escalation process alternately, system has been avoided because upgrading failure and must use special equipment to refresh the situation of this system.
The above only is preferred embodiment of the present invention, and is in order to restriction the present invention, within the spirit and principles in the present invention not all, any modification of being made, is equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (12)
1, a kind of method of embedded system upgrading is characterized in that this method may further comprise the steps:
A, be dividing logic regions on the nonvolatile memory of embedded system, and specify the partial data to be upgraded before a zone is used to preserve updating operation;
B, when this system need upgrade, download required upgrade file, and with after original part to be upgraded copies to the appointed area of nonvolatile memory on the nonvolatile memory, use institute's data downloaded file this part to be upgraded carried out updating operation;
C, when this system starts next time, judge the whether normal termination of escalation process last time, if then normally start this embedded system, otherwise after the appointed area data that copy to nonvolatile memory before will upgrading last time return to original position, start this embedded system.
2, method according to claim 1, it is characterized in that the described logic region of step a comprises: start-up code district, operating system district, file system area, the fault-tolerant district and the system upgrade process logo area that are used to preserve the preceding partial data to be upgraded of updating operation.
3, method according to claim 2 is characterized in that, comprises upgrading successfully indicate, upgrade Notation Of Content and upgrade data length parameter in the described system upgrade process logo area at least.
4, method according to claim 1, it is characterized in that, described step b further comprises: after application institute data downloaded file finishes to this part upgrading to be upgraded, judge whether also have the zone to need upgrading in the nonvolatile memory logic region again, if, repeated execution of steps b then, otherwise, this embedded system normally started.
5, according to claim 1 or 4 described methods, it is characterized in that, described step b further comprises: embedded system bootstrap program is connected with upgrade server by outside connected mode, and whether needs are upgraded to judge this system according to the upgrading configuration of downloading from upgrade server.
6, method according to claim 5 is characterized in that, described outside connected mode comprises that network connects, and serial ports connects, the parallel port connects and is connected with USB.
7, method according to claim 3 is characterized in that, described step b further comprises:
After original part to be upgraded copies to the appointed area of nonvolatile memory on the nonvolatile memory, the upgrading in the system upgrade process logo area successfully indicated be not changed to not;
After updating operation finishes, the upgrading in the system upgrade process logo area is successfully indicated to be changed to successfully again;
Whether normal termination is successfully to indicate according to the upgrading in the system upgrade process logo area to judge to step c described last time of escalation process.
8, method according to claim 5, it is characterized in that, described step c is: if last time, escalation process was non-normal termination, this system is connected with upgrade server once more, and judges whether successful connection, if, then carry out updating operation, otherwise, after the appointed area data that copy to nonvolatile memory before will upgrading last time return to original position, start this embedded system.
9, method according to claim 1 is characterized in that, described step c further comprises: after the appointed area data that copy to nonvolatile memory before will upgrading last time return to original position, re-execute updating operation.
10, method according to claim 3 is characterized in that,
Described step b further comprises: after original part to be upgraded copies to the appointed area of nonvolatile memory on the nonvolatile memory, according to the content and the big or small upgrading Notation Of Content and the upgrade data length parameter that is provided with in the system upgrade process logo area of institute's copy data;
Described step c is according to the upgrading Notation Of Content in the system upgrade process logo area, obtain to upgrade last time and carry out the object of updating operation before the improper end at last, according to the upgrade data length parameter in the system upgrade process logo area, obtain to upgrade last time carry out the data length of updating operation at last before the improper end after, the data of the respective length of duplicating from the appointed area of nonvolatile memory are written to original position again.
11, method according to claim 7, it is characterized in that, upgrading in the described system upgrade process logo area successfully is masked as a shared zone bit of different logic regions to be upgraded in the nonvolatile memory, or different logic region to be upgraded is used different zone bits respectively.
12, method according to claim 1 is characterized in that, original part to be upgraded is the partial data of the total data or the part to be upgraded of part to be upgraded on the described nonvolatile memory.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 03153386 CN1277214C (en) | 2003-08-12 | 2003-08-12 | Embedded system upgrading method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 03153386 CN1277214C (en) | 2003-08-12 | 2003-08-12 | Embedded system upgrading method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1581101A true CN1581101A (en) | 2005-02-16 |
| CN1277214C CN1277214C (en) | 2006-09-27 |
Family
ID=34580037
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 03153386 Expired - Lifetime CN1277214C (en) | 2003-08-12 | 2003-08-12 | Embedded system upgrading method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1277214C (en) |
Cited By (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100386725C (en) * | 2005-03-16 | 2008-05-07 | 华为技术有限公司 | Mobile station of updatable mobile state software and updating method |
| CN100463414C (en) * | 2006-12-25 | 2009-02-18 | 杭州华三通信技术有限公司 | A method and device for remote batch upgrade of the embedded device |
| CN101520734A (en) * | 2008-12-17 | 2009-09-02 | 康佳集团股份有限公司 | Method for upgrading data in flash memory, network TV and interactive set-top box thereof |
| CN101847111A (en) * | 2009-03-27 | 2010-09-29 | 富士通株式会社 | Terminal device, data providing system, data provide method and computer program |
| CN102270144A (en) * | 2010-06-04 | 2011-12-07 | 鸿富锦精密工业（深圳）有限公司 | Embedded network equipment and method for upgrading firmware by using same |
| CN102508684A (en) * | 2011-11-14 | 2012-06-20 | 宁波三星电气股份有限公司 | Method for downloading and updating programs of distribution transformer monitoring terminal |
| CN102508686A (en) * | 2011-11-30 | 2012-06-20 | 苏州希图视鼎微电子有限公司 | Method and system for realizing safe upgrading of system |
| CN102591683A (en) * | 2011-12-28 | 2012-07-18 | 睿成汇商科技有限公司 | Updating method and updating system for embedded operation system |
| CN102622280A (en) * | 2011-01-06 | 2012-08-01 | 苏州科达科技有限公司 | Control method and control device used for software version upgrade and based on dual file system |
| WO2012126360A1 (en) * | 2011-03-23 | 2012-09-27 | 惠州Tcl移动通信有限公司 | Method for recovering original software when mobile terminal has failed in software upgrade |
| CN102830984A (en) * | 2011-06-14 | 2012-12-19 | 联想(北京)有限公司 | Method for updating firmware, chip and communication terminal |
| CN103530139A (en) * | 2012-07-04 | 2014-01-22 | 中兴通讯股份有限公司 | Mobile terminal upgrading method, system and equipment |
| CN103995717A (en) * | 2014-05-07 | 2014-08-20 | 南京国电南自电网自动化有限公司 | Method for upgrading software in embedded device |
| CN104156279A (en) * | 2014-08-04 | 2014-11-19 | 上海斐讯数据通信技术有限公司 | Backup method for configuration data of router |
| CN104331312A (en) * | 2014-11-24 | 2015-02-04 | 东软熙康健康科技有限公司 | Firmware updating method and embedded device |
| CN104572352A (en) * | 2015-01-12 | 2015-04-29 | 福建升腾资讯有限公司 | POS terminal key data backup recovery method |
| CN104615385A (en) * | 2015-02-13 | 2015-05-13 | 福州瑞芯微电子有限公司 | Data interaction method |
| CN105404533A (en) * | 2015-11-09 | 2016-03-16 | 珠海格力电器股份有限公司 | Program upgrading method and device |
| CN105468393A (en) * | 2014-09-10 | 2016-04-06 | 启碁科技股份有限公司 | Module version upgrading method and terminal apparatus |
| CN106708586A (en) * | 2017-01-11 | 2017-05-24 | 湘潭大学 | Handheld instrument and method for automatic online updating of embedded system programs |
| CN106776128A (en) * | 2016-11-29 | 2017-05-31 | 邦彦技术股份有限公司 | Method for ensuring normal start of Linux operating system |
| CN113138791A (en) * | 2021-05-18 | 2021-07-20 | 拉扎斯网络科技（上海）有限公司 | Upgrade processing method and device based on embedded system and electronic equipment |
| CN114328344A (en) * | 2021-11-26 | 2022-04-12 | 上海航天科工电器研究院有限公司 | DSP application program online upgrading method based on serial port |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP5081076B2 (en) * | 2008-06-23 | 2012-11-21 | 株式会社リコー | Memory management apparatus, image forming apparatus, and memory management method |
-
2003
- 2003-08-12 CN CN 03153386 patent/CN1277214C/en not_active Expired - Lifetime
Cited By (37)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100386725C (en) * | 2005-03-16 | 2008-05-07 | 华为技术有限公司 | Mobile station of updatable mobile state software and updating method |
| CN100463414C (en) * | 2006-12-25 | 2009-02-18 | 杭州华三通信技术有限公司 | A method and device for remote batch upgrade of the embedded device |
| CN101520734A (en) * | 2008-12-17 | 2009-09-02 | 康佳集团股份有限公司 | Method for upgrading data in flash memory, network TV and interactive set-top box thereof |
| CN101847111A (en) * | 2009-03-27 | 2010-09-29 | 富士通株式会社 | Terminal device, data providing system, data provide method and computer program |
| CN101847111B (en) * | 2009-03-27 | 2012-11-21 | 富士通株式会社 | Terminal apparatus, data providing system, and data providing method |
| CN102270144A (en) * | 2010-06-04 | 2011-12-07 | 鸿富锦精密工业（深圳）有限公司 | Embedded network equipment and method for upgrading firmware by using same |
| CN102270144B (en) * | 2010-06-04 | 2014-12-10 | 鸿富锦精密工业（深圳）有限公司 | Embedded network equipment and method for upgrading firmware by using same |
| CN102622280B (en) * | 2011-01-06 | 2014-10-15 | 苏州科达科技股份有限公司 | Control method and control device used for software version upgrade and based on dual file system |
| CN102622280A (en) * | 2011-01-06 | 2012-08-01 | 苏州科达科技有限公司 | Control method and control device used for software version upgrade and based on dual file system |
| WO2012126360A1 (en) * | 2011-03-23 | 2012-09-27 | 惠州Tcl移动通信有限公司 | Method for recovering original software when mobile terminal has failed in software upgrade |
| CN102830984B (en) * | 2011-06-14 | 2016-07-06 | 联想(北京)有限公司 | Method, chip and the communication terminal that firmware updates |
| CN102830984A (en) * | 2011-06-14 | 2012-12-19 | 联想(北京)有限公司 | Method for updating firmware, chip and communication terminal |
| CN102508684A (en) * | 2011-11-14 | 2012-06-20 | 宁波三星电气股份有限公司 | Method for downloading and updating programs of distribution transformer monitoring terminal |
| CN102508686A (en) * | 2011-11-30 | 2012-06-20 | 苏州希图视鼎微电子有限公司 | Method and system for realizing safe upgrading of system |
| CN102591683A (en) * | 2011-12-28 | 2012-07-18 | 睿成汇商科技有限公司 | Updating method and updating system for embedded operation system |
| CN102591683B (en) * | 2011-12-28 | 2016-08-17 | 厦门锐谷通信设备有限公司 | The update method of a kind of embedded OS and system |
| CN103530139A (en) * | 2012-07-04 | 2014-01-22 | 中兴通讯股份有限公司 | Mobile terminal upgrading method, system and equipment |
| CN103530139B (en) * | 2012-07-04 | 2016-09-28 | 中兴通讯股份有限公司 | A kind of method of updating mobile terminal, system and equipment |
| CN103995717A (en) * | 2014-05-07 | 2014-08-20 | 南京国电南自电网自动化有限公司 | Method for upgrading software in embedded device |
| CN103995717B (en) * | 2014-05-07 | 2017-04-05 | 南京国电南自电网自动化有限公司 | A kind of method of embedded device software upgrading |
| CN104156279A (en) * | 2014-08-04 | 2014-11-19 | 上海斐讯数据通信技术有限公司 | Backup method for configuration data of router |
| CN104156279B (en) * | 2014-08-04 | 2018-10-12 | 上海斐讯数据通信技术有限公司 | A kind of backup method of router configuration data |
| CN105468393B (en) * | 2014-09-10 | 2019-06-14 | 启碁科技股份有限公司 | Module release upgrade method and terminal installation |
| CN105468393A (en) * | 2014-09-10 | 2016-04-06 | 启碁科技股份有限公司 | Module version upgrading method and terminal apparatus |
| CN104331312A (en) * | 2014-11-24 | 2015-02-04 | 东软熙康健康科技有限公司 | Firmware updating method and embedded device |
| CN104331312B (en) * | 2014-11-24 | 2018-04-27 | 东软熙康健康科技有限公司 | A kind of firmware upgrade method and embedded device |
| CN104572352A (en) * | 2015-01-12 | 2015-04-29 | 福建升腾资讯有限公司 | POS terminal key data backup recovery method |
| CN104572352B (en) * | 2015-01-12 | 2018-02-23 | 福建升腾资讯有限公司 | A kind of POS terminal critical data back-up restoring method |
| CN104615385B (en) * | 2015-02-13 | 2017-12-19 | 福州瑞芯微电子股份有限公司 | A kind of data interactive method |
| CN104615385A (en) * | 2015-02-13 | 2015-05-13 | 福州瑞芯微电子有限公司 | Data interaction method |
| CN105404533A (en) * | 2015-11-09 | 2016-03-16 | 珠海格力电器股份有限公司 | Program upgrading method and device |
| CN106776128A (en) * | 2016-11-29 | 2017-05-31 | 邦彦技术股份有限公司 | Method for ensuring normal start of Linux operating system |
| CN106776128B (en) * | 2016-11-29 | 2020-04-21 | 邦彦技术股份有限公司 | Method for ensuring normal start of Linux operating system |
| CN106708586A (en) * | 2017-01-11 | 2017-05-24 | 湘潭大学 | Handheld instrument and method for automatic online updating of embedded system programs |
| CN106708586B (en) * | 2017-01-11 | 2019-11-15 | 湘潭大学 | A kind of handheld instrument and method for the update of embedded system program automatic on-line |
| CN113138791A (en) * | 2021-05-18 | 2021-07-20 | 拉扎斯网络科技（上海）有限公司 | Upgrade processing method and device based on embedded system and electronic equipment |
| CN114328344A (en) * | 2021-11-26 | 2022-04-12 | 上海航天科工电器研究院有限公司 | DSP application program online upgrading method based on serial port |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1277214C (en) | 2006-09-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1277214C (en) | Embedded system upgrading method | |
| US8271833B2 (en) | Method, system and article of manufacture for system recovery | |
| US8051044B1 (en) | Method and system for continuous data protection | |
| EP3724764B1 (en) | Write-ahead style logging in a persistent memory device | |
| CN1205555C (en) | Hard disk data backup and restore method | |
| US6658435B1 (en) | Disk image backup/restore with data preparation phase | |
| EP1770513B1 (en) | Method and system for booting and automatically updating software, and recovering from update error | |
| US8108447B2 (en) | Systems and methods for garbage collection in deduplicated data systems | |
| KR100515890B1 (en) | Method of efficiently recovering database | |
| US8341386B2 (en) | Method for updating basic input/output system and method for repairing thereof | |
| US7702659B2 (en) | Robust, self-maintaining file system | |
| US20070055969A1 (en) | System and method for updating firmware | |
| US6513051B1 (en) | Method and system for backing up and restoring files stored in a single instance store | |
| KR101421364B1 (en) | Processing device and write method | |
| US6643753B2 (en) | Methods and systems for managing heap creation and allocation | |
| EP2329366B1 (en) | Performing a pre-update on a non volatile memory | |
| CN103299276A (en) | Software updating process for an embedded device | |
| CN101331444A (en) | Online storage volume shrink | |
| CN111625249A (en) | Automatic upgrading and rollback method and device for Internet of things equipment | |
| CN109086078A (en) | Android system upgrade method, device, server and mobile terminal | |
| CN113127263B (en) | Kernel crash recovery method, device, equipment and storage medium | |
| CN106547589A (en) | A kind of upgrade-system and upgrade method | |
| US20030237021A1 (en) | Automatic restoration of software applications in a mobile computing device | |
| EP2071463B1 (en) | Method for processing a file, storage medium and processing arrangement | |
| KR100575996B1 (en) | How to Upgrade Image Files to Run the System |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CX01 | Expiry of patent term | ||
| CX01 | Expiry of patent term |
Granted publication date: 20060927 |