TWI776579B - Processing method and device of firmware updating - Google Patents

Abstract

The processing method and device of firmware updating is provided. The processing method comprise of the steps obtaining a device list of a server, and the device list has at least one device; creating a core device tree information according to a mainboard of the server; creating a peripheral device tree information according to the device list; creating a backplane device tree information according to the device list; packing the core device tree information, the peripheral device tree information and backplane device tree information into an object firmware.

Description

Firmware update processing method and device

A method and device for updating firmware, in particular, a method and device for updating firmware of a server and its peripheral devices.

With the increase of various computing demands, it also drives the rapid development of servers. When deploying a server, in addition to the computing power of the processor, the expansion capability of the server should also be considered. Generally speaking, a server can expand various peripheral devices through a backplane. For example, the server is connected to external storage devices, fans or sensors through the backplane.

Due to the combination of the server and various peripheral devices, there are many styles. For example, servers of the same model may have different numbers of backplanes, fans, and sensors for different numbers of blade motherboards. If the development of the corresponding device tree source information (Device Tree Source) is proposed for each motherboard and peripheral devices, this will greatly increase the development and maintenance costs of back-end personnel.

In view of this, the processing method of firmware update includes obtaining a device list of the motherboard, and the device list records at least one peripheral device; generating core device tree source information according to the motherboard; generating device device tree source information of each peripheral device according to the device list and at least one backplane device tree source information; the core device tree source information, the equipment device tree source information and the backplane device tree source information are encapsulated into object files. The processing method of the firmware update can provide the same target file to the same series of servers, and deploy the corresponding hardware description information according to the added peripheral devices. In addition to facilitating the client to obtain the target file to be updated, the back-end developer can reduce the cost of repeated maintenance.

In some embodiments, the step of encapsulating the core device tree source information, the equipment device tree source information and the backplane device tree source information into object files includes compiling the equipment device tree source information into a device intermediate file; according to The backplane quantity information of the motherboard generates a corresponding amount of the backplane device tree source information; compiling the backplane device tree source information into a backplane intermediate file; compiling the core device tree source information into a core file; Files, backplane intermediate files and core files are encapsulated as object files.

In some embodiments, after the step of encapsulating the target file, the first computer includes sending the target file to the second computer; judging the checksum value of the current description file and the target file of the second computer; The sum value is different from the checksum value of the target file, and the current description file is updated according to the target file.

In some embodiments, the firmware update processing method includes acquiring a first device list and a second device list of the motherboard, the first device list having at least one first peripheral device, and the second device list having at least one second peripheral device ; Generate core device tree source information according to the motherboard; generate first equipment device tree source information and at least one first backplane device tree source information of each first peripheral device according to the first equipment list; A second equipment device tree source information and at least one second backplane device tree source information of a second peripheral device; the core device tree source information, the first equipment device tree source information, the first backplane device tree source information, the first The source information of the second equipment device tree and the source information of the second backplane device tree are encapsulated into object files.

In some embodiments, the step of encapsulating into an object file includes compiling the first equipment device tree source information and the second equipment device tree source information into a first equipment intermediate file and a second equipment intermediate file, respectively; according to The first backplane quantity information and the second backplane quantity information of the motherboard respectively generate corresponding quantities of the first backplane device tree source information and the second backplane device tree source information; The device tree source information and the second backplane device tree source information are compiled into a first backplane intermediate file and a second backplane intermediate file respectively; the core device tree source information is compiled into a core file; the first device intermediate file and The first backplane intermediate file is encapsulated into a first file group; the second device intermediate file and the second backplane intermediate file are encapsulated into a second file group; the core file, the first file group and the second file group are encapsulated as targets document.

In some embodiments, the step of encapsulating the first file group and the second file group into target files includes sending the target file from the first computer to the second computer; judging the verification between the current description file of the second computer and the target file Sum value; if the checksum value of the current description file is different from the checksum value of the target file, select the first file group or the second file group from the target file according to the motherboard and version information of the second computer.

In some embodiments, the firmware update processing device includes a first transmission unit, a first storage unit, and a first processor; the first transmission unit acquires a device list of the motherboard, and the device list records at least one peripheral device; the first storage unit The unit stores the processing program, the device list and the target file; the first processor is coupled to the first transmission unit and the first storage unit, the first processor executes the processing program, and the first processor generates the core device tree source information according to the motherboard, The first processor generates at least one equipment device tree source information and at least one backplane device tree source information according to the equipment list, and the first processor generates the core device tree source information, the equipment device tree source information and the backplane device tree Source information is packaged into object files.

In some embodiments, the second computer has a second transmission unit, a second storage unit and a second processor, the second processor is coupled to the second transmission unit and the second storage unit, and the second transmission unit is connected to the first transmission unit The computer, the second storage unit stores the update program, the guide program and the current description file, the second processor executes the update program and the guide program, and the update program obtains the target file from the first storage unit through the second transmission unit through the first transmission unit , the bootstrap program updates the second computer according to the target file, and the bootstrap program updates the second computer according to the target file.

In some embodiments, the bootstrap program determines whether the checksum value of the current description file and the target file are the same. If the checksum value of the current description file is different from the checksum value of the target file Update the current description file.

The firmware update processing method and system provide flexible packaging and update of device firmware, so that the same target file can support multiple sets of different servers and corresponding peripheral devices. Developers can arbitrarily match the core files with the device firmware and backplane firmware to match the information of different versions of the server.

Please refer to FIG. 1 , which is a schematic diagram of a hardware structure of an embodiment. The firmware update processing system 001 includes a processing device (corresponding to the first computer 100 in FIG. 1 ) and an external server 200 . For convenience of description, the processing device is hereinafter referred to as the first computer 100 . The first computer 100 includes a first transmission unit 110 , a first storage unit 120 and a first processor 130 . The first processor 130 is coupled to the first transmission unit 110 and the first storage unit 120 . The first transmission unit 110 obtains the device list 210 of the motherboard. The first transmission unit 110 can be connected to the external server 200 through the Ethernet network or access the storage device of the communication bus to obtain a device list 210 . The communication bus can be Universal Serial Bus (USB), Serial Advanced Technology Attachment (SATA), Peripheral Component Interconnect (PCI) or fast peripheral Component Interconnect Standard (Peripheral Component Interconnect Express, PCIE).

The device list 210 records the version information 214 of the motherboard and peripheral devices connected to the motherboard. The version information 214 may be, but is not limited to, the model of the motherboard, the version of the current description file, the product project, or the product model of the first computer 100 . The peripheral device can be, but not limited to, a backplane, a fan, a sensor, a connection port, a signal light, or a control chip, and the like. In addition, the number of backplanes contained in the equipment list 210 is mainly based on the maximum value and the connected type of the servers of the same series of products. For example, there are two series of servers using the same motherboard, which are server A and server B respectively. Server A can be connected to 10 sets of backplanes, while server B can be connected to 5 sets of backplanes. The number of connectable backplanes for the motherboard will be recorded in the device list 210 as 10 groups.

In some embodiments, the first computer 100 may selectively connect to the external server 200 . The external server 200 generates a corresponding equipment list 210 according to the bill of materials (BOM) of each development project. The first computer 100 obtains the equipment list 210 of the development project through the first transmission unit 110 . The equipment list 210 records the server model, the type and quantity of the backplane, and the type and quantity of the peripheral equipment of the development project. Different development projects may use the same server, but the backplane and peripheral equipment to which the server belongs will be different.

The first storage unit 120 stores the processing program 121 , the equipment list 210 , the target file 123 and the operating system (without reference numerals). The first processor 130 executes the operating system and the processing program 121 . The following description will focus on the processing program 121 for convenience, but in the actual operation, the first processor 130 is still used as the core of the physical processing. The types of operating systems are Linux operating systems, UNIX operating systems or other BSD operating systems. The processing program 121 is used to generate the device tree source information (DTS) and the target file 123 . The processing program 121 generates the corresponding device tree source information according to the peripheral devices in the device list 210, and compiles the device tree source information into the output of the Device Tree Blob (DTB) or the Device Tree Blob Overlay (DTBO) result.

In this embodiment, the processing program 121 can generate corresponding device tree source information according to the motherboard and peripheral devices contained in the device list 210 . The processing program 121 generates the core device tree source information 211 according to the motherboard and version information 214 . The processing program 121 generates the device device tree source information 212 according to the peripheral devices. The processing program 121 generates the backplane device tree source information 213 according to the type and quantity of the backplane. The processing program 121 can respectively generate a variety of equipment device tree source information 212 according to the types of peripheral equipment, and generate a corresponding number of equipment device tree source information 212 according to the same type of peripheral equipment.

To further illustrate the processing method for updating the hardware description files of the server and the peripheral devices to which it belongs, please refer to FIG. 2 . The method for updating the hardware description files of the server and its peripheral devices includes the following steps: Step S310: the first computer obtains a device list of the motherboard, and the device list records at least one peripheral device; Step S320: Generate core device tree source information according to the motherboard; Step S330 : generating equipment device tree source information and at least one backplane device tree source information of each peripheral device according to the equipment list; and Step S340: Encapsulate the core device tree source information, the equipment device tree source information and the backplane device tree source information into target files.

First, the first computer 100 obtains the device list 210 of the motherboard through the first transmission unit 110 . The first computer 100 executes the processing program 121 , and the processing program 121 generates the core device tree source information 211 according to the motherboard recorded in the device list 210 . The processing program 121 generates the device device tree source information 212 and the backplane device tree source information 213 according to the peripheral devices recorded in the device list 210 .

Next, the processing program 121 compiles the device device tree source information 212 into a device intermediate file 412 . The processing program 121 can use a Device Tree Compiler (DTC) to compile the device tree source information 212 . The processing program 121 generates the device intermediate files 412 one by one according to the type and quantity of the device device tree source information 212 . In other words, each device intermediate file 412 corresponds to one device device tree source information 212 .

The processing program 121 obtains information on the number or type of backplanes from the device list 210 . The processing program 121 generates a corresponding number of backplane device tree source information 213 according to the backplane quantity information. The processing program 121 compiles the backplane device tree source information 213 according to the type and quantity of the backplane, and generates a backplane intermediate file 413 corresponding to the type and quantity.

In one embodiment, the processing program 121 may use a Device Tree Overlay or a Device Tree Blob Overlay call processing for the backplane device tree source information 213 . The processing program 121 can add the device tree source information of the new peripheral device on the basis of the existing device tree source information through the aforementioned superposition processing. Overlay processing can be used to coordinate the sharing of hardware resources across backplanes, such as backplane priorities for pins, memory segments, interrupt handling, or registers.

Next, the processing program 121 compiles the core device tree source information 211 of the motherboard into a core intermediate file 411 . Please refer to FIG. 3 , which is a schematic diagram of device tree source information and corresponding intermediate files according to an embodiment. After the processing program 121 completes the aforementioned core intermediate file 411 , the device intermediate file 412 and the backplane intermediate file 413 , the processing program 121 processes the version information 214 of the motherboard, the core intermediate file 411 , the device intermediate file 412 and the backplane intermediate file 413 . packaged, and the packaged result is the object file 123 .

The processing program 121 is packaged according to the core intermediate file 411 , the device intermediate file 412 and the backplane intermediate file 413 , as shown in FIG. 4 , for example. The processing program 121 stores the target file 123 in the first storage unit 120 . In addition, during the process of encapsulating the object file 123 , the processing program 121 may also calculate the checksum value of the object file 123 . When the processing program 121 encapsulates the target file 123, the processing program 121 also adds the checksum value together.

In one embodiment, the firmware update processing system 001 further includes a second computer 500 . The second computer 500 includes a motherboard 540 , a second transmission unit 510 , a second storage unit 520 and a second processor 530 , as shown in FIG. 5 . The second computer 500 may be, but is not limited to, a server, a personal computer, or a notebook computer with an X86 architecture, and may also be an Advanced RISC Machine (ARM) computing device. The second processor 530 is coupled to the second transmission unit 510 and the second storage unit 520 . The second transmission unit 510 is connected to the first computer 100 , and the second transmission unit 510 is used for transmitting the target file 123 . The second storage unit 520 stores the update program 521 , the boot program 522 and the current description file 523 . The current description file 523 is the hardware description file used in the operation of the second computer 500 .

The second processor 530 executes the update program 521 and the boot program 522 . The second processor 530 may be a baseboard control manager (Board Management Controller, BMC) or a central processing unit (Central Processing Unit, CPU), which is determined according to the hardware architecture of the second computer 500 . The update program 521 obtains the corresponding target file 123 from the first computer 100 according to the version information 214 of the motherboard 540 of the second computer 500 . Alternatively, the user obtains the target file 123 with a specific version number from the first computer 100 through the update program 521 . The bootstrap 522 updates the current description file 523 of the second computer 500 according to the target file 123 . The boot program 522 can be implemented by Uboot of the Linux operating system or a bootloader of the UNIX operating system. The motherboard 540 can expand the peripheral device 550 or the backplane 560 according to the version information 214 .

When the navigation program 522 updates the target file 123, the navigation program 522 will perform the following processing steps, which are shown in FIG. 6 . The update target file 123 of the bootstrap 522 includes: Step S610: the bootloader determines whether the checksum values of the current description file and the target file are the same; Step S620: If the checksum value of the current description file is different from the checksum value of the target file, the bootloader updates the current description file according to the target file; and Step S630: If the checksum value of the current description file is equal to the checksum value of the target file, the bootloader sends a prompt message.

When the navigator 522 updates the target file 123 , the navigator 522 determines whether the checksum value of the target file 123 is the same as the checksum value of the current description file 523 . The checksum value can be based on the numerical result obtained by the target file 123 and the hash function. In general, two identical content files will get the same checksum value. Therefore, the bootloader 522 determines whether the checksum value of the current description file 523 and the checksum value of the target file 123 are the same before updating. If the checksum value of the current description file 523 is different from the checksum value of the target file 123, the bootstrap program 522 will only enter the update process of the hardware resource file. On the contrary, the boot program 522 regards the target file 123 and the current description file 523 as the same version of the hardware resource file, and issues a prompt message to prompt the user. For example: a dialog box (meaning a prompt message) pops up on the display screen of the operating system.

First, the bootloader 522 loads the kernel intermediate file 411 into the memory segment. Next, the boot program 522 confirms the type and quantity of the device intermediate file 412 according to the version information 214 . The bootloader 522 loads each device intermediate file 412 into the memory segment. The bootstrap program 522 can import the device tree source information of the peripheral devices one by one according to the serial number of the device intermediate file 412 or the superposition of the device tree. Finally, the bootloader 522 loads each backplane intermediate file 413 into the memory segment. Similarly, the bootstrap program 522 can also add the backplane 560 and the associated device (for example, a sensor or a fan) by stacking the device tree.

For servers of the same series, the main board 540 of the server can be matched with different peripheral devices or backplanes 560 . For this embodiment, the schematic diagram of the system architecture shown in FIG. 1 or FIG. 5 may be used, and the system shown in FIG. 7 may be used at the same time. FIG. 7 is a schematic diagram of the encapsulation process flow of the target file of the server according to this embodiment, which includes the following steps: Step S710: Obtain a first device list and a second device list, the first device list has at least one first peripheral device, and the second device list has at least one second peripheral device; Step S720: Generate core device tree source information according to the motherboard; Step S730: Generate first device device tree source information and at least one first backplane device tree source information of each first peripheral device according to the first device list; Step S740: Generate second device device tree source information and at least one second backplane device tree source information of each second peripheral device according to the second device list; and Step S750: Encapsulate the core device tree source information, the first equipment device tree source information, the first backplane device tree source information, the second equipment device tree source information, and the second backplane device tree source information into object files.

The first computer 100 acquires the first device list 210 and the second device list 210 of the motherboard 540 . The first device list 210 and the second device list 210 are products of the same motherboard 540 and different series. The first device list 210 records the first peripheral device. The second device list 210 records second peripheral devices. The number or variety of first peripheral devices may not be exactly the same as the number or variety of second peripheral devices. The first processor 130 executes the processing program 121 .

The processing program 121 generates the core device tree source information 211 , the first equipment device tree source information 212 and the first backplane device tree source information 213 according to the first device list 210 . The processing program 121 generates the second device device tree source information 212 and the first backplane device tree source information 213 according to the core device tree source information 211 and the second device list 210 . The processing program 121 performs related processing on the target file 123 according to the generated device tree source information, as shown in FIG. 8 : Step S810: Compile the first equipment device tree source information and the second equipment device tree source information into the first equipment intermediate file and the second equipment intermediate file respectively; Step S820: respectively generating a corresponding number of first backplane device tree source information and second backplane device tree source information according to the first backplane quantity information of the first equipment list and the second backplane quantity information of the second equipment list; Step S830: Compile the first backplane device tree source information and the second backplane device tree source information into a first backplane intermediate file and a second backplane intermediate file, respectively; Step S840: Compile the core device tree source information into a core file; Step S850: encapsulating the first device intermediate file and the first backplane intermediate file into a first file group; Step S860: encapsulating the second device intermediate file and the second backplane intermediate file into a second file group; and Step S870: Encapsulate the core file, the first file group and the second file group into a target file.

The processing program 121 compiles the source information of the first equipment device tree (without labels) and the source information of the second equipment device tree (without labels) into the first equipment intermediate file 911 and the second equipment intermediate file 921 respectively. The number of the first device intermediate files 911 corresponds to the number of source information of the first device tree; the number of the second device intermediate files 921 also corresponds to the number of source information of the second device tree.

The processing program 121 generates first backplane device tree source information (unlabeled) according to the number of backplanes in the first device list 210 (hereinafter referred to as the first number of backplanes). The processing program 121 generates the second backplane device tree source information 213 according to the number of backplanes in the second device list 210 (hereinafter referred to as the second backplane number). Next, the processing program 121 compiles the first backplane device tree source information 213 and the second backplane device tree source information 213 into the first backplane intermediate file 912 and the second backplane intermediate file 922, respectively. The number of the first backplane intermediate files 912 is equal to the number of the first backplanes, and the number of the second backplane intermediate files 922 is equal to the number of the second backplanes.

The processing program 121 compiles the core device tree source information 211 into a core intermediate file 411 . Since the first device list 210 and the second device list 210 both use the same motherboard 540 , the processing program 121 can determine the two device lists 210 according to the version information 214 before compiling. The processing program 121 can use the latest version information 214 as a basis for selecting the core device tree source information 211 .

The processing program 121 encapsulates the first device intermediate file 412 and the first backplane intermediate file 413 into a first file group 910 . The processing program 121 also encapsulates the second device intermediate file 412 and the second backplane intermediate file 413 into a second file group 920 . Finally, the processing program 121 encapsulates the core intermediate file 411 , the first file group 910 and the second file group 920 into the target file 123 , as shown in FIG. 9 . In FIG. 9 , the multiple files circled by the dotted frame are the file groups of the same group. If the first computer 100 receives the third device list 210, the first computer 100 generates a third file group (without a label) according to the aforementioned actions. The processing program 121 encapsulates the first file group 910 , the second file group 920 and the third file group in the target file 123 .

The first computer 100 sends the target file 123 to the second computer 500 . The second computer 500 determines whether the checksum value of its current description file 523 and the received target file 123 are the same. If the checksum value of the current description file 523 is different from the checksum value of the target file 123 , the second computer 500 and the bootstrap program 522 will only perform the process of updating the target file 123 . In this embodiment, the boot program 522 selects the first file group 910 or the second file group 920 from the target files 123 according to the version information 214 of the motherboard 540 . Alternatively, the user selects one of the target files 123, and the boot program 522 performs the firmware update process.

To illustrate this embodiment clearly, two device lists 210 and the generated object file are taken as an example, but are not limited to the allocation of hardware resources. For example, the equipment list I and the equipment list II respectively record two sets of servers, and the two servers use the same motherboard, which are server A and server B respectively. Different numbers of peripheral devices 550 and backplanes 560 are mounted on the server A and the server B, respectively. Please refer to Table 1 and FIG. 10 , which are schematic diagrams of the device list and source information of each device tree in this embodiment. The equipment list in Table 1 describes the types and quantities of the peripheral equipment 550 and the backplane 560 . The peripheral device 550 is an integrated bus circuit (Inter-Integrated Circuit, I2C for short), and the suffix of I2C represents the device number. In Table 1, the backplane 560 is represented by "BP", and the suffix of BP is the backplane number. Each backplane 560 can be connected to different devices, and the connected devices are shown in Table 1. motherboard Peripherals backplane Equipment list_I MB_a I2C_4; I2C_5 BP_1 (fan*1, temperature sensor*1); BP_2 (fan*2, temperature sensor*1) Equipment List_II MB_a I2C_5; I2C_6; I2C_7 BP_1 (fan*1, temperature sensor*2) Table 1. List of peripherals included in the equipment list

The processing program 121 generates the core device tree source information 211 , the device device tree source information 212 and the backplane device tree source information 213 of the motherboard a according to the device list I and the device list II, respectively. Since the two device lists I and II use the same motherboard a, the processing program 121 will generate a set of core device tree source information 211 . The processing program 121 generates the device tree source information 212 with I2C_4 and I2C_5 according to the peripheral equipment 550 and the backplane 560 contained in the device list I, and the processing program 121 generates the backplane device tree source information 213 with BP_1 and BP_2 . Similarly, the processing program 121 generates corresponding equipment device tree source information 212 and backplane device tree source information 213 according to the device list II.

Next, the processing program 121 compiles the corresponding intermediate file according to the device list I and the device list II, as shown in FIG. 3 . The processing program 121 encapsulates each intermediate file into a corresponding first file group 910 according to the equipment list I, and the processing program 121 encapsulates each intermediate file into a corresponding second file group 920 according to the equipment list II, as shown in FIG. 9 .

The firmware update processing method and system provide flexible packaging and update of device firmware, so that the same target file 123 can support multiple sets of different servers and corresponding peripheral devices 550 . The developer can arbitrarily match the core file with the hardware description file of the peripheral device 550 and the hardware description file of the backplane 560 so as to conform to the different version information 214 of the server.

001: Processing system for firmware update 100: First Computer 110: The first transmission unit 120: The first storage unit 121: Handler 123: target file 130: The first processor 200: External server 210: Equipment List 211: Core device tree source information 212: Device device tree source information 213: Backplane device tree source information 214: Version Information 411: core intermediate file 412: Device intermediate file 413: Backplane intermediate file 500: Second Computer 510: Second transmission unit 520: Second storage unit 521: Updater 522: Bootstrap 523: Current description file 530: Second processor 540: Motherboard 550: Peripherals 560: Backplane 910: The first file group 911: First device intermediate file 912: First backplane intermediate file 920: The second file group 921: Second device intermediate file 922: Second backplane intermediate file S310, S320, S330, S340: Steps S610, S620, S630: Steps S710, S720, S730, S740, S750: Steps S810, S820, S830, S840, S850, S860, S870: Steps

[FIG. 1] is a schematic diagram of a hardware architecture of an embodiment. [ FIG. 2 ] is a schematic diagram of an update flow of the hardware description files of the server and the peripheral devices to which it belongs according to an embodiment. 3 is a schematic diagram of device tree source information and corresponding intermediate files according to an embodiment. FIG. 4 is a schematic diagram of the structure of an object file according to an embodiment. [ FIG. 5 ] is a schematic diagram of a system architecture of a first computer and a second computer according to an embodiment. FIG. 6 is a schematic diagram of the operation flow of the boot program updating the target file according to an embodiment. FIG. 7 is a schematic diagram of a process flow of packaging a target file of a server according to an embodiment. [ FIG. 8 ] is a schematic flowchart of object file compilation according to an embodiment. [FIG. 9] is a schematic diagram of the structure of an object file of an embodiment. FIG. 10 is a schematic diagram of the code of the source information of the device tree according to an embodiment.

001: Processing system for firmware update

100: First Computer

110: The first transmission unit

120: The first storage unit

121: Handler

123: target file

130: The first processor

200: External server

210: Equipment List

211: Core device tree source information

212: Device device tree source information

213: Backplane device tree source information

214: Version Information

Claims (11)

A method for processing firmware update, comprising: obtaining a device list of a motherboard from an external server by a first computer, the device list recording at least one peripheral device; the first computer generating a core device according to the motherboard tree source information; the first computer generates a device device tree source information and at least one backplane device tree source information of each of the peripheral devices according to the equipment list; and the first computer generates the core device tree source information, the device The device tree source information and the backplane device tree source information are packaged into an object file. The method for processing firmware update according to claim 1, wherein the step of encapsulating the core device tree source information, the equipment device tree source information and the backplane device tree source information into the target file comprises: encapsulating each Compile the device tree source information into a device intermediate file respectively; generate a corresponding number of backplane device tree source information according to a backplane quantity information of the motherboard; compile each of the backplane device tree source information separately is a backplane intermediate file; compiles the core device tree source information into a core file; and encapsulates the device intermediate file, the backplane intermediate file and the core file into the object file. The method for processing firmware update according to claim 2, wherein after the step of encapsulating the target file, the method includes: Sending the target file to a second computer by a first computer; judging a checksum value of a current description file of the second computer and the target file; and if the checksum value of the current description file is different Based on the checksum value of the object file, replace the current description file with the object file. The method for processing firmware update according to claim 3, wherein the step of judging the checksum value of the current description file and the target file of the second computer comprises: obtaining a motherboard of the second computer and the a version information of the motherboard; select at least one of the backplane intermediate file, the core file and the device intermediate files from the target file according to the version information; and according to the selected backplane intermediate file, the core file The checksum value corresponding to the device intermediate files is generated. A method for processing firmware update, comprising: obtaining a first device list and a second device list of a motherboard from a first computer from an external server, the first device list having at least one first peripheral device, The second device list has at least one second peripheral device; the first computer generates a core device tree source information according to the motherboard; the first computer generates a first peripheral device for each first peripheral device according to the first device list a device tree source information and at least one first backplane device tree source information; the first computer generates a second device device tree source information and at least one second device tree source information for each of the second peripheral devices according to the second device list backplane device tree source information; and The first computer encapsulates the core device tree source information, the first equipment device tree source information, the first backplane device tree source information, the second equipment device tree source information and the second backplane device tree source information for a target file. The method for processing firmware update according to claim 5, wherein the step of encapsulating into the target file comprises: compiling the first equipment device tree source information and the second equipment device tree source information into a first an equipment intermediate file and a second equipment intermediate file; according to a first backplane quantity information of the first equipment list and a second backplane quantity information of the second equipment list, a corresponding number of the first backplanes are respectively generated The board device tree source information and the second backplane device tree source information; the first backplane device tree source information and the second backplane device tree source information are compiled into a first backplane intermediate file and a second backplane intermediate file; compile the core device tree source information into a core file; encapsulate the first equipment intermediate file and the first backplane intermediate file into a first file group; the second equipment intermediate file The file and the second backplane intermediate file are packaged into a second file group; and the core file, the first file group and the second file group are packaged into the target file. The method for processing firmware update according to claim 6, wherein the step of encapsulating the first file group and the second file group into the target file includes: sending the target file from a first computer to a second computer computer; Judging a current description file of the second computer and a checksum value of the target file; and if the checksum value of the current description file is different from the checksum value of the target file, according to the second The motherboard of the computer and a version information of the motherboard select the first file group or the second file group from the target file. A firmware update processing device, comprising: a first transmission unit for acquiring a device list from an external server, the device list corresponding to a motherboard and the device list recording at least one peripheral device; a first storage unit, storing a processing program, the device list and a target file; and a first processor coupled to the first transmission unit and the first storage unit, the first processor executes the processing program, the first processor Generates a core device tree source information according to the motherboard, the first processor generates at least one equipment device tree source information and at least one backplane device tree source information according to the device list, the first processor generates the core device tree source information The information, the equipment device tree source information and the backplane device tree source information are packaged into the object file. The firmware update processing device of claim 8, wherein the first processor compiles a device intermediate file according to the source information of the device device tree, and the first processor compiles a device intermediate file according to a backplane quantity information of the motherboard generating a corresponding number of the backplane device tree source information, the first processor compiles the core device tree source information into a core file, and the first processor compiles the backplane device tree source information into a backplane an intermediate file, the first processor encapsulates the device intermediate file, the backplane intermediate file and the core file into the target file. The firmware update processing device of claim 8, comprising a second computer having a second transmission unit, a second storage unit and a second processor, the second processor is coupled to the second computer The second transmission unit and the second storage unit, the second transmission unit is connected to the first transmission unit, the second storage unit stores an update program, a boot program and a current description file, the second processor executes The update program and the guide program, the update program obtains the target file from the first storage unit through the second transmission unit through the first transmission unit, and the guide program updates the second computer according to the target file. The firmware update processing device of claim 10, wherein the boot program determines whether a checksum value of the current description file and the target file is the same, and if the checksum value of the current description file is different Based on the checksum value of the object file, the bootloader updates the current description file according to the object file.

Images