CN117785238A - Firmware upgrade method, device, electronic equipment and computer-readable storage medium - Google Patents

Abstract

Embodiments of the present application provide a firmware upgrade method, device, electronic equipment, and computer-readable storage medium, which belong to the technical field of firmware upgrade. The method includes: System A enters recovery mode. If the current uboot version of system A is lower than the latest uboot version, back up the current uboot version in the uboot partition of system B; upgrade the uboot partition of system A according to the latest uboot version; If the upgrade of system A is abnormal, start system B, restore the uboot partition of system A based on the current uboot version backed up through system B, and restart system A. In this way, the number of upgrades of the uboot partition of system A can be reduced and the stability and reliability of OTA can be improved. When the uboot partition of system A is abnormally erased, system B can be restored and system A can be restarted to avoid system A becoming bricked. Improve the reliability of the A system upgrade process.

Description

Firmware upgrade method, device, electronic equipment and computer-readable storage medium

Technical field

The present application relates to the technical field of firmware upgrade, and in particular to a firmware upgrade method, device, electronic device and computer-readable storage medium.

Background technique

Currently, the OTA (Over The Air) upgrade solutions for existing systems on the market mainly include recovery mode and AB system mode. In recovery mode, power failure or other abnormalities are not allowed when upgrading the boot loader (uboot), otherwise the upgrade will fail and the system will freeze, and users will not be able to use it normally. In AB system mode, the system needs to occupy double the resource space, which is costly.

Contents of the invention

In order to solve the above technical problems, embodiments of the present application provide a firmware upgrade method, device, electronic device, and computer-readable storage medium.

In a first aspect, embodiments of the present application provide a firmware upgrade method, which method includes:

If system A needs to be upgraded, the latest OTA upgrade package is downloaded, and system A enters recovery mode. System A includes uboot partition and other partitions;

In the recovery mode, compare the latest uboot version of the latest OTA upgrade package with the current uboot version of the A system;

If the current uboot version is lower than the latest uboot version, back up the current uboot version in the uboot partition of system B;

Upgrading the uboot partition of the A system according to the latest uboot version;

If the A system upgrade is abnormal, start the B system, restore the uboot partition of the A system according to the backed up current uboot version through the B system, and restart the A system.

In one embodiment, the method further includes:

If the current uboot version is higher than or equal to the latest uboot version, the uboot partition of the A system will not be upgraded, and other partitions of the A system will be upgraded according to the latest OTA upgrade package.

In one embodiment, the method further includes:

If a power outage or an abnormal upgrade of the uboot partition of the system A is detected, it is determined that the upgrade of the system A is abnormal.

In one embodiment, the uboot partition upgrade abnormal event includes a uboot partition upgrade package verification exception and/or a uboot partition upgrade package writing exception.

In one embodiment, after restarting the A system, the method further includes:

Determine other partition upgrade packages in the latest OTA upgrade package except the uboot partition upgrade package;

Upgrade other partitions of system A according to the other partition upgrade package.

In one embodiment, if system A needs to be upgraded, before system A enters recovery mode, the method further includes:

Determine whether the system startup item is the A system;

If the system startup item is the A system, it is determined whether the A system needs to be upgraded according to the upgrade flag configuration file.

In one embodiment, after the uboot partition of system B backs up the current uboot version, the method further includes:

Set the system startup item to the B system.

In a second aspect, embodiments of the present application provide a firmware upgrade device. The firmware upgrade device includes:

The download module is used to download the latest OTA upgrade package if system A needs to be upgraded, and system A enters recovery mode. System A includes uboot partition and other partitions;

A comparison module, configured to compare the latest uboot version of the latest OTA upgrade package with the current uboot version of the A system in the recovery mode;

A backup module, used for backing up the current uboot version in the uboot partition of system B if the current uboot version is lower than the latest uboot version;

An upgrade module, used to upgrade the uboot partition of system A according to the latest uboot version;

A startup module is used to start the B system if the upgrade of the A system is abnormal, restore the uboot partition of the A system according to the backed up current uboot version through the B system, and restart the A system.

In a third aspect, embodiments of the present application provide an electronic device, including a memory and a processor. The memory is used to store a computer program. The computer program executes the firmware upgrade method provided in the first aspect when the processor is running. .

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium storing a computer program, which executes the firmware upgrade method provided in the first aspect when running on a processor.

The firmware upgrade method, device, electronic device and computer-readable storage medium provided by the present application are as follows: if system A needs to be upgraded, the latest OTA upgrade package is downloaded and system A enters recovery mode; the latest uboot version of the latest OTA upgrade package is compared with the current uboot version of system A; if the current uboot version is lower than the latest uboot version, the current uboot version is backed up in the uboot partition of system B; the uboot partition of system A is upgraded according to the latest uboot version; if the upgrade of system A is abnormal, system B is started, and the uboot partition of system A is restored by system B according to the backed-up current uboot version, and system A is restarted. In this way, the number of uboot partition upgrades of system A can be reduced, the stability and reliability of OTA can be improved, and when the uboot partition of system A is abnormally erased, system A can be restarted through system B to avoid the situation where system A becomes bricked, thereby improving the reliability of the upgrade process of system A.

Description of drawings

In order to explain the technical solutions of the present application more clearly, the drawings required to be used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present application and therefore should not be interpreted as It is regarded as limiting the protection scope of this application. In the various drawings, similar components are numbered similarly.

FIG1 shows a schematic diagram of a process of a firmware upgrade method provided in an embodiment of the present application;

Figure 2 shows another schematic flowchart of a firmware upgrade method provided by an embodiment of the present application;

FIG3 shows another schematic diagram of a firmware upgrade method according to an embodiment of the present application;

Figure 4 shows another schematic flowchart of the firmware upgrade method provided by an embodiment of the present application;

FIG5 shows a schematic diagram of the structure of a firmware upgrade device provided in an embodiment of the present application.

Icons: 500 - firmware upgrade device, 501 - download module, 502 - comparison module, 503 - backup module, 504 - upgrade module, 505 - start module.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, rather than all of the embodiments.

The components of the embodiments of the present application generally described and illustrated in the figures herein may be arranged and designed in a variety of different configurations. Accordingly, the following detailed description of the embodiments of the application provided in the appended drawings is not intended to limit the scope of the claimed application, but rather to represent selected embodiments of the application. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without any creative work shall fall within the scope of protection of this application.

Hereinafter, the terms "comprising", "having" and their cognates, which may be used in various embodiments of the present application, are only intended to represent specific features, numbers, steps, operations, elements, components or combinations of the foregoing. and should not be understood as first excluding the presence of one or more other features, numbers, steps, operations, elements, components or combinations of the foregoing or adding one or more features, numbers, steps, operations, elements, components or the possibility of a combination of the foregoing.

Furthermore, the terms “first”, “second”, “third”, etc. are merely used for distinguishing descriptions and are not to be understood as indicating or implying relative importance.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which various embodiments of this application belong. Said terms (such as terms defined in commonly used dictionaries) will be interpreted to have the same meaning as the contextual meaning in the relevant technical field and will not be interpreted as having an idealized meaning or an overly formal meaning, Unless otherwise expressly defined in the various embodiments of this application.

Example 1

The embodiment of this application provides a firmware upgrade method.

Referring to Figure 1, the firmware upgrade method includes steps S101-S105. Each step is described below.

Step S101, if system A needs to be upgraded, download the latest OTA upgrade package, and system A enters recovery mode. System A includes uboot partition and other partitions.

In this embodiment, whether system A needs to be upgraded can be determined based on the upgrade flag configuration file. The latest OTA upgrade package includes uboot partition upgrade package and other partition upgrade packages. The uboot partition of system A is set with the current uboot partition version, and other partitions of system A are also set with the current version.

Step S102: In the recovery mode, compare the latest uboot version of the latest OTA upgrade package with the current uboot version of the A system.

In this embodiment, it is determined whether the latest uboot version of the latest OTA upgrade package is higher than the current uboot version of system A. If the latest uboot version is higher than the current uboot version of system A, step S103 is performed. If the latest uboot version is lower than or equal to the current uboot version of system A, the uboot partition of system A will not be updated, which can reduce the number of uboot partition upgrades, reduce uboot partition loss, and improve upgrade efficiency.

Step S103: If the current uboot version is lower than the latest uboot version, back up the current uboot version in the uboot partition of system B.

It should be noted that the B system in this embodiment is the minimum system. In the B system, it is only responsible for restoring the uboot partition of the A system. Compared with the B system in the traditional solution, it occupies less memory space, saves resource space waste, and greatly improves the cost performance of the product. When it is necessary to upgrade, first back up the current uboot version of the uboot partition of the A system in the uboot partition of the B system, and then switch the system startup item to the B system next time, and reduce the upgrade times by judging the version number of the uboot partition. If the version number is higher than or equal to the uboot version number in the OTA package, it is not necessary to upgrade uboot, and only upgrade other partitions. When erasing the uboot partition of the A system, an abnormal situation occurs, and the system automatically restarts and switches to the B system to start, automatically restores the uboot partition of the A system through the B system, and then restarts again to enter the A system, which can greatly improve the reliability and stability of the upgrade.

In one embodiment, after the uboot partition of system B backs up the current uboot version, the method further includes:

Set the system startup item to the B system.

In this way, system B can be automatically started the next time the system is started.

Step S104: Upgrade the uboot partition of system A according to the latest uboot version.

In this embodiment, the uboot partition of the A system will be upgraded based on the latest uboot version only when the latest uboot version is higher than the current uboot version of the A system, thereby reducing the upgrade operation of the uboot partition of the A system, reducing the loss of the uboot partition and improving resource utilization.

Referring to Figure 2, the firmware upgrade method also includes steps S106-S107.

Step S106, determine other partition upgrade packages in the latest OTA upgrade package except the uboot partition upgrade package;

Step S107: Upgrade other partitions of system A according to the other partition upgrade package.

In this embodiment, after the uboot partition of system A is successfully upgraded, other partitions can be further upgraded, or the uboot partition of system A is upgraded and recognized, and system B restores the uboot partition of system A and restarts system A. Upgrade other partitions of system A according to the downloaded OTA upgrade package.

Step S105, if the upgrade of the A system is abnormal, start the B system, restore the uboot partition of the A system according to the backed up current uboot version through the B system, and restart the A system.

In this embodiment, system A is the running system, system B is the recovery system, and system B is the minimum system. Except for the uboot partition, there are no other partitions, which reduces resource occupation. During the OTA upgrade of system A, if the uboot upgrade fails or there is a power outage during the upgrade, system B can automatically restart and then run in system B. System B will restore the uboot of system A and then switch to system A again. This ensures the reliability and stability of the system. Since system B is only responsible for basic driver initialization and restoring uboot of system A, it can greatly reduce its occupation of system resources and solve the problem of erasing and writing uboot partition of system A. At this time, if an abnormality occurs, it is very likely to become bricked, so as to improve availability.

It should be added that in the traditional AB system model, the contents of system A and system B are not necessarily the same, but both systems are complete systems. When running for the first time (if it is version 1.0), on system A Run, if you need to upgrade to version 2.0, system B will be refreshed, and then run on system B the next time you start it. If you need to upgrade to version 3.0 next time, it will be updated to system A, and then restart on system A. run. Under abnormal conditions, if one of the systems A and B (such as system A) fails to run, it will automatically jump to another system (such as system B) to ensure the reliability of the system. The most obvious shortcoming of the existing AB system mode is that two complete systems need to be saved, which consumes high resources.

Compared with the existing upgrade using the recovery mode alone, the firmware upgrade solution provided by this embodiment that combines the recovery mode and the AB system has higher stability and reliability. Compared with the existing solution of using the AB system alone for upgrade, the firmware upgrade solution provided by this embodiment that combines the recovery mode and the AB system has a smaller resource usage and can greatly save costs.

In one implementation, the firmware upgrade method further includes:

If a power outage or an abnormal upgrade of the uboot partition of the system A is detected, it is determined that the upgrade of the system A is abnormal.

It should be added that the uboot partition upgrade abnormal event includes a uboot partition upgrade package verification exception and/or a uboot partition upgrade package writing exception.

In one implementation, the firmware upgrade method further includes:

If the current uboot version is higher than or equal to the latest uboot version, the uboot partition of the A system is not upgraded, and other partitions of the A system are upgraded according to the latest OTA upgrade package.

In this way, the number of upgrades can be reduced by judging the version number of the uboot partition. If the version number is higher than or equal to the uboot version number in the OTA package, there is no need to upgrade uboot. Only other partitions can be upgraded, which reduces the number of upgrades of the uboot partition and improves firmware upgrades. efficiency, improving the stability and reliability of firmware upgrades.

Referring to Figure 3, the firmware upgrade method also includes steps S108-S109.

Step S108, determine whether the system startup item is the A system;

Step S109: If the system startup item is the A system, determine whether the A system needs to be upgraded according to the upgrade flag configuration file.

In addition, it can also be determined whether the system startup item is the B system. If the system startup item is the B system, the B system is started, and the current uboot version of the A system's uboot partition is backed up through the B system.

The firmware upgrade method provided in this embodiment will be described below with reference to FIG. 4 .

Step S401: AB system is selected and the system is started.

Step S402, determining whether to start the B system.

In this step, if system B is started, step S403 is entered. If system B is started, system A is started, then step S405 is entered.

Step S403: Mount and restore the uboot partition of system A.

Step S404: Start system A and initialize it.

Step S405: Determine whether the system needs to be upgraded.

In this step, if system A needs to be upgraded, proceed to step S406; if system A does not need to be upgraded, proceed to step S4013.

Step S406: Download the latest OTA upgrade package.

Step S407, enter recovery mode.

Step S408: Obtain the latest uboot version from the OTA upgrade package.

Step S409: Determine whether the latest uboot version is lower than or equal to the current uboot version.

In this step, if the latest uboot version is higher than the current uboot version, step S4010 is entered. If the latest uboot version is lower than or equal to the current uboot version, step S4012 is entered.

Step S4010: Back up the uboot partition and set the next system startup to system B startup.

In this step, back up the current uboot partition version of system A in the uboot partition of system B.

Step S4011, upgrade the uboot partition and set the system to start as system A the next time it starts.

In this step, the uboot partition of system A is upgraded based on the latest uboot version.

Step S4012: Upgrade partitions other than the uboot partition.

After the uboot partition of system A is upgraded, upgrade other partitions of system A. If the upgrade of the uboot partition of system A fails, set the system startup item to system B, restore the uboot partition of system A through system B, and restart system A.

Step S4013: The upgrade is completed and the system enters the normal working state.

After the uboot partition of system A is upgraded, you only need to change the system startup item to system A startup, and no other additional operations are required. Before upgrading the uboot partition of system A, the system startup item will be set to system B startup. If the upgrade is abnormal, then when the system restarts again, it will enter system B startup and perform recovery of the uboot partition of system A, and then set the system startup item to system A startup. After the system restarts again, system A can start normally because the uboot partition has been restored.

The firmware upgrade method provided in this embodiment is as follows: if the A system needs to be upgraded, the latest OTA upgrade package is downloaded, and the A system enters the recovery mode, wherein the A system includes the uboot partition and other partitions; in the recovery mode, the latest uboot version of the latest OTA upgrade package is compared with the current uboot version of the A system; if the current uboot version is lower than the latest uboot version, the current uboot version is backed up in the uboot partition of the B system; the uboot partition of the A system is upgraded according to the latest uboot version; if the A system upgrade is abnormal, the B system is started, and the uboot partition of the A system is restored by the B system according to the backed-up current uboot version, and the A system is restarted. In this way, if the current uboot version is lower than the latest uboot version, the uboot partition of the A system is upgraded according to the latest uboot version, which can reduce the number of uboot partition upgrades of the A system, improve the stability and reliability of OTA, and the B system is the minimum system including the uboot partition, which saves resources to the greatest extent and greatly improves the cost performance of the product. When the uboot partition of the A system is abnormally erased, the B system is restored and the A system is restarted to avoid the bricking of the A system and improve the reliability of the A system upgrade process.

Example 2

In addition, an embodiment of the present application provides a firmware upgrade device.

As shown in Figure 5, the firmware upgrade device 500 includes:

The download module 501 is used to download the latest OTA upgrade package if the A system needs to be upgraded, and the A system enters the recovery mode. The A system includes the uboot partition and other partitions;

The comparison module 502 is used to compare the latest uboot version of the latest OTA upgrade package with the current uboot version of the A system in the recovery mode;

The backup module 503 is used to back up the current uboot version in the uboot partition of system B if the current uboot version is lower than the latest uboot version;

An upgrade module 504 is used to upgrade the uboot partition of the A system according to the latest uboot version;

The startup module 505 is used to start the B system if the upgrade of the A system is abnormal, restore the uboot partition of the A system according to the backed up current uboot version through the B system, and restart the A system.

In one implementation, the upgrade module 504 is also configured to not upgrade the uboot partition of system A if the current uboot version is higher than or equal to the latest uboot version, and update all uboot partitions according to the latest OTA upgrade package. Upgrade other partitions of system A mentioned above.

In one embodiment, the firmware upgrade device 500 includes:

A determination module, configured to determine an abnormality in the upgrade of system A if a power outage or an abnormal event in the uboot partition upgrade of system A is detected.

In one embodiment, the uboot partition upgrade abnormal event includes a uboot partition upgrade package verification exception and/or a uboot partition upgrade package writing exception.

In one embodiment, the upgrade module 504 is also configured to determine other partition upgrade packages in the latest OTA upgrade package except the uboot partition upgrade package after restarting the A system;

Upgrade other partitions of system A according to the other partition upgrade package.

In one embodiment, the firmware upgrade device 500 includes:

A judgment module, used to judge whether the system startup item is the A system;

If the system startup item is system A, it is determined according to the upgrade flag configuration file whether system A needs to be upgraded.

In one embodiment, the firmware upgrade device 500 includes:

A setting module is configured to set the system startup item to the system B after the uboot partition of the system B backs up the current uboot version.

The firmware upgrade device 500 provided in this embodiment can implement the firmware upgrade method provided in Embodiment 1, and will not be described again here to avoid repetition.

In the firmware upgrade device provided in this embodiment, if system A needs to be upgraded, the latest OTA upgrade package is downloaded, and system A enters the recovery mode. System A includes the uboot partition and other partitions; in the recovery mode, all Compare the latest uboot version of the latest OTA upgrade package with the current uboot version of the A system; if the current uboot version is lower than the latest uboot version, back up the current uboot version in the uboot partition of the B system ; Upgrade the uboot partition of the A system according to the latest uboot version; if the A system upgrade is abnormal, start the B system, and restore the A system according to the backed up current uboot version through the B system uboot partition, restart the A system. In this way, the current uboot version is lower than the latest uboot version, and upgrading the uboot partition of system A according to the latest uboot version can reduce the number of uboot partition upgrades of system A and improve the stability and reliability of OTA. System B is the smallest system including uboot partition, which saves resources to the greatest extent and greatly improves the product's cost performance. When the uboot partition of system A is abnormally erased, system B can be restored and system A can be restarted to prevent system A from becoming bricked and improve the reliability of the upgrade process of system A.

Example 3

In addition, an embodiment of the present application provides an electronic device, including a memory and a processor. The memory stores a computer program. When the computer program is run on the processor, the firmware upgrade method provided in Embodiment 1 is executed.

The electronic device provided in this embodiment can implement the firmware upgrade method provided in Embodiment 1, which will not be described again to avoid duplication.

Example 4

This application also provides a computer-readable storage medium. A computer program is stored on the computer-readable storage medium. When the computer program is executed by a processor, the firmware upgrade method provided in Embodiment 1 is implemented.

In this embodiment, the computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

The computer-readable storage medium provided in this embodiment can implement the firmware upgrade method provided in Embodiment 1, and will not be described again here to avoid repetition.

It should be noted that, as used herein, the terms "include", "comprises" or any other variation thereof are intended to cover a non-exclusive inclusion, such that a process, method, article or terminal that includes a series of elements not only includes those elements, It also includes other elements not expressly listed or inherent in such process, method, article or terminal. Without further limitation, an element defined by the statement "comprises a..." does not exclude the presence of other identical elements in the process, method, article, or terminal that includes the element.

Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.

The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above-mentioned specific implementations. The above-mentioned specific implementations are only illustrative and not restrictive. Those of ordinary skill in the art will Inspired by this application, many forms can be made without departing from the purpose of this application and the scope protected by the claims, all of which fall within the protection of this application.

Claims (10)

1. A method of firmware upgrade, the method comprising:

if the A system needs to be upgraded, downloading a latest OTA upgrade package, wherein the A system enters a recovery mode and comprises a uboot partition and other partitions;

in the recovery mode, comparing the latest uboot version of the latest OTA upgrade package with the current uboot version of the A system;

if the current uboot version is lower than the latest uboot version, backing up the current uboot version in a uboot partition of a B system;

upgrading the uboot partition of the A system according to the latest uboot version;

if the upgrading of the A system is abnormal, starting the B system, recovering the uboot partition of the A system according to the current backup uboot version through the B system, and restarting the A system.

2. The method according to claim 1, wherein the method further comprises:

if the current uboot version is higher than or equal to the latest uboot version, not upgrading the uboot partition of the A system, and upgrading other partitions of the A system according to the latest OTA upgrade package.

3. The method according to claim 1, wherein the method further comprises:

and if the power failure or the uboot partition upgrading abnormal event of the A system is detected, determining that the A system is abnormal in upgrading.

4. The method of claim 3, wherein the uboot partition upgrade exception event comprises a uboot partition upgrade package check exception and/or a uboot partition upgrade package write exception.

5. The method of claim 1, wherein after restarting the a-system, further comprising:

determining other partition upgrade packages except a uboot partition upgrade package in the latest OTA upgrade package;

and upgrading the other partitions of the A system according to the other partition upgrade packages.

6. The method of claim 1, wherein if the a-system needs to be upgraded, the method further comprises, before the a-system enters the recovery mode:

judging whether a system starting item is the A system or not;

if the system starting item is the A system, judging whether the A system needs to be upgraded according to the upgrade mark configuration file.

7. The method of claim 1, wherein after the backup of the current uboot version by a uboot partition of a B system, the method further comprises:

and setting a system start item as the B system.

8. A firmware upgrade apparatus, the apparatus comprising:

the downloading module is used for downloading the latest OTA upgrade package if the A system needs to be upgraded, wherein the A system enters a recovery mode and comprises a uboot partition and other partitions;

the comparison module is used for comparing the latest uboot version of the latest OTA upgrade package with the current uboot version of the A system in the recovery mode;

the backup module is used for backing up the current uboot version in a uboot partition of the B system if the current uboot version is lower than the latest uboot version;

the upgrading module is used for upgrading the uboot partition of the A system according to the latest uboot version;

and the starting module is used for starting the B system if the upgrading of the A system is abnormal, recovering the uboot partition of the A system according to the current backup uboot version by the B system, and restarting the A system.

9. An electronic device comprising a memory and a processor, the memory storing a computer program that, when executed by the processor, performs the firmware upgrade method of any one of claims 1-7.

10. A computer readable storage medium, characterized in that it stores a computer program which, when run on a processor, performs the firmware upgrade method of any one of claims 1 to 7.