Firmware burning method and device, electronic equipment and medium
During the production process of the appliance, the specific identifiers associated with the motherboard are read, and the corresponding station is determined whether the corresponding station is the previous station of the current station, and the program is burned when necessary, the problem of omissions in the motherboard processing process is solved, and the production efficiency is improved and costs are reduced.
Patent Information
- Application Number
- CN202411948949.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-26
- Publication Date
- 2025-05-02
AI Technical Summary
During the centralized production stage of the appliance, due to misoperation of production line personnel, there are omissions in the processing process of the motherboard, which brings the risk of abnormal firmware burning, thereby increasing product failure rate, reducing production efficiency and increasing costs.
By reading the specific identifier associated with the target motherboard under the current station, it is determined whether the corresponding station is the previous station of the current station. If so, burn the corresponding program in the target motherboard to ensure that the motherboard processing is not missed.
It effectively avoids omissions in motherboard processing, reduces firmware burnout abnormalities, reduces product defect rate, improves production efficiency, and reduces costs.
Smart Images
Figure CN119917119A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the technical field of electronic equipment, and in particular, relates to a firmware burning method, device, electronic equipment and medium. Background Art
[0002] During the production of the device, the mainboard needs to be processed according to the process to achieve firmware burning.
[0003] During the centralized production phase of the equipment, due to the large volume of product shipments, it has been found that due to misoperation by production line personnel, some motherboard processing procedures are missed, resulting in the risk of abnormal firmware burning. These problems will lead to an increase in product defect rate, reduced production efficiency and increased costs. Summary of the invention
[0004] The embodiments of the present application provide a firmware burning method, device, electronic device and medium to solve the problem in the prior art that there are omissions in the processing procedures of the motherboard, which brings the risk of abnormal firmware burning.
[0005] A first aspect of an embodiment of the present application provides a firmware burning method, comprising:
[0006] Reading, at the first station, a specific identifier stored in association with the target motherboard;
[0007] In case the specific identifier is read, determining a second workstation corresponding to the specific identifier;
[0008] If the second workstation is the previous workstation of the first workstation, the first program is burned into the target mainboard.
[0009] A second aspect of an embodiment of the present application provides a firmware burning device, including:
[0010] A data reading module, used for reading a specific identifier stored in association with a target mainboard at a first workstation;
[0011] A data determination module, configured to determine a second workstation corresponding to the specific identifier when the specific identifier is read;
[0012] A program burning module is used to burn the first program in the target mainboard if the second workstation is the previous workstation of the first workstation.
[0013] A third aspect of an embodiment of the present application provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the method described in the first aspect when executing the computer program.
[0014] A fourth aspect of an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method described in the first aspect are implemented.
[0015] A fifth aspect of the present application provides a computer program product, which, when executed on an electronic device, enables the electronic device to execute the steps of the method described in the first aspect.
[0016] As can be seen from the above, in the scheme of the embodiment of the present application, the specific identifier stored in association with the target mainboard is read at the current workstation, so that the specific identifier recorded in the mainboard is introduced during the processing of the mainboard. When the specific identifier can be read for the current mainboard, it is determined whether the workstation corresponding to the specific identifier is the previous workstation of the current workstation to determine whether there is any process omission in the processing of the mainboard, and when the workstation corresponding to the specific identifier is the previous workstation of the current workstation, the program is burned in the target mainboard, which can effectively avoid process omissions in the processing of the mainboard, reduce firmware burning anomalies, reduce product defective rate, improve production efficiency and reduce costs. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0018] Figure 1 This is a process of a firmware burning method provided in an embodiment of the present application Figure 1 ;
[0019] Figure 2 This is a process of a firmware burning method provided in an embodiment of the present application Figure 2 ;
[0020] Figure 3 is a structural diagram of a firmware burning device provided in an embodiment of the present application;
[0021] Figure 4 It is a structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0022] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.
[0023] It should be understood that when used in this specification and the appended claims, the term "comprising" indicates the presence of described features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof.
[0024] It should also be understood that the terms used in this application specification are only for the purpose of describing specific embodiments and are not intended to limit the application. As used in this application specification and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" are intended to include plural forms.
[0025] It should be further understood that the term “and / or” used in the specification and appended claims refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.
[0026] As used in this specification and the appended claims, the term "if" may be interpreted as "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if [described condition or event] is detected" may be interpreted as meaning "upon determination" or "in response to determining" or "upon detection of [described condition or event]" or "in response to detecting [described condition or event]," depending on the context.
[0027] In a specific implementation, the electronic devices described in the embodiments of the present application include, but are not limited to, other portable devices such as mobile phones, laptop computers, or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and / or touch pads). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with a touch-sensitive surface (e.g., touch screen displays and / or touch pads).
[0028] In the following discussion, an electronic device including a display and a touch-sensitive surface is described. However, it should be understood that the electronic device may include one or more other physical user interface devices such as a physical keyboard, mouse, and / or joystick.
[0029] The electronic device supports various applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk burning application, a spreadsheet application, a game application, a telephone application, a video conferencing application, an email application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital camcorder application, a web browsing application, a digital music player application, and / or a digital video player application.
[0030] Various applications that can be executed on an electronic device can use at least one common physical user interface device such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the electronic device can be adjusted and / or changed between applications and / or within corresponding applications. In this way, a common physical architecture of an electronic device (e.g., a touch-sensitive surface) can support a variety of applications with user interfaces that are intuitive and transparent to the user.
[0031] It should be understood that the size of the serial numbers of the steps in this embodiment does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.
[0032] In order to illustrate the technical solution described in this application, a specific embodiment is provided below for illustration.
[0033] See also Figure 1 , Figure 1 This is a process of a firmware burning method provided in an embodiment of the present application Figure 1 .like Figure 1 As shown, a firmware burning method comprises the following steps:
[0034] Step 101, reading a specific identifier stored in association with a target motherboard at a first workstation.
[0035] During the production of the device, the motherboard needs to be processed according to the process to achieve firmware burning. Different processes are set with corresponding workstations. At each workstation, the motherboard needs to complete the corresponding process processing operations.
[0036] Optionally, the mainboard is, for example, a PCB (Printed Circuit Board).
[0037] The specific identifier is the identification information of the workstation. The specific identifier is used to identify that the current mainboard has completed the processing operation of the corresponding process in the workstation corresponding to the specific identifier. The specific identifier is the UID (User Identification) of the workstation, for example, it can be an identifier that uniquely identifies the workstation, such as the workstation name, workstation number, specific characters, etc.
[0038] When a workstation completes the processing operation on the mainboard in the current process, the specific identifier corresponding to the workstation is written into the storage device for record.
[0039] Here, when the target motherboard is transferred to the current first workstation, the specific identifier associated with the target motherboard is read in the first workstation. When reading the specific identifier, data can be read from the storage device based on a specific storage address.
[0040] If the specific identifier is read, step 102 may be executed.
[0041] If the specific identifier is not read, it is considered that there is omission in the process processing, and omission identification information indicating that there is omission in the process processing of the target mainboard can be generated, and the omission identification information is used to indicate that the target mainboard is returned to the previous station of the first station for processing.
[0042] The first workstation performs a first process, and the previous workstation of the first workstation performs a second process, and the second process is the previous process of the first process.
[0043] In this process, the specific identifier stored in association with the target motherboard is read at the current workstation, and the specific identifier recorded in the motherboard is introduced during the processing of the motherboard. Based on whether the specific identifier can be read, it is determined whether there are any process omissions in the processing of the motherboard. When the specific identifier is not read, omission identification information is generated to indicate that there are process omissions in the current motherboard, and an indication is given that the current motherboard needs to return to the previous workstation to complete the processing of the corresponding process. This can effectively intercept defective motherboards with process omissions, reduce firmware burning anomalies, reduce product defective rates, improve production efficiency and reduce costs.
[0044] Step 102: When a specific identifier is read, determine a second workstation corresponding to the specific identifier.
[0045] Optionally, an association relationship may be established between the specific identifier and the corresponding workstation. After the specific identifier is read, the second workstation corresponding to the current specific identifier may be determined based on the association relationship between the specific identifier and the workstation.
[0046] Step 103: If the second workstation is the previous workstation of the first workstation, the first program is burned into the target motherboard.
[0047] Among them, the first program can be a functional software program that needs to be burned into the motherboard during the mass production stage, or it can be a motherboard test program, or a program for data configuration of the motherboard, or a program for personalized addition and deletion of functions of the motherboard, etc.
[0048] If the second workstation is the previous workstation of the first workstation, it can be determined that the process of the previous workstation of the current second workstation has been completed, and the first program can be burned into the target mainboard.
[0049] Optionally, the second workstation may be a workstation corresponding to the last process in the process flow.
[0050] In one example, when it is determined in the second workstation that the process of the previous workstation has been completed and the current second workstation is a mass production software program burning workstation, the mass production software program can be burned in the target motherboard.
[0051] In an optional implementation, in step 103 , burning the first program in the target mainboard may be performed by burning the first program in the target mainboard in a data-overwriting manner.
[0052] In this way, the program written in the completed process can be erased, ensuring the validity of the data written in the newly written program, avoiding interference of other programs on the function of the newly written program, and reducing the space occupied by unnecessary programs.
[0053] In the above steps, the specific identifier stored in association with the target motherboard is read at the current workstation, so that the specific identifier recorded in the motherboard is introduced during the processing of the motherboard. When the specific identifier can be read for the current motherboard, it is determined whether the workstation corresponding to the specific identifier is the previous workstation of the current workstation to determine whether there is any process omission in the processing of the motherboard. When the workstation corresponding to the specific identifier is the previous workstation of the current workstation, the program is burned in the target motherboard, which can effectively avoid process omissions in the processing of the motherboard, reduce firmware burning anomalies, reduce product defective rate, improve production efficiency and reduce costs.
[0054] In an embodiment different from step 103, if the second workstation is not the previous workstation of the first workstation, it is considered that the motherboard has not been processed by the previous workstation of the current workstation, and there is a process processing omission. Omission identification information indicating that there is a process processing omission in the target motherboard can be generated, and the omission identification information is used to indicate that the target motherboard is returned to the previous workstation for processing.
[0055] This process determines whether there are any process omissions in the processing of the mainboard by judging whether the workstation corresponding to the specific identifier is the previous workstation of the current workstation, and generates omission identification information indicating that there are process omissions in the current mainboard when the workstation corresponding to the specific identifier is not the previous workstation of the current workstation, thereby indicating that the current mainboard needs to return to the previous workstation to complete the processing operation of the corresponding process. This can effectively intercept defective mainboards with process omissions, reduce firmware burning anomalies, reduce product defective rates, improve production efficiency and reduce costs.
[0056] Combination Figure 2 As shown, another burning process in the firmware burning method is also provided in the embodiment of the present application, which specifically includes the following steps:
[0057] Step 201, burning the second program to the target motherboard.
[0058] The second program may be a mainboard test program, or a program for configuring data on the mainboard, or a program for adding or deleting personalized functions on the mainboard.
[0059] The second software program may be an independent test program written in advance.
[0060] Step 202: Perform a first processing operation on the target motherboard based on the second program at a third workstation.
[0061] Optionally, the third workstation is a workstation before the first workstation in the above embodiment. Alternatively, the process corresponding to the third workstation is a process before the process corresponding to the first workstation.
[0062] When the second program is a motherboard test program, the first processing operation is a corresponding motherboard test operation. In an optional embodiment, for example, when the second program is a motherboard test program, a performance test is performed on the motherboard, such as testing whether there are abnormalities in the function realization, power consumption, standby current, resistance value of heating components, etc. of the motherboard.
[0063] Alternatively, when the second program is a program for configuring data on the mainboard, the first processing operation is a corresponding operation for configuring data on the mainboard, such as configuring data such as standby time, heating temperature, etc.
[0064] Alternatively, when the second program is a program for personalized addition and deletion of functions of the mainboard, the first processing operation is a corresponding operation for personalized addition and deletion of functions of the mainboard, such as turning on the data reminder function of the remaining power, turning off the voice reminder function of the remaining power, etc.
[0065] Optionally, in one embodiment, the second program is a test program, and step 202 performs a first processing operation on the target motherboard based on the second program at the third station, including:
[0066] The third station performs a motherboard test operation on the target motherboard based on the test program, wherein the motherboard test operation includes a first result of passing the test and a second result of failing the test.
[0067] In an optional implementation process, the test program in the mainboard is triggered to test the mainboard. If the test passes, it means the mainboard is good, and an indication of the test passing may be displayed on the test stand, a green light may be turned on, etc., and the specific identifier of the current workstation and the test time may be recorded. If the test fails, it means the mainboard is abnormal, and a warning may be issued to eliminate the defective mainboard.
[0068] Step 203: When the execution result of the first processing operation is the first result, the identifier of the third workstation is stored as a specific identifier in association with the target mainboard.
[0069] Optionally, the first result may be a specific execution result achieved after the first processing operation is executed, such as a detection pass execution result output after the motherboard detection processing operation is executed, or a specific execution result after other processing operations are executed.
[0070] In this step, when the execution result after the processing operation is completed is a specific result, the specific identifier of the current workstation is associated with the target motherboard and stored to identify that the motherboard has completed the processing operation of the corresponding process in the current workstation, so that the next workstation can easily view and use the stored data. Specifically, it is convenient for the next workstation to read the specific identifier stored in association with the motherboard to determine whether there is any process omission in the motherboard, avoid process omissions in the motherboard processing, and reduce firmware burning abnormalities.
[0071] Optionally, step 203, while storing the identifier of the third workstation as a specific identifier in association with the target mainboard, further includes:
[0072] The processing operation data corresponding to the first result is associated with the target mainboard and stored.
[0073] The processing operation data at least includes: version information of the second program, operation items of the first processing operation and the first result. The processing operation data may also include motherboard batch, execution time of the processing operation, execution duration and other processing operation data.
[0074] The operation item of the first processing operation is, for example, a data modification item, a function setting item, a function detection item, etc.
[0075] In this process, when the processing operation performed on the mainboard is a specific execution result, the processing operation data in this situation and the specific identifier of the current workstation are associated with the target mainboard for storage, so as to achieve effective storage of the relevant data under the specific execution result, so that the next workstation can conveniently view and use the relevant data under the specific execution result.
[0076] In an optional implementation, step 203 stores the identifier of the third workstation as a specific identifier in association with the target mainboard, including:
[0077] Initiate a data write operation; after the data write operation is completed, read the written storage data from the storage device; when the written storage data is consistent with the target data, determine that the target data is written successfully; when the storage data is inconsistent with the target data, return to the step of initiating the data write operation.
[0078] The data writing operation is used to associate the target data with the target mainboard and then write the target data to the storage device, and the target data includes an identifier of the third workstation.
[0079] When the target data is written into the storage device, the identifier of the third workstation contained therein is associated with the target mainboard as a specific identifier and then written into the storage device.
[0080] In addition to the identifier of the third workstation, the target data may also include processing operation data of the first processing operation, which may specifically be processing operation data corresponding to the first result when the execution result of the first processing operation is the first result. The processing operation data may specifically be version information of the second program, operation items and the first result of the first processing operation, or may be a motherboard batch, execution time and execution duration of the processing operation, etc.
[0081] In the above processing procedure, after the data write operation is completed, the data write address of the data write operation in the storage device can be recorded. When reading the written storage data from the storage device, the data can be read based on the data write address. If the read data is consistent with the target data to be written by the data write operation, it means that the target data is written successfully. If the read data is inconsistent with the target data to be written by the data write operation, it is determined that the target data has failed to be written. Or if no data is read based on the data write address, it is also determined that the target data has failed to be written.
[0082] When it is determined that the target data writing fails, the data writing operation can be re-executed to rewrite the target data into the storage device until it is determined that the target data writing is successful, thereby ensuring the effective storage of the target data associated with the current workstation, so that the next workstation can conveniently view and use the relevant data under the specific execution result.
[0083] See also Figure 3 , Figure 3 This is a structural diagram of a firmware burning device provided in an embodiment of the present application. For ease of explanation, only the parts related to the embodiment of the present application are shown.
[0084] The firmware burning device 300 comprises:
[0085] A data reading module 301 is used to read a specific identifier stored in association with a target motherboard at a first workstation;
[0086] A data determination module 302 is used to determine the second workstation corresponding to the specific identifier when the specific identifier is read;
[0087] The program burning module 303 is used to burn the first program in the target mainboard if the second workstation is the previous workstation of the first workstation.
[0088] Optionally, the firmware burning device 300 further includes:
[0089] An execution module is used to burn a second program to the target motherboard; perform a first processing operation on the target motherboard based on the second program at a third workstation; when the execution result of the first processing operation is a first result, store the identifier of the third workstation as the specific identifier in association with the target motherboard.
[0090] Optionally, the second program is a test program, and the execution module is specifically used to:
[0091] A motherboard test operation is performed on the target motherboard based on the test program at the third station; the motherboard test operation includes the first result of passing the test and the second result of failing the test.
[0092] Optionally, the execution module is further used to:
[0093] When the execution result of the first processing operation is the first result, the processing operation data corresponding to the first result is associated with the target mainboard and stored; the processing operation data includes at least: version information of the second program, operation items of the first processing operation and the first result.
[0094] Optionally, the execution module is specifically used to:
[0095] Initiating a data writing operation, the data writing operation is used to associate target data with the target mainboard and then write the target data to a storage device, the target data including an identifier of the third workstation;
[0096] After the data writing operation is completed, reading the written storage data from the storage device;
[0097] When the written storage data is consistent with the target data, determining that the target data is written successfully;
[0098] In the case that the stored data is inconsistent with the target data, the step of initiating the data writing operation is returned to be executed.
[0099] Optionally, the firmware burning device 300 further includes:
[0100] A generation module is used to generate missing identification information indicating that there is a process omission on the target mainboard when the specific identifier is not read, and the missing identification information is used to indicate that the target mainboard is returned to the previous workstation for processing.
[0101] Optionally, the program burning module is specifically used for:
[0102] The first program is burned in the target mainboard in a data-overwriting manner.
[0103] The firmware burning device provided in the embodiment of the present application can implement each process of the embodiment of the above-mentioned firmware burning method and can achieve the same technical effect. To avoid repetition, it will not be described here.
[0104] Figure 4 4 is a structural diagram of an electronic device provided in an embodiment of the present application. As shown in the figure, the electronic device 4 of the embodiment includes: at least one processor 40 ( Figure 4 Only one is shown in the figure), a memory 41, and a computer program 42 stored in the memory 41 and executable on the at least one processor 40, wherein the processor 40 implements the steps of any of the above-mentioned method embodiments when executing the computer program 42.
[0105] The electronic device 4 may be a HNB (Heat Not Burning) device.
[0106] The electronic device 4 may include, but is not limited to, a processor 40 and a memory 41. Those skilled in the art will appreciate that Figure 4It is only an example of the electronic device 4 and does not constitute a limitation of the electronic device 4. It may include more or fewer components than shown in the figure, or a combination of certain components, or different components. For example, the electronic device may also include input and output devices, network access devices, buses, etc.
[0107] The processor 40 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc.
[0108] The memory 41 may be an internal storage unit of the electronic device 4, such as a hard disk or memory of the electronic device 4. The memory 41 may also be an external storage device of the electronic device 4, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the electronic device 4. Further, the memory 41 may also include both an internal storage unit and an external storage device of the electronic device 4. The memory 41 is used to store the computer program and other programs and data required by the electronic device. The memory 41 may also be used to temporarily store data that has been output or is to be output.
[0109] The technicians in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated in a processing unit, or each unit can exist physically separately, or two or more units can be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, which will not be repeated here.
[0110] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.
[0111] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0112] In the embodiments provided in the present application, it should be understood that the disclosed devices / electronic devices and methods can be implemented in other ways. For example, the device / electronic device embodiments described above are merely schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0113] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0114] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0115] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electric carrier signal, telecommunication signal and software distribution medium. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.
[0116] The present application implements all or part of the processes in the above-mentioned embodiment methods, and may also be implemented through a computer program product. When the computer program product runs on an electronic device, the electronic device can implement the steps in the above-mentioned method embodiments when the computer program product is executed.
[0117] The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.
Claims
1. A firmware burning method, characterized in that: include: Reading, at the first station, a specific identifier stored in association with the target motherboard; In case the specific identifier is read, determining a second workstation corresponding to the specific identifier; If the second workstation is the previous workstation of the first workstation, the first program is burned into the target mainboard.
2. The method according to claim 1, characterized in that The method further comprises: Burning the second program to the target motherboard; performing a first processing operation on the target motherboard based on the second program at a third station; In a case where the execution result of the first processing operation is the first result, the identifier of the third workstation is stored as the specific identifier in association with the target mainboard.
3. The method according to claim 2, characterized in that The second program is a test program, and the performing a first processing operation on the target motherboard based on the second program at the third station includes: A motherboard test operation is performed on the target motherboard based on the test program at the third station; the motherboard test operation includes the first result of passing the test and the second result of failing the test.
4. The method according to claim 2, characterized in that: In the case where the execution result of the first processing operation is a first result, the method further includes: storing the processing operation data corresponding to the first result in association with the target mainboard; The processing operation data at least includes: version information of the second program, operation items of the first processing operation, and the first result.
5. The method according to claim 2, characterized in that: The storing the identifier of the third workstation as the specific identifier in association with the target mainboard includes: Initiating a data writing operation, the data writing operation is used to associate target data with the target mainboard and then write the target data to a storage device, the target data including an identifier of the third workstation; After the data writing operation is completed, reading the written storage data from the storage device; When the written storage data is consistent with the target data, determining that the target data is written successfully; In the case that the stored data is inconsistent with the target data, the step of initiating the data writing operation is returned to be executed.
6. The method according to claim 1, characterized in that After the first station reads the specific identifier stored in association with the target motherboard, the method further includes: In the case where the specific identifier is not read, omission identification information is generated to indicate that there is an omission in the process of processing the target mainboard, and the omission identification information is used to indicate that the target mainboard is returned to the previous station for processing.
7. The method according to any one of claims 1 to 6, characterized in that: The step of burning the first program in the target mainboard includes: The first program is burned in the target mainboard in a data-overwriting manner.
8. A firmware burning device, characterized in that: include: A data reading module, used for reading a specific identifier stored in association with a target mainboard at a first workstation; A data determination module, configured to determine a second workstation corresponding to the specific identifier when the specific identifier is read; A program burning module is used to burn the first program in the target mainboard if the second workstation is the previous workstation of the first workstation.
9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.
10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.