DPU card firmware burning method, system and storage medium

Through the communication connection between the control terminal and the firmware writing terminal and the use of the powered PCIE board, the problem of cumbersome and inefficient writing of the traditional DPU card firmware is solved, and the efficient and simplified writing process and scale expansion is achieved, reducing the frequency of user operation and cost.

CN117573148BActive Publication Date: 2024-12-03YUSUR TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202311446394.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-11-01
Publication Date
2024-12-03
Estimated Expiration
2043-11-01

AI Technical Summary

Technical Problem

The firmware writing method of traditional DPU card is complicated and inefficient. It requires manual disassembly and installation of the writing terminal to replace the DPU card. The number of card slots on the device motherboard is limited and cannot be expanded.

Method used

Through the control terminal and the firmware writing terminal, the communication connection is established, the writing task is assigned, and the firmware writing is burned by powering on the PCIE board, the writing process of the DPU card is simplified, the efficiency is improved, and multiple terminals are supported to write in parallel, which expands the The number of card slots reduces the frequency of manual operation of users.

Benefits of technology

The DPU card firmware writing process is simplified, the writing efficiency is improved, the cost and user operation complexity is reduced, the system adaptability and scalability is enhanced, and the success rate is improved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117573148B_ABST
    Figure CN117573148B_ABST
Patent Text Reader

Abstract

The present invention provides a DPU card firmware burning method, system and storage medium, the method comprising: searching for at least one firmware burning terminal through a control terminal; in the case of finding a firmware burning terminal, establishing a communication connection with the current firmware burning terminal found through the control terminal and sending a burning task and a corresponding firmware file to the current firmware burning terminal; determining a DPU card on a powered-on PCIE board currently connected to the current firmware burning terminal through the current firmware burning terminal; executing a firmware burning script through the current firmware burning terminal, burning the firmware file into the DPU card and obtaining a burning process verification result; in the case of the burning process verification result indicating that the DPU card burning process is correct, determining whether there are remaining burning tasks in the burning task list through the current firmware burning terminal; in the case of no remaining burning tasks, ending the burning task of the current firmware burning terminal. The present invention can solve the problem of cumbersome and inefficient DPU card firmware burning process.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a DPU card firmware burning method, system and storage medium. Background Art

[0002] In today's digital age, the generation and processing of data are experiencing an unprecedented explosive growth. From the Internet to the Internet of Things, from artificial intelligence to big data analysis, the scale and complexity of data are showing an exponential growth trend. In this context, efficient, fast and reliable data processing has become a core requirement of all walks of life. However, the development cost of finished chips is expensive and the development cycle is extremely long. It may cost tens of millions of dollars and take a year to keep a chip at one time. Based on this, the data processing unit (DPU) plays an extremely important role in this context. With the continuous growth of data processing needs, high-performance DPU cards have become an urgent need in various application fields. Therefore, in order to maintain competitive advantages in a highly competitive market environment and meet the ever-changing market needs, technological innovation to improve the efficiency of DPU card firmware burning is imminent.

[0003] The traditional DPU card firmware burning method includes: installing the DPU card on the device mainboard of the burning terminal, and loading the firmware file into the DPU card through a specific Field-Programmable Gate Array (FPGA) development tool.

[0004] However, in the traditional DPU card firmware burning method, since the DPU card is installed on the device mainboard, when the DPU card needs to be replaced, the operator needs to manually disassemble the shell of the installation burning terminal to replace the DPU card. At the same time, the number of card slots on the device mainboard of the burning terminal is limited and cannot be expanded. Therefore, there is a problem that the DPU card firmware burning process is cumbersome and inefficient. Summary of the invention

[0005] In view of this, the embodiments of the present invention provide a DPU card firmware burning method, system and storage medium to eliminate or improve one or more defects in the prior art and solve the problem that the DPU card firmware burning process is cumbersome and inefficient.

[0006] One aspect of the present invention provides a DPU card firmware burning method, which is applied to a DPU card firmware burning system, wherein the DPU card firmware burning system includes a control terminal and at least one firmware burning terminal, and at least one powered PCIE board correspondingly connected to each firmware burning terminal, and each powered PCIE board is provided with at least one PCIE card slot; the method includes the following steps:

[0007] Sending connection instructions to at least one firmware burning terminal respectively through the control terminal to search for at least one firmware burning terminal;

[0008] When the firmware burning terminal is found, a communication connection is established with the found current firmware burning terminal through the control terminal;

[0009] Based on the communication connection, the burning task is allocated to the current firmware burning terminal through the control terminal, so that the current firmware burning terminal adds the received burning task to the burning task list;

[0010] Send the firmware file corresponding to the burning task to the current firmware burning terminal through the control terminal;

[0011] Determine the DPU card on the powered PCIE board to which the current firmware burning terminal is currently connected through the current firmware burning terminal;

[0012] Execute the firmware burning script through the current firmware burning terminal, burn the firmware file into the DPU card and obtain the burning process verification result;

[0013] When the result of the burning process verification indicates that the burning process of the DPU card is correct, determine whether there are remaining burning tasks in the burning task list through the current firmware burning terminal;

[0014] When there is no remaining burning task, the burning task of the current firmware burning terminal is terminated.

[0015] Optionally, in the case where there are remaining burning tasks, the method further includes:

[0016] Outputting a replacement prompt message through the current firmware burning terminal to prompt the user to replace the DPU card on the powered PCIE board currently connected to the current firmware burning terminal;

[0017] In response to the received feedback indication, a step of determining, through the current firmware burning terminal, a DPU card on a powered-on PCIE board to which the current firmware burning terminal is currently connected is performed.

[0018] Optionally, when the number of the DPU card is at least one, executing the firmware burning script through the current firmware burning terminal to burn the firmware file into the DPU card includes:

[0019] Get the PCIE card number corresponding to each DPU card;

[0020] Based on the order of the PCIE card numbers, the firmware burning script is executed through the current firmware burning terminal to burn the firmware files into the DPU cards in sequence.

[0021] Optionally, when there is at least one DPU card, the firmware burning script is executed through the current firmware burning terminal to burn the firmware file into the DPU card, including: executing the firmware burning script through the current firmware burning terminal to burn the firmware file into the DPU card in parallel.

[0022] Optionally, the firmware file includes a programming file and a programming configuration file. The firmware burning script is executed through the current firmware burning terminal to burn the firmware file into the DPU card, including:

[0023] Execute the firmware burning script through the current firmware burning terminal to burn the configuration information in the programming file into the DPU card;

[0024] Verify the DPU card through the programming verification file to obtain the programming process verification result.

[0025] Optionally, assigning the burning task to the current firmware burning terminal through the control terminal includes:

[0026] By controlling the terminal according to the number of current firmware burning terminals, the burning task is evenly distributed to the current firmware burning terminals;

[0027] or,

[0028] The preset DPU card link quantity corresponding to each current firmware burning terminal is obtained through the control terminal; and the burning task is allocated to the found firmware burning terminal based on the preset DPU card link quantity.

[0029] Optionally, when the firmware burning terminal is not found, the method further includes:

[0030] The control terminal outputs connection prompt information to prompt the user to check the current programming environment.

[0031] Optionally, when the verification result indicates that the DPU card programming process is wrong, the method further includes:

[0032] The firmware burning terminal outputs error prompt information to prompt the user to check the current burning environment.

[0033] Another aspect of the present invention provides a DPU card firmware burning system, the system comprising: a control terminal and at least one firmware burning terminal, at least one powered PCIE board correspondingly connected to each firmware burning terminal, each powered PCIE board being provided with at least one PCIE card slot and a card slot interface corresponding to each PCIE card slot;

[0034] The control terminal is used to: send a connection instruction to at least one firmware burning terminal respectively to find at least one firmware burning terminal; when the firmware burning terminal is found, establish a communication connection with the current firmware burning terminal found; based on the communication connection, assign the burning task to the current firmware burning terminal, so that the current firmware burning terminal adds the received burning task to the burning task list; send the firmware file corresponding to the burning task to the current firmware burning terminal;

[0035] The firmware burning terminal is used for: determining the DPU card on the currently connected powered PCIE board when receiving the burning task and the firmware file; executing the firmware burning script to burn the firmware file into the DPU card; the firmware burning script is a TCL script; the firmware burning script is used to load the firmware file into the DPU card, and after the burning process is completed, verify the burning process of the DPU card to obtain the burning process verification result; when the burning process verification result indicates that the DPU card burning process is correct, determining whether there are remaining burning tasks in the burning task list; when there are no remaining burning tasks, ending the burning task of the firmware burning terminal.

[0036] Another aspect of the present invention provides a computer-readable storage medium having a computer program stored thereon, characterized in that when the program is executed by a processor, the steps of the above-mentioned DPU card firmware burning method are implemented.

[0037] The beneficial effects of the present invention are at least:

[0038] The DPU card firmware burning method, system and storage medium of the present invention respectively send connection instructions to at least one firmware burning terminal through a control terminal to find at least one firmware burning terminal; when the firmware burning terminal is found, establish a communication connection with the found current firmware burning terminal through the control terminal; based on the communication connection, assign the burning task to the current firmware burning terminal through the control terminal, so that the current firmware burning terminal adds the received burning task to the burning task list; send the firmware file corresponding to the burning task to the current firmware burning terminal through the control terminal; determine the DPU card on the powered PCIE board currently connected to the current firmware burning terminal through the current firmware burning terminal; execute the firmware burning script through the current firmware burning terminal, burn the firmware file into the DPU card and obtain the burning process verification result; when the burning process verification result indicates that the DPU card burning process is correct, confirm through the current firmware burning terminal Whether there are remaining burning tasks in the burning task list; when there are no remaining burning tasks, the burning task of the current firmware burning terminal is ended; the problem of cumbersome and inefficient DPU card firmware burning process can be solved; the burning task is assigned to the currently connected firmware burning terminal through the control terminal, the firmware burning terminal is connected to the powered PCIE board, and the powered PCIE board is provided with at least one PCIE card slot, and the firmware file is burned into the DPU network card inserted in the PCIE card slot; there is no need for users to manually disassemble the shell and mainboard of the firmware burning terminal frequently and restart the firmware burning terminal, so the DPU card firmware burning process can be simplified and the DPU card burning efficiency can be improved; at the same time, a communication connection is established between the control terminal and at least one firmware burning terminal, so that the control terminal can simultaneously control multiple firmware burning terminals to execute burning tasks, and in the case of a large number of burning tasks, the DPU card firmware burning efficiency can be further improved.

[0039] Furthermore, a powered PCIE board is connected to a firmware burning terminal, and the DPU card is installed on the powered PCIE board for firmware burning. Through the scalability of the powered PCIE board, the number of PCIE card slots of the powered PCIE board connected to the firmware burning terminal can be expanded, and the scale of DPU card firmware burning can be increased. At the same time, the powered PCIE board only needs to be connected to the firmware burning terminal, is not restricted by the environment, and can be placed at any position in the burning environment. Therefore, the problem of low adaptability and poor scalability caused by the environmental restrictions of the computing device is avoided.

[0040] Furthermore, by replacing the mainboard of the computing device with a powered-on PCIE board, when there are a large number of burning tasks, there is no need to use a large number of computing devices, which can reduce the cost of burning the DPU card firmware.

[0041] Furthermore, by replacing the mainboard of the computing device with a powered-on PCIE board, the user does not need to manually disassemble the computing device, thereby reducing the frequency of manual operations by the user. The user does not need to judge the burning process or learn a complicated burning process. The user only needs to replace the DPU card to be burned and provide error information feedback, thereby reducing the user's learning cost and the probability of firmware burning failure due to manual operation errors by the user, thereby increasing the success rate of DPU card firmware burning.

[0042] Furthermore, since computing devices are precision instruments and the shell disassembly steps are relatively many, precision instrument motherboard protection facilities are also many, such as: clips, screws and wiring tape, etc., by powering on the PCIE board to replace the motherboard of the computing device, there is no need for users to manually disassemble the computing device, thereby reducing the frequency of user manual operations, reducing the time for hardware replacement, computing device shell disassembly time and motherboard replacement time, which can reduce time costs and improve firmware burning efficiency.

[0043] Additional advantages, purposes, and features of the present invention will be described in part in the following description, and will become apparent to those skilled in the art after studying the following, or may be learned from the practice of the present invention. The purposes and other advantages of the present invention may be achieved and obtained by the structures specifically indicated in the specification and the accompanying drawings.

[0044] Those skilled in the art will appreciate that the objectives and advantages that can be achieved with the present invention are not limited to the above specific description, and the above and other objectives that can be achieved by the present invention will be more clearly understood from the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] The drawings described herein are used to provide a further understanding of the present invention, constitute a part of this application, and do not constitute a limitation of the present invention. The components in the drawings are not drawn to scale, but are only for illustrating the principles of the present invention. In order to facilitate the illustration and description of some parts of the present invention, the corresponding parts in the drawings may be enlarged, that is, they may become larger relative to other components in the exemplary device actually manufactured according to the present invention. In the drawings:

[0046] Figure 1 A schematic diagram of a DPU card estimation and burning system structure in one embodiment of the present invention;

[0047] Figure 2 is a schematic diagram of a powered PCIE board in one embodiment of the present invention;

[0048] Figure 3 is a schematic diagram of a computing device structure in an embodiment of the present invention;

[0049] Figure 4 This is a flow chart of a method for burning DPU card firmware in another embodiment of the present invention;

[0050] Figure 5 A schematic diagram of a DPU card estimation and burning system structure in another embodiment of the present invention;

[0051] Figure 6 This is a flow chart of a method for burning DPU card firmware in another embodiment of the present invention;

[0052] Figure 7 This is a flow chart of a method for burning DPU card firmware in another embodiment of the present invention;

[0053] Figure 8 is a block diagram of a DPU card firmware burning device in another embodiment of the present invention;

[0054] Fig. 9 is a block diagram of an electronic device in another embodiment of the present invention. DETAILED DESCRIPTION

[0055] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the embodiments and the accompanying drawings. Here, the illustrative embodiments of the present invention and their descriptions are used to explain the present invention, but are not intended to limit the present invention.

[0056] It should also be noted that, in order to avoid obscuring the present invention due to unnecessary details, only structures and / or processing steps closely related to the solutions according to the present invention are shown in the accompanying drawings, while other details that are not closely related to the present invention are omitted.

[0057] It should be emphasized that the term “include / comprises” when used herein refers to the presence of features, elements, steps or components, but does not exclude the presence or addition of one or more other features, elements, steps or components.

[0058] It should also be noted that, unless otherwise specified, the term “connection” herein may refer not only to a direct connection but also to an indirect connection involving an intermediate.

[0059] Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. In the accompanying drawings, the same reference numerals represent the same or similar components, or the same or similar steps.

[0060] First, several terms involved in the embodiments of the present application are introduced.

[0061] Data Processing Unit (DPU): DPU is a hardware unit specially designed for data processing. Its main function is to achieve efficient, fast and reliable data processing and analysis. DPU plays an important role in various application scenarios, from data centers to IoT devices, from edge computing to deep learning reasoning, and can provide excellent performance and efficiency. As a specialized data processing unit, DPU is one of the indispensable key technologies in the modern digital era, and is of great significance to promoting technological innovation and application development in various fields.

[0062] Data Processing Unit card: DPU card refers to a hardware acceleration card composed of an FPGA chip and a dedicated deep learning processor. DPU cards usually contain highly specialized hardware and software, designed to provide high-performance data processing and computing capabilities to meet the needs of various applications. DPU cards can be used to accelerate various data-intensive tasks such as artificial intelligence reasoning, machine learning, large-scale data analysis, etc. Its design goal is to provide higher computing efficiency and energy efficiency, reduce the load on the host CPU, and provide faster data processing speed through specially optimized hardware and software architecture.

[0063] Peripheral Component Interconnect Express (PCIE): is a computer bus standard used to connect internal hardware devices, especially expansion cards (such as graphics cards, sound cards, network adapters, etc.), and other components on the motherboard (such as storage controllers, network controllers, etc.). It is currently widely used

[0064] PCI Express Power Distribution Board: A PCI Express Power Distribution Board is a board used to distribute the power supply of a PCI Express (PCIE) interface. It is usually used to connect the power supply to one or more PCIE devices to ensure that these devices can work properly and provide sufficient power supply.

[0065] Field-Programmable Gate Array: FPGA is a programmable logic device, which is an integrated circuit chip with programmable logic and resource units. Compared with traditional ASIC (Application-Specific Integrated Circuit), FPGA has higher flexibility and reconfigurability, allowing designers to customize and optimize circuits according to specific application requirements. FPGA development tools and technologies have made online burning possible. Through online burning, new firmware files can be loaded into the FPGA chip through the network or other communication methods without interrupting the operation of the hardware. Using this technology, there is no need to shut down the computer to transfer new firmware files to the FPGA through remote control to achieve function updates and configuration changes.

[0066] FPGA technology is an ideal choice for accelerating the rapid application of DPU technology due to its flexibility, programmability and high performance. In the early stages of designing and verifying the DPU, a preliminary DPU chip prototype can be built using FPGA technology to verify the correctness and performance of the design. Specifically, FPGA technology allows designers to implement the functions of the DPU at the hardware level and simulate its calculation and data processing processes through programmable logic and circuit elements. This prototype chip is highly flexible and can be modified and optimized multiple times without changing the hardware structure. Using FPGA as a prototype of the DPU chip, designers can quickly verify the functions and performance of the DPU, accelerate the design and development process, and reduce the risk of later development. FPGA allows hardware functions to be reprogrammed after deployment. This programmability needs to be achieved through firmware burning to ensure that the FPGA is correctly configured for the required functions.

[0067] Tool Command Language (TCL): is a scripting programming language originally designed for controlling electronic design automation (EDA) tools, as well as for automation and integration in engineering and science. TCL has a simple, easy-to-learn syntax and is widely used to create scripts and automate tasks. It is often used to interact with various software tools, applications, and systems to achieve automation, custom functionality, and rapid prototyping. TCL can also be used to write test scripts, configuration files, and batch tasks, making it widely used in computer science and engineering.

[0068] Firmware: Firmware is a program written into an erasable programmable read-only memory (EPROM) or an electrically erasable programmable read-only memory (EEPROM). Firmware files are the most basic and lowest-level software, and are the bridge between the device and the operating system.

[0069] Vivado (Vivado Design Suite): Vivado is an integrated design environment. It provides hardware engineers and designers with a comprehensive toolset for creating, verifying, and implementing complex digital circuits and systems. Vivado is designed to accelerate the FPGA design process, improve productivity, and support a comprehensive workflow from design to verification to implementation.

[0070] Python script: A Python script is a text file written in the Python programming language that contains a series of Python codes and instructions to perform specific tasks, operations, or functions. Python is a high-level, general-purpose programming language that is widely used in various application areas, including software development, data analysis, scientific computing, automation, network programming, etc.

[0071] Shell script: A shell script is a text file that contains a series of operating system commands and script statements used to perform a series of operations and tasks in a command line interface (called a shell). Shell scripts are usually executed by a shell interpreter, which is an interpreter provided by the operating system to parse and execute the commands in the script.

[0072] Computing Device: Computing Device refers to various types of computing devices including personal computers, servers and other similar devices, which have unpackaged motherboards and can be customized by users to replace hardware devices, whether they are desktop computers, servers or other computer devices.

[0073] Hardware Manager: Hardware Manager is a Vivado tool set used to start the hardware manager so that it can connect to, configure, and manage FPGA devices.

[0074] MCS File: MCS file is a file format for binary data of FPGA devices. MCS files usually contain data bytes represented in hexadecimal format, which can be configuration bitstreams, programs, firmware or other data used to program or configure in the target device. The format of MCS files can also contain checksums, address information and other metadata to ensure the integrity and correctness of the data.

[0075] PRM File: A PRM file is a file format that is usually used to describe the parameters and settings of a programming operation. This file is usually used by programming tools to ensure that the correct parameters and configurations are used when performing programming operations on hardware devices. This method is used to verify the accuracy of the programming operation.

[0076] BIN File: BIN file is a universal binary file format used to store any type of binary data. It is similar to MCS file in this method. The file contains FPGA data and is used to load specific functional firmware into the hardware device. It is the main firmware data storage format used by our company.

[0077] This embodiment provides a structural diagram of a DPU card firmware burning system.

[0078] like Figure 1 As shown, the DPU card firmware burning system includes: a control terminal 110 and at least one firmware burning terminal 120, at least one powered PCIE board 130 correspondingly connected to each firmware burning terminal 120, and each powered PCIE board 130 is provided with at least one PCIE card slot.

[0079] The control terminal 110 refers to a computing device capable of allocating and scheduling burning tasks, and the firmware burning terminal 120 refers to a computing device capable of receiving and completing burning tasks allocated by the control terminal 110. Optionally, the control terminal 110 and the firmware burning terminal 120 may be a personal computer, a server, etc., and the device type of the control terminal 110 and the device type of the firmware burning terminal 120 may be the same or different. This embodiment does not limit the implementation of the control terminal 110 and the firmware burning terminal 120.

[0080] Figure 1 In the description, the number of the firmware burning terminal 120 is one as an example. In actual implementation, the number of the firmware burning terminals 120 is one or at least two. This implementation does not limit the number of the firmware burning terminals 120.

[0081] It should be noted that the control terminal 110 and the firmware burning terminal 120 are only for functional distinction. In actual implementation, the same terminal can be both the control terminal 110, that is, the terminal that assigns the burning task; and the firmware burning terminal 120, that is, the terminal that establishes a communication connection with the terminal that assigns the burning task and receives the burning task.

[0082] The burning task refers to a task of writing a specific firmware (such as software, operating system, firmware program, etc.) to a target device. In this embodiment, the burning task can be a task set by a user through an input device (such as a mouse or keyboard, etc.) connected to the control terminal 110 to set the program installed in the control terminal 110, or it can be sent to the control terminal 110 by other devices that have established a communication connection with the control terminal 110. This embodiment does not limit the implementation method of the burning task.

[0083] Generally, a task allocation program is installed in the control terminal 110. The task allocation program is a program installed in the control terminal 110, and has the function of establishing a communication connection with the firmware burning terminal 120 and allocating firmware burning tasks according to the firmware burning terminal 120 with which the communication connection is established. The task allocation program can be a separately developed application program, or a functional module embedded in an existing program, such as a small program or a web page. This embodiment does not limit the implementation method of the task allocation program.

[0084] Specifically, in this embodiment, the control terminal 110 is used to: send connection instructions to at least one firmware burning terminal 120 respectively to find at least one firmware burning terminal 120; when the firmware burning terminal 120 is found, establish a communication connection with the current firmware burning terminal 120 found; based on the communication connection, assign the burning task to the current firmware burning terminal 120, so that the current firmware burning terminal 120 adds the received burning task to the burning task list; send the firmware file corresponding to the burning task to the current firmware burning terminal 120.

[0085] In this embodiment, the firmware file is pre-stored in the built-in storage medium of the control terminal 110. After the control terminal 110 assigns the burning task to the firmware burning terminal 120 that currently establishes a communication connection, the firmware file is sent to the specified path of the firmware burning terminal 120 based on the communication connection, so that the firmware burning terminal 120 can burn the firmware file into the DPU card according to the instruction of the burning task after receiving the burning task. The DPU card is installed on a powered PCIE board 130 connected to the firmware burning terminal 120.

[0086] In actual implementation, the firmware file can also be stored in an external storage medium independent of the control terminal 110, such as a USB flash drive, a hard disk, etc., or stored in a cloud server. This embodiment does not limit the storage method of the firmware file.

[0087] like Figure 1 As shown, each firmware burning terminal 120 is connected to a powered PCIE board 130. Figure 1In the figure, the number of powered PCIE boards 130 connected to the firmware burning terminal 120 is one as an example for explanation. In actual implementation, the number of powered PCIE boards 130 is one or at least two. This implementation does not limit the number of powered PCIE boards 130.

[0088] Each powered PCIE board 130 is provided with at least one PCIE card slot.

[0089] In one example, each PCIE card slot has a corresponding card slot interface. Accordingly, the DPU card is installed on the powered PCIE board 130 through the PCIE card slot provided on the powered PCIE board 130; the firmware burning terminal 120 is connected to the card slot interface on the powered PCIE board 130, and based on the card slot interface, the firmware file is burned into the DPU card.

[0090] For example: Reference Figure 2 ,by Figure 2 Taking the powered PCIE board 130 as an example, there are 4 PCIE card slots on it, and each PCIE card slot has a corresponding card slot interface; the DPU card is inserted into the 4 PCIE card slots, and the firmware burning terminal is respectively connected to the card slot interfaces corresponding to the 4 PCIE card slots.

[0091] In another example, the DPU card includes a link interface, the DPU card is installed in a PCIE card slot, the firmware burning terminal is connected to the DPU card and the powered PCIE board 130 through the link interface on the DPU card, and based on the link interface, the firmware file is burned into the DPU card.

[0092] In the traditional DPU card firmware system, refer to Figure 3 The PCIE card slot is set on the motherboard of the computing device. When the DPU card needs to be replaced, the operator needs to shut down the computing device and manually disassemble the shell of the computing device. After replacing the DPU card, the shell of the computing device is assembled and the computing device is started again, which makes the DPU card firmware burning process cumbersome and the firmware file burning efficiency low.

[0093] In this embodiment, the burning task is assigned to the currently connected firmware burning terminal 120 through the control terminal 120, and the firmware burning terminal 120 is connected to the powered PCIE board; at least one PCIE card slot is provided on the powered PCIE board, and the user does not need to manually disassemble, install and restart the firmware burning terminal 120, thereby simplifying the DPU card firmware burning process and improving the DPU card burning efficiency.

[0094] Specifically, the firmware burning terminal 120 is used to: determine the DPU card on the currently connected powered PCIE board when receiving the burning task and the firmware file; execute the firmware burning script to burn the firmware file into the DPU card; the firmware burning script is used to load the firmware file into the DPU card, and after the burning is completed, verify the burning process of the DPU card to obtain the burning process verification result; when the burning process verification result indicates that the DPU card burning process is correct, determine whether there are remaining burning tasks in the burning task list; when there are no remaining burning tasks, end the firmware burning terminal burning task.

[0095] Among them, the firmware burning script is a script that executes the firmware file burning and feeds back the burning process verification results. It is a TCL script written based on the FPGA firmware burning TCL mode technology.

[0096] The following is a detailed introduction to the DPU card firmware burning method provided by this application.

[0097] like Figure 4 As shown, the embodiment of the present application provides a DPU card firmware burning method, and this embodiment uses the method for Figure 1 Taking the system shown in FIG. 1 as an example, the method at least includes steps S401 to S408:

[0098] Step S401: sending a connection instruction to at least one firmware burning terminal respectively through a control terminal to search for at least one firmware burning terminal.

[0099] Before executing the firmware file burning task, it is necessary to first determine the available firmware burning terminals in the firmware burning terminal. Based on this, in this embodiment, the control terminal sends a connection instruction to each firmware burning terminal respectively to find an available firmware burning terminal in at least one firmware burning terminal as the current firmware burning terminal.

[0100] Step S402: when a firmware burning terminal is found, a communication connection is established with the found current firmware burning terminal through the control terminal.

[0101] The communication connection between the control terminal and the current firmware burning terminal includes a wired connection and / or a wireless communication connection. This embodiment does not limit the type of the communication connection between the control terminal and the current firmware burning terminal.

[0102] In one example, a wired communication connection is established between the control terminal and each firmware burning terminal.

[0103] In another example, a wireless communication connection is established between the control terminal and each firmware burning terminal.

[0104] In addition, after the control terminal sends the connection instruction, if no feedback information is received from the firmware burning terminal, the control terminal also needs to send a prompt message to prompt the user to check the current burning environment, including the device status of the firmware burning terminal or the device status of the control terminal.

[0105] Specifically, when the firmware burning terminal is not found, the method further includes: outputting connection prompt information through the control terminal to prompt the user to check the current burning environment.

[0106] The implementation of the prompt information includes but is not limited to: text information display instructions; and / or prompt audio.

[0107] When the prompt information is a text information display instruction, the connection prompt information is output through the control terminal to prompt the user to check the current programming environment, including: sending the text information display instruction to the designated program through the control terminal.

[0108] In one example, the designated program is a program installed in a designated device, and the designated program has the function of displaying text information. The designated program may be a separately developed application program, or a functional module embedded in an existing program. This embodiment does not limit the implementation method of the designated program.

[0109] The designated device is connected to the control terminal by wire or wireless communication, and the designated device has a display function to display the text information displayed by the designated program. Schematically, the designated device includes an electronic device with a display interface such as a mobile phone and / or a tablet computer, and this embodiment does not limit the implementation method of the designated device.

[0110] In another example, the designated program is a program installed in the control terminal. At this time, the control terminal is also provided with a display component to display the text information displayed by the designated program.

[0111] In the case where the prompt information is a prompt audio, the control terminal also includes an audio output component. Accordingly, outputting the connection prompt information through the control terminal to prompt the user to check the current programming environment includes: playing the prompt audio through the audio output component of the control terminal.

[0112] In other embodiments, the prompt information may also include an audio prompt instruction, and the audio prompt instruction is used to instruct the designated program to play a prompt audio. Accordingly, outputting the connection prompt information through the control terminal to prompt the user to check the current programming environment includes: sending an audio prompt instruction to the designated program through the control terminal. Alternatively, the prompt information includes at least two of a prompt audio, a text information display instruction, and an audio prompt instruction. This embodiment does not limit the implementation method of the prompt information.

[0113] Step S403, based on the communication connection, the burning task is allocated to the current firmware burning terminal through the control terminal, so that the current firmware burning terminal adds the received burning task to the burning task list.

[0114] The burning task includes at least one burning subtask. After establishing a communication connection with an available current firmware burning terminal among at least one firmware burning terminal, the control terminal allocates each burning subtask in the burning task to the current firmware burning terminal according to a preset allocation method, so that the current firmware burning terminal adds the received burning task to a task list.

[0115] In this embodiment, allocating the burning subtask in the burning task to the current firmware burning terminal according to the preset allocation method includes at least the following situations:

[0116] The first one is a preset allocation method that evenly allocates the burning task to each current firmware burning terminal according to the number of current firmware burning terminals.

[0117] The second is a preset allocation method, which is based on the programming capability of each current firmware programming terminal, and allocates the programming task to each current firmware programming terminal in proportion.

[0118] In this embodiment, each current firmware burning terminal is connected to at least one powered PCIE board, and each powered PCIE board is provided with at least one PCIE card slot. After establishing a communication connection with the current firmware burning terminal, the control terminal obtains the preset DPU card link quantity of each current firmware burning terminal based on the communication connection to determine the burning capacity of each firmware burning terminal.

[0119] The preset DPU card link quantity refers to the number of DPU cards that can be linked to the pre-set firmware burning terminal, and the preset DPU card link quantity is less than or equal to the number of PCIE card slots of the firmware burning terminal.

[0120] For example: Reference Figure 5, take the case where the burning task includes 12 burning subtasks, and the current number of firmware burning terminals is 2, including firmware burning terminal A1 and firmware burning terminal A2; wherein the firmware burning terminal A1 is connected to the powered PCIE board B1 and the powered PCIE board B2 respectively, and the firmware burning terminal A2 is connected to the powered PCIE board B3; when there are 4 PCIE card slots on each powered PCIE board and the preset number of DPU card links is 4, 8 burning subtasks are allocated to the firmware burning terminal A1, and 4 burning subtasks are allocated to the firmware burning terminal A2; when the powered PCIE board B1 includes 1 PCIE card slot and the preset number of DPU card links is 1, the powered PCIE board B2 includes 3 PCIE card slots and the preset number of DPU card links is 2, and the powered PCIE board B3 includes 8 PCIE card slots and the preset number of DPU card links is 3, 2 burning subtasks are allocated to the firmware burning terminal A1, and 10 burning subtasks are allocated to the firmware burning terminal A2.

[0121] Specifically, the burning task is allocated to the current firmware burning terminal through the control terminal, including: allocating the burning task evenly to the current firmware burning terminal according to the number of current firmware burning terminals through the control terminal; or, obtaining the preset DPU card link number corresponding to each current firmware burning terminal through the control terminal; and allocating the burning task to the found firmware burning terminal based on the preset DPU card link number.

[0122] In actual implementation, the number of powered-on PCIE boards and the preset number of DPU card links corresponding to each firmware burning terminal can also be pre-stored in the control terminal. After establishing a communication connection with each current firmware burning terminal, the control terminal obtains the terminal identification of each current firmware burning terminal, and obtains the number of powered-on PCIE boards and the number of PCIE card slots corresponding to each current firmware terminal based on the terminal identification.

[0123] The terminal identification is a number, a letter, or a combination of numbers and letters, and is used to uniquely indicate the firmware burning terminal; this embodiment does not limit the implementation method of the terminal identification.

[0124] Specifically, the preset DPU card link quantity corresponding to each current firmware burning terminal is obtained through the control terminal, including: based on the communication connection, receiving the current terminal identifier sent by each current firmware burning terminal through the control terminal; and finding out the preset DPU card link quantity corresponding to each current firmware burning terminal according to the current terminal identifier and the preset relationship between the terminal identifier and the preset DPU card link quantity through the control terminal.

[0125] In another embodiment, after establishing a communication connection with the current firmware burning terminal, the control terminal obtains the number of PCIE card slots and / or computing resources of each current firmware burning terminal based on the communication connection to determine the burning capability of each firmware burning terminal.

[0126] In another embodiment, after establishing a communication connection with the current firmware burning terminal, the control terminal obtains the number of currently linked DPU cards of each current firmware burning terminal based on the communication connection to determine the burning capability of each firmware burning terminal.

[0127] The computing resources include central processing unit resources (CPU Resources) and memory resources, etc. This embodiment does not limit the types of computing resources.

[0128] Step S404: Send the firmware file corresponding to the burning task to the current firmware burning terminal through the control terminal.

[0129] Among them, the firmware files include programming files and programming configuration files.

[0130] Programming files are the core files in the firmware burning process. They contain the actual firmware code, data or program. Programming files describe the device's functions, operating system, driver, etc., usually expressed in binary or specific format code. Programming files are responsible for updating the device's firmware to give it new features or fix existing problems.

[0131] The programming configuration file contains the configuration information of the burning process to ensure that the firmware is correctly burned to the target device. The programming configuration file includes configuration parameters such as the address range of the burning, the burning options, and the burning algorithm. The programming configuration file is very important to ensure the accuracy and effectiveness of the burning. They ensure that the programming file is correctly written to the specified location of the device.

[0132] Step S405, determining, through the current firmware burning terminal, a DPU card on a powered-on PCIE board to which the current firmware burning terminal is currently connected.

[0133] Step S406, executing the firmware burning script through the current firmware burning terminal, burning the firmware file into the DPU card through the card slot interface and obtaining the burning process verification result.

[0134] In this embodiment, each current firmware burning terminal is respectively connected to a corresponding powered PCIE board to burn the firmware file into the DPU card, wherein the DPU card is inserted into the PCIE card slot.

[0135] Since the number of PCIE card slots on each powered PCIE board is at least one, in this embodiment, the number of DPU cards inserted in each powered PCIE board is also at least one.

[0136] Accordingly, executing the firmware burning script through the current firmware burning terminal to burn the firmware file into the DPU card includes at least one of the following situations:

[0137] The first method is to burn the firmware files into the DPU cards in the order of the PCIE card numbers.

[0138] In this embodiment, a temporary card number is assigned to the DPU card after it is installed in the PCIE card slot. The DPU cards on the same powered-on PCIE board have different corresponding numbers, and the DPU cards installed on different powered-on PCIE boards have the same or different corresponding numbers.

[0139] Specifically, when the number of DPU cards is at least one, the firmware burning script is executed through the current firmware burning terminal to burn the firmware file into the DPU card, including: obtaining the PCIE card number corresponding to each DPU card; based on the arrangement order of the PCIE card numbers, the firmware burning script is executed through the current firmware burning terminal to burn the firmware files into the DPU cards in sequence.

[0140] For example: Reference Figure 5 Taking the firmware burning terminal A2 as an example, the powered PCIE board B3 connected to the firmware burning terminal A2 includes 3 PCIE card slots, and the PCIE card numbers are P1, P2 and P3 respectively; when the firmware burning terminal A2 is burning the firmware, the firmware file is burned in sequence according to the order of P1, P2 and P3; or, when the firmware burning terminal A2 is burning the firmware, the firmware file is burned in sequence according to the order of P3, P2 and P1.

[0141] The second method is to burn the firmware files into the DPU card in parallel.

[0142] Specifically, when there is at least one DPU card, the firmware burning script is executed through the current firmware burning terminal to burn the firmware file into the DPU card, including: executing the firmware burning script through the current firmware burning terminal to burn the firmware files into the DPU cards in parallel.

[0143] In other embodiments, each current firmware burning terminal burns the firmware file in a manner including parallel burning and sequential burning in the order of PCIE card numbers; the current firmware burning can determine which method to use based on current computing resources.

[0144] Specifically, executing the firmware burning script through the current firmware burning terminal to burn the firmware file into the DPU card also includes: obtaining the computing resources corresponding to the current burning terminal through the current firmware burning terminal; when the current computing resources are greater than or equal to the preset computing resources, burning the firmware file into the DPU card in parallel;

[0145] Alternatively, when the current computing resources are less than the preset computing resources, obtain the PCIE card number corresponding to each DPU card; based on the arrangement order of the PCIE card numbers, execute the firmware burning script through the current firmware burning terminal to burn the firmware files into the DPU cards in sequence.

[0146] In addition, the firmware file in this embodiment includes a programming file and a programming configuration file. Accordingly, the firmware burning script is executed through the current firmware burning terminal to burn the firmware file into the DPU card, including: executing the firmware burning script through the firmware burning terminal to burn the configuration information in the programming file into the DPU card; verifying the DPU card through the programming verification file to obtain the burning process verification result.

[0147] Step S407: when the burning process verification result indicates that the DPU card burning process is correct, determine whether there are any remaining burning tasks in the burning task list through the current firmware burning terminal.

[0148] If the verification results of the burning process corresponding to the DPU card all indicate that the burning process is correct, a step of determining whether there are remaining burning tasks in the burning task list through the current firmware burning terminal is performed.

[0149] When the burning mode is parallel burning of the DPU cards on the powered PCIE board, if one or at least two of the burning process verification results corresponding to the DPU card indicate a burning process error, an error prompt message is output through the firmware burning terminal.

[0150] For example, if the number of DPU cards installed on the powered PCIE board is 2, if one or two of the burning process verification results corresponding to the two DPU cards indicate a burning process error, an error prompt message is output through the current firmware burning terminal.

[0151] Specifically, when the verification result indicates that the DPU card burning process is wrong, the method further includes: outputting error prompt information through the firmware burning terminal to prompt the user to check the current burning environment.

[0152] Accordingly, when the burning method is to burn in sequence according to the order of PCIE card numbers, if the currently fed back burning process verification result indicates that the burning process is wrong, an error prompt message is output through the firmware burning terminal.

[0153] For example: taking the number of DPU cards on the powered PCIE board as 2 as an example, if after executing the burning of the first DPU card, the burning process verification result obtained indicates that the burning failed, an error prompt message is output through the current firmware burning terminal; or, after executing the burning of the first DPU card, the burning process verification result obtained indicates that the burning is successful, then the burning of the second DPU card is executed. If the burning process verification result corresponding to the second DPU card indicates that the burning failed, an error prompt message is output through the current firmware burning terminal.

[0154] Step S408, when there is no remaining burning task, the burning task of the current firmware burning terminal is terminated.

[0155] In this embodiment, when there are no remaining tasks in the task list corresponding to the current firmware burning terminal, the burning task corresponding to the current firmware burning terminal has been completed; accordingly, when there are remaining tasks in the task list, a prompt message is output through the current firmware burning terminal to prompt the user to replace the DPU card, and then, after receiving the feedback indication indicated by the user, the DPU card inserted in the connected powered PCIE board is determined, and the burning of the firmware file is executed until the task list is cleared.

[0156] Specifically, when there are remaining burning tasks, the method also includes: outputting replacement prompt information through the current firmware burning terminal to prompt the user to replace the DPU card on the powered PCIE board to which the current firmware burning terminal is currently connected; in response to the received feedback indication, executing the step of determining the DPU card on the powered PCIE board to which the current firmware burning terminal is currently connected through the current firmware burning terminal.

[0157] The feedback indication refers to an indication input to the current firmware burning terminal by a user through an input device connected to the current firmware burning terminal, such as a keyboard or a mouse, after the DPU card is replaced; or the feedback indication refers to an indication input by a user through interaction with a display screen of the current firmware burning terminal after the DPU card is replaced. This embodiment does not limit the implementation method of the feedback indication.

[0158] In order to more clearly understand the DPU card firmware burning method provided by the present application, an example is given below to illustrate the method. In this example, the firmware burning terminal is used to implement automatic burning through a programming language script as an example for explanation, wherein the programming language script refers to a script that combines a python script with a shell script, which is used to combine the operating system information of the firmware burning terminal and the firmware burning script feedback to form a complete DPU card firmware burning automation system as a whole, refer to Figure 6 The method includes the following steps S601 to S618:

[0159] Step S601, specifying a burning program by punching in a programming language script; wherein the specified burning program includes Vivado Hardware Manager (Vivado Hardware Manager) or Quartus Prime Programmer (Quartus Prime Programmer) and the like.

[0160] Step S602, connecting to a powered PCIE board, allowing a non-joint test operation group to connect.

[0161] Step S603, determine whether to open the target hardware, if the target hardware is opened, execute step S604; otherwise, execute step S617; wherein the target hardware includes a powered PCIE board and hardware built into the firmware burning terminal, such as a network card built into the firmware burning terminal.

[0162] Step S604, selecting a powered-on PCIE board.

[0163] Step S605, refresh the powered-on PCIE board without updating the hardware detection.

[0164] Step S606: Create a hardware configuration storage object of the powered-on PCIE board.

[0165] Step S607, setting programming options.

[0166] Step S608, power on the PCIE board.

[0167] Step S609, setting the programming address range.

[0168] Step S610, determining whether the programming file path is set, if the programming file path is set, executing step S611; otherwise, executing step S618. The programming file is an MCS file or a BIN file.

[0169] Step S611, determining whether the programming parameter file path is set; if the programming parameter file path is set, executing step S612, otherwise executing step S618. The programming parameter file is a PRM file.

[0170] Step S612, setting the termination mode of unused pins.

[0171] Step S613, setting the burning options.

[0172] Step S614, execute the firmware burning script to start the burning process.

[0173] Step S615, restart the powered-on PCIE board.

[0174] Step S616, refresh the powered-on PCIE board and execute step S619.

[0175] Step S617, generate an error number and feedback the first error prompt information, and execute step S619. The first error prompt information is used to prompt the user to check the current programming environment.

[0176] Step S618, generating an error number and feeding back a second error prompt message, and executing step S619. The second error prompt message is used to prompt the user to check the current programming environment.

[0177] Step S619, exit the programming language script.

[0178] In order to more clearly understand the DPU card firmware burning method provided by the present application, another example is given below to illustrate the method. In this example, the above-mentioned DPU card firmware burning system is used as an example for explanation. Figure 7 The method includes the following steps S701 to S711:

[0179] Step S701, starting a target program of the control terminal through the control terminal, and sending a connection instruction to the firmware burning terminal to find the firmware burning terminal.

[0180] Step S702, determining whether a firmware burning terminal is found by controlling the terminal, if a firmware burning terminal is found, executing step S703, otherwise, executing step S711.

[0181] Step S704, sending the firmware file to the firmware burning terminal through the control terminal.

[0182] Step S705, executing the burning script through the firmware burning terminal.

[0183] Step S706, determining whether the firmware burning script is executed normally through the firmware burning terminal, if the firmware burning script is executed normally, executing step S707, otherwise executing step S708.

[0184] Step S707, outputting a replacement prompt message through the firmware burning terminal to prompt the user to replace the DPU card and continue to execute the burning task until the burning task is cleared, and then executing step S712.

[0185] Step S708: Generate an error number through the firmware burning terminal and output an error prompt message to prompt the user to check the current burning environment.

[0186] Step S709, receiving user feedback indication through the firmware burning terminal, and determining whether the burning task can be continued. If the burning task can be continued, executing step S707, otherwise, executing step S710.

[0187] Step S710: Generate an error number and feedback error prompt information through the firmware burning terminal.

[0188] Step S711, ending the target program in the control terminal through the control terminal.

[0189] The DPU card firmware burning method provided in this embodiment sends connection instructions to at least one firmware burning terminal respectively through a control terminal to find at least one firmware burning terminal; when the firmware burning terminal is found, a communication connection is established with the found current firmware burning terminal through the control terminal; based on the communication connection, the burning task is assigned to the current firmware burning terminal through the control terminal, so that the current firmware burning terminal adds the received burning task to the burning task list; the firmware file corresponding to the burning task is sent to the current firmware burning terminal through the control terminal; the DPU card on the powered-on PCIE board currently connected to the current firmware burning terminal is determined through the current firmware burning terminal; the firmware burning script is executed through the current firmware burning terminal to burn the firmware file into the DPU card and obtain the burning process verification result; when the burning process verification result indicates that the DPU card burning process is correct, the current firmware burning terminal The terminal determines whether there are remaining burning tasks in the burning task list; when there are no remaining burning tasks, the burning task of the current firmware burning terminal is ended; the problem of cumbersome and inefficient DPU card firmware burning process can be solved; the burning task is assigned to the currently connected firmware burning terminal through the control terminal, the firmware burning terminal is connected to the powered PCIE board, and the powered PCIE board is provided with at least one PCIE card slot, and the firmware file is burned into the DPU network card inserted in the PCIE card slot; there is no need for users to manually disassemble and install and restart the firmware burning terminal frequently, therefore, the DPU card firmware burning process can be simplified and the DPU card burning efficiency can be improved; at the same time, a communication connection is established between the control terminal and at least one firmware burning terminal, so that the control terminal can simultaneously control multiple firmware burning terminals to execute burning tasks, and in the case of a large number of burning tasks, the DPU card firmware burning efficiency can be further improved.

[0190] Furthermore, a powered PCIE board is connected to a firmware burning terminal, and the DPU card is installed on the powered PCIE board for firmware burning. Through the scalability of the powered PCIE board, the number of PCIE card slots of the powered PCIE board connected to the firmware burning terminal can be expanded, and the scale of DPU card firmware burning can be increased. At the same time, the powered PCIE board only needs to be connected to the firmware burning terminal, is not restricted by the environment, and can be placed at any position in the burning environment. Therefore, the problem of low adaptability and poor scalability caused by the environmental restrictions of the computing device is avoided.

[0191] Furthermore, by replacing the mainboard of the computing device with a powered-on PCIE board, when there are a large number of burning tasks, there is no need to use a large number of computing devices, which can reduce the cost of burning the DPU card firmware.

[0192] Furthermore, by replacing the mainboard of the computing device with a powered-on PCIE board, the user does not need to manually disassemble the computing device, thereby reducing the frequency of manual operations by the user. The user does not need to judge the burning process or learn a complicated burning process. The user only needs to replace the DPU card to be burned and provide error information feedback, thereby reducing the user's learning cost and the probability of firmware burning failure due to manual operation errors by the user, thereby increasing the success rate of DPU card firmware burning.

[0193] Furthermore, since computing devices are precision instruments and the shell disassembly steps are relatively many, precision instrument motherboard protection facilities are also many, such as: clips, screws and wiring tape, etc., by powering on the PCIE board to replace the motherboard of the computing device, there is no need for users to manually disassemble the computing device, thereby reducing the frequency of user manual operations, reducing the time for hardware replacement, computing device shell disassembly time and motherboard replacement time, which can reduce time costs and improve firmware burning efficiency.

[0194] This embodiment provides a DPU card firmware burning device, such as Figure 8 As shown. In this embodiment, the device is applied to Figure 1 In the DPU card firmware burning system shown, the device includes at least the following modules: a terminal search module 810, a communication connection module 820, a task allocation module 830, a file sending module 840, a hardware determination module 850, a script execution module 860, a task determination module 870 and a task end module 880.

[0195] The terminal search module 810 is used to send a connection instruction to at least one firmware burning terminal through the control terminal to search for at least one firmware burning terminal.

[0196] The communication connection module 820 is used to establish a communication connection with the found current firmware burning terminal through the control terminal when the firmware burning terminal is found.

[0197] The task allocation module 830 is used to allocate the burning task to the current firmware burning terminal through the control terminal based on the communication connection, so that the current firmware burning terminal adds the received burning task to the burning task list.

[0198] The file sending module 840 is used to send the firmware file corresponding to the burning task to the current firmware burning terminal through the control terminal.

[0199] The hardware determination module 850 is used to determine, through the current firmware burning terminal, the DPU card on the powered-on PCIE board to which the current firmware burning terminal is currently connected.

[0200] The script execution module 860 is used to execute the firmware burning script through the current firmware burning terminal, burn the firmware file into the DPU card and obtain the burning process verification result.

[0201] The task determination module 870 is used to determine whether there are any remaining burning tasks in the burning task list through the current firmware burning terminal when the burning process verification result indicates that the DPU card burning process is correct.

[0202] The task ending module 880 is used to end the burning task of the current firmware burning terminal when there is no remaining burning task.

[0203] For relevant details, refer to the above method and system embodiments.

[0204] It should be noted that: the DPU card firmware burning device provided in the above embodiment only uses the division of the above functional modules as an example when burning the DPU card firmware. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the DPU card firmware burning device is divided into different functional modules to complete all or part of the functions described above. In addition, the DPU card firmware burning device provided in the above embodiment and the DPU card firmware burning method embodiment belong to the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0205] This embodiment provides an electronic device, such as Fig. 9 The electronic device can be Figure 1 The electronic device at least comprises a processor 901 and a memory 902.

[0206] The processor 901 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 901 may be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). The processor 901 may also include a main processor and a coprocessor. The main processor is a processor for processing data in the awake state, also known as a CPU (Central Processing Unit); the coprocessor is a low-power processor for processing data in the standby state. In some embodiments, the processor 901 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 901 may also include an AI (Artificial Intelligence) processor, which is used to process computing operations related to machine learning.

[0207] The memory 902 may include one or more computer-readable storage media, which may be non-transitory. The memory 902 may also include a high-speed random access memory, and a non-volatile memory, such as one or more disk storage devices, flash memory storage devices. In some embodiments, the non-transitory computer-readable storage medium in the memory 902 is used to store at least one instruction, which is used to be executed by the processor 901 to implement the DPU card firmware burning method provided in the method embodiment of the present application.

[0208] In some embodiments, the electronic device may further optionally include: a peripheral device interface and at least one peripheral device. The processor 901, the memory 902 and the peripheral device interface may be connected via a bus or a signal line. Each peripheral device may be connected to the peripheral device interface via a bus, a signal line or a circuit board. Schematically, the peripheral devices include but are not limited to: a radio frequency circuit, a touch display screen, an audio circuit, and a power supply.

[0209] Of course, the electronic device may also include fewer or more components, which is not limited in this embodiment.

[0210] Optionally, the present application also provides a computer-readable storage medium, in which a program is stored, and the program is loaded and executed by a processor to implement the DPU card firmware burning method of the above method embodiment.

[0211] The technical features of the above-described embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above-described embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0212] Obviously, the embodiments described above are only some embodiments of the present application, rather than all embodiments. Based on the embodiments in the present application, ordinary technicians in this field can make other different forms of changes or modifications without making creative work, which should all fall within the scope of protection of the present application.

Claims

1. A DPU card firmware burning method, characterized in that: The invention is applied to a DPU card firmware burning system, wherein the DPU card firmware burning system comprises a control terminal and at least one firmware burning terminal, at least one powered PCIE board correspondingly connected to each firmware burning terminal, each powered PCIE board being used to distribute the power supply of the PCIE interface; each powered PCIE board is provided with at least one PCIE card slot; each PCIE card slot has a corresponding card slot interface, and a DPU card is installed on the powered PCIE board through the PCIE card slot; the firmware burning terminal is respectively connected to the card slot interface on the corresponding powered PCIE board; each powered PCIE board is also used to expand the number of PCIE card slots of the powered PCIE board connected to the firmware burning terminal through the extensibility of each powered PCIE board; the method comprises the following steps: Sending connection instructions to the at least one firmware burning terminal respectively through the control terminal to search for the at least one firmware burning terminal; When a firmware burning terminal is found, a communication connection is established with the found current firmware burning terminal through the control terminal; Based on the communication connection, allocating the burning task to the current firmware burning terminal through the control terminal, so that the current firmware burning terminal adds the received burning task to the burning task list; Sending the firmware file corresponding to the burning task to the current firmware burning terminal through the control terminal; Determine, through the current firmware burning terminal, a DPU card on a powered PCIE board to which the current firmware burning terminal is currently connected; Execute the firmware burning script through the current firmware burning terminal, burn the firmware file into the DPU card based on the card slot interface and obtain the burning process verification result; When the burning process verification result indicates that the DPU card burning process is correct, determining whether there are any remaining burning tasks in the burning task list through the current firmware burning terminal; When there is no remaining burning task, the burning task of the current firmware burning terminal is terminated.

2. The DPU card firmware burning method according to claim 1, characterized in that: In the case where there are remaining burning tasks, the method further includes: Outputting replacement prompt information through the current firmware burning terminal to prompt the user to replace the DPU card on the powered PCIE board currently connected to the current firmware burning terminal; In response to the received feedback indication, the step of determining, through the current firmware burning terminal, a DPU card on a powered-on PCIE board to which the current firmware burning terminal is currently connected is performed.

3. The DPU card firmware burning method according to claim 1, characterized in that: In the case that the number of the DPU card is at least one, executing the firmware burning script through the current firmware burning terminal to burn the firmware file into the DPU card includes: Get the PCIE card number corresponding to each DPU card; Based on the arrangement order of the PCIE card numbers, the firmware burning script is executed through the current firmware burning terminal to burn the firmware files into the DPU card in sequence.

4. The DPU card firmware burning method according to claim 1, characterized in that: In the case that the number of the DPU cards is at least one, executing the firmware burning script through the current firmware burning terminal to burn the firmware file into the DPU card includes: executing the firmware burning script through the current firmware burning terminal to burn the firmware files into the DPU cards in parallel.

5. The DPU card firmware burning method according to claim 1, characterized in that: The firmware file includes a programming file and a programming configuration file, and the step of executing a firmware burning script through the current firmware burning terminal to burn the firmware file into the DPU card includes: Execute the firmware burning script through the current firmware burning terminal to burn the configuration information in the programming file into the DPU card; The DPU card is verified through the programming configuration file to obtain the programming process verification result.

6. The DPU card firmware burning method according to claim 1, characterized in that: The allocating the burning task to the current firmware burning terminal through the control terminal includes: Distributing the burning task evenly to the current firmware burning terminals according to the number of the current firmware burning terminals by the control terminal; or, The preset DPU card link quantity corresponding to each current firmware burning terminal is obtained through the control terminal; and the burning task is allocated to the found firmware burning terminal based on the preset DPU card link quantity.

7. The DPU card firmware burning method according to claim 1, characterized in that: In the case that the firmware burning terminal is not found, the method further includes: The control terminal outputs connection prompt information to prompt the user to check the current programming environment.

8. The DPU card firmware burning method according to claim 1, characterized in that: When the verification result indicates that the DPU card programming process is wrong, the method further includes: The firmware burning terminal outputs an error prompt message to prompt the user to check the current burning environment.

9. A DPU card firmware burning system, characterized in that: The system comprises: a control terminal and at least one firmware burning terminal, at least one powered PCIE board correspondingly connected to each firmware burning terminal, each powered PCIE board being used to distribute the power supply of the PCIE interface; each powered PCIE board being provided with at least one PCIE card slot; each PCIE card slot having a corresponding card slot interface, and a DPU card being installed on the powered PCIE board through the PCIE card slot; the firmware burning terminal being respectively connected to the card slot interface on the corresponding powered PCIE board; each powered PCIE board being further used to expand the number of PCIE card slots of the powered PCIE board connected to the firmware burning terminal through the extensibility of each powered PCIE board; The control terminal is used to: send a connection instruction to the at least one firmware burning terminal respectively to find the at least one firmware burning terminal; when the firmware burning terminal is found, establish a communication connection with the current firmware burning terminal found; based on the communication connection, assign the burning task to the current firmware burning terminal, so that the current firmware burning terminal adds the received burning task to the burning task list; send the firmware file corresponding to the burning task to the current firmware burning terminal; The firmware burning terminal is used to: determine the DPU card on the currently connected powered PCIE board when receiving the burning task and the firmware file; execute the firmware burning script to burn the firmware file into the DPU card based on the card slot interface; the firmware burning script is a TCL script; the firmware burning script is used to load the firmware file into the DPU card, and verify the burning process of the DPU card after the burning process is completed to obtain a burning process verification result; when the burning process verification result indicates that the DPU card burning process is correct, determine whether there are remaining burning tasks in the burning task list; if there are no remaining burning tasks, end the burning task of the firmware burning terminal.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the steps of the method according to any one of claims 1 to 8 are implemented.