CN101739266A - Firmware updating method - Google Patents
Firmware updating method Download PDFInfo
- Publication number
- CN101739266A CN101739266A CN200810178371A CN200810178371A CN101739266A CN 101739266 A CN101739266 A CN 101739266A CN 200810178371 A CN200810178371 A CN 200810178371A CN 200810178371 A CN200810178371 A CN 200810178371A CN 101739266 A CN101739266 A CN 101739266A
- Authority
- CN
- China
- Prior art keywords
- information block
- block
- information
- bios
- version
- 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
- 238000000034 method Methods 0.000 title abstract description 12
- 238000012360 testing method Methods 0.000 abstract description 3
- 238000012545 processing Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 8
- 238000013507 mapping Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 239000000758 substrate Substances 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The invention discloses a firmware updating method which comprises the following steps: providing a basic input/output system (BIOS) which comprises a first information block; providing a baseboard management controller (BMC) firmware which comprises a second information block corresponding to the first information block; then, when the BIOS executes power on self test (POST), recognizing system hardware information and judging whether the second information block is in line with the system hardware information or not; if the second information block is not in line with the system hardware information, updating the second information block by the BIOS according to the content of the first information block; if the second information block is in line with the system hardware information, further judging the advancement of the versions of the first information block and the second information block by the BIOS; and if the version of the first information block is more advanced than the version of the second information block, updating the second information block by the BIOS according to the content of the first information block.
Description
Technical field
The present invention relates to a kind of firmware update, particularly relate to and a kind ofly can be simultaneously baseboard management controller firmware and Basic Input or Output System (BIOS) be made the firmware update that upgrades.
Background technology
For server, baseboard management controller (Baseboard Management Controller, BMC) become stronger day by day for the function of system management, baseboard management controller and Basic Input or Output System (BIOS) (Basic InputOutput System, BIOS) cooperation between is also tight day by day, the considerable monitor task of baseboard management controller needs the cooperation of Basic Input or Output System (BIOS) just can finish, and this just needs to cooperatively interact between both firmware.
But, because being independently, writes by the code of baseboard management controller firmware and Basic Input or Output System (BIOS), therefore,, just must upgrade another person's appropriate section simultaneously in case upgrade both wherein appropriate sections.On the one hand, because baseboard management controller firmware and Basic Input or Output System (BIOS) code is different, need provide both renewal versions respectively; On the other hand, both upgrade respectively by needs, in renewal process, in case omitted wherein one renewal, will cause both can't cooperate operation, the problem that generation can't be expected.
Summary of the invention
The invention provides a kind of firmware update, utilize and upgrade the baseboard management controller firmware, upgrade sensitive information record block and configuration block in the Basic Input or Output System (BIOS) simultaneously, when avoiding changing dissimilar central processing units, the sensitive information recorded information of legacy version and configuration info can cover the sensitive information recorded information and the configuration info of redaction.
The present invention proposes a kind of firmware update, and its Bao draws together Xia Lie Bu Sudden.Basic Input or Output System (BIOS) is provided, and it comprises first information block.The baseboard management controller firmware is provided, and it comprises the second information block, and is corresponding with first information block.Now, Basic Input or Output System (BIOS) when carrying out the start selftest, the recognition system hardware information, judge the second information block whether with the system hardware information conforms.If the second information block and system hardware information do not meet, Basic Input or Output System (BIOS) is according to the content update second information block of first information block.If the second information block and system hardware information conforms, Basic Input or Output System (BIOS) is further judged the new and old of the first information block and the second information block version.If the version of first information block is newly in the version of the second information block, Basic Input or Output System (BIOS) is according to the content update second information block of first information block.
In one embodiment of this invention, the further Bao of this firmware update draws together Xia Lie Bu Sudden: the refresh routine of carrying out baseboard management controller; Judge version new and old of the version of the second information block and first information block; If the version of the second information block then upgrades the first information block and the second information block simultaneously newly in the version of first information block; And if the version of the second information block not newly in the version of first information block, does not then upgrade first information block.
In one embodiment of this invention, the first information block and the second information block comprise sensitive information record (Sensor Data Record, SDR) block.
In one embodiment of this invention, the first information block and the second information block comprise configuration (Configuration) block.
Comprehensive the above, when the version of baseboard management controller firmware during, when the baseboard management controller firmware is done to upgrade, can upgrade sensitive information record block and configuration block in the Basic Input or Output System (BIOS) in the lump newly in Basic Input or Output System (BIOS).By this, can avoid when changing dissimilar central processing units the sensitive information recorded information and the configuration info that can override redaction with the sensitive information recorded information and the configuration info of legacy version.
Above-mentioned explanation only is the general introduction of technical solution of the present invention, for can clearer understanding technological means of the present invention, and can be implemented according to the content of instructions, below with preferred embodiment of the present invention and conjunction with figs. describe in detail as after.
Description of drawings
Fig. 1 is the firmware block synoptic diagram of baseboard management controller and Basic Input or Output System (BIOS) according to an embodiment of the invention.
Fig. 2 is firmware update process flow diagram according to an embodiment of the invention.
Fig. 3 is firmware update process flow diagram according to another embodiment of the present invention.
Embodiment
(Baseboard Management Controller, BMC) firmware (firmware) is as a whole, and all codes are all write together for baseboard management controller in the past.(Basic Input Output System BIOS), is exactly with its " modularization " and the present invention at first takes a kind of brand-new mode to write baseboard management controller firmware and Basic Input or Output System (BIOS).
Fig. 1 is the firmware block synoptic diagram of baseboard management controller and Basic Input or Output System (BIOS) according to an embodiment of the invention.Baseboard management controller firmware 120 and Basic Input or Output System (BIOS) 110 all have sensitive information record block 130 and configuration block 140.Wherein, baseboard management controller firmware image groove is decomposed into the several separate part, be respectively merged file (Combined file) block and information block, wherein the information block can be divided into sensitive information log file (Sensor Data Record file) block and configuration file (Configuration file) block again.Wherein, merged file is made up of general type code (Generic code), be responsible for most of basic functions of baseboard management controller, and these functions and system platform has nothing to do, and therefore no matter can directly bring use future on any platform.In addition two parts be used for memory substrate Management Controller respectively configuration info and deposit the sensitive information recorded information, and these two parts are closely bound up with the platform of server.And Basic Input or Output System (BIOS) comprises the information block simultaneously, and is corresponding with the information block of baseboard management controller firmware mapping file.The information block of Basic Input or Output System (BIOS) is divided into sensitive information log file block and configuration file block equally, and is corresponding respectively with the sensitive information log file block and the configuration file block of baseboard management controller firmware.And the content of above-mentioned configuration file block is deposited in the configuration block 140, and the content of sensitive information log file block is deposited in the sensitive information record block 130.
Be example with a kind of server master board of the central processing unit that can support a plurality of series and the sensitive information of central processing unit thereof below, firmware update of the present invention is described.
In the central processing unit that this mainboard is supported, wherein the part central processing unit is to use the voltage of 1.1V, other central processing unit then is to use the voltage of 1.2V, therefore in order to make the monitoring voltage that sensor can be correct just need use different sensitive information records according to different CPU types, (Basic Input Output System, cooperation BIOS) just can be finished and this action just needs baseboard management controller and Basic Input or Output System (BIOS).Therefore the present invention keeps the sensitive information log file simultaneously in Basic Input or Output System (BIOS) and baseboard management controller, so that all can have sensitive information record block in Basic Input or Output System (BIOS) and baseboard management controller firmware.
Firmware update of the present invention comprises two parts: go to upgrade the step of baseboard management controller firmware and the step of going to upgrade Basic Input or Output System (BIOS) according to the baseboard management controller firmware according to Basic Input or Output System (BIOS).
According to the step of updating BIOS baseboard management controller firmware, it can be as described in the following method.Fig. 2 is firmware update process flow diagram according to an embodiment of the invention.Please refer to Fig. 2, shown in step S201, provide Basic Input or Output System (BIOS), it comprises first information block, and wherein this first information block can write down block or configuration block for sensitive information.Shown in step S202, the baseboard management controller firmware is provided, it comprises the second information block, the second information block is corresponding with first information block.Then, in step S203, at start selftest (Power On Self Test, POST) in the process, Basic Input or Output System (BIOS) is removed recognition system hardware information (for example CPU type), and judge the second information block (is example with sensitive information record block) whether with the system hardware information conforms.
If the current sensitive information record block of system hardware information and baseboard management controller does not meet, that is the judged result of step S203 is a "No", execution in step S204 then, Basic Input or Output System (BIOS) will write down block with the sensitive information that the content in its sensitive information record block goes to upgrade in the baseboard management controller firmware, makes it can be applicable to current system hardware (for example central processing unit).If the current sensitive information record of CPU type and baseboard management controller meets, that is the judged result of step S203 is "Yes", and then execution in step S205 is new and old with the version of sensitive information block in further judgement Basic Input or Output System (BIOS) and the baseboard management controller firmware.If the version of the first information block of Basic Input or Output System (BIOS) (that is sensitive information record block) is newer, then execution in step S206 is to go the content in the sensitive information record block of Basic Input or Output System (BIOS) to upgrade the sensitive information record block in the baseboard management controller firmware; Otherwise, then finish this firmware update.
In the process of start selftest, as shown in Figure 1, Basic Input or Output System (BIOS) 110 has absolute control, and the sensitive information that whether upgrades baseboard management controller firmware 120 with decision writes down block 130, and baseboard management controller then is in and is subjected to the status.Therefore, when the record of the sensitive information in the baseboard management controller 120 block version writes down the new words of block than the sensitive information in the Basic Input or Output System (BIOS) 110, then in the process of start selftest, do not remove to upgrade the sensitive information record block in the baseboard management controller 120, cover in order to avoid the record of the sensitive information in the newer baseboard management controller 120 of version block is compared old version, but still can't solve the baseboard management controller firmware and the Basic Input or Output System (BIOS) sensitive information writes down the conforming problem of block version.Wherein, the execution sequence of step S201 and S202 for convenience of description, but not in order to the restriction embodiments of the invention, that is the execution sequence of step S201 and S202 can exchange, and do not hinder the enforcement of present embodiment.
Newly go into the problem of sensitive information block version in the Lose Chu Xi System firmware in basic Lose for the further sensitive information block version that solves in the baseboard management controller, firmware update of the present invention further comprises the step of going to upgrade Basic Input or Output System (BIOS) according to the baseboard management controller firmware, as shown in Figure 3, specifically comprise:
At first shown in step S301, carry out baseboard management controller firmware update program.Then, version new and old that sensitive information writes down block (that is second information block) in the step S302 version that can judge the record block of sensitive information in the baseboard management controller (that is first information block) and the Basic Input or Output System (BIOS).If in the baseboard management controller firmware version of sensitive information record block new in Basic Input or Output System (BIOS) the version of sensitive information record block, execution in step S303 then is to upgrade sensitive information record block in the Basic Input or Output System (BIOS) simultaneously.If the non-version of sensitive information record block in Basic Input or Output System (BIOS) newly of sensitive information record block in the baseboard management controller, then execution in step S304 does not upgrade sensitive information record block in the Basic Input or Output System (BIOS).
For instance,, just must upgrade, with the problem of revising baseboard management controller and increase its function the baseboard management controller firmware when the baseboard management controller firmware pushes away when bringing out a new edition.Then, can carry out the refresh routine of baseboard management controller, the firmware mapping file of redaction be write in the baseboard management controller firmware, with the action that the baseboard management controller firmware is upgraded.After the firmware image groove writes the baseboard management controller firmware, the version of sensitive information record block in record block of the sensitive information in the firmware mapping file and the Basic Input or Output System (BIOS) can be made comparisons, newer so which to be judged.The version of supposing the record of sensitive information in firmware mapping file block is newer, then sensitive information is write down block and writes sensitive information record block in the Basic Input or Output System (BIOS), with the synchronous renewal information block relevant with baseboard management controller.If the version of sensitive information record block is not newer in the firmware mapping file, then sensitive information record block in the Basic Input or Output System (BIOS) is not upgraded.
In addition, after firmware mapping file writes the baseboard management controller firmware, also can utilize making comparisons in the version of the record of sensitive information in baseboard management controller firmware block and the Basic Input or Output System (BIOS).If the version of sensitive information record block is new in Basic Input or Output System (BIOS) in the baseboard management controller firmware, the record of the sensitive information in Basic Input or Output System (BIOS) block then utilize the content of the record of sensitive information in baseboard management controller firmware block to cover sensitive information record block in the Basic Input or Output System (BIOS), so that can upgrade synchronously; Otherwise, then do not upgrade.
What deserves to be mentioned is, above-mentioned refresh routine, can be undertaken by the updating software that the substrate dealer is provided, perhaps write batch file and carry out the renewal of baseboard management controller firmware, it can be had by this area knows the knowledgeable or substrate kind and different usually, can finish present embodiment by these method for updating equally.Person more, the comparison of the foregoing description firmware version and the order that writes thereof, also can know that usually the knowledgeable changes with territory, this area, also can compare earlier, write Basic Input or Output System (BIOS) then, write the baseboard management controller firmware again, perhaps earlier relatively, write the baseboard management controller firmware then, write Basic Input or Output System (BIOS) again.
So far, in the Basic Input or Output System (BIOS) version of sensitive information record block be bound to identical with version in the baseboard management controller firmware, perhaps new version in the baseboard management controller firmware.As long as at first carried out the step of going to upgrade Basic Input or Output System (BIOS) according to the baseboard management controller firmware, so when changing dissimilar central processing units, because sensitive information record block is bound to equal or new version in the baseboard management controller firmware in the Basic Input or Output System (BIOS), so when Basic Input or Output System (BIOS) is upgraded the sensitive information record block of baseboard management controller firmware in the self-testing process of start, just can be directly upgrade version in the baseboard management controller, and can not have the inconsistent and insurmountable problem of both versions according to the version of the sensitive information record block of Basic Input or Output System (BIOS).
The above, central processing unit only is an example, can also be other hardware on the mainboard, such as internal memory etc.; And sensitive information record block also only is one of them example of information block, and it can also be the configuration block, and the combination of sensitive information record block and configuration block, and its updating steps is basic identical, does not repeat them here.In addition, be to carry out the step of removing to upgrade the baseboard management controller firmware according to Basic Input or Output System (BIOS) earlier, still carry out the step of going to upgrade Basic Input or Output System (BIOS) according to the baseboard management controller firmware earlier, can go to select according to actual conditions.
The above, it only is preferred embodiment of the present invention, be not that the present invention is done any pro forma restriction, though the present invention discloses as above with preferred embodiment, yet be not in order to limit the present invention, any those skilled in the art, in not breaking away from the technical solution of the present invention scope, when the structure that can utilize above-mentioned announcement and technology contents are made a little change or be modified to the equivalent embodiment of equivalent variations, but every content that does not break away from technical solution of the present invention, according to technical spirit of the present invention to any simple modification that above embodiment did, equivalent variations and modification all still belong in the scope of technical solution of the present invention.
Claims (4)
1. firmware update is characterized in that comprising:
One Basic Input or Output System (BIOS) is provided, comprises a first information block;
One baseboard management controller firmware is provided, comprises one second information block, corresponding with this first information block;
This Basic Input or Output System (BIOS) when carrying out the start selftest, the recognition system hardware information, judge this second information block whether with this system hardware information conforms;
If this second information block and this system hardware information do not meet, this Basic Input or Output System (BIOS) is according to this second information block of content update of this first information block;
If this second information block and this system hardware information conforms, this Basic Input or Output System (BIOS) is further judged the new and old of this first information block and this second information block version; And
If the version of this first information block is newly in the version of this second information block, this Basic Input or Output System (BIOS) is according to this second information block of content update of this first information block.
2. firmware update according to claim 1 is characterized in that further comprising:
Carry out the refresh routine of this baseboard management controller;
Judge version new and old of the version of this second information block and this first information block;
If the version of this second information block newly in the version of first information block, then upgrades this first information block and this second information block simultaneously; And
If the version of this second information block does not then upgrade this first information block not newly in the version of this first information block.
3. firmware update according to claim 1 and 2 is characterized in that this first information block and this second information block comprise sensitive information record block.
4. firmware update according to claim 1 and 2 is characterized in that this first information block and this second information block comprise the configuration block.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200810178371 CN101739266B (en) | 2008-11-27 | 2008-11-27 | Firmware updating method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200810178371 CN101739266B (en) | 2008-11-27 | 2008-11-27 | Firmware updating method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101739266A true CN101739266A (en) | 2010-06-16 |
| CN101739266B CN101739266B (en) | 2013-05-15 |
Family
ID=42462792
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 200810178371 Expired - Fee Related CN101739266B (en) | 2008-11-27 | 2008-11-27 | Firmware updating method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101739266B (en) |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102779057A (en) * | 2012-06-29 | 2012-11-14 | 浪潮(北京)电子信息产业有限公司 | Base board management controller and automatic upgrade system and method thereof |
| CN102811436A (en) * | 2011-06-03 | 2012-12-05 | 联想(北京)有限公司 | Firmware updating method and device |
| CN103092735A (en) * | 2011-10-28 | 2013-05-08 | 英业达科技有限公司 | Method for updating node states |
| CN103138974A (en) * | 2011-11-28 | 2013-06-05 | 英业达科技有限公司 | Server rack system of managing rotating speeds of fan |
| CN103136019A (en) * | 2011-11-29 | 2013-06-05 | 国际商业机器公司 | Method and device used for uploading configuration information |
| CN103246583A (en) * | 2012-02-09 | 2013-08-14 | 鸿富锦精密工业（深圳）有限公司 | Electronic device with bulk molding compound (BMC) firmware repairing function and repairing method |
| CN103412775A (en) * | 2013-08-12 | 2013-11-27 | 浪潮电子信息产业股份有限公司 | Method for refreshing BMC firmware intelligently and automatically |
| CN103513999A (en) * | 2012-06-25 | 2014-01-15 | 联想(北京)有限公司 | Electronic device and method for updating system firmware |
| CN104516757A (en) * | 2013-09-26 | 2015-04-15 | 纬创资通股份有限公司 | Firmware updating method |
| CN105955857A (en) * | 2016-04-29 | 2016-09-21 | 浪潮电子信息产业股份有限公司 | Method and device for testing BIOS (Basic Input Output System) |
| CN106445577A (en) * | 2015-08-12 | 2017-02-22 | 广达电脑股份有限公司 | Updating method, server system and non-transitory computer readable medium |
| CN103685404B (en) * | 2012-09-17 | 2017-03-08 | 英业达科技有限公司 | Network service system and its method updating firmware |
| CN106484474A (en) * | 2016-10-09 | 2017-03-08 | 合肥联宝信息技术有限公司 | Firmware upgrade method, device and computer |
| CN113900934A (en) * | 2021-09-29 | 2022-01-07 | 苏州浪潮智能科技有限公司 | Multi-mirror mixed refresh test method, system, terminal and storage medium |
| TWI775360B (en) * | 2021-03-23 | 2022-08-21 | 宏碁股份有限公司 | Storage device for recording status of hardware component of computer system and computer implementation method thereof |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101295255B (en) * | 2007-04-27 | 2011-05-18 | 英业达股份有限公司 | Firmware updating system and method |
-
2008
- 2008-11-27 CN CN 200810178371 patent/CN101739266B/en not_active Expired - Fee Related
Cited By (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102811436A (en) * | 2011-06-03 | 2012-12-05 | 联想(北京)有限公司 | Firmware updating method and device |
| CN102811436B (en) * | 2011-06-03 | 2017-06-27 | 联想(北京)有限公司 | A kind of firmware update and device |
| CN103092735A (en) * | 2011-10-28 | 2013-05-08 | 英业达科技有限公司 | Method for updating node states |
| CN103138974A (en) * | 2011-11-28 | 2013-06-05 | 英业达科技有限公司 | Server rack system of managing rotating speeds of fan |
| CN103136019A (en) * | 2011-11-29 | 2013-06-05 | 国际商业机器公司 | Method and device used for uploading configuration information |
| CN103246583A (en) * | 2012-02-09 | 2013-08-14 | 鸿富锦精密工业（深圳）有限公司 | Electronic device with bulk molding compound (BMC) firmware repairing function and repairing method |
| CN103513999A (en) * | 2012-06-25 | 2014-01-15 | 联想(北京)有限公司 | Electronic device and method for updating system firmware |
| CN102779057A (en) * | 2012-06-29 | 2012-11-14 | 浪潮(北京)电子信息产业有限公司 | Base board management controller and automatic upgrade system and method thereof |
| CN103685404B (en) * | 2012-09-17 | 2017-03-08 | 英业达科技有限公司 | Network service system and its method updating firmware |
| CN103412775A (en) * | 2013-08-12 | 2013-11-27 | 浪潮电子信息产业股份有限公司 | Method for refreshing BMC firmware intelligently and automatically |
| CN104516757A (en) * | 2013-09-26 | 2015-04-15 | 纬创资通股份有限公司 | Firmware updating method |
| CN106445577A (en) * | 2015-08-12 | 2017-02-22 | 广达电脑股份有限公司 | Updating method, server system and non-transitory computer readable medium |
| CN105955857A (en) * | 2016-04-29 | 2016-09-21 | 浪潮电子信息产业股份有限公司 | Method and device for testing BIOS (Basic Input Output System) |
| CN106484474A (en) * | 2016-10-09 | 2017-03-08 | 合肥联宝信息技术有限公司 | Firmware upgrade method, device and computer |
| TWI775360B (en) * | 2021-03-23 | 2022-08-21 | 宏碁股份有限公司 | Storage device for recording status of hardware component of computer system and computer implementation method thereof |
| CN113900934A (en) * | 2021-09-29 | 2022-01-07 | 苏州浪潮智能科技有限公司 | Multi-mirror mixed refresh test method, system, terminal and storage medium |
| CN113900934B (en) * | 2021-09-29 | 2024-01-12 | 苏州浪潮智能科技有限公司 | Multi-mirror hybrid refresh test method, system, terminal and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101739266B (en) | 2013-05-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101739266B (en) | Firmware updating method | |
| US10599538B2 (en) | Usage profile based recommendations | |
| US8423991B2 (en) | Embedded network device and firmware upgrading method | |
| US20200272450A1 (en) | Software updating apparatus, vehicle, and software updating method | |
| US20030051235A1 (en) | Method and apparatus for verifying and analyzing computer software installation | |
| US9075695B2 (en) | Version conflict checking to installable unit | |
| CN109933348A (en) | The update method and device of Bootloader in a kind of electronic control unit | |
| CN101556634B (en) | Method and system for managing and controlling using authority of external apparatus | |
| CN103577201A (en) | Embedded dual system updating method and system | |
| CN102308280B (en) | Basic input/output system BIOS configuration data management method and system | |
| CN110515641A (en) | The update method of server firmware, apparatus and system | |
| US7765439B2 (en) | Traceability management apparatus, storage medium storing program, and tracing method | |
| CN105700919A (en) | BMS application rapid update method and update system | |
| CN102750109A (en) | Data synchronization system and method | |
| CN103455750B (en) | The high peace verification method of a kind of embedded device and device | |
| CN103365684A (en) | Updating method and multi-domain embedded system | |
| TW201734762A (en) | Data loading method and motherboard | |
| CN106648441A (en) | Method and device for transferring equipment partition information | |
| CN115421750A (en) | Method, device, terminal and storage medium for noninductive upgrading of server firmware | |
| US8020048B2 (en) | Power-on self test program management apparatus and its management method and program | |
| CN100511145C (en) | Method of updating system for managing data of input / output system | |
| CN1294481C (en) | Method for updating and recovering system by bootstrap program | |
| CN111949278B (en) | Method, system, terminal and storage medium for automatically installing MCS system | |
| CN114691440B (en) | Data extraction method and device of equipment, computer equipment and storage medium | |
| CN111078714B (en) | Data processing method and device |
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 | ||
| ASS | Succession or assignment of patent right |
Owner name: INVENTEC TECHNOLOGY CORP. Free format text: FORMER OWNER: YINGYEDA CO., LTD., TAIWAN Effective date: 20130710 Owner name: YINGYEDA CO., LTD., TAIWAN Effective date: 20130710 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| COR | Change of bibliographic data |
Free format text: CORRECT: ADDRESS; FROM: TAIWAN, CHINA TO: 201114 MINHANG, SHANGHAI |
|
| TR01 | Transfer of patent right |
Effective date of registration: 20130710 Address after: 201114 Minhang District Pu Xing Road, No. 789, Shanghai Patentee after: Inventec Technology Co., Ltd. Patentee after: Inventec Corporation Address before: Taipei City, Taiwan Chinese Shilin District Hougang Street No. 66 Patentee before: Inventec Corporation |
|
| CB03 | Change of inventor or designer information | ||
| CB03 | Change of inventor or designer information |
Inventor after: Zhao Chunfang Inventor before: Tan Tan Inventor before: Chen Zhifeng |
|
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20170913 Address after: 075000, unit 102, building 27, East dormitory, Worker Village, Qiaodong District, Hebei City, Zhangjiakou Patentee after: Zhao Chunfang Address before: 201114 Minhang District Pu Xing Road, No. 789, Shanghai Co-patentee before: Inventec Corporation Patentee before: Inventec Technology Co., Ltd. |
|
| CP02 | Change in the address of a patent holder | ||
| CP02 | Change in the address of a patent holder |
Address after: Xinyi Road Xiufeng District, Guilin city 541001 No. 93 the Guangxi Zhuang Autonomous Region Patentee after: Zhao Chunfang Address before: 075000, unit 102, building 27, East dormitory, Worker Village, Qiaodong District, Hebei City, Zhangjiakou Patentee before: Zhao Chunfang |
|
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20130515 Termination date: 20171127 |