CN114911488B - UEFI firmware LOGO replacement and recovery method based on domestic processor platform - Google Patents
UEFI firmware LOGO replacement and recovery method based on domestic processor platform Download PDFInfo
- Publication number
- CN114911488B CN114911488B CN202210453175.2A CN202210453175A CN114911488B CN 114911488 B CN114911488 B CN 114911488B CN 202210453175 A CN202210453175 A CN 202210453175A CN 114911488 B CN114911488 B CN 114911488B
- Authority
- CN
- China
- Prior art keywords
- logo
- firmware
- picture
- bmp
- file
- 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
- 238000000034 method Methods 0.000 title claims abstract description 31
- 238000011084 recovery Methods 0.000 title abstract description 6
- 230000006870 function Effects 0.000 claims description 5
- 239000003086 colorant Substances 0.000 claims description 3
- 238000002360 preparation method Methods 0.000 claims description 3
- 230000002159 abnormal effect Effects 0.000 description 3
- 238000012360 testing method Methods 0.000 description 3
- 238000006243 chemical reaction Methods 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000000354 decomposition reaction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/63—Image based installation; Cloning; Build to order
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to a UEFI firmware LOGO replacement and recovery method based on a domestic processor platform, and belongs to the field of computers. According to the invention, the space is declared on Flash for storing LOGO pictures during compiling, and when firmware runs, flash is erased and BMP format pictures are written into Flash, 0 is written first and then picture data are written. The invention can replace LOGO pictures when the firmware is started on the premise of not updating the BIOS firmware without being limited by times and sizes. The invention achieves the aim that a user can replace and start LOGO by himself after the product is delivered. The method meets the requirement of conveniently replacing the start LOGO from a firmware provider to a user on the premise of not updating the firmware.
Description
Technical Field
The invention belongs to the field of computers, and particularly relates to a UEFI firmware LOGO replacement and recovery method based on a domestic processor platform.
Background
The computer starts LOGO pictures to be displayed twice, when the firmware performs POST (Power On Self Test, power-on self-test) self-test for the first time, the LOGO pictures compiled into the BIOS (Basic Input Output System ) firmware are displayed on a screen, and the picture content comprises information of a main board manufacturer and the like; and when the second time is to enter the operating system, the LOGO picture integrated in the operating system is displayed on a screen, and the content contains information of the manufacturer of the operating system and the like. The invention designs a method for replacing the starting LOGO and recovering the default starting LOGO in BIOS firmware Setup aiming at the LOGO when the domestic computer firmware is started.
Firmware starts LOGO and can show mainboard manufacturer information when POST, and the customer often needs to change the LOGO picture that accords with self show demand, like the LOGO of customer's company etc.. In the past, a customer provided a LOGO image to be displayed before the product was shipped, and the LOGO image was compiled into firmware by a firmware provider and then burned into a firmware chip. If the firmware needs to be changed to start LOGO, the LOGO picture in the engineering file needs to be replaced, recompilation is performed, and new firmware is burned again; or like foreign x86 platform, edit the picture area in the binary file of firmware by special tool, burn the new firmware again. This has the disadvantage that after the customer takes the firmware file, no convenient LOGO replacement can be performed by himself. And after the firmware is configured and modified, if the firmware is burned again, the default values of the BIOS firmware parameters which meet the operation needs of the client before are easily lost.
In the development of domestic BIOS firmware, the customer's demand frequency for customization and replacement of start-up LOGO is increasing. However, the existing technical solution is based on updating the whole BIOS firmware to replace the start-up LOGO contained in the firmware, and lacks a certain degree of flexibility for the client. The invention aims to write a startup LOGO picture required by a client into a reserved space on Flash without updating BIOS firmware, judge a BMP file identifier of the space during startup, and select to load firmware default LOGO or custom LOGO updated by a user.
Disclosure of Invention
First, the technical problem to be solved
The invention aims to provide a UEFI firmware LOGO replacing and recovering method based on a domestic processor platform, so as to solve the problem that a client lacks a certain flexibility degree based on the prior art scheme of updating the whole BIOS firmware to replace the start LOGO contained in the firmware.
(II) technical scheme
In order to solve the technical problems, the invention provides a UEFI firmware LOGO replacement and recovery method based on a domestic processor platform, which comprises the following steps:
the firmware compiling preparation work comprises the steps of declaring a continuous space in a file defining the size of the firmware, and storing replaced starting LOGO pictures; burning the compiled firmware into Flash;
when the firmware is started, the flow of entering Setup update LOGO is as follows:
s11, when the update start LOGO is selected, firstly judging whether the file suffix is in a BMP format or not and whether the file content contains a BMP format file identifier or not, and determining that the file format and the content meet the standard;
s12, if the file is a BMP picture, declaring a pointer with the same size as the space, and setting the initial value of the pointer to be all 0' through Al locateZeroPool;
s13, copying the BMP picture to the pointer assigned in the S12;
s14, SPI erasing is carried out on the space by the SPI, and at the moment, all byte contents in the area are erased to be 1;
s15, writing all content pointers covered by '0' which exceed the size of the picture data and are covered by BMP picture data in S13 into the Flash space which is erased in S14;
when the method is started normally, whether LOGO is updated or not is judged, and the current priority LOGO picture is displayed:
s21, the LOGO judging priority when the firmware is started is as follows: when a client updates LOGO pictures conforming to the BMP format, the pictures appointed by the client are preferentially displayed;
s22, when the LOGO is not updated in the S21, continuing the drawing flow of the default LOGO by the program for drawing the LOGO picture, and displaying the default LOGO when the firmware is compiled;
s23, when the LOGO is judged to be updated in S21, the program for drawing the LOGO picture continues to update the drawing flow of the LOGO, and the updated LOGO is displayed;
s24, after the LOGO is updated, recovering the default LOGO to erase the new LOGO written on Flash.
Further, defining the file with the size of the firmware as a file fdf, deciding to participate in compiling the file or the data content for the file fdf, compiling to generate binary firmware, and finally burning the binary firmware into Flash; the firmware Layout defined by fdf is certain, so that the address of Flash corresponding to the declared address can be determined.
Further, the continuous space size is 3Mb.
Further, BMP format file identifiers are 'b' and'm'.
Further, in the step S13, the BMP picture read in S11 is copied to the pointer assigned in S12 through CopyMem.
Further, after writing in step S15, the data stored in the space includes BMP format header and picture content that conform to the size of the picture, and all "0" values exceeding the size of the picture, and this partial values will not affect the calculation of RGB colors when the firmware starts drawing the LOGO picture, even if the partial values are read into the pointer of the drawing function.
Further, in step S21, the pointer pointing to the region where the LOGO picture in the Flash corresponding to the space is located is read, the content of the region is parsed according to BMP file header format, and whether the LOGO update is performed is determined according to whether the BMP file identifiers of "b" and "m" are included in the file header.
Further, in the step S24, it is determined whether the BMP file identifier described in S11 is present or not at the time of erasing.
Further, the step S24 further includes: if the default LOGO needs to be recovered, reading SPI erasing minimum units containing the BMP picture file format header on Flash into a memory pointer, only modifying the content of the 54-byte BMP file format header to be 0, and then writing the SPI erasing minimum units.
Further, the SPI erasure minimum unit is 4KB.
(III) beneficial effects
The invention provides a UEFI firmware LOGO replacement and recovery method based on a domestic processor platform, and relates to two technical key points, namely, a declaration space stored on Flash for LOGO pictures during compiling, that is, when firmware runs, flash is erased, and picture data are written after '0' is written when pictures in BMP format are written into Flash.
First, the space declaration of Flash has two requirements: 1. the space occupied is guaranteed not to conflict with other compile-time drive files and not with BIOS firmware content that is dynamically loaded to memory addresses at run-time (e.g., content in NvRam is mapped to an address that is within a firmware mapping address range). 2. The occupied space starts and ends with byte aligned addresses. The two purposes of this are that, on one hand, the written BMP picture data is guaranteed not to influence the normal operation of other drivers of the firmware, and on the other hand, byte alignment is needed when the BMP picture is read from Flash to involve data exceeding the Mb level.
Secondly, when the firmware runs to Setup to replace the LOGO picture, a full '0' pointer with the same size as the defined picture storage area needs to be declared first, and then the read BMP picture data is filled in the pointer. The reason for this is that when Flash is erased by SPI, there is a limit to the size of the data area to be read/written each time, and although there is a difference in implementation of each drive, it is basically impossible to write byte by byte. And the Flash is erased and written through the SPI, the erased area is all '1', and if the space exceeding the size of the picture is not written with all '0'. After the erasing is successful, when the firmware is started again, a value of '1' exceeding the size range of the picture may be read into a pointer for drawing LOGO, and the picture drawn on the screen may have abnormal display (such as a white horizontal bar and the like).
The invention provides and realizes a firmware starting LOGO replacing method based on Flash reading and writing aiming at domestic firmware by combining with the current method for updating firmware starting LOGO. The method can replace LOGO pictures when the firmware is started on the premise of not updating the BIOS firmware without being limited by times and sizes. The purpose that a user can replace and start LOGO by himself after the product is delivered is achieved. The method meets the requirement of conveniently replacing the start LOGO from a firmware provider to a user on the premise of not updating the firmware.
Drawings
FIG. 1 is a flow chart of a UEFI firmware LOGO replacement and restoration method based on a domestic processor platform.
Detailed Description
To make the objects, contents and advantages of the present invention more apparent, the following detailed description of the present invention will be given with reference to the accompanying drawings and examples.
Aiming at the domestic computer platform, after the basic function driving module is added, the domestic computer firmware chip space is still partially undeveloped and utilized, and according to the size of the residual space of the firmware Flash, a section of continuous address space can be declared on the firmware Flash for storing BMP picture data. By utilizing the characteristic that Flash can be read and written, the option of erasing the above area is set under Setup for updating the BMP picture data stored on Flash. Since the firmware content is mapped to a fixed memory address at start-up, the BMP picture written after update can be read at the fixed offset address and drawn on the screen.
When the firmware is started, judging whether the address for storing the LOGO picture contains a file identifier of the BMP format picture in a program for drawing the LOGO: if yes, indicating that the user performs LOGO picture updating, reading data of the user into a pointer for drawing a LOGO program; otherwise, the default LOGO at firmware compile time is displayed normally. In addition, if the user selects to restore the firmware default LOGO after updating the LOGO, the data of the BMP file header part of the LOGO picture is covered by 0, and the BMP file information cannot be acquired during starting so as to restore the default LOGO display.
The following decomposition descriptions are made for the embodiments of the present invention:
firstly, firmware compiling preparation work:
1) A contiguous space of 3Mb size is declared in the file defining the firmware size (. Fdf) for storing the replaced boot LOGO picture. Fdf the files are decided to participate in the compiled files or data content, binary firmware is generated through compiling, and finally the binary firmware is burnt into Flash. Since the firmware Layout defined by fdf is certain, the address of Flash to which the asserted address corresponds can be determined. The space has exclusivity: firstly, the address can not be allocated when the application uses the memory space, and secondly, the address can not be allocated when the application uses the memory space;
2) Burning the compiled firmware into Flash;
when the firmware is started, the flow of entering Setup update LOGO is as follows:
s11, when the update start LOGO is selected, firstly judging whether the file suffix is in a BMP format, and whether the file content contains BMP format file identifiers such as 'b' and'm', and determining that the file format and the content meet the standard;
s12, if the file in S11 is a BMP picture, declaring a pointer which is equal to the space size (3 Mb) defined in 1), and setting the initial value of the pointer to be all 0' through Al locateZeroPool;
the purpose of assigning an all "0" initial value to the pointer declared in S12 is to ensure that the non-BMP picture data portion will not be misused after writing into Flash. The reason is that the Nor Flash chip reads based on the standard SPI 'erase before write' operation, 4K alignment is needed during writing, for the content exceeding the upper limit of the definition space in the BMP image itself but smaller than 1), the value is still 0xFF after the execution of the 'erase before erase' operation, and when the LOGO image is drawn, the BMP file format conversion interface function ConvertetBumpToGopBlt provided by the EDK can erroneously calculate 0xFF when RGB color conversion is carried out, so that abnormal strip lines appear at the edge part of the image when the LOGO is drawn;
s13, copying the BMP picture read in the S11 into a pointer assigned in the S12 through a copyMem;
s14, SPI erasing is carried out on the space defined in the step 1), and at the moment, all byte contents in the area are erased to be 1;
s15, writing all 3Mb content pointers covered by '0' and exceeding the size of the picture data in the BMP picture data and the picture data in the S13 into the Flash space after erasing in the S14. At this time, the data stored in the space includes BMP format header and picture content conforming to the size of the picture, and all "0" values exceeding the size of the picture, and this partial values will not affect the calculation of RGB colors even if read into the pointer of the drawing function when the firmware starts drawing the LOGO picture;
when the method is started normally, whether LOGO is updated or not is judged, and the current priority LOGO picture is displayed:
because the invention adopts a scheme that updated LOGO and LOGO added in compiling coexist, judgment is needed when the LOGO is drawn;
s21, the LOGO judging priority when the firmware is started is as follows: when the client updates the LOGO picture conforming to the BMP format, the picture appointed by the client is preferentially displayed. Reading a pointer of an area where a LOGO picture is located in a Flash corresponding to the space defined in the pointing 1), analyzing the content of the pointer according to a BMP file header format, and judging whether LOGO updating is performed according to whether the file header contains BMP file identifiers (signatures) of 'b' and'm';
s22, when the LOGO is not updated in the S21, continuing the drawing flow of the default LOGO by the program for drawing the LOGO picture, and displaying the default LOGO when the firmware is compiled;
s23, when the LOGO is judged to be updated in S21, the program for drawing the LOGO picture continues to update the drawing flow of the LOGO, and the updated LOGO is displayed;
s24, after the LOGO is updated, the default LOGO can be selected to be recovered to erase the new LOGO written on Flash. When erasing, it is also judged whether or not the BMP file identifier of ' b'm ' or the like described in S11 is present;
s25, if the default LOGO needs to be recovered, reading SPI erasing minimum units (4 KB) containing the BMP picture file format header on Flash into a memory pointer, only modifying the content of the 54-byte BMP file format header to be 0, and then writing the SPI erasing minimum units. Because the BMP picture stored in Flash is judged to pass through the BMP file header when starting in the step S21, the writing time can be saved, and the default firmware starting LOGO can be quickly recovered.
The invention relates to two technical key points, namely, a space is declared on Flash for storing LOGO pictures during compiling, and when firmware runs, flash is erased and BMP format pictures are written into Flash, then picture data are written in 0.
First, the space declaration of Flash has two requirements: 1. the space occupied is guaranteed not to conflict with other compile-time drive files and not with BIOS firmware content that is dynamically loaded to memory addresses at run-time (e.g., content in NvRam is mapped to an address that is within a firmware mapping address range). 2. The occupied space starts and ends with byte aligned addresses. The two purposes of this are that, on one hand, the written BMP picture data is guaranteed not to influence the normal operation of other drivers of the firmware, and on the other hand, byte alignment is needed when the BMP picture is read from Flash to involve data exceeding the Mb level.
Secondly, when the firmware runs to Setup to replace the LOGO picture, a full '0' pointer with the same size as the defined picture storage area needs to be declared first, and then the read BMP picture data is filled in the pointer. The reason for this is that when Flash is erased by SPI, there is a limit to the size of the data area to be read/written each time, and although there is a difference in implementation of each drive, it is basically impossible to write byte by byte. And the Flash is erased and written through the SPI, the erased area is all '1', and if the space exceeding the size of the picture is not written with all '0'. After the erasing is successful, when the firmware is started again, a value of '1' exceeding the size range of the picture may be read into a pointer for drawing LOGO, and the picture drawn on the screen may have abnormal display (such as a white horizontal bar and the like).
The invention provides and realizes a firmware starting LOGO replacing method based on Flash reading and writing aiming at domestic firmware by combining with the current method for updating firmware starting LOGO. The method can replace LOGO pictures when the firmware is started on the premise of not updating the BIOS firmware without being limited by times and sizes. The purpose that a user can replace and start LOGO by himself after the product is delivered is achieved. The method meets the requirement of conveniently replacing the start LOGO from a firmware provider to a user on the premise of not updating the firmware.
The foregoing is merely a preferred embodiment of the present invention, and it should be noted that modifications and variations could be made by those skilled in the art without departing from the technical principles of the present invention, and such modifications and variations should also be regarded as being within the scope of the invention.
Claims (10)
1. The UEFI firmware LOGO replacing and recovering method based on the domestic processor platform is characterized by comprising the following steps:
the firmware compiling preparation work comprises the steps of declaring a continuous space in a file defining the size of the firmware, and storing replaced starting LOGO pictures; burning the compiled firmware into Flash;
when the firmware is started, the flow of entering Setup update LOGO is as follows:
s11, when the update start LOGO is selected, firstly judging whether the file suffix is in a BMP format or not and whether the file content contains a BMP format file identifier or not, and determining that the file format and the content meet the standard;
s12, if the file is a BMP picture, declaring a pointer with the same size as the space, and setting the initial value of the pointer to be all 0' through AllocateZeroPool;
s13, copying the BMP picture to the pointer assigned in the S12;
s14, SPI erasing is carried out on the space by the SPI, and at the moment, all byte contents in the area are erased to be 1;
s15, writing all content pointers covered by '0' which exceed the size of the picture data and are covered by BMP picture data in S13 into the Flash space which is erased in S14;
when the method is started normally, whether LOGO is updated or not is judged, and the current priority LOGO picture is displayed:
s21, the LOGO judging priority when the firmware is started is as follows: when a client updates LOGO pictures conforming to the BMP format, the pictures appointed by the client are preferentially displayed;
s22, when the LOGO is not updated in the S21, continuing the drawing flow of the default LOGO by the program for drawing the LOGO picture, and displaying the default LOGO when the firmware is compiled;
s23, when the LOGO is judged to be updated in S21, the program for drawing the LOGO picture continues to update the drawing flow of the LOGO, and the updated LOGO is displayed;
s24, after the LOGO is updated, recovering the default LOGO to erase the new LOGO written on Flash.
2. The method for replacing and recovering UEFI firmware LOGO based on the domestic processor platform according to claim 1, wherein the file with the defined firmware size is a file fdf, and the file fdf is decided to participate in compiling the file or the data content, and binary firmware is generated through compiling and finally burnt in Flash; the firmware Layout defined by fdf is certain, so that the address of Flash corresponding to the declared address can be determined.
3. The UEFI firmware LOGO replacement and restoration method based on a domestic processor platform of claim 2, wherein the continuous space size is 3Mb.
4. The UEFI firmware LOGO replacement and restoration method based on a domestic processor platform of claim 1, wherein BMP format file identifiers are 'b' and'm'.
5. The method for replacing and recovering the UEFI firmware LOGO based on the domestic processor platform as claimed in claim 1, wherein in the step S13, the BMP picture read in the step S11 is copied into the pointer assigned in the step S12 through CopyMem.
6. The method according to any one of claims 1-5, wherein after writing in step S15, the data stored in the space includes BMP format header and picture content corresponding to the size of the picture, and a value of all "0" exceeding the size of the picture, which does not affect the calculation of RGB colors even if the data is read into the pointer of the drawing function when the firmware starts drawing the LOGO picture.
7. The method for replacing and recovering the UEFI firmware LOGO based on the domestic processor platform according to claim 1, wherein in step S21, a pointer pointing to an area where the LOGO picture in the Flash corresponding to the space is located is read, the content is parsed according to BMP file header format, and whether LOGO updating is performed is judged according to whether the BMP file header contains BMP file identifiers of "b" and "m".
8. The method for replacing and recovering UEFI firmware LOGO based on the domestic processor platform as claimed in claim 7, wherein in said step S24, it is determined whether the BMP file identifier described in S11 is present or not when the user erases the UEFI firmware LOGO.
9. The UEFI firmware LOGO replacement and restoration method based on the domestic processor platform of claim 8, further comprising, after step S24: if the default LOGO needs to be recovered, reading SPI erasing minimum units containing the BMP picture file format header on Flash into a memory pointer, only modifying the content of the 54-byte BMP file format header to be 0, and then writing the SPI erasing minimum units.
10. The UEFI firmware LOGO replacement and restoration method based on a domestic processor platform of claim 9, wherein the SPI erasure minimum unit is 4KB.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210453175.2A CN114911488B (en) | 2022-04-27 | 2022-04-27 | UEFI firmware LOGO replacement and recovery method based on domestic processor platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210453175.2A CN114911488B (en) | 2022-04-27 | 2022-04-27 | UEFI firmware LOGO replacement and recovery method based on domestic processor platform |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114911488A CN114911488A (en) | 2022-08-16 |
| CN114911488B true CN114911488B (en) | 2024-04-09 |
Family
ID=82764767
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210453175.2A Active CN114911488B (en) | 2022-04-27 | 2022-04-27 | UEFI firmware LOGO replacement and recovery method based on domestic processor platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114911488B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103207797A (en) * | 2013-03-15 | 2013-07-17 | 南京工业大学 | Capsule type customized updating method based on universal extensible firmware interface firmware system |
| CN104133796A (en) * | 2014-08-15 | 2014-11-05 | 广东欧珀移动通信有限公司 | Method and device for coding and decoding image in smart mobile terminal LK |
| CN104778052A (en) * | 2014-01-14 | 2015-07-15 | 深圳中电长城信息安全系统有限公司 | Method and device for flashing firmware program and startup logo |
| CN105320553A (en) * | 2015-12-07 | 2016-02-10 | 浪潮集团有限公司 | Method and system for updating network card firmware based on domestic processor platform |
| CN112800429A (en) * | 2021-01-28 | 2021-05-14 | 北京工业大学 | Method for protecting driver in UEFI BIOS firmware system based on foundation |
| CN113626822A (en) * | 2021-06-28 | 2021-11-09 | 苏州浪潮智能科技有限公司 | UEFI (unified extensible firmware interface) firmware starting method and device integrating Linux |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10871955B2 (en) * | 2018-02-08 | 2020-12-22 | Insyde Software Corp. | System and method for providing firmware data updates |
-
2022
- 2022-04-27 CN CN202210453175.2A patent/CN114911488B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103207797A (en) * | 2013-03-15 | 2013-07-17 | 南京工业大学 | Capsule type customized updating method based on universal extensible firmware interface firmware system |
| CN104778052A (en) * | 2014-01-14 | 2015-07-15 | 深圳中电长城信息安全系统有限公司 | Method and device for flashing firmware program and startup logo |
| CN104133796A (en) * | 2014-08-15 | 2014-11-05 | 广东欧珀移动通信有限公司 | Method and device for coding and decoding image in smart mobile terminal LK |
| CN105320553A (en) * | 2015-12-07 | 2016-02-10 | 浪潮集团有限公司 | Method and system for updating network card firmware based on domestic processor platform |
| CN112800429A (en) * | 2021-01-28 | 2021-05-14 | 北京工业大学 | Method for protecting driver in UEFI BIOS firmware system based on foundation |
| CN113626822A (en) * | 2021-06-28 | 2021-11-09 | 苏州浪潮智能科技有限公司 | UEFI (unified extensible firmware interface) firmware starting method and device integrating Linux |
Non-Patent Citations (2)
| Title |
|---|
| UEFI计算机系统快速调试方法的实现;高云岭;杨国栋;郭元兴;;信息安全与通信保密;20120710(第07期);全文 * |
| 基于ARM7 STM32控制点阵液晶屏的设计;吕鹏;栾童童;;橡塑技术与装备;20151215(第24期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114911488A (en) | 2022-08-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3491519B1 (en) | Optimized uefi reboot process | |
| US5522076A (en) | Computer system having BIOS (basic input/output system)-ROM (Read Only Memory) writing function | |
| US6167511A (en) | Method to reflect BIOS set up changes into ACPI machine language | |
| US20040230963A1 (en) | Method for updating firmware in an operating system agnostic manner | |
| US20040162930A1 (en) | Highly componentized system architecture with loadable virtual memory manager | |
| KR20010006749A (en) | Storing system-level mass storage configuration data in non-volatile memory on each mass storage device to allow for reboot/power-on reconfiguration of all installed mass storage devices to the same configuration as last use | |
| JP2002525701A (en) | Method and apparatus for standardizing the use of non-volatile storage in BIOS-ROM | |
| US20070101115A1 (en) | Information processing device, bios processing method and program | |
| US6637023B1 (en) | Method and system for updating read-only software modules | |
| CN114756296B (en) | Readable-writable mounting starting method and device, storage medium and electronic equipment | |
| JP2004070946A (en) | System and method using vendor-long descriptor in acpi for ceccsr | |
| US9489209B2 (en) | Bios graphical setup engine | |
| CN113741792B (en) | Method for storing data by singlechip, singlechip and readable storage medium | |
| CN116009921A (en) | Method, device and medium for upgrading embedded operating system | |
| CN114911488B (en) | UEFI firmware LOGO replacement and recovery method based on domestic processor platform | |
| CN111241008B (en) | Method, device and controller for correcting EEPROM variable and address | |
| CN114127685A (en) | Electronic device and control method thereof | |
| CN116560739A (en) | Boot sign customization method, device, equipment and storage medium | |
| CN110825421A (en) | Firmware upgrading method and system and readable storage medium | |
| JPH06324857A (en) | Computer system | |
| CN112130789B (en) | Method for converting insufficient space of RAM (random Access memory) in chip into flash storage in chip | |
| KR20030060342A (en) | Booting method for personal digital assistant | |
| CN101408845B (en) | Updating method and related updating system | |
| JP2008009494A (en) | Image forming device | |
| CN111813454A (en) | Electronic device, startup picture display method and computer readable storage medium |
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 |