CN103207797A - Capsule type customized updating method based on universal extensible firmware interface firmware system - Google Patents
Capsule type customized updating method based on universal extensible firmware interface firmware system Download PDFInfo
- Publication number
- CN103207797A CN103207797A CN2013100839591A CN201310083959A CN103207797A CN 103207797 A CN103207797 A CN 103207797A CN 2013100839591 A CN2013100839591 A CN 2013100839591A CN 201310083959 A CN201310083959 A CN 201310083959A CN 103207797 A CN103207797 A CN 103207797A
- Authority
- CN
- China
- Prior art keywords
- firmware
- capsule
- uefi
- file
- fixer
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 239000002775 capsule Substances 0.000 title claims abstract description 55
- 238000000034 method Methods 0.000 title claims abstract description 30
- 230000015654 memory Effects 0.000 claims description 14
- 238000011161 development Methods 0.000 claims description 5
- 239000000284 extract Substances 0.000 claims description 2
- 238000012795 verification Methods 0.000 claims description 2
- 238000002360 preparation method Methods 0.000 claims 1
- 238000005516 engineering process Methods 0.000 abstract description 8
- 230000007246 mechanism Effects 0.000 abstract description 6
- 238000011084 recovery Methods 0.000 abstract description 4
- 230000008901 benefit Effects 0.000 abstract description 3
- 238000007796 conventional method Methods 0.000 abstract 1
- 230000006870 function Effects 0.000 description 5
- 230000005540 biological transmission Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 230000018109 developmental process Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 2
- 101100016034 Nicotiana tabacum APIC gene Proteins 0.000 description 1
- 230000005856 abnormality Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 239000007963 capsule composition Substances 0.000 description 1
- 230000002860 competitive effect Effects 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000004069 differentiation Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000033772 system development Effects 0.000 description 1
- 230000009897 systematic effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The invention provides a Capsule type customized updating method based on a universal extensible firmware interface firmware system, which is based on a Capsule mechanism of a universal extensible firmware interface UEFI firmware system, gets rid of the dependence of the current mainstream firmware updating technology on system management interrupt SMI drive, obtains a firmware volume FV module to be updated by analyzing the Capsule, identifies the FV module, and writes the acquired data into a target address of a firmware file system, thereby realizing the updating of the selected FV and getting rid of the conventional method of updating the whole BIOS. The Capsule mechanism solves the problem that the updating tools cannot be unified on different hardware platforms and operating systems. The firmware updating method has the advantages of flexibility and high application value. The method can be applied to the aspects of firmware remote refreshing, firmware automatic recovery and the like.
Description
Technical field
The invention belongs to the software upgrading technical field of computer software engineering technology, specifically refer to the capsule-type customization update method based on general Extensible Firmware Interface fixer system.
Background technology
Along with cloud computing etc. is used deeply based on the related service of internet, the client firmware customization becomes new application focus in the fields such as card Securities, finance, telecommunications.Such as embedded products such as the network equipment and self-assistant information service terminals, need make equipment have unique function rather than as multi-purpose computer, come work.Therefore the system development merchant seeks just day by day by increasing more characteristic, so that product has differentiation and obtain competitive edge, and fixer system is strengthen this specific character desirable local.As user interface, guide fast and increase special function etc.But the problem that the singularity of these industries is brought thereupon is that the firmware renewal is more frequent, yet present firmware renewal technology refreshes at whole Basic Input or Output System (BIOS) (BIOS).And in the actual application, only need be to certain part drives among the BIOS, application module upgrades or add and just can meet the demands, traditional firmware update mode inefficiency that seems in this case.
Present update mechanism needs CPU to support SMM (System Management Mode) System Management Mode.Entering the SMM pattern is to be caused by look-at-me SMI, and SMI by processor SMI# pin signal effectively or receive the message of advanced programmable controller APIC bus.It is maskable external interrupt and be independent of other interruption and abnormality processing not.When processor is checked through SMI, wait for that all instructions are carried out and memory access deposits the current processor context in after finishing and cuts SMM pattern execution SMI handling procedure among the SMRAM then.Adopt the support that SMI drives among the BIOS that places one's entire reliance upon of the method for refreshing of this technology, so the success ratio that refreshes of the reliability effect firmware of SMI driver.
The prior art feature introduction that the present invention relates to:
UEFI: be used for software interface between defining operation system and the system firmware, the interface of being responsible for Power-On Self-Test, attended operation system and attended operation system and hardware being provided.The UEFI framework has the advantages such as support of the programming of C language, modular design, graphic interface, file system.The UEFI technology has incorporated many characteristics of embedded OS, the device drives development model (EFI Driver Model) that oneself is arranged as UEFI, reduced the burden that hardware vendor's development equipment drives on the one hand, on the other hand, for different hardware devices provides extendible interface.In addition, UEFI has own shell (UEFI Shell), and the developer can develop application program miscellaneous.The UEFI standard is divided into before the os starting: safeguard protection stage (SEC), context initialization phase (PEI), driving execution environment stage (DXE) and guiding device choice phase (BDS) four-stage; describe in detail system from power up, processor initialization, hardware initialization, judgement start the path, system strategy is set, user's configuration interface, to the detailed process that enters operating system.
Capsule: the skimble-scamble problem of interface when carrying out data transmission in order to solve different operating system and fixer system, UEFI has defined a kind of data structure of variable-length.Allow in operating system, data to be passed to the UEFI firmware by it, realize as functions such as modification BIOS parameters.The UEFI standard calls Capsule to the data structure of this type of variable-length.
Firmware binaries file after UEFI firmware file system (Firmware File System): the UEFI compiling is called FD (Firmware Device) file, and it is made up of a series of firmware volume FV (Firmware Volume).FV mainly contains two types: system FV, and its purpose is mainly deposited firmware code, as hardware driving, application program; Non-volatile memories FV is mainly used in storage system variable, configuration file, daily record etc.The appearance of firmware file system make can be in limited firmware stores space memory module driving file more effectively.
EDK II: be up-to-date BIOS development platform framework.
Flash: the storer of preserving UEFI firmware file system.
Tradition firmware renewal technology exists hardware platform, refresh tool and can't unify between different platform, can not customize renewal to specifying firmware driving, firmware application programs; The conventional brush new mechanism depends critically upon system management interrupt SMI(System Management Interrupt among the BIOS) support that drives, so the success ratio that refreshes of the reliability effect firmware of SMI driver.
Summary of the invention
Technical matters to be solved by this invention is to overcome the deficiencies in the prior art, proposes the capsule-type customization update method based on general Extensible Firmware Interface fixer system; The Capsule standard that described method utilizes UEFI to provide is identified firmware volume FV module in firmware layer, the data of obtaining is write the method for firmware file aims of systems address, and do not need entire flash is upgraded.This technology can solve traditional firmware hardware, operating system are relied on problem, realizes the renewal of appointed function module, and practicality is stronger.
In order to solve the problems of the technologies described above, the technical solution adopted in the present invention is:
Based on the capsule-type customization update method of general Extensible Firmware Interface fixer system, described capsule Capsule formula customization update method is divided into two parts: refresh routine in refresh routine, the UEFI fixer system under the operating system; Described method comprises the steps:
Steps A is utilized Extensible Firmware Interface Development Framework EDK II compiling standard, and the firmware volume FV module that needs are upgraded compiles, and firmware volume FV is packaged into capsule Capsule;
Step B, refresh routine finds the position of firmware volume FV among the Capsule under the operating system by capsule Capsule header structure body, judge whether that according to the current free memory situation of system needs carry out piecemeal to Capsule, piecemeal then is divided into littler data cell capsule SubCapsule if desired, and is each capsule SubCapsule storage allocation space, unit;
Step C, refresh routine arranges computing machine and enters the S3 sleep state under the operating system, wakes up by the real-time clock setting, enters the UEFI fixer system, utilize the characteristics that internal storage data is not lost in the computing machine sleep state, the unit capsule SubCapsule in the UEFI fixer system access memory;
Step D, the UEFI fixer system was identified and merge cells capsule SubCapsule in the context initialization PEI stage, obtain complete capsule Capsule, location address and the relevant information such as size of the Capsule after merging in internal memory write handing-over piece HOB (Hand-off Block) chained list;
Step e, the UEFI fixer system is driving the execution environment DXE stage, utilizes handing-over piece HOB chained list to resolve Capsule, extracts the FV module that is kept at wherein, the verification by FV and judge whether FV is legal, and read wherein driving or application program;
Step F is called the driving that drives the execution environment DXE stage among the UEFI and is distributed loading Dispatch to serve, and the dependence between judgement drives is found and execution UEFI firmware renewal driving according to correct order;
Step G, the UEFI firmware upgrades to drive and reads firmware image location of content figure Flash map, obtain firmware volume FV to be updated positional information in firmware binaries file FD, last UEFI firmware upgrades to drive firmware volume FV module to be updated in the internal memory is write among the firmware binaries file FD.
In the described steps A, described Extensible Firmware Interface Development Framework EDK II compiling standard is the FD file by the firmware binaries file after this standard compiling, and described FD file comprises firmware volume FV, and described FV is the elementary cell of storage code and data; The position of each FV in the firmware binaries file is described by firmware image location of content figure Flash Map.
Among the described step C, described handing-over piece HOB chained list is one group of data block, and this data block is used for data are delivered to the execution environment DXE stage that drives from the initialization preparation layer PEI stage.
The invention has the beneficial effects as follows: the present invention proposes the capsule-type customization update method based on general Extensible Firmware Interface fixer system, described method is based on the capsule Capsule mechanism of general Extensible Firmware Interface UEFI fixer system, break away from present main flow firmware renewal technology and relied on system management interrupt SMI driving, by Capsule is resolved, obtain firmware volume FV module to be updated, and the FV module identified, the data of obtaining are write firmware file aims of systems address, thereby realize selected FV is upgraded, broken away from needs whole BIOS method for updating in the past.Capsule mechanism has solved the problem that more new tool can't be unified on different hardware platforms, operating system.This firmware update has more dirigibility, using value height.Can be applicable to aspects such as firmware remote reflash, the automatic recovery of firmware.
Description of drawings
Fig. 1 is renewal process flow diagram of the present invention.
Fig. 2 is renewal frame diagram of the present invention.
Embodiment
Below in conjunction with accompanying drawing, the capsule-type customization update method based on general Extensible Firmware Interface fixer system that the present invention is proposed is elaborated:
The present invention is based on the capsule-type customization update method of general Extensible Firmware Interface fixer system, Fig. 1 is the renewal process flow diagram of described method, and by EDK II compiling standard, the FV module that needs are upgraded compiles, and FV is packaged into Capsule.In UEFI fixer system start-up course, Capsule is resolved, and obtain start address and the size of FV in Flash, thereby reach the designing requirement that selected FV is upgraded.Concrete steps are as follows:
Step (1): according to EDK II compiling standard, the FV module that needs are upgraded compiles, and FV is packaged into Capsule.
Step (2): refresh routine finds the position of firmware volume FV among the Capsule under the operating system by Capsule header structure body member, judge whether needs are carried out piecemeal to Capsule according to the current free memory situation of system, then be divided into littler data cell SubCapsule if desired, and be each data cell SubCapsule storage allocation space.
Step (3): computing machine is set enters the S3 sleep state, utilize the characteristics that internal storage data is not lost in the sleep state, wake back PC up and enter the UEFI fixer system.
Step (4): utilize the characteristics that internal storage data is not lost in the sleep state, wake back PC up and enter the UEFI fixer system, and merging the SubCapsule piece in the stage at subsequently PEI, make its recovery become a complete Capsule, location address and the size of the Capsule after merging in internal memory write handing-over piece HOB (Hand-off Block) chained list.
Step (5): the UEFI fixer system enters into the DXE stage.Remove to handle Capsule by parameters such as address in internal memory of the Capsule that from the HOB chained list, obtains, sizes, the FV that is kept at is wherein therefrom separated.Call the power function of UEFI FV is further resolved, effect and CheckSum by verification FV judge whether FV is legal, and reading and saving driving, application program therein.
Step (6): call DXE service Dispatch among the UEFI, this driving is added in the doubly linked list, and by judging the dependence between driving, the UEFI firmware that satisfies service requirement is upgraded driving add in the driving chained list of UEFI system, calculate entry address and the operation of driving by the traversal chained list.
Step (7): the UEFI firmware upgrades to drive and reads firmware image location of content figure Flash map, obtain FV to be updated relevant information such as position in Flash, and call the Device ID that FLASH chip supported protocol removes to attempt reading Flash, obtain corresponding Flash read-write and drive, call UEFI firmware renewal driving at last FV module to be updated in the internal memory is write Flash.
Transmission has following advantage based on the Capsule specification data: transmission mode between different operating system and the fixer system is unified; Data read is finished in fixer system, prevents unwarranted operational access under the operating system, improves security; Being not limited to variable informations such as systematic parameter in the data in the Capsule bag, also can be the executive routine in the UEFI fixer system, and it is more flexible that it is compared with other transmission modes.
Fig. 2 has provided the process synoptic diagram of this update method from operating system to the UEFI fixer system, as shown in the figure: under the operating system more new tool Capsule is carried out piecemeal, be each unit capsule SubCapsule storage allocation; Refresh routine arranges computing machine and enters the S3 sleep state under the operating system, and by real-time clock waking-up, computing machine enters the UEFI fixer system; Identify and merge cells capsule SubCapsule in the PEI stage of UEFI fixer system, obtain complete capsule Capsule; The UEFI fixer system enters the DXE stage, and resolve Capsule and extract the firmware volume FV module that is kept at wherein, and driving, the application program of reading and saving in firmware volume; Load and move the UEFI firmware that reads and upgrade driving, firmware volume FV module to be updated in the internal memory is write firmware binaries file FD.
The present invention can utilize Capsule mechanism to solve the problem that more new tool can't be unified on different hardware platforms, operating system effectively to specifying the FV module to upgrade.This firmware update has more dirigibility, using value height.Can be applicable to aspects such as firmware remote reflash, the automatic recovery of firmware.
Claims (3)
1. based on the capsule-type customization update method of general Extensible Firmware Interface fixer system, it is characterized in that this capsule-type customization update method comprises two parts: refresh routine in refresh routine, the UEFI fixer system under the operating system; Described method comprises the steps:
Steps A is utilized Extensible Firmware Interface Development Framework EDK II compiling standard, and the firmware volume FV module that needs are upgraded compiles, and firmware volume FV is packaged into capsule Capsule;
Step B, refresh routine finds the position of firmware volume FV among the Capsule under the operating system by capsule Capsule header structure body, judge whether that according to the current free memory situation of system needs carry out piecemeal to Capsule, piecemeal then is divided into littler data cell capsule SubCapsule if desired, and is each capsule SubCapsule storage allocation space, unit;
Step C, refresh routine arranges computing machine and enters the S3 sleep state under the operating system, wakes up by the real-time clock setting, enters the UEFI fixer system, the unit capsule SubCapsule in the UEFI fixer system access memory;
Step D, the UEFI fixer system enters the context initialization PEI stage, and identification and merge cells capsule SubCapsule obtain complete capsule Capsule, and location address and the size of the Capsule after merging in internal memory write handing-over piece HOB chained list;
Step e, the UEFI fixer system is driving the execution environment DXE stage, utilizes handing-over piece HOB chained list, resolves Capsule, extracts the FV module that is kept at wherein, the verification by FV and judge whether FV is legal, and read wherein driving or application program;
Step F is called the driving that drives the execution environment DXE stage among the UEFI and is distributed loading Dispatch to serve, and the dependence between judgement drives is found and execution UEFI firmware renewal driving according to correct order;
Step G, UEFI firmware upgrade to drive and read firmware image location of content figure Flash map, obtain the positional information of firmware volume FV to be updated in firmware binaries file FD, and firmware volume FV module to be updated in the internal memory is write among the firmware binaries file FD.
2. the capsule-type based on general Extensible Firmware Interface fixer system according to claim 1 customizes update method, it is characterized in that, in the steps A, described Extensible Firmware Interface Development Framework EDK II compiling standard, be the FD file by the firmware binaries file after the compiling of this standard, described FD file comprises firmware volume FV, and described FV is the elementary cell of storage code and data; The position of each FV in the firmware binaries file described by firmware image location of content figure Flash Map.
3. the capsule-type based on general Extensible Firmware Interface fixer system according to claim 1 customizes update method, it is characterized in that, among the step C, described handing-over piece HOB chained list is one group of data block, and this data block is used for data are delivered to the execution environment DXE stage that drives from the initialization preparation layer PEI stage.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201310083959 CN103207797B (en) | 2013-03-15 | 2013-03-15 | Capsule type customized updating method based on universal extensible firmware interface firmware system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 201310083959 CN103207797B (en) | 2013-03-15 | 2013-03-15 | Capsule type customized updating method based on universal extensible firmware interface firmware system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103207797A true CN103207797A (en) | 2013-07-17 |
| CN103207797B CN103207797B (en) | 2013-11-27 |
Family
ID=48755028
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 201310083959 Active CN103207797B (en) | 2013-03-15 | 2013-03-15 | Capsule type customized updating method based on universal extensible firmware interface firmware system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103207797B (en) |
Cited By (25)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104573529A (en) * | 2015-01-28 | 2015-04-29 | 加弘科技咨询(上海)有限公司 | BIOS firmware dividing and updating method and system |
| CN104572165A (en) * | 2014-03-21 | 2015-04-29 | 中电科技（北京）有限公司 | UEFI (Unified Extensible Firmware Interface) firmware implementation method based on Feiteng server |
| CN104572061A (en) * | 2014-03-21 | 2015-04-29 | 中电科技（北京）有限公司 | UEFI (Unified Extensible Firmware Interface) firmware implementation method based on Loongson server |
| CN104572166A (en) * | 2014-03-21 | 2015-04-29 | 中电科技（北京）有限公司 | UEFI (Unified Extensible Firmware Interface) firmware implementation method based on Feiteng desk computer |
| CN104572164A (en) * | 2014-03-21 | 2015-04-29 | 中电科技（北京）有限公司 | UEFI (Unified Extensible Firmware Interface) firmware implementation method based on Feiteng portable computer |
| CN104915280A (en) * | 2015-06-03 | 2015-09-16 | 浪潮集团有限公司 | Method for acquiring computer hardware information based on UEFI (unified extensible firmware interface) driving mode |
| CN106201608A (en) * | 2016-07-01 | 2016-12-07 | 南京百敖软件有限公司 | Computer UEFI firmware update |
| CN106909351A (en) * | 2015-12-22 | 2017-06-30 | 中电科技（北京）有限公司 | A kind of implementation method of the EXT file system based on UEFI firmwares |
| CN107423068A (en) * | 2017-07-31 | 2017-12-01 | 山东超越数控电子有限公司 | The method that a variety of file system are realized in UEFI BIOS |
| CN107463412A (en) * | 2017-08-17 | 2017-12-12 | 郑州云海信息技术有限公司 | A kind of method and device of upgrading BIOS |
| CN107463408A (en) * | 2017-08-11 | 2017-12-12 | 郑州云海信息技术有限公司 | The method and device of clearing password is prevented during a kind of upgrading BIOS |
| CN108399076A (en) * | 2018-03-02 | 2018-08-14 | 山东超越数控电子股份有限公司 | A kind of firmware update and device based on UEFI |
| CN108536453A (en) * | 2017-03-03 | 2018-09-14 | 台湾聚引移动有限公司 | The method of the unified Extensible Firmware Interface firmware of update |
| CN108845834A (en) * | 2018-06-01 | 2018-11-20 | 上海兆芯集成电路有限公司 | Computer installation |
| CN109478135A (en) * | 2016-07-28 | 2019-03-15 | 微软技术许可有限责任公司 | The UEFI of optimization reboots process |
| CN109472131A (en) * | 2018-11-09 | 2019-03-15 | 济南浪潮高新科技投资发展有限公司 | A kind of capsule-type UEFI firmware remote-control method based on BMC with safety certification |
| CN109992517A (en) * | 2019-04-03 | 2019-07-09 | 中电科技（北京）有限公司 | Firmware module adjustment method and system based on UEFI |
| CN110363011A (en) * | 2019-07-19 | 2019-10-22 | 腾讯科技（深圳）有限公司 | Method and apparatus for verifying the safety of the BIOS based on UEFI |
| WO2020000947A1 (en) * | 2018-06-29 | 2020-01-02 | 郑州云海信息技术有限公司 | Method, apparatus, and device for refreshing encapsulated bios data |
| CN112231477A (en) * | 2020-10-20 | 2021-01-15 | 淮阴工学院 | Text classification method based on improved capsule network |
| WO2022036670A1 (en) * | 2020-08-21 | 2022-02-24 | Intel Corporation | Methods and apparatus to perform an enhanced s3 protocol to update firmware with a boot script update |
| CN114611109A (en) * | 2022-01-06 | 2022-06-10 | 四川大学 | UEFI (unified extensible firmware interface) firmware security audit method based on single classification |
| CN114911488A (en) * | 2022-04-27 | 2022-08-16 | 北京计算机技术及应用研究所 | UEFI (unified extensible firmware interface) firmware LOGO replacing and recovering method based on domestic processor platform |
| CN115328629A (en) * | 2022-08-11 | 2022-11-11 | 江苏卓易信息科技股份有限公司 | Method for performing real-time embedded management by expanding UEFI (unified extensible firmware interface) firmware on bare metal |
| WO2023102799A1 (en) * | 2021-12-09 | 2023-06-15 | Intel Corporation | Firmware apparatus, device, method and computer program |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070300050A1 (en) * | 2006-06-08 | 2007-12-27 | Zimmer Vincent J | Maintaining early hardware configuration state |
| CN102541606A (en) * | 2011-12-31 | 2012-07-04 | 曙光信息产业股份有限公司 | Method and device for remote management of BIOS (basic input/output system) configuration based on UEFI (unified extensible firmware interface |
| CN102567550A (en) * | 2011-12-31 | 2012-07-11 | 曙光信息产业股份有限公司 | Method and device for collecting data of emergency event in operating system (OS) |
-
2013
- 2013-03-15 CN CN 201310083959 patent/CN103207797B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070300050A1 (en) * | 2006-06-08 | 2007-12-27 | Zimmer Vincent J | Maintaining early hardware configuration state |
| CN102541606A (en) * | 2011-12-31 | 2012-07-04 | 曙光信息产业股份有限公司 | Method and device for remote management of BIOS (basic input/output system) configuration based on UEFI (unified extensible firmware interface |
| CN102567550A (en) * | 2011-12-31 | 2012-07-11 | 曙光信息产业股份有限公司 | Method and device for collecting data of emergency event in operating system (OS) |
Cited By (30)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104572165B (en) * | 2014-03-21 | 2017-10-27 | 中电科技（北京）有限公司 | A kind of UEFI firmware implementation methods based on FT server |
| CN104572165A (en) * | 2014-03-21 | 2015-04-29 | 中电科技（北京）有限公司 | UEFI (Unified Extensible Firmware Interface) firmware implementation method based on Feiteng server |
| CN104572061A (en) * | 2014-03-21 | 2015-04-29 | 中电科技（北京）有限公司 | UEFI (Unified Extensible Firmware Interface) firmware implementation method based on Loongson server |
| CN104572166A (en) * | 2014-03-21 | 2015-04-29 | 中电科技（北京）有限公司 | UEFI (Unified Extensible Firmware Interface) firmware implementation method based on Feiteng desk computer |
| CN104572164A (en) * | 2014-03-21 | 2015-04-29 | 中电科技（北京）有限公司 | UEFI (Unified Extensible Firmware Interface) firmware implementation method based on Feiteng portable computer |
| CN104573529A (en) * | 2015-01-28 | 2015-04-29 | 加弘科技咨询(上海)有限公司 | BIOS firmware dividing and updating method and system |
| CN104915280A (en) * | 2015-06-03 | 2015-09-16 | 浪潮集团有限公司 | Method for acquiring computer hardware information based on UEFI (unified extensible firmware interface) driving mode |
| CN106909351A (en) * | 2015-12-22 | 2017-06-30 | 中电科技（北京）有限公司 | A kind of implementation method of the EXT file system based on UEFI firmwares |
| CN106201608A (en) * | 2016-07-01 | 2016-12-07 | 南京百敖软件有限公司 | Computer UEFI firmware update |
| CN109478135A (en) * | 2016-07-28 | 2019-03-15 | 微软技术许可有限责任公司 | The UEFI of optimization reboots process |
| CN108536453A (en) * | 2017-03-03 | 2018-09-14 | 台湾聚引移动有限公司 | The method of the unified Extensible Firmware Interface firmware of update |
| CN107423068A (en) * | 2017-07-31 | 2017-12-01 | 山东超越数控电子有限公司 | The method that a variety of file system are realized in UEFI BIOS |
| CN107463408A (en) * | 2017-08-11 | 2017-12-12 | 郑州云海信息技术有限公司 | The method and device of clearing password is prevented during a kind of upgrading BIOS |
| CN107463412A (en) * | 2017-08-17 | 2017-12-12 | 郑州云海信息技术有限公司 | A kind of method and device of upgrading BIOS |
| CN108399076A (en) * | 2018-03-02 | 2018-08-14 | 山东超越数控电子股份有限公司 | A kind of firmware update and device based on UEFI |
| CN108845834A (en) * | 2018-06-01 | 2018-11-20 | 上海兆芯集成电路有限公司 | Computer installation |
| WO2020000947A1 (en) * | 2018-06-29 | 2020-01-02 | 郑州云海信息技术有限公司 | Method, apparatus, and device for refreshing encapsulated bios data |
| CN109472131A (en) * | 2018-11-09 | 2019-03-15 | 济南浪潮高新科技投资发展有限公司 | A kind of capsule-type UEFI firmware remote-control method based on BMC with safety certification |
| CN109992517A (en) * | 2019-04-03 | 2019-07-09 | 中电科技（北京）有限公司 | Firmware module adjustment method and system based on UEFI |
| CN109992517B (en) * | 2019-04-03 | 2023-12-26 | 昆仑太科(北京)技术股份有限公司 | UEFI-based firmware module debugging method and system |
| CN110363011A (en) * | 2019-07-19 | 2019-10-22 | 腾讯科技（深圳）有限公司 | Method and apparatus for verifying the safety of the BIOS based on UEFI |
| CN110363011B (en) * | 2019-07-19 | 2024-05-07 | 腾讯科技（深圳）有限公司 | Method and apparatus for verifying security of UEFI-based BIOS |
| WO2022036670A1 (en) * | 2020-08-21 | 2022-02-24 | Intel Corporation | Methods and apparatus to perform an enhanced s3 protocol to update firmware with a boot script update |
| CN112231477A (en) * | 2020-10-20 | 2021-01-15 | 淮阴工学院 | Text classification method based on improved capsule network |
| CN112231477B (en) * | 2020-10-20 | 2023-09-22 | 淮阴工学院 | Text classification method based on improved capsule network |
| WO2023102799A1 (en) * | 2021-12-09 | 2023-06-15 | Intel Corporation | Firmware apparatus, device, method and computer program |
| CN114611109A (en) * | 2022-01-06 | 2022-06-10 | 四川大学 | UEFI (unified extensible firmware interface) firmware security audit method based on single classification |
| CN114911488A (en) * | 2022-04-27 | 2022-08-16 | 北京计算机技术及应用研究所 | UEFI (unified extensible firmware interface) firmware LOGO replacing and recovering method based on domestic processor platform |
| CN114911488B (en) * | 2022-04-27 | 2024-04-09 | 北京计算机技术及应用研究所 | UEFI firmware LOGO replacement and recovery method based on domestic processor platform |
| CN115328629A (en) * | 2022-08-11 | 2022-11-11 | 江苏卓易信息科技股份有限公司 | Method for performing real-time embedded management by expanding UEFI (unified extensible firmware interface) firmware on bare metal |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103207797B (en) | 2013-11-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103207797B (en) | Capsule type customized updating method based on universal extensible firmware interface firmware system | |
| CN102236621B (en) | Computer interface information configuration system and method | |
| US9558016B2 (en) | Platform system, method for changing support hardware configuration of universal extensible firmware interface basic input output system and computer program product | |
| CN105579953B (en) | Flexible boot code framework | |
| CN109478135A (en) | The UEFI of optimization reboots process | |
| CN105814541B (en) | The method of computer equipment and computer equipment internal storage starting | |
| CN101573687B (en) | Reconfiguring a secure system | |
| CN102073520A (en) | Dynamic management system and method for C++ application program version | |
| CN105930186B (en) | The method for loading software of multi -CPU and software loading apparatus based on multi -CPU | |
| CN104572164A (en) | UEFI (Unified Extensible Firmware Interface) firmware implementation method based on Feiteng portable computer | |
| US20160210141A1 (en) | Hot-Swapping Operating Systems Using Inter-Partition Application Migration | |
| CN102662717A (en) | Bootstrap starting method of embedded system | |
| CN103853586A (en) | Method of realizing wireless card driver in UEFI (unified extensible firmware interface) layer | |
| CN104572165A (en) | UEFI (Unified Extensible Firmware Interface) firmware implementation method based on Feiteng server | |
| CN104156234A (en) | Multi-core processor starting and bootloader big-little endian mode adapting method device | |
| CN104111857A (en) | Method for automatically configuring parameters of multi-model BIOS | |
| CN108874458A (en) | A kind of the firmware starting method and multicore SoC device of multicore SoC | |
| CN106201608A (en) | Computer UEFI firmware update | |
| CN108021405A (en) | The driving method and device of storage medium in a kind of SOC system starting process | |
| CN104137074A (en) | Optimization of resource usage in a multi-environment computing system | |
| CN110515671A (en) | Initial method, apparatus for initializing, terminal device and readable storage medium storing program for executing | |
| CN104714792A (en) | Multi-process shared data processing method and device | |
| CN106126211A (en) | A kind of MCU In-circuit programming system supporting debugging interface | |
| CN106155682A (en) | A kind of linux system based on SDMA controller starts method and system | |
| CN105354066A (en) | OTA (over the air) downloading method and device and intelligent terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |