CN116257265A - Firmware updating method and device of wearable device and wearable device - Google Patents

Firmware updating method and device of wearable device and wearable device Download PDF

Info

Publication number
CN116257265A
CN116257265A CN202211090901.5A CN202211090901A CN116257265A CN 116257265 A CN116257265 A CN 116257265A CN 202211090901 A CN202211090901 A CN 202211090901A CN 116257265 A CN116257265 A CN 116257265A
Authority
CN
China
Prior art keywords
firmware
wearable device
recovery
information
update
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202211090901.5A
Other languages
Chinese (zh)
Inventor
张巍巍
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Anhui Huami Information Technology Co Ltd
Original Assignee
Anhui Huami Information Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Anhui Huami Information Technology Co Ltd filed Critical Anhui Huami Information Technology Co Ltd
Priority to CN202211090901.5A priority Critical patent/CN116257265A/en
Publication of CN116257265A publication Critical patent/CN116257265A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1415—Saving, restoring, recovering or retrying at system level
    • G06F11/1433—Saving, restoring, recovering or retrying at system level during software upgrading
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files

Abstract

The disclosure provides a firmware updating method and device of a wearable device and the wearable device, wherein the method comprises the following steps: running a boot loader firmware; judging whether the wearable equipment needs firmware updating or not through the boot loading firmware; in response to determining that a firmware update is required, running a target recovery firmware; and updating at least one application firmware in the wearable device through the target recovery firmware. According to the method and the device for updating the firmware, the guide loading firmware is operated, and whether the firmware in the wearable device needs to be updated or not is judged through the guide loading firmware, so that the firmware in the wearable device is triggered to be updated, a user can be timely guided to update the firmware of the wearable device, frequent update guide starting of the user can be effectively avoided, stability and convenience of firmware update are effectively improved, and reliability of firmware update is improved.

Description

Firmware updating method and device of wearable device and wearable device
Technical Field
The disclosure relates to the technical field of wearable devices, and in particular relates to a firmware updating method and device of a wearable device and the wearable device.
Background
In recent years, the heat of the wearable device is continuously increased, the technology is more mature, and meanwhile, the maintenance and updating problems of the wearable device are also gradually concerned.
In the related art, when a firmware in a wearable device fails, the wearable device is usually required to be restarted, or a user is prompted to press a designated key for a long time when the wearable device is started, and a resource file in the wearable device is cleared to restore the firmware.
In these modes, the stability and convenience of firmware repair are insufficient, and the firmware cannot be effectively updated, so that the firmware repair reliability is poor.
Disclosure of Invention
The present disclosure aims to solve, at least to some extent, one of the technical problems in the related art.
Therefore, an object of the present disclosure is to provide a method, an apparatus, a wearable device, and a storage medium for updating firmware of a wearable device, which can timely guide a user to update the firmware of the wearable device, effectively avoid frequent update guide start by the user, effectively improve stability and convenience of firmware update, and improve reliability of firmware update.
The firmware updating method of the wearable device provided by the embodiment of the first aspect of the disclosure comprises the following steps: running a boot loader firmware; judging whether the wearable equipment needs firmware updating or not through the boot loading firmware; in response to determining that a firmware update is required, running a target recovery firmware; and updating at least one application firmware in the wearable device through the target recovery firmware.
According to the firmware updating method of the wearable device, which is provided by the embodiment of the first aspect of the disclosure, firmware is loaded by running a boot loader; judging whether the wearable equipment needs firmware updating or not through the boot loading firmware; in response to determining that a firmware update is required, running a target recovery firmware; at least one application firmware in the wearable device is updated through the target recovery firmware, and as the boot loader firmware is operated, whether the firmware in the wearable device needs to be updated or not is judged through the boot loader firmware, so that the firmware in the wearable device is triggered to be updated, a user can be timely guided to update the firmware of the wearable device, frequent update boot start of the user can be effectively avoided, stability and convenience of firmware update are effectively improved, and reliability of firmware update is improved.
A firmware updating apparatus of a wearable device provided by an embodiment of a second aspect of the present disclosure includes: at least one module for executing the flow and/or steps in the firmware update method of the wearable device proposed by the embodiment of the first aspect of the present disclosure.
The firmware updating apparatus of the wearable device provided by the embodiment of the second aspect of the present disclosure loads firmware by running a boot; judging whether the wearable equipment needs firmware updating or not through the boot loading firmware; in response to determining that a firmware update is required, running a target recovery firmware; at least one application firmware in the wearable device is updated through the target recovery firmware, and as the boot loader firmware is operated, whether the firmware in the wearable device needs to be updated or not is judged through the boot loader firmware, so that the firmware in the wearable device is triggered to be updated, a user can be timely guided to update the firmware of the wearable device, frequent update boot start of the user can be effectively avoided, stability and convenience of firmware update are effectively improved, and reliability of firmware update is improved.
According to a third aspect of the present disclosure, there is provided a wearable device comprising: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform a firmware update method of the wearable device of an embodiment of the first aspect of the present disclosure.
According to a fourth aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer instructions for causing the computer to perform a firmware update method of a wearable device of an embodiment of the first aspect of the present disclosure is presented.
According to a fifth aspect of the present disclosure, there is provided a computer program product comprising a computer program which, when executed by a processor, implements a firmware update method of a wearable device of an embodiment of the first aspect of the present disclosure.
Additional aspects and advantages of the disclosure will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the disclosure.
Drawings
The foregoing and/or additional aspects and advantages of the present disclosure will become apparent and readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings, in which:
Fig. 1 is a flowchart of a firmware update method of a wearable device according to an embodiment of the disclosure;
fig. 2 is a flowchart of a firmware update method of a wearable device according to another embodiment of the present disclosure;
FIG. 3 is a schematic diagram of a backup recovery mode triggering process according to another embodiment of the present disclosure;
FIG. 4 is a schematic diagram of a hint information according to another embodiment of the present disclosure;
fig. 5 is a flowchart of a firmware update method of a wearable device according to another embodiment of the present disclosure;
FIG. 6 is a schematic diagram of a target backup restoration firmware selection according to another embodiment of the present disclosure;
fig. 7 is a schematic structural diagram of a firmware updating apparatus of a wearable device according to an embodiment of the disclosure;
fig. 8 is a schematic structural diagram of a firmware updating apparatus of a wearable device according to another embodiment of the present disclosure;
fig. 9 illustrates a block diagram of an exemplary wearable device suitable for use in implementing embodiments of the present disclosure.
Detailed Description
Embodiments of the present disclosure are described in detail below, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to like or similar elements or elements having like or similar functions throughout. The embodiments described below by referring to the drawings are exemplary only for explaining the present disclosure and are not to be construed as limiting the present disclosure. On the contrary, the embodiments of the disclosure include all alternatives, modifications, and equivalents as may be included within the spirit and scope of the appended claims.
Fig. 1 is a flowchart of a firmware update method of a wearable device according to an embodiment of the disclosure.
It should be noted that, the execution body of the firmware updating method of the wearable device in this embodiment is a firmware updating apparatus of the wearable device, and the apparatus may be implemented in a software and/or hardware manner, and the apparatus may be configured in the wearable device, and the wearable device, for example, a smart watch, a smart bracelet, etc., which is not limited thereto.
The wearable device can be worn directly on the body or be integrated into a user's clothing or accessory. The wearable device is not only a hardware device, but also realizes corresponding functions through software support, data interaction and cloud interaction.
As shown in fig. 1, the firmware updating method of the wearable device includes:
s101: running boot-loader firmware.
The firmware used for performing boot update on the firmware in the wearable device may be referred to as boot loading firmware, and the boot loading firmware may be specifically, for example, boot loading firmware Bootloader firmware, where the Bootloader is executed before the kernel of the operating system is executed. The hardware device may be initialized and a memory space map may be created, thereby bringing the system's software and hardware environment to a suitable state to prepare the correct environment for invoking the operating system kernel, without limitation.
The method and the device have the advantages that the guide starting updating is realized based on the guide loading firmware, the frequent guide starting updating depending on a user can be effectively avoided, so that the convenience and the flexibility of updating are effectively improved, and the guide loading firmware and the firmware to be updated are mutually independent, so that the design complexity of the guide loading firmware can be effectively avoided, excessive transformation cost is avoided, and the effective balance of cost and effect is realized when the guide loading firmware is configured to realize the guide starting updating.
In some embodiments, the wearable device may be controlled to operate the boot loader based on a trigger of the external device or a related operation of the user, or a trigger condition of the wearable device to operate the boot loader may be preset, a current condition (for example, a scene condition where the wearable device is located or a condition of a content currently operated by the wearable device) is detected, and when the current condition is determined to meet the trigger condition, the wearable device is triggered to operate the boot loader, which is not limited.
Optionally, in the embodiment of the present disclosure, in response to the start or reset of the wearable device, the boot loader firmware is operated, and since the boot loader firmware is operated when the wearable device is started or reset, an error operation of the boot loader firmware can be effectively avoided, and stability of firmware update is improved.
In the embodiment of the disclosure, the step of executing the boot loader is triggered to be executed when the wearable device is detected to be about to perform a starting action or perform a resetting action.
That is, in the embodiment of the present disclosure, when the wearable device is started or reset, the boot loader firmware may be run to determine whether the firmware in the wearable device needs to be updated, so when the wearable device is monitored to be started or reset, it indicates that the configured firmware needs to be updated with a larger probability, at this time, the boot loader firmware may be triggered to run to trigger the subsequent step of guiding the firmware update in the wearable device, so that the time when the firmware in the wearable device needs to be updated can be determined in time, and the timeliness and effectiveness of the firmware update are ensured.
In the embodiment of the disclosure, the boot-loader firmware may be invoked and run based on the memory address of the boot-loader firmware in the wearable device to trigger the execution of the subsequent steps.
For example, the boot-loaded firmware may be invoked and executed by a processor of the wearable device, which may be a computing unit contained in the wearable device, such as a micro control unit (Micro Controller Unit, MCU) or the like, or may also be a central processor or the like, without limitation, based on a memory address of the boot-loaded firmware in the wearable device.
In the embodiment of the disclosure, the boot loader is executed, and then whether the wearable device needs to be updated with firmware is judged through the boot loader, which can be seen in the following embodiment.
S102: and judging whether the wearable equipment needs firmware updating or not through the boot loading firmware.
In the embodiment of the disclosure, whether the firmware in the wearable device needs to be updated or not can be determined by guiding and loading the firmware to determine whether the firmware in the wearable device needs to be updated, and the firmware updating mode can be backup recovery, online updating and the like, so that when the firmware in the wearable device needs to be updated, the firmware in the wearable device is updated, and the firmware in the wearable device is recovered to a normally-usable state, or the firmware version of the wearable device is updated and the like.
In some embodiments, an update mode may be configured for the wearable device, and when the wearable device runs the boot loader firmware, it is determined that the wearable device enters the update mode and needs to perform firmware update, where the update mode is one of the system modes of the wearable device, and the update mode may be, for example, a backup mode, a recovery mode, an upgrade mode, and so on, which is not limited.
In the embodiment of the disclosure, whether the wearable device has a condition of entering the update mode or not can be judged based on the boot loading firmware, and whether the firmware of the wearable device needs to be updated or not is further judged.
In the embodiment of the disclosure, whether the wearable device needs to be updated with firmware can be confirmed to the user through the prompt information, the user can confirm the prompt information through corresponding operations (such as key confirmation and the like), when the running of the boot loader firmware is detected, the user can be prompted to confirm to update the firmware through an interface interaction mode, and after the user confirms, the wearable device is confirmed to need to update the firmware, so that the method is not limited.
In some embodiments, it may be supported to determine whether the wearable device needs to perform firmware update based on the number of key presses, time, frequency, etc. of the user, or it may also be supported to determine whether the wearable device needs to perform firmware update based on the manner of user gesture, face recognition, etc., without limitation.
Of course, it may be implemented in any other possible manner to determine whether the wearable device needs to be updated by using the boot-loader firmware, for example, a status detection code is added in the boot-loader firmware, the boot-loader firmware is used to detect the current status of the wearable device, and a certain recognition determination algorithm is combined according to the current status to determine whether the wearable device needs to be updated, or the status detection firmware may be preconfigured, and the wearable device jumps from the boot-loader firmware to the corresponding status detection firmware, and uses the status detection firmware to determine whether the wearable device needs to be updated, and transmits the detection result to the boot-loader firmware, which is not limited.
S103: in response to determining that a firmware update is required, the target recovery firmware is run.
The firmware is used for carrying out backup recovery and backup update on the wearable equipment.
In the embodiment of the disclosure, the recovery firmware can be used for performing operations such as backup recovery and backup update, and in the wearable device, the recovery firmware can be multiple, and different recovery firmware can contain the same or different resource information, so that in the embodiment of the disclosure, the multiple recovery firmware can be supported to be set, the multiple recovery firmware realizes redundancy setting, and the problem that firmware update of the wearable device cannot be realized due to damage of a certain recovery firmware can be effectively avoided, which is not limited.
Wherein the firmware selected for firmware update from the plurality of recovery firmware may be referred to as a target recovery firmware.
In the embodiment of the disclosure, after the wearable device determines that firmware update is required, the target recovery firmware is selected from a plurality of recovery firmware, the target recovery firmware is loaded into the memory by using the processor, and the target recovery firmware is operated, or an identification code corresponding to the target recovery firmware may be set, after the wearable device is determined to enter the update mode, the identification code is determined, and the corresponding target recovery firmware is operated according to the identification code, which is not limited.
S104: and updating at least one application firmware in the wearable device through the target recovery firmware.
Among other things, the operating system and system applications in the wearable device may be referred to as application firmware.
In the embodiment of the disclosure, the target recovery firmware may be used to obtain resource information required by finer firmware, update at least one application firmware in the wearable device, or detect an application firmware whose version is not satisfactory, and update the application firmware whose version is not satisfactory through the target recovery firmware, which is not limited.
For example, the target recovery firmware may be used to read the upgrade package data from a designated location in the file system, and write the software firmware therein (that is, the upgrade package data and the software firmware may be used as resource information) to a code running device of the wearable device, for example, norflash (a non-volatile memory) to implement update processing on at least one application firmware in the wearable device, or may also be used to read the upgrade package data from a designated location in the file system, and write the resource file therein (that is, the upgrade package data and the resource file may be used as resource information) to a storage device of the wearable device, for example, nand (a computer flash memory device), emmc (an embedded memory) and the like, and then trigger operations such as reformatting the wearable device to implement update processing on at least one application firmware in the wearable device, which is not limited.
In this embodiment, firmware is loaded by running a boot; judging whether the wearable equipment needs firmware updating or not through the boot loading firmware; in response to determining that a firmware update is required, running a target recovery firmware; at least one application firmware in the wearable device is updated through the target recovery firmware, and as the boot loader firmware is operated, whether the firmware in the wearable device needs to be updated or not is judged through the boot loader firmware, so that the firmware in the wearable device is triggered to be updated, a user can be timely guided to update the firmware of the wearable device, frequent update boot start of the user can be effectively avoided, stability and convenience of firmware update are effectively improved, and reliability of firmware update is improved.
Fig. 2 is a flowchart of a firmware update method of a wearable device according to another embodiment of the disclosure.
As shown in fig. 2, the firmware updating method of the wearable device includes:
s201: running boot-loader firmware.
The description of S201 may be specifically referred to the above embodiments, and will not be repeated here.
S202: and acquiring at least one of starting information, state information and user operation information of the wearable device through the boot loader.
The starting information is information corresponding to the wearable device in the starting process, such as a starting reason of the wearable device, a starting time, and the like, and is not limited.
The state information is state information corresponding to the wearable device after being started, such as an update state, an error state, a charging state, and the like, which is not limited.
The user operation information is user operation corresponding to the wearable device in the starting process, such as long-pressing a starting key, or performing certain operation on a screen, and the like, which is not limited.
In the embodiment of the disclosure, after the boot loader is executed, at least one of start information, state information and user operation information of the wearable device may be obtained through the boot loader, so as to realize a subsequent judgment of whether the wearable device needs to be updated with firmware.
That is, the embodiments of the present disclosure support various factors such as preset startup information, state information, and user operation information, so as to determine the startup condition of the wearable device, thereby more conveniently determining the state of the wearable device at startup.
S203: judging whether the wearable device needs to be subjected to firmware update according to at least one of starting information, state information and user operation information of the wearable device.
In the embodiment of the disclosure, the condition information corresponding to the start information, the state information and the user operation information may be set respectively.
Optionally, in some embodiments, when at least one of the plurality of predetermined conditions is not met, and determining that the wearable device needs to be subjected to firmware updating, and determining that the wearable device does not need to be subjected to firmware updating when all the requirements are met.
Of course, any one of the start information, the state information, and the user operation information of the wearable device may also be selected as a factor for determining whether the wearable device needs to be updated with firmware, which is not limited.
Optionally, determining a start reason of the wearable device according to the start information of the wearable device, and determining whether the wearable device is in a charging connection state according to the state information of the wearable device in response to determining that the start reason indication of the wearable device does not belong to abnormal start; in response to the wearable device being in a charging connection state, determining that the wearable device needs to be subjected to firmware update according to user operation information, determining whether the wearable device is in the charging connection state according to state information of the wearable device due to the fact that the wearable device needs to be subjected to firmware update according to starting information of the wearable device, and determining that the wearable device needs to be subjected to firmware update according to the user operation information, the method can ensure that the wearable device needs to be subjected to firmware update stably and accurately, accurately judging the firmware update intention of a user, and effectively avoiding misoperation.
Wherein, the abnormal start may be, for example, cold start (restart of the wearable device by cutting off the power), or may be, for example, too long start time, generation of a programmatic error during the start, etc., which is not limited
The charging connection state is a connection state in which the wearable device is in wired charging or wireless charging, that is, in the charging connection state, the wearable device is performing a charging operation.
The user operation information is corresponding operation information of the user on the wearable device, such as triggering of a preset key, triggering duration, triggering of preset interaction of a screen, a fingerprint, a voice and the like, which is not limited.
The user operation information in the embodiment of the present disclosure may, for example, satisfy the duration threshold for the duration of the preset key, and of course, the user operation information may also be set as any other possible triggering manner, which is not limited.
In the embodiment of the disclosure, a combination of a plurality of conditions may be set to determine whether the wearable device needs to perform firmware update, that is, the start reason indication of the wearable device does not belong to abnormal start, and the wearable device is in a charging connection state, and when corresponding user operation information is detected, it is determined that the wearable device needs to perform firmware update.
The determining that the start reason indication of the wearable device does not belong to abnormal start may be based on a processor in the wearable device, and the determining that the start reason of the wearable device is not limited may be based on reading a reset reason by a specified register, for example, starting by turning on power, resetting by controlling a reset pin, resetting by a watchdog, or the like.
It can be understood that if the wearable device does not belong to abnormal starting, it is determined that the reason for restarting the wearable device is not due to the fact that the power supply is cut off or the power supply is stopped, then the larger probability is due to the reason of the firmware, then the charging connection state of the wearable device can be determined, when the wearable device is in the charging connection state, the process of carrying out backup recovery on the firmware can be determined to obtain more power resources, interruption of the backup recovery process is avoided, and user operation information obtained by detecting the wearable device is combined, so that false triggering of a user is effectively avoided, when the condition is combined, the firmware update of the wearable device is determined, the time for carrying out the firmware update of the wearable device can be accurately determined, the false triggering is effectively avoided while the accuracy of the determination is ensured, and the firmware update effect of the wearable device is improved.
In the embodiment of the disclosure, the user operation information may be set to trigger the preset key for a certain duration threshold, the duration threshold may be 1 second, or may also be set to any other possible duration threshold such as 3 seconds, 5 seconds, etc., which is not limited, and when the duration trigger time of the preset key meets the duration threshold, it may be determined that firmware update needs to be performed on the wearable device.
Of course, some embodiments of the present disclosure further support setting detection manners of various user operation information, such as recognition manners of face recognition, voice recognition, fingerprint recognition, and the like, or may also be, for example, connected to multiple devices, detect firmware update instructions sent by other devices, for example, connect a wearable device to a computer, and send the firmware update instructions to the wearable device by the computer, which is not limited.
For example, as shown in fig. 3, fig. 3 is a schematic diagram illustrating a backup recovery mode triggering procedure according to another embodiment of the disclosure, wherein,
in S301, a restart reason is acquired;
in S302, it is determined whether the restart cause is abnormal start, if so, S303 is executed, and if the part is abnormal start, S308 is executed;
In S303, a charging state of the wearable device is acquired;
in S304, it is determined whether the wearable device is being charged, if so, S305 is executed, and if not, S308 is executed;
in S305, detecting a key triggering condition of the wearable device;
in S306, it is determined whether the trigger duration of the preset key exceeds the duration threshold, if yes, S307 is executed, and if not, S308 is executed;
in S307, a backup operation is detected, and it is determined that firmware update is required for the wearable device;
in S308, no backup operation is detected, and it is determined that the wearable device does not need to perform firmware update.
In the embodiment of the disclosure, the abnormal start may be a non-cold start, when the target state is determined to be the non-cold start, the charging connection state corresponding to the wearable device is obtained, that is, whether the charging device is connected is detected, after the charging device is determined to be connected, user operation information is determined, a user operation key is detected, when the trigger duration reaches a duration threshold, the backup operation is determined to be detected, and it is determined that the wearable device needs to be subjected to firmware update, otherwise, it is determined that the backup operation is not detected, and it is determined that the wearable device does not need to be subjected to firmware update.
Alternatively, in other embodiments, the startup information, the state information, and the user operation information may be freely configured as firmware update conditions, for example, only the startup information and the user operation information may be used to determine whether the wearable device needs to be updated with firmware, or only the user operation information may be used to determine whether the wearable device needs to be updated with firmware, which is not limited.
S204: in response to determining that a firmware update is required, the target recovery firmware is run.
The description of S204 may be specifically referred to the above embodiments, and will not be repeated here.
S205: generating user prompt information through the target recovery firmware, wherein the user prompt information is used for prompting whether to agree to carry out firmware updating processing on the wearable equipment.
In embodiments of the present disclosure, after determining that a firmware update is required, a user prompt may be generated by the target recovery firmware. That is, after determining that the corresponding firmware update is to be performed on the wearable device, user prompt information may be generated to update the user according to the user prompt information.
The user prompt information in the embodiment of the disclosure may specifically be, for example, a prompt interface, or prompt voice, prompt message, etc. determined by the user, which is not limited.
S206: and in response to the target recovery firmware receiving a confirmation instruction for the prompt information, updating at least one application firmware by the target recovery firmware.
In the embodiment of the disclosure, a user may confirm the prompt information and generate a confirmation instruction, and after receiving the confirmation instruction for the prompt information, the target recovery firmware triggers to execute firmware update to update at least one application firmware.
In the embodiment of the disclosure, the prompt information may include guiding information to guide the user to make a corresponding operation so as to generate a confirmation instruction.
The embodiment of the disclosure supports setting various generation modes of confirmation instructions, such as setting a certain key rhythm, and a user triggers a key according to the preset key rhythm, or may also set other interaction modes for the wearable device, such as triggering a plurality of preset keys synchronously, or triggering keys according to a preset sequence, and the like, which is not limited.
For example, as shown in fig. 4, fig. 4 is a schematic diagram of prompt information provided by another embodiment of the present disclosure, where the wearable device may identify a user intention to determine whether to trigger firmware update based on the user intention, and may prompt the user to press a key for a long time to confirm to avoid misoperation of the user, in fig. 3, when the user presses the key until a progress bar in an interface of the wearable device is full, the user releases his hands and repeats again until after 3 times, it is determined that to trigger firmware update, and the number of times of key presses may be set according to actual needs, which is not limited.
S207: in response to determining that no firmware update is required, at least one application firmware is run.
In the embodiment of the disclosure, when one or more of the start information, the state information and the user operation information do not meet the firmware update condition, it may be determined that the wearable device does not need to perform firmware update, and at least one application firmware in the wearable device may be directly started at this time to implement normal operation of the wearable device.
In this embodiment, since the boot loader firmware is run and the boot loader firmware is used to determine whether the wearable device needs to update the firmware, so as to trigger updating of the firmware in the wearable device, the user can be timely guided to update the firmware of the wearable device, frequent update boot start of the user can be effectively avoided, stability and convenience of firmware update are effectively improved, and reliability of firmware update is improved. Because whether the wearable device needs to be updated with firmware is judged according to at least one of the starting information, the state information and the user operation information of the wearable device, when the at least one of the starting information, the state information and the user operation information of the wearable device is determined to meet the firmware updating condition, the user is timely guided to update the firmware of the wearable device, the frequent update guiding starting of the user can be effectively avoided, the stability and the convenience of the firmware updating are effectively improved, and the reliability of the firmware updating is improved. The method comprises the steps of determining the starting reason of the wearable device according to the starting information of the wearable device, determining whether the wearable device is in a charging connection state according to the state information of the wearable device, and determining that the wearable device needs to be subjected to firmware updating according to the user operation information, so that the wearable device can be ensured to be stably and accurately determined to be subjected to the firmware updating. Because the target recovery firmware receives the confirmation instruction for the prompt information, at least one firmware is updated through the target recovery firmware, the firmware updating intention of the user can be accurately judged, and misoperation is effectively avoided. Because the at least one application firmware is operated in response to the determination that the firmware update is not needed, the application firmware in the wearable device can be operated in time when the determination that the firmware update is not needed, the stability of the firmware update of the wearable device is effectively improved, the firmware update effect is improved, and the use experience of a user is prevented from being influenced.
Fig. 5 is a flowchart of a firmware update method of a wearable device according to another embodiment of the disclosure.
As shown in fig. 5, the firmware updating method of the wearable device includes:
s501: running boot-loader firmware.
S502: and judging whether the wearable equipment needs firmware updating or not through the boot loading firmware.
The descriptions of S501-S502 may be specifically referred to the above embodiments, and are not repeated herein.
S503: obtaining information of each recovery firmware of the plurality of recovery firmware by bootloading the firmware, the information of the recovery firmware including at least one of: check code, history upgrade information.
The verification code is used for verifying whether the corresponding recovery firmware is valid or matched, a combination of numbers, letters, symbols and the like can be used as the verification code, firmware or a program for identifying the verification code can be added into the wearable equipment and used for identifying the verification code required to be upgraded in a plurality of verification codes, and the verification code is not limited to the verification code
The historical upgrade information is historical information corresponding to firmware update in the wearable device.
In the embodiment of the disclosure, the update document may be recorded as the history upgrade information by the wearable device system, or the history upgrade information may be extracted from the update log of the wearable device, which is not limited.
In the embodiment of the disclosure, information such as check codes, historical upgrade information and the like can be inserted into the recovery firmware, and the information of the recovery firmware is read when the boot loader firmware is operated.
In other embodiments, a corresponding information acquisition system may be provided, and the information acquisition system may be accessed based on the boot loader firmware to trigger the information acquisition system to determine and acquire information of the recovery firmware, which is not limited thereto.
S504: and determining target recovery firmware from the plurality of recovery firmware according to the information of each recovery firmware in the plurality of recovery firmware and operating.
The information of the recovery firmware may be, for example, specifically, an identification code of the recovery firmware, version information of the recovery firmware, summary information of the recovery firmware, or the like, which is not limited.
In the embodiment of the present disclosure, a plurality of recovery firmware may be configured, where a recovery firmware selected from the plurality of recovery firmware to update the wearable device firmware may be referred to as a target recovery firmware, and the target recovery firmware may be a recovery firmware with a highest upgrade success rate from the plurality of recovery firmware, or may also be a recovery firmware with a latest version number from the plurality of recovery firmware, which is not limited.
Optionally, in some embodiments of the present disclosure, verification processing is performed on the check code of each recovery firmware in the recovery firmware to obtain a verification result, and if the verification result indicates that verification of the check codes of at least two recovery firmware in the recovery firmware is successful, the target recovery firmware is determined according to the historical upgrade information of the at least two recovery firmware.
The verification code is used for verifying whether the corresponding recovery firmware is valid or matched, a combination of numbers, letters, symbols and the like can be used as the verification code, and firmware or a program for identifying the verification code can be added into the wearable device to be used for identifying the verification code corresponding to the target recovery firmware in a plurality of verification codes, so that the verification code is not limited.
The verification result is a matching result of the check codes, the required check codes can be configured in advance, recovery firmware carrying the required check codes is identified from a plurality of recovery firmware, and the number of the recovery firmware carrying the required check codes can be zero, one or a plurality of recovery firmware.
In the embodiment of the disclosure, when the number of recovered firmware carrying the required check code is zero, the firmware update failure can be directly judged.
In the embodiment of the disclosure, when the number of recovery firmware carrying the required check code is one, the recovery firmware may be directly used as the target recovery firmware.
In the embodiment of the disclosure, when the number of the recovery firmware carrying the required check code is at least two, the target recovery firmware is determined according to the historical upgrade information of the at least two recovery firmware.
Optionally, the historical upgrade information includes historical upgrade result information and an upgrade serial number, and according to the historical upgrade result information of the plurality of recovered firmware, recovered firmware meeting a preset condition from the plurality of recovered firmware is determined as the target recovered firmware, wherein the preset condition includes at least one of the following: the upgrade failure probability indicated by the historical upgrade result information is lowest, and the latest upgrade time indicated by the upgrade serial number is relatively short, because when the number of check codes is at least two, a plurality of recovery firmware is screened according to the historical upgrade information, the recovery firmware with the highest starting success probability can be selected as the target recovery firmware, and the reliability of the firmware update of the wearable equipment is effectively improved.
The historical upgrade result information may include historical information such as start success times, upgrade failure times, and the like.
The number of times of starting the recovery firmware is the number of times of starting the recovery firmware, the number of times of upgrading success is the number of times of successful completion of upgrading by using the recovery firmware, and the difference between the number of times of starting and the number of times of upgrading success can be called as the number of times of upgrading failure, that is, the number of times of starting-the number of times of upgrading success=the number of times of upgrading failure, which is not limited.
It can be understood that the backup recovery firmware has two indexes of a start-up frequency and an upgrade success frequency, when the backup recovery firmware is judged to run each time, the start-up frequency is increased by one, and when the backup recovery firmware is determined to run successfully, that is, the upgrade success frequency is increased by one, and the difference between the start-up frequency and the upgrade success frequency, that is, the upgrade failure frequency is determined.
In the embodiment of the disclosure, since different recovery firmware has the same or different starting times and upgrading success times, the upgrading failure times corresponding to the different recovery firmware may be the same or different, and thus, the target recovery firmware may be determined by comparing the upgrading failure times.
In the embodiment of the disclosure, the minimum upgrade failure frequency can be used as a judgment basis for indicating that the upgrade failure probability is the lowest.
The number of upgrade failures with the smallest number of upgrade failures may be referred to as the minimum number of upgrade failures.
It can be understood that, since the minimum upgrade failure number indicates that the difference between the start-up number and the upgrade success number is the minimum, that is, the success rate is higher when the recovery firmware corresponding to the minimum upgrade failure number is updated during operation.
In the embodiment of the disclosure, when the verification result indicates that verification of the verification codes of at least two recovery firmware in the recovery firmware is successful, a difference value between the starting times and the upgrading success times can be used to determine the recovery firmware corresponding to the minimum difference value, and when the number of times of occurrence of the minimum upgrading failure times is one time, the recovery firmware corresponding to the minimum upgrading failure times is used as the target recovery firmware.
In the embodiment of the present disclosure, the number of occurrences of the minimum upgrade failure times is one, which indicates that, among the plurality of upgrade failure times, the number of the minimum upgrade failure times is only one, for example, if the number of occurrences of 3 upgrade failure times is "0", "1", and "3", respectively, the minimum number of occurrences of "0" is "0", and the number of occurrences of "0" is only one, and the recovery firmware corresponding to the minimum number of occurrences of "0" may be regarded as the target recovery firmware, and if the number of occurrences of 3 upgrade failure times is "1", "1", and "3", respectively, the minimum number of occurrences of "1" is "1", and the number of occurrences of "1" is two, and at this time, the target recovery firmware cannot be determined further according to the upgrade serial number and other manners, and this is not limited.
The upgrade serial number, which is a serial number corresponding to the upgrade of the recovery firmware, is understood that the recovery firmware may be updated and upgraded, and after the update and upgrade, the corresponding upgrade serial number is configured, that is, the update and upgrade conditions of the recovery firmware, such as the update time, the update times, etc., may be determined according to the upgrade serial number, which is not limited.
In the embodiment of the disclosure, one with a relatively short latest upgrade time can be judged as the target recovery firmware according to the upgrade serial number between at least two recovery firmware.
In the embodiment of the disclosure, after updating and upgrading the recovery firmware, the upgrade serial number can be updated, and when updating and upgrading the recovery firmware next time, the upgrade serial number is read in advance, and the recovery firmware to which the newer upgrade serial number belongs is selected as the target recovery firmware, which is not limited.
For example, if one of the two recovery firmware is selected as the target recovery firmware, as shown in fig. 6, fig. 6 is a schematic diagram of target recovery firmware selection according to another embodiment of the disclosure, wherein:
in S601, the check code of the recovery firmware 1 and the check code of the recovery firmware 2 are read.
In S602, it is determined whether the recovery firmware 1 and the recovery firmware 2 are available according to the check code.
If neither recovery firmware 1 nor recovery firmware 2 is available, then it is determined that the update failed. If at least one of the recovery firmware 1 and the recovery firmware 2 is available, S603 is performed.
In S603, the history upgrade information of the recovery firmware 1 and the recovery firmware 2 is read.
In S604, it is determined whether the recovery firmware 1 and the recovery firmware 2 are available according to the history upgrade information.
If either of the recovery firmware 1 and the recovery firmware 2 is available, S605 is executed, and if both the recovery firmware 1 and the recovery firmware 2 are available, S606 is executed.
In S605, it is determined whether recovery firmware 1 is available. If available, recovery firmware 1 is selected as the target recovery firmware, and if not available, recovery firmware 2 is selected as the target recovery firmware.
In S606, it is determined whether the upgrade failure probabilities indicated by the historical upgrade result information of the recovery firmware 1 and the recovery firmware 2 are the same. If not, executing S607, if yes, executing S608;
in S607, the number of upgrade failures of the recovery firmware 1 and the recovery firmware 2 is compared.
If the number of upgrade failures of the recovery firmware 1 is greater than the number of upgrade failures of the recovery firmware 2, the recovery firmware 2 is selected, otherwise, the recovery firmware 1 is selected.
In S608, the latest upgrade times indicated by the upgrade serial numbers of the recovery firmware 1 and the recovery firmware 2 are compared.
If the latest upgrade time indicated by the upgrade serial number of the recovery firmware 1 is relatively short, the recovery firmware 1 is selected, otherwise, the recovery firmware 2 is selected.
In S609, the target restoration firmware is determined.
In S610, it is determined whether the number of upgrade failures of the target recovery firmware is less than 10, if yes, S611 is executed, if no, it is determined that the upgrade fails.
In S611, the execution target recovery firmware.
In the embodiment of the disclosure, two recovery firmware (recovery firmware 1 and recovery firmware 2) are taken as examples, that is, when two recovery firmware are unavailable, the firmware update failure is judged, if any one of the two recovery firmware is available, the available recovery firmware is taken as a target recovery firmware, if the two recovery firmware are available, the two recovery firmware are selected, the upgrade failure times of the two selectable recovery firmware and the upgrade serial number can be compared to select the target recovery firmware, after the target recovery firmware is determined, the reliability of the firmware update of the target recovery firmware can be further verified, that is, the threshold value of the upgrade failure times is set, for example, 10 times, the size of the threshold value can be dynamically adjusted according to the actual requirement, no limitation is made on the problem, when the upgrade failure times of the target recovery firmware reach the threshold value, the update failure times of the target recovery firmware do not reach the threshold value, the target recovery firmware is operated, and the wearable device is updated by using the target recovery firmware. In other embodiments, it may be further determined in S607 whether the number of upgrade failures of the selected recovery firmware reaches a preset threshold, and if the number of upgrade failures does not reach the preset threshold, S608 is executed, otherwise, it is directly determined that the upgrade fails.
In the embodiment of the present disclosure, the target recovery firmware may be selected according to the size of the upgrade failure number and the update and old of the upgrade serial number, which may be that the size of the upgrade failure number is first determined, if the size of the upgrade failure number is the same, the update and old of the upgrade serial number may be determined, or the update and old of the upgrade serial number may be predetermined, and if the update time of the upgrade serial number is the same, the size of the upgrade failure number may be determined, or the target recovery firmware may be selected by combining the size of the upgrade failure number and the update and old of the upgrade serial number, which is not limited.
S505: and updating at least one application firmware in the wearable device through the target recovery firmware.
The description of S505 may be specifically referred to the above embodiments, and will not be repeated here.
S506: and upgrading at least one recovery firmware except the target recovery firmware in the plurality of recovery firmware.
In the embodiment of the disclosure, after updating the firmware in the wearable device, at least one recovery firmware except the target recovery firmware can be updated to update the failed or outdated recovery firmware, so that the recovery firmware in the wearable device can be updated and updated in time, and the availability of the recovery firmware is ensured.
In the embodiment of the disclosure, other recovery firmware except the target recovery firmware may be upgraded in multiple recovery firmware, one or more other recovery firmware is selected for upgrading, and in the upgrading process, the oldest version may be selected according to the upgrading serial number of the recovery firmware, or the upgrading process may be performed according to the other recovery firmware with the longest last upgrading duration, or the recovery firmware with the largest number of times of upgrading failure may be selected for upgrading, which is not limited.
In this embodiment, since the boot loader firmware is run and the boot loader firmware is used to determine whether the wearable device needs to update the firmware, so as to trigger updating of the firmware in the wearable device, the user can be timely guided to update the firmware of the wearable device, frequent update boot start of the user can be effectively avoided, stability and convenience of firmware update are effectively improved, and reliability of firmware update is improved. The method comprises the steps of obtaining information of each recovery firmware in a plurality of recovery firmware through boot loading, determining and running target recovery firmware from the plurality of recovery firmware according to the information of each recovery firmware in the plurality of recovery firmware, flexibly selecting the target recovery firmware, enhancing the stability of firmware updating of the wearable device, quickly and effectively screening out the target recovery firmware from the plurality of recovery firmware by using a mode of identifying check codes, guaranteeing the running stability of the target recovery firmware, effectively improving the obtaining success rate of resource information, selecting the recovery firmware with highest starting success probability according to historical upgrading information as the target recovery firmware when the number of matched check codes is a plurality of, effectively improving the reliability of firmware updating of the wearable device, determining the recovery firmware with a newer version according to upgrading determination target recovery firmware when the historical upgrading result information is unable to determine the target recovery firmware, improving the flexibility and the stability of firmware updating of the wearable device, improving the stability of the firmware updating of the firmware with the newer version, reducing the updating of the recovery firmware or updating failure, and improving the reliability of the recovery firmware updating result of the firmware, and effectively improving the reliability of the firmware updating of the wearable device.
The disclosure also proposes a firmware updating apparatus of a wearable device, including: at least one module for executing the flow and/or steps in the firmware update method of the wearable device proposed by the above embodiment of the present disclosure.
Optionally, in some embodiments, as shown in fig. 7, fig. 7 is a schematic structural diagram of a firmware updating apparatus of a wearable device according to an embodiment of the disclosure, where the firmware updating apparatus 70 of the wearable device may include:
a first running module 701, configured to run boot loader firmware;
a judging module 702, configured to judge whether firmware update is needed to be performed on the wearable device through bootloading firmware;
a second operation module 703, configured to operate the target recovery firmware in response to determining that firmware update is required;
and a processing module 704, configured to update at least one application firmware in the wearable device through the target recovery firmware.
In some embodiments of the present disclosure, as shown in fig. 8, fig. 8 is a schematic structural diagram of a firmware updating apparatus of a wearable device according to another embodiment of the present disclosure, and a first operation module 701 is specifically configured to:
in response to the wearable device booting or resetting, the boot loader firmware is run.
In some embodiments of the present disclosure, as shown in fig. 8, the apparatus further comprises:
a third running module 705 for running at least one application firmware in response to determining that no firmware update is required.
In some embodiments of the present disclosure, as shown in fig. 8, the determining module 702 is specifically configured to:
acquiring at least one of starting information, state information and user operation information of the wearable device through the boot loader;
judging whether the wearable device needs to be subjected to firmware update according to at least one of starting information, state information and user operation information of the wearable device.
In some embodiments of the present disclosure, as shown in fig. 8, the determining module 702 is specifically configured to:
determining a starting reason of the wearable equipment according to starting information of the wearable equipment;
in response to determining that the start reason of the wearable device indicates that the start reason does not belong to abnormal start, determining whether the wearable device is in a charging connection state according to state information of the wearable device;
and responding to the wearable device in a charging connection state, and determining that the wearable device needs to be subjected to firmware update according to the user operation information.
In some embodiments of the present disclosure, as shown in fig. 8, the processing module 704 is specifically configured to:
Generating user prompt information through the target recovery firmware, wherein the user prompt information is used for prompting whether to agree to carry out firmware update processing on the wearable equipment;
and in response to the target recovery firmware receiving a confirmation instruction for the prompt information, updating at least one application firmware by the target recovery firmware.
In some embodiments of the present disclosure, as shown in fig. 8, the wearable device includes a plurality of recovery firmware;
a second operation module 703, comprising:
an acquisition sub-module 7031, configured to acquire, by bootloading firmware, information of each of a plurality of recovery firmware, where the information of the recovery firmware includes at least one of: check code, history upgrade information;
a determining submodule 7032 is configured to determine a target recovery firmware from the plurality of recovery firmware and run the target recovery firmware according to information of each recovery firmware in the plurality of recovery firmware.
In some embodiments of the present disclosure, as shown in fig. 8, the determining submodule 7032 is specifically configured to:
verifying the check code of each recovery firmware in the recovery firmware to obtain a verification result;
and responding to the verification result to indicate that verification codes of at least two recovery firmware in the recovery firmware are successfully verified, and determining the target recovery firmware according to the historical upgrading information of the at least two recovery firmware.
In some embodiments of the present disclosure, as shown in fig. 8, the historical upgrade information includes historical upgrade result information, an upgrade serial number;
wherein, confirm submodule 7032 is specifically used for:
determining recovery firmware meeting preset conditions from the plurality of recovery firmware as target recovery firmware according to historical upgrading result information of the plurality of recovery firmware, wherein the preset conditions comprise at least one of the following: the upgrade failure probability indicated by the historical upgrade result information is lowest, and the latest upgrade time indicated by the upgrade serial number is relatively short.
In some embodiments of the present disclosure, as shown in fig. 8, the apparatus further comprises:
and the upgrading module 706 is configured to upgrade at least one recovery firmware other than the target recovery firmware from the plurality of recovery firmware.
Corresponding to the firmware updating method of the wearable device provided by the embodiments of fig. 1 to 6, the present disclosure further provides a firmware updating apparatus of the wearable device, and since the firmware updating apparatus of the wearable device provided by the embodiments of the present disclosure corresponds to the firmware updating method of the wearable device provided by the embodiments of fig. 1 to 6, an implementation of the firmware updating method of the wearable device is also applicable to the firmware updating apparatus of the wearable device provided by the embodiments of the present disclosure, which is not described in detail in the embodiments of the present disclosure.
In this embodiment, firmware is loaded by running a boot; judging whether the wearable equipment needs firmware updating or not through the boot loading firmware; in response to determining that a firmware update is required, running a target recovery firmware; at least one application firmware in the wearable device is updated through the target recovery firmware, and as the boot loader firmware is operated, whether the firmware in the wearable device needs to be updated or not is judged through the boot loader firmware, so that the firmware in the wearable device is triggered to be updated, a user can be timely guided to update the firmware of the wearable device, frequent update boot start of the user can be effectively avoided, stability and convenience of firmware update are effectively improved, and reliability of firmware update is improved.
In order to implement the above-described embodiments, the present disclosure also proposes a non-transitory computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements a firmware update method of a wearable device as proposed by the foregoing embodiments of the present disclosure.
To achieve the above embodiments, the present disclosure further proposes a wearable device, including: the system comprises a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor executes the program to realize the firmware updating method of the wearable device according to the previous embodiment of the disclosure.
To achieve the above-described embodiments, the present disclosure also proposes a computer program product which, when executed by a processor, performs a firmware update method of a wearable device as proposed by the foregoing embodiments of the present disclosure.
Fig. 9 illustrates a block diagram of an exemplary wearable device suitable for use in implementing embodiments of the present disclosure. The wearable device 12 shown in fig. 9 is only one example and should not impose any limitations on the functionality and scope of use of embodiments of the present disclosure.
As shown in fig. 9, wearable device 12 is in the form of a general purpose computing device. Components of wearable device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, a bus 18 that connects the various system components, including the system memory 28 and the processing units 16. Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include industry Standard architecture (Industry Standard Architecture; hereinafter ISA) bus, micro channel architecture (Micro Channel Architecture; hereinafter MAC) bus, enhanced ISA bus, video electronics standards Association (Video Electronics Standards Association; hereinafter VESA) local bus, and peripheral component interconnect (Peripheral Component Interconnection; hereinafter PCI) bus.
Wearable device 12 typically includes a variety of computer system readable media. Such media can be any available media that can be accessed by wearable device 12 and includes both volatile and nonvolatile media, removable and non-removable media.
Memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (Random Access Memory; hereinafter: RAM) 30 and/or cache memory 32. Wearable device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from or write to non-removable, nonvolatile magnetic media (not shown in FIG. 9, commonly referred to as a "hard disk drive").
Although not shown in fig. 9, a magnetic disk drive for reading from and writing to a removable nonvolatile magnetic disk (e.g., a "floppy disk"), and an optical disk drive for reading from or writing to a removable nonvolatile optical disk (e.g., a compact disk read only memory (Compact Disc Read Only Memory; hereinafter CD-ROM), digital versatile read only optical disk (Digital Video Disc Read Only Memory; hereinafter DVD-ROM), or other optical media) may be provided. In such cases, each drive may be coupled to bus 18 through one or more data medium interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules configured to carry out the functions of the various embodiments of the disclosure.
A program/utility 40 having a set (at least one) of program modules 42 may be stored in, for example, memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment. Program modules 42 generally perform the functions and/or methods in the embodiments described in this disclosure.
The wearable device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), one or more devices that enable a user to interact with the wearable device 12, and/or any devices (e.g., network card, modem, etc.) that enable the wearable device 12 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 22. Also, the wearable device 12 may communicate with one or more networks (e.g., a local area network (Local Area Network; hereinafter: LAN), a wide area network (Wide Area Net work; hereinafter: WAN) and/or a public network, such as the internet) through the network adapter 20. As shown, network adapter 20 communicates with other modules of wearable device 12 via bus 18. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in connection with wearable device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
The processing unit 16 executes various functional applications and data processing by running programs stored in the system memory 28, for example, implementing the firmware update method of the wearable device mentioned in the foregoing embodiment.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
It should be noted that in the description of the present disclosure, the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Furthermore, in the description of the present disclosure, unless otherwise indicated, the meaning of "a plurality" is two or more.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and further implementations are included within the scope of the preferred embodiment of the present disclosure in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the embodiments of the present disclosure.
It should be understood that portions of the present disclosure may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits having logic gates for implementing logic functions on data signals, application specific integrated circuits having suitable combinational logic gates, programmable Gate Arrays (PGAs), field Programmable Gate Arrays (FPGAs), and the like.
Those of ordinary skill in the art will appreciate that all or a portion of the steps carried out in the method of the above-described embodiments may be implemented by a program to instruct related hardware, where the program may be stored in a computer readable storage medium, and where the program, when executed, includes one or a combination of the steps of the method embodiments.
Furthermore, each functional unit in the embodiments of the present disclosure may be integrated in one processing module, or each unit may exist alone physically, or two or more units may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules. The integrated modules may also be stored in a computer readable storage medium if implemented in the form of software functional modules and sold or used as a stand-alone product.
The above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, or the like.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present disclosure. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
Although embodiments of the present disclosure have been shown and described above, it will be understood that the above embodiments are illustrative and not to be construed as limiting the present disclosure, and that variations, modifications, alternatives, and variations may be made to the above embodiments by one of ordinary skill in the art within the scope of the present disclosure.

Claims (13)

1. A method for updating firmware of a wearable device, comprising:
running a boot loader firmware;
judging whether the wearable equipment needs firmware updating or not through the boot loading firmware;
in response to determining that a firmware update is required, running a target recovery firmware;
and updating at least one application firmware in the wearable device through the target recovery firmware.
2. The method of claim 1, wherein the running boot-loader firmware comprises:
in response to the wearable device being booted or reset, running boot-loader firmware.
3. The method of claim 1, wherein the method further comprises:
the at least one application firmware is run in response to determining that no firmware update is required.
4. A method as claimed in any one of claims 1 to 3, wherein said determining, by said bootloader firmware, whether said wearable device requires a firmware update comprises:
Acquiring at least one of starting information, state information and user operation information of the wearable equipment through the boot loading firmware;
judging whether the wearable device needs to be subjected to firmware update or not according to at least one of starting information, state information and user operation information of the wearable device.
5. The method of claim 4, wherein the determining whether the wearable device needs firmware update according to at least one of startup information, status information, and user operation information of the wearable device comprises:
determining a starting reason of the wearable equipment according to the starting information of the wearable equipment;
in response to determining that the start reason of the wearable device indicates that the start reason does not belong to abnormal start, determining whether the wearable device is in a charging connection state according to state information of the wearable device;
and responding to the wearable equipment in a charging connection state, and determining that the wearable equipment needs to be subjected to firmware update according to the user operation information.
6. The method of any of claims 1-5, wherein the updating at least one application firmware in the wearable device by the target recovery firmware comprises:
Generating user prompt information through the target recovery firmware, wherein the user prompt information is used for prompting whether to agree to perform firmware update processing on the wearable equipment;
and in response to the target recovery firmware receiving a confirmation instruction for the prompt message, updating the at least one application firmware through the target recovery firmware.
7. The method of any of claims 1-6, wherein the wearable device comprises a plurality of recovery firmware;
the running the target recovery firmware in response to determining that a firmware update is required includes:
obtaining information of each recovery firmware of the plurality of recovery firmware through the boot loader firmware, wherein the information of the recovery firmware comprises at least one of the following: check code, history upgrade information;
and determining the target recovery firmware from the plurality of recovery firmware according to the information of each recovery firmware in the plurality of recovery firmware and operating the target recovery firmware.
8. The method of claim 7, wherein determining the target recovery firmware from the plurality of recovery firmware and operating based on information of each recovery firmware in the plurality of recovery firmware comprises:
Verifying the verification code of each recovery firmware in the recovery firmware to obtain a verification result;
and responding to the verification result to indicate that verification codes of at least two recovery firmware in the recovery firmware are successfully verified, and determining the target recovery firmware according to the historical upgrading information of the at least two recovery firmware.
9. The method of claim 7 or 8, wherein the historical upgrade information includes historical upgrade result information, an upgrade serial number;
wherein the determining the target recovery firmware from the plurality of recovery firmware according to the information of each recovery firmware in the plurality of recovery firmware and operating the target recovery firmware comprises:
determining, as the target recovery firmware, recovery firmware satisfying a preset condition from among the plurality of recovery firmware according to historical upgrade result information of the plurality of recovery firmware, wherein the preset condition includes at least one of: the upgrade failure probability indicated by the historical upgrade result information is lowest, and the latest upgrade time indicated by the upgrade serial number is relatively short.
10. The method of any one of claims 7 to 9, wherein the method further comprises:
And upgrading at least one recovery firmware except the target recovery firmware in the plurality of recovery firmware.
11. Firmware updating means of a wearable device, characterized by comprising at least one module for performing the flow and/or steps in the method of any of claims 1-10.
12. A wearable device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein, the liquid crystal display device comprises a liquid crystal display device,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of firmware update of the wearable device of any of claims 1-10.
13. A non-transitory computer readable storage medium storing computer instructions, wherein the computer instructions are for causing the computer to perform the method of firmware update of the wearable device of any of claims 1-10.
CN202211090901.5A 2022-09-07 2022-09-07 Firmware updating method and device of wearable device and wearable device Pending CN116257265A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211090901.5A CN116257265A (en) 2022-09-07 2022-09-07 Firmware updating method and device of wearable device and wearable device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211090901.5A CN116257265A (en) 2022-09-07 2022-09-07 Firmware updating method and device of wearable device and wearable device

Publications (1)

Publication Number Publication Date
CN116257265A true CN116257265A (en) 2023-06-13

Family

ID=86681479

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211090901.5A Pending CN116257265A (en) 2022-09-07 2022-09-07 Firmware updating method and device of wearable device and wearable device

Country Status (1)

Country Link
CN (1) CN116257265A (en)

Similar Documents

Publication Publication Date Title
CN108304282B (en) Control method of double BIOS and related device
EP3690653A1 (en) Bios recovery and update
CN109905770B (en) Terminal starting method and device and terminal
US20130061090A1 (en) Partial rebooting recovery apparatus and method
CN105814541A (en) Computer device and memory starting method for computer device
CN113254048B (en) Method, device and equipment for updating boot program and computer readable medium
KR20140066535A (en) Electronic apparatus, method for update firmware, computer-readable recording medium
CN110780942A (en) System starting method and device, node equipment and computer readable storage medium
CN115113905A (en) Firmware upgrading method and firmware upgrading device
US20100287364A1 (en) Boot systems and methods, and related devices
US7360074B2 (en) Method for remote flashing of a bios memory in a data processing system
TW202131170A (en) Firmware corruption recovery
CN111399888B (en) Audio processing chip processing method and device and electronic equipment
CN112035171A (en) Factory setting restoration method and system based on UEFI firmware
CN109086085B (en) Operating system start management method and device
CN116257265A (en) Firmware updating method and device of wearable device and wearable device
CN115827069A (en) Starting control method, system and device for server mainboard
CN114237722B (en) System starting method, device, equipment and engineering vehicle
CN115033296A (en) UEFI and Linux-based domestic operating system starting method and UEFI and Linux-based domestic operating system starting device
CN114115958A (en) Program starting method and terminal equipment
CN111382009B (en) Automatic system maintenance method and computer equipment with automatic maintenance function
TW202223655A (en) Computer system and method capable of self-monitoring and restoring an operation of operating system
CN112817642A (en) Method and device for starting EFI operating system by X86 platform through automatic firmware switching
CN112395121A (en) Drive loading processing method and device, storage medium and computer equipment
CN115373906B (en) Backup starting method, device, equipment and chip of embedded system architecture

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination