CN108121562B - Firmware version switching method, electronic device and BIOS chip - Google Patents
Firmware version switching method, electronic device and BIOS chip Download PDFInfo
- Publication number
- CN108121562B CN108121562B CN201711426402.8A CN201711426402A CN108121562B CN 108121562 B CN108121562 B CN 108121562B CN 201711426402 A CN201711426402 A CN 201711426402A CN 108121562 B CN108121562 B CN 108121562B
- Authority
- CN
- China
- Prior art keywords
- version
- chip
- firmware
- information
- electronic device
- 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a firmware version switching method which is applied to electronic equipment, wherein the electronic equipment stores information of at least two firmware versions of a first chip, the method comprises the steps of determining one firmware version from the at least two firmware versions as a specific version, and executing a refreshing instruction for writing the information of the specific version into the first chip. The disclosure also provides an electronic device and a BIOS chip.
Description
Technical Field
The disclosure relates to a firmware version switching method, electronic equipment and a BIOS chip.
Background
With the continuous development of electronic technology, the version of a chip in an electronic device is also updated. However, different versions of chips may suffer from various compatibility problems during practical use. Taking TPM (Trusted Platform Module) security chips as an example, a TPM2.0 is usually used as a standard configuration at present, however, the TPM2.0 chip can only be used in win7x 64 or win8 and above versions of operating systems, and if a user wants to use the win7x32 operating system, the TPM2.0 chip cannot work.
Disclosure of Invention
One aspect of the present disclosure provides a firmware version switching method applied to an electronic device, where information of at least two firmware versions of a first chip is stored on the electronic device, the method includes determining one firmware version of the at least two firmware versions as a specific version, and executing a refresh instruction, where the specific version of information is written into the first chip.
Optionally, the determining one firmware version from the at least two firmware versions as the specific version includes acquiring system version information, and determining one firmware version corresponding to the system version information from the at least two firmware versions as the specific version based on the system version information.
Optionally, the acquiring the system version information includes determining the system version information based on a partition format of the system.
Optionally, the determining one firmware version from the at least two firmware versions as the specific version includes authenticating the user, and determining one firmware version from the at least two firmware versions as the specific version based on an input of the user after the authentication is passed.
Optionally, the firmware version switching method further includes, when the refresh command fails to execute, judging the number of times the refresh command is executed currently, and executing the refresh command again when the number of times is smaller than a preset value.
Optionally, the firmware version switching method further includes configuring basic information of the first chip when the refresh command is executed successfully.
Optionally, when the electronic device meets a preset condition, a storage space of the first chip is configured.
Optionally, information of at least two firmware versions of the first chip is stored on the BIOS chip.
Another aspect of the present disclosure provides a firmware version switching system including a determination module and an execution module. And the determining module is used for determining one firmware version from the at least two firmware versions as a specific version. And the execution module is used for executing a refreshing instruction and writing the information of the specific version into the first chip.
Another aspect of the present disclosure provides an electronic device comprising a first chip, a processor, and a storage medium storing information for at least two firmware versions of the first chip, and computer readable instructions that, when executed by the processor, cause the processor to perform the method of any one of the above.
Another aspect of the present disclosure provides a BIOS chip having information of at least two firmware versions of a first chip stored thereon.
Another aspect of the present disclosure provides a non-volatile storage medium storing computer executable instructions that when executed are configured to implement a method as described above.
Another aspect of the present disclosure provides a computer program comprising computer executable instructions which when executed are for implementing a method as described above.
Drawings
For a more complete understanding of the present disclosure and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:
fig. 1 schematically illustrates an application scenario of a firmware version switching method according to an embodiment of the present disclosure;
FIG. 2 schematically illustrates a flow chart of a firmware version switching method according to an embodiment of the disclosure;
FIG. 3 schematically illustrates a flow chart of determining one firmware version from at least two firmware versions as a particular version in accordance with an embodiment of the present disclosure;
FIG. 4 schematically illustrates a flow chart for determining one firmware version from at least two firmware versions as a particular version according to another embodiment of the present disclosure;
FIG. 5 schematically illustrates a flow chart of a firmware version switching method according to another embodiment of the present disclosure;
FIG. 6 schematically illustrates a block diagram of a firmware version switching system according to an embodiment of the present disclosure;
FIG. 7 schematically illustrates a block diagram of a determination module according to an embodiment of the disclosure;
FIG. 8 schematically illustrates a block diagram of a determination module according to another embodiment of the present disclosure;
FIG. 9 schematically illustrates a block diagram of a firmware version switching system according to another embodiment of the present disclosure; and
fig. 10 schematically illustrates a block diagram of an electronic device according to an embodiment of the disclosure.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is only exemplary and is not intended to limit the scope of the present disclosure. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the concepts of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and/or the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner.
Where expressions like at least one of "A, B and C, etc. are used, the expressions should generally be interpreted in accordance with the meaning as commonly understood by those skilled in the art (e.g.," a system having at least one of A, B and C "shall include, but not be limited to, a system having a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a formulation similar to at least one of "A, B or C, etc." is used, in general such a formulation should be interpreted in accordance with the ordinary understanding of one skilled in the art (e.g. "a system with at least one of A, B or C" would include but not be limited to systems with a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). It should also be appreciated by those skilled in the art that virtually any disjunctive word and/or phrase presenting two or more alternative items, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the items, either of the items, or both. For example, the phrase "a or B" should be understood to include the possibility of "a" or "B", or "a and B".
Some of the block diagrams and/or flowchart illustrations are shown in the figures. It will be understood that some blocks of the block diagrams and/or flowchart illustrations, or combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the instructions, when executed by the processor, create means for implementing the functions/acts specified in the block diagrams and/or flowchart.
Thus, the techniques of this disclosure may be implemented in hardware and/or software (including firmware, microcode, etc.). Additionally, the techniques of this disclosure may take the form of a computer program product on a computer-readable medium having instructions stored thereon, the computer program product being usable by or in connection with an instruction execution system. In the context of this disclosure, a computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the instructions. For example, a computer-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. Specific examples of the computer readable medium include: magnetic storage devices such as magnetic tape or hard disk (HDD); optical storage devices such as compact discs (CD-ROMs); a memory, such as a Random Access Memory (RAM) or a flash memory; and/or a wired/wireless communication link.
Embodiments of the present disclosure provide a firmware version switching method that provides a possibility for firmware version switching of a chip by integrating two version information.
Fig. 1 schematically illustrates an application scenario of a firmware version switching method according to an embodiment of the present disclosure.
As shown in fig. 1, there may be compatibility issues with different firmware versions of the chip. Taking TPM (Trusted Platform Module) security chip as an example, the TPM security chip is a security chip conforming to the standard of a trusted platform module, and can effectively protect a computer and prevent illegal users from accessing. The chip is generally configured by taking the version of TPM2.0 as a standard at present, however, the TPM2.0 chip can only be used in operating systems with the version of win7x 64 or win8 and above, and if a user wants to use the operating system with the version of win7x32, the TPM2.0 chip cannot work. Currently, in order to enable the system of win7x32 to use the TPM 1.2, the selection and setting of the device need to be completed before the device leaves the factory, after leaving the factory, the user cannot change the version of the TPM, and if the user upgrades the system in the use process and wants to use the version of TPM2.0, only the replacement of the motherboard can be realized. Alternatively, the user reloads the original win8 system to win7x32 and wants to be able to use the functionality of the TPM, also only by replacing the motherboard with the chip of TPM 1.2.
Fig. 2 schematically illustrates a flowchart of a firmware version switching method according to an embodiment of the present disclosure.
As shown in fig. 2, the method is applied to an electronic device on which information of at least two firmware versions of a first chip is stored, and includes operations S210 and S220.
In operation S210, one firmware version is determined as a specific version from among the at least two firmware versions.
In operation S220, a refresh command is executed for writing the specific version of information into the first chip.
The method can flexibly switch the firmware version of the first chip, and improves the flexibility and applicability of the electronic equipment. In the production process, the system type used by the user does not need to be determined, and the configuration process is reduced. On the other hand, in the user angle, the proper version can be flexibly selected, and the condition of lacking data can not occur.
According to the embodiment of the disclosure, the first chip may be various chips attached to the electronic device, such as the TPM security chip described above, but the embodiment of the disclosure is not limited thereto.
According to the embodiment of the disclosure, the first chip at least comprises more than two firmware versions, and the suitable versions can be selected for use according to requirements. Information of these firmware versions is stored in the electronic device so that the first chip is refreshed with this information when the versions are switched.
According to an embodiment of the present disclosure, one firmware version is determined as a specific version from among the at least two firmware versions in operation S210. The selection may be based on system compatibility considerations, e.g., TPM2.0 version cannot be used for win7x32, or may be based on user preference, e.g., in a win10 system, the user still wishes to use TPM 1.2 version.
Operation S210 in some embodiments of the present disclosure is described below in conjunction with fig. 3.
Fig. 3 schematically illustrates a flow chart of determining one firmware version from at least two firmware versions as a particular version according to an embodiment of the present disclosure.
As shown in fig. 3, the method includes operations S310 and S320.
In operation S310, system version information is acquired.
In operation S320, a firmware version corresponding to the system version information is determined as a specific version from among the at least two firmware versions based on the system version information.
According to some embodiments of the present disclosure, in a system start-up state, version information of a current system may be directly read, and a firmware version corresponding to the system version information may be determined as a specific version from the at least two firmware versions based on the system version information.
For example, for TPM 1.2 version and TPM2.0 version, if the version of the current system is read as win7x32, then based on compatibility considerations, only TPM 1.2 version can be determined for use as the particular version.
According to the embodiment of the disclosure, if the setting of the first chip needs to be completed when the electronic device is started, the read system version information may be stored in the nonvolatile storage medium first, and then the system may be restarted. And when the system is restarted, determining one firmware version corresponding to the system version information from the at least two firmware versions as a specific version based on the system version information.
According to an embodiment of the disclosure, the acquiring the system version information includes determining the system version information based on a partition format of the system.
Specifically, the partition format of the system may be, for example, a hard disk partition of MBR (Master Boot Record ) or a hard disk partition of GPT (GUID Partion Table, GUID disk partition table, where GUID is Globally Unique Identifier, globally unique identifier). Since the hard disk partition of the MBR is used by default in the win7 system and the hard disk partition of the GPT is used by default in the higher system, whether to use the TPM version 2.0 can be preliminarily determined by determining whether to be the hard disk partition of the GPT. If the system uses the hard disk partition of the MBR, it needs to further determine whether the system is win7x 64, if yes, the TPM version 2.0 is used, otherwise the TPM version 1.2 is used.
According to the embodiment of the disclosure, the UEFI (Unified Extensible Firmware Interface ) boot must be used in the partition format of the GPT, so it can also be determined whether it is the hard disk partition of the GPT by being the UEFI boot at the time of the electronic device start-up.
According to the method, a firmware version can be automatically determined according to the system version information and written into the first chip, so that user operation is simplified, and user experience is improved.
According to other embodiments of the present disclosure, the firmware version of the first chip may be selected according to user preferences. Operation S210 in other embodiments of the present disclosure is described below with reference to fig. 4.
Fig. 4 schematically illustrates a flow chart of determining one firmware version from at least two firmware versions as a particular version according to another embodiment of the present disclosure.
As shown in fig. 4, the method includes operations S410 and S420.
In operation S410, the user is authenticated.
After the authentication is passed, one firmware version is determined as a specific version from the at least two firmware versions based on the input of the user in operation S420.
According to embodiments of the present disclosure, the electronic device may also provide a way to actively select the firmware version of the first chip. For example, at power-on, the user is prompted to make a selection. Since this content requires a person skilled in the art to set up, the setting by the ordinary user may be due to system incompatibility or other reasons leading to system errors, a process of authenticating the user may be included before the user inputs. Only when the user authentication is passed, one firmware version is allowed to be determined as a specific version from the at least two firmware versions according to the input of the user. The method provides an active way of selecting for a particular person.
Fig. 5 schematically illustrates a flowchart of a firmware version switching method according to another embodiment of the present disclosure.
As shown in fig. 5, the method includes operations S210, S220, and S510 to S550. Operations S210 and S220 are similar to the embodiment illustrated in fig. 2, and will not be repeated here.
In operation S510, it is determined whether the refresh instruction is successfully executed, and in case of successful execution, operation S520 is executed, otherwise operation S530 is executed.
According to embodiments of the present disclosure, the firmware version of the first chip may not be successfully refreshed when the refresh instruction is executed for some unpredictable reasons. Accordingly, in operation S510, it is determined whether the refresh instruction is successfully executed.
In operation S520, basic information of the first chip is configured. According to the embodiment of the disclosure, when the electronic device meets a preset condition, the storage space of the first chip is configured. The method can configure the storage space of the first chip according to the requirements of certain specific electronic equipment.
According to the embodiment of the disclosure, after the firmware version is refreshed, the first chip cannot be directly used, but the updated version needs to be configured correspondingly, for example, the bus type (LPC/SPI/I2C) where the TPM chip is located, various modes (FIPS, lowpower) and the like are configured. In particular, on some specific models, a targeted personalized configuration may also be required, such as configuration of NVRAM storage space of the TPM, etc. The method can automatically configure the first chip after the refresh is successful.
In operation S530, it is determined whether the number of times the refresh command has been executed exceeds a preset value, if not, operation S540 is executed, otherwise, operation S550 is executed.
Since the firmware version of the chip has a limited refresh lifetime, i.e. when the refresh times of the firmware of the chip exceeds a certain threshold, the chip is likely to be damaged in hardware and thus not usable, and thus the refresh times need to be controlled. For example, the first chip is likely to be damaged after 128 times of refreshing, and the maximum number of refreshing times per one change of firmware version information may be set to 5 times. Therefore, at operation S530, it may be judged whether the number of times the refresh instruction has been currently executed exceeds 5 times, if so, operation S540 is executed if not exceeding 5 times, otherwise, operation S550 is executed.
In operation S540, the refresh instruction is executed again. According to an embodiment of the present disclosure, the electronic device is allowed to execute the refresh instruction again, for example, in case no more than 5 times, attempting to refresh the firmware version of the first chip.
In operation S550, an error message is returned, and the flow ends. According to the embodiment of the disclosure, if the version is changed for the time exceeding the prescribed 5 times of refreshing, error information is returned, refreshing is stopped, and the electronic equipment or the user is asked to check the reason, so that rapid damage caused by continuously refreshing the firmware when errors occur is avoided. The method ensures the service life of the chip by limiting the refreshing times when each version is changed.
According to an embodiment of the disclosure, information of at least two firmware versions of the first chip is stored on the BIOS chip.
According to the embodiment of the disclosure, since the information of the firmware version is stored on the BIOS chip, the electronic device can refresh the firmware version of the first chip when being started, and can be configured and validated after being refreshed, so that the need of restarting the system after the version is selected is avoided, and the version updating process is completed.
Fig. 6 schematically illustrates a block diagram of a firmware version switch system 600 according to an embodiment of the disclosure.
As shown in fig. 6, firmware version switch system 600 includes a determination module 610 and an execution module 620.
The determining module 610, for example, performs operation S210 described above with reference to fig. 2, for determining one firmware version from the at least two firmware versions as a specific version.
The execution module 620, for example, executes operation S220 described above with reference to fig. 2, to execute a refresh instruction for writing the specific version of information to the first chip.
Fig. 7 schematically illustrates a block diagram of a determination module 610 according to an embodiment of the disclosure.
As shown in fig. 7, the determination module 610 includes an acquisition sub-module 710 and a first determination sub-module 720.
The acquisition sub-module 710, for example, performs operation S310 described above with reference to fig. 3, for acquiring system version information.
The first determining sub-module 720, for example, performs operation S320 described above with reference to fig. 3, for determining, as a specific version, one firmware version corresponding to the system version information from the at least two firmware versions based on the system version information.
Fig. 8 schematically illustrates a block diagram of a determination module 610 according to another embodiment of the disclosure.
As shown in fig. 8, the determination module 610 includes an authentication submodule 810 and a second determination submodule 820.
The authentication sub-module 810, for example, performs operation S410 described above with reference to fig. 4, for authenticating the user.
The second determining sub-module 820, for example, performs operation S420 described above with reference to fig. 4, for determining one firmware version from the at least two firmware versions as a specific version based on the input of the user after the authentication is passed.
Fig. 9 schematically illustrates a block diagram of a firmware version switch system 900 according to another embodiment of the present disclosure.
As shown in fig. 9, the firmware version switching system includes a determining module 610, an executing module 620, a first judging module 910, a configuring module 920, a second judging module 930, a controlling module 940, and a prompting module 950. The determining module 610 and the executing module 620 are similar to the embodiments shown in fig. 6 to 8, and are not described herein.
The first determining module 910, for example, performs the operation S510 described above with reference to fig. 5, and is configured to determine whether the refresh command is successfully executed.
The configuration module 920, for example, performs operation S520 described above with reference to fig. 5, and is configured to configure basic information of the first chip.
The second determining module 930 is configured to perform, for example, the operation S530 described above with reference to fig. 5, and determine whether the number of times the refresh command has been executed exceeds a preset value.
The control module 940, for example, performs operation S540 described above with reference to fig. 5, for executing the refresh instruction again.
The prompt module 950, for example, performs operation S550 described above with reference to fig. 5, for returning an error message.
It will be appreciated that the above modules may be combined in one module to be implemented, or any one of the modules may be split into a plurality of modules. Alternatively, at least some of the functionality of one or more of the modules may be combined with at least some of the functionality of other modules and implemented in one module. According to embodiments of the invention, at least one of the above-described modules may be implemented at least in part as hardware circuitry, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system-on-chip, a system-on-a-substrate, a system-on-a-package, an Application Specific Integrated Circuit (ASIC), or any other reasonable manner of integrating or packaging circuitry, such as hardware or firmware, or in any suitable combination of three implementations of software, hardware, and firmware. Alternatively, at least one of the above modules may be implemented at least partly as a computer program module, which when executed by a computer may perform the functions of the respective module.
Fig. 10 schematically illustrates a block diagram of an electronic device according to an embodiment of the disclosure.
As shown in fig. 10, the electronic device 1000 includes a processor 1010 and a computer readable storage medium 1020. The electronic device 1000 may perform the methods described above with reference to fig. 2-5 to flexibly switch firmware versions of the first chip, improving the flexibility and applicability of the electronic device.
In particular, the processor 1010 may include, for example, a general purpose microprocessor, an instruction set processor and/or an associated chipset and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. The processor 1010 may also include on-board memory for caching purposes. The processor 1010 may be a single processing unit or a plurality of processing units for performing different actions of the method flows according to embodiments of the present disclosure described with reference to fig. 2-5.
The readable storage medium 1020 may be, for example, any medium capable of containing, storing, transmitting, propagating or transmitting instructions. For example, a readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. Specific examples of the readable storage medium include: magnetic storage devices such as magnetic tape or hard disk (HDD); optical storage devices such as compact discs (CD-ROMs); a memory, such as a Random Access Memory (RAM) or a flash memory; and/or a wired/wireless communication link.
The readable storage medium 1020 may include a computer program 1021, which computer program 1021 may include code/computer executable instructions that when executed by the processor 1010 cause the processor 1010 to perform the method flow described above in connection with fig. 2-5 and any variations thereof.
The computer program 1021 may be configured with computer program code comprising, for example, computer program modules. For example, in an example embodiment, code in the computer program 1021 may include one or more program modules, including 1021A, modules 1021B, … …, for example. It should be noted that the division and number of modules is not fixed, and that a person skilled in the art may use suitable program modules or combinations of program modules according to the actual situation, which when executed by the processor 1010, enable the processor 1010 to perform the method flows and any variations thereof as described above in connection with fig. 2-5.
The processor 1010 may perform the method flows described above in connection with fig. 2-5 and any variations thereof, according to embodiments of the present disclosure.
According to an embodiment of the invention, at least one of the above-described modules may be implemented as a computer program module described with reference to fig. 10, which when executed by the processor 1010, may implement the respective operations described above.
Those skilled in the art will appreciate that the features recited in the various embodiments of the disclosure and/or in the claims may be provided in a variety of combinations and/or combinations, even if such combinations or combinations are not explicitly recited in the disclosure. In particular, the features recited in the various embodiments of the present disclosure and/or the claims may be variously combined and/or combined without departing from the spirit and teachings of the present disclosure. All such combinations and/or combinations fall within the scope of the present disclosure.
While the present disclosure has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents. The scope of the disclosure should, therefore, not be limited to the above-described embodiments, but should be determined not only by the following claims, but also by the equivalents of the following claims.
Claims (7)
1. A firmware version switching method applied to an electronic device, wherein information of at least two firmware versions of a first chip is stored on the electronic device, the method comprising:
determining one firmware version from the at least two firmware versions as a specific version; and
executing a refreshing instruction, wherein the refreshing instruction is used for writing the information of the specific version into the first chip, the information of at least two firmware versions of the first chip is stored on a BIOS chip, and the first chip is a TPM security chip;
wherein said determining a firmware version from said at least two firmware versions as a particular version comprises:
acquiring system version information, wherein the system version information is determined based on a partition format of a system; and
and determining one firmware version corresponding to the system version information from the at least two firmware versions as a specific version based on the system version information.
2. The method of claim 1, wherein the determining one firmware version from the at least two firmware versions as a particular version comprises:
authenticating the user; and
after the authentication is passed, one firmware version is determined as a specific version from the at least two firmware versions based on an input of a user.
3. The method of claim 1, further comprising:
when the refresh instruction fails to execute, judging the number of times that the refresh instruction is executed currently; and
and executing the refreshing instruction again when the times are smaller than a preset value.
4. The method of claim 1, further comprising:
and when the refresh instruction is successfully executed, configuring the basic information of the first chip.
5. The method of claim 4, further comprising:
and when the electronic equipment meets the preset condition, configuring the storage space of the first chip.
6. An electronic device, comprising:
a first chip;
a processor; and
a storage medium storing information of at least two firmware versions of the first chip, and computer readable instructions which, when executed by the processor, cause the processor to perform the method of any of claims 1-5.
7. A BIOS chip having stored thereon information of at least two firmware versions of a first chip, the first chip being a TPM security chip, to allow an electronic device to perform the method of any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711426402.8A CN108121562B (en) | 2017-12-25 | 2017-12-25 | Firmware version switching method, electronic device and BIOS chip |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711426402.8A CN108121562B (en) | 2017-12-25 | 2017-12-25 | Firmware version switching method, electronic device and BIOS chip |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108121562A CN108121562A (en) | 2018-06-05 |
| CN108121562B true CN108121562B (en) | 2024-01-23 |
Family
ID=62231604
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711426402.8A Active CN108121562B (en) | 2017-12-25 | 2017-12-25 | Firmware version switching method, electronic device and BIOS chip |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108121562B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110231946A (en) * | 2019-05-20 | 2019-09-13 | 出门问问信息科技有限公司 | The firmware update and restoration methods of electronic equipment, device, equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1577309A (en) * | 2003-06-30 | 2005-02-09 | 台湾积体电路制造股份有限公司 | Machine automation program update system and method, and computer-readable storage medium |
| CN102567135A (en) * | 2010-12-13 | 2012-07-11 | 联想(北京)有限公司 | Refreshing/recovering method and electronic equipment |
| CN104040424A (en) * | 2011-12-28 | 2014-09-10 | 富士胶片株式会社 | Camera system, camera body and interchangeable lens |
| CN104298526A (en) * | 2014-09-28 | 2015-01-21 | 北京畅游天下网络技术有限公司 | Software updating method and device |
| EP3035644A2 (en) * | 2014-12-15 | 2016-06-22 | Sap Se | Determined configuration update for edge components |
| CN106528097A (en) * | 2016-10-21 | 2017-03-22 | 浙江大华技术股份有限公司 | Version synchronization method for two pieces of BIOS (Basic Input/ Output System) firmware, and electronic equipment |
| CN106843915A (en) * | 2015-12-03 | 2017-06-13 | 比亚迪股份有限公司 | A kind of firmware switching method and apparatus |
-
2017
- 2017-12-25 CN CN201711426402.8A patent/CN108121562B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1577309A (en) * | 2003-06-30 | 2005-02-09 | 台湾积体电路制造股份有限公司 | Machine automation program update system and method, and computer-readable storage medium |
| CN102567135A (en) * | 2010-12-13 | 2012-07-11 | 联想(北京)有限公司 | Refreshing/recovering method and electronic equipment |
| CN104040424A (en) * | 2011-12-28 | 2014-09-10 | 富士胶片株式会社 | Camera system, camera body and interchangeable lens |
| CN104298526A (en) * | 2014-09-28 | 2015-01-21 | 北京畅游天下网络技术有限公司 | Software updating method and device |
| EP3035644A2 (en) * | 2014-12-15 | 2016-06-22 | Sap Se | Determined configuration update for edge components |
| CN106843915A (en) * | 2015-12-03 | 2017-06-13 | 比亚迪股份有限公司 | A kind of firmware switching method and apparatus |
| CN106528097A (en) * | 2016-10-21 | 2017-03-22 | 浙江大华技术股份有限公司 | Version synchronization method for two pieces of BIOS (Basic Input/ Output System) firmware, and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108121562A (en) | 2018-06-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106293507B (en) | Electronic device with external memory and method of operating the same | |
| US9507604B2 (en) | Boot method and boot system | |
| KR101802800B1 (en) | Media protection policy enforcement for multiple-operating-system environments | |
| CN102779050B (en) | The system and method for the guide performance of acceleration is provided | |
| CN105745617B (en) | Selective power management for pre-boot firmware updates | |
| US8489922B2 (en) | Networked recovery system | |
| KR102358470B1 (en) | Boot loader update firmware, method for updating boot loader | |
| CN107463369B (en) | Access device control method and device for virtual desktop | |
| US20120191960A1 (en) | Booting computing devices | |
| CN104603792A (en) | Secure firmware updates | |
| US20180253556A1 (en) | Selective restoration and authentication of a secure image | |
| US9323933B2 (en) | Apparatus and method for selecting and booting an operating system based on path information | |
| US8621195B2 (en) | Disabling communication ports | |
| WO2016062146A1 (en) | Serial number information update method, device and terminal | |
| US8689291B2 (en) | Wireless access device and method | |
| KR20130142073A (en) | Method and terminal for using mobile memory card to boot up mobile phone operating system | |
| CN108984196A (en) | A kind of method for upgrading system and Android TV system set-top box of Android TV system set-top box | |
| US20130080751A1 (en) | Method and device for updating bios program for computer system | |
| CN104951330B (en) | Method for operating multiple operating systems and electronic device thereof | |
| US20150234650A1 (en) | Method of managing firmware and electronic device thereof | |
| CN116028267A (en) | Dual-system secure mobile phone resetting method and device, server and storage medium | |
| CN108121562B (en) | Firmware version switching method, electronic device and BIOS chip | |
| US10007529B2 (en) | Data terminal running mode switching method, device, and data terminal | |
| CN114127685B (en) | Electronic device and control method thereof | |
| US11385705B2 (en) | Display apparatus and operating method thereof |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |