Software burning method, to-be-burnt hardware, storage medium and program product

Abstract

The invention relates to a software burning method, to-be-burnt hardware, a storage medium and a program product. The method comprises the following steps: acquiring production information written by general basic software; the general basic software is pre-burnt to a memory; the project software is accessed to a network and obtains the production information from corresponding equipment through the network; and burning the project software to the memory. By adopting the method, software burning errors can be reduced.

Description

Technical Field

[0001] The present application relates to the technical field of software burning, and in particular to a software burning method, hardware to be burned, a storage medium, and a program product. Background Art

[0002] With the rapid development of smart hardware, the Internet of Things, automotive electronics, industrial automation, and other fields, the application scenarios of embedded devices have exploded. The core functions of these devices rely on pre-installed software (firmware) on the chip. Faulty or missing software can cause device malfunctions at best, or even lead to safety hazards (such as malfunctions in automotive electronic systems). Therefore, a high-precision, efficient, and traceable software programming process has become a core component of modern manufacturing. Traditional software programming methods mostly use offline or online methods, using automated programming machines and parallel programming. However, as the number of product types increases, the number of software versions increases, making software programming with these methods prone to errors. Summary of the Invention

[0003] Based on this, it is necessary to provide a software burning method, hardware to be burned, storage medium and program product that can reduce software burning errors in response to the above technical problems.

[0004] A software burning method, the method comprising: Acquiring production information written by universal basic software; the universal basic software is pre-burned into a memory; Project software for accessing a network and obtaining the production information from corresponding equipment via the network; Burn the project software into the memory.

[0005] A hardware to be burned, characterized in that the hardware to be burned is used to implement the steps of each software burning method embodiment.

[0006] A computer-readable storage medium stores a computer program, which implements the steps of various software burning method embodiments when the computer program is executed by a processor.

[0007] A computer program product includes a computer program, which implements the steps of various software burning method embodiments when executed by a processor.

[0008] The above-mentioned software burning method, hardware to be burned, storage medium and program product, the universal basic software is the software common to all hardware to be burned, and can be pre-burned into the memory on a large scale without distinguishing different projects, so that simple functions such as writing production information, accessing the network, etc. can be realized through the universal basic software. The project software that obtains production information from the corresponding equipment through the network, burns the project software into the memory, and upgrades it to the normal project software through the universal basic software, realizing customized software automatic burning, reducing software burning errors, and eliminating the need for production personnel to operate, thereby ensuring the correctness of software burning. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 A diagram showing an application environment of a software burning method according to an embodiment; Figure 2 1 is a flow chart of a software burning method according to an embodiment; Figure 3 A schematic diagram of a software release process in one embodiment; Figure 4 1 is a flow chart of a software burning method according to another embodiment; Figure 5 FIG. 4 is a flow chart of a software burning method in yet another embodiment. DETAILED DESCRIPTION

[0010] It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0011] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0012] It should be noted that all directional indications in the embodiments of the present application (such as up, down, left, right, front, back, etc.) are only used to explain the relative position relationship, movement status, etc. between the components under a certain specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indication will also change accordingly. The connection can be a direct connection or an indirect connection.

[0013] In addition, the descriptions of "first", "second", etc. in this application are for descriptive purposes only and should not be understood as indicating or implying their relative importance or implicitly indicating the number of the technical features indicated. Therefore, the features defined as "first" or "second" may explicitly or implicitly include at least one of such features. In addition, the technical solutions between the various embodiments can be combined with each other, but this must be based on the fact that they can be implemented by ordinary technicians in this field. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such combination of technical solutions does not exist and is not within the scope of protection required by this application.

[0014] It can be understood that the “connection” in the following embodiments should be understood as “electrical connection”, “communication connection”, etc. if there is transmission of electrical signals or data between the connected circuits, modules, units, etc.

[0015] It can be understood that the operation of "obtaining data" in the embodiments of the present application includes but is not limited to the following implementation methods: directly reading the original data pre-stored in the device; or indirect acquisition after data collection, conversion and processing.

[0016] The software burning method provided in each embodiment of the present application can be applied to Figure 1 application environment. Figure 1 FIG. 1 is an application environment diagram of a software burning method in one embodiment. Figure 1 The system includes hardware to be programmed 110 and a server 120. The hardware to be programmed 110 can be a motherboard to be programmed, a PCB (Printed Circuit Board) to be programmed, or a device to be programmed. The hardware to be programmed 110 includes a memory 1101. Memory 1101 is programmed with common basic software. The server 120 can be implemented as a standalone server or a server cluster consisting of multiple servers. The methods in various embodiments of the present application are described using the hardware to be programmed 110 as an example.

[0017] In one embodiment, a software burning method is applied to hardware to be burned, comprising the following steps: Step 202: Acquire production information written by universal basic software, which is pre-burned into the memory.

[0018] Among them, the general basic software is a BIOS (Basic Input / Output System), which is a program solidified on the computer motherboard. It is mainly responsible for hardware initialization and self-test (POST) when the computer is turned on, and provides basic hardware operation interfaces to provide support for operating system loading.

[0019] Production information uniquely identifies each piece of hardware to be programmed. Examples include product identification, version number, and production batch. Product identification can include a serial number (SN) to distinguish between different items. For example, the SN for all products of the same type is the same.

[0020] The memory can be an external memory of the hardware to be burned, such as EMMC (Embedded Multi Media Card), NAND FLASH (NAND-type Flash Memory), NOR FLASH (NOR-type Flash Memory), etc.

[0021] Specifically, during the production process, the universal basic software is first burned into the memory using an online burning method. The memory chip is attached to the PCB, and the resulting hardware to be burned can achieve simple functions. The hardware to be burned is then written with production information using the pre-burned universal basic software.

[0022] Step 204: Access the network and obtain the project software of production information from the corresponding equipment through the network.

[0023] The corresponding device can be a server, which pre-stores the project software corresponding to the production information. Project software is customized, and different serial numbers may correspond to different project software. Project software includes the target operating system and target application.

[0024] Specifically, the hardware to be burned has a network interface. The network interface can be a wireless network interface or a wired network interface. The hardware to be burned accesses the network through the network interface and obtains the project software corresponding to the production information from the server.

[0025] Step 206: Burn the project software into the memory.

[0026] Specifically, the hardware to be burned stores the project software downloaded from the corresponding device into the memory.

[0027] In this embodiment, the universal basic software is common to all hardware to be burned. It can be pre-burned into the memory on a large scale without distinguishing between different projects, so that simple functions such as writing production information and accessing the network can be realized through the universal basic software. The project software that obtains production information from the corresponding device through the network is burned into the memory, and is upgraded to the software of the normal project through the universal basic software, thereby realizing customized software automatic burning, reducing software burning errors, and ensuring the correctness of software burning without the need for production personnel to operate.

[0028] In one embodiment, the project software for accessing a network and obtaining production information from corresponding equipment via the network includes: Project software that accesses the local area network and obtains production information from the server through the local area network.

[0029] Specifically, the hardware to be burned can be connected to a local area network through a wired network interface, and obtain the project software corresponding to the production information from a server through the local area network.

[0030] In this embodiment, a local area network is accessed, and the project software of production information is obtained from the server through the local area network. The project software is stored on the server, and no related image exists on the local terminal device, which can reduce the risk of software leakage.

[0031] In one embodiment, the project software for obtaining production information from a server via a local area network includes: Request the project software download address from the server through the local area network. The project software download address is used to instruct the server to download the corresponding project software; Receive the project software returned by the server through the local area network.

[0032] The project software download address is an address located in the server, which is used to indicate the location of the project software.

[0033] Specifically, after the production information is written, the hardware to be burned automatically connects to the network and requests the project software download address from the server through the local area network. The server downloads the corresponding project software from the project software download address and receives the project software returned by the server through the local area network.

[0034] In this embodiment, a project software download address is requested from the server through the local area network. The project software download address is used to instruct the server to download the corresponding project software. Receiving the project software returned by the server through the local area network can reduce the risk of software leakage and automatically burn the project software without the need for production personnel to operate.

[0035] In one embodiment, the general basic software includes a system boot program and a recovery system.

[0036] Specifically, the system boot loader is the first software that runs when the computer starts. It is responsible for initializing the hardware, loading the operating system kernel and transferring its control.

[0037] A recovery system is a special environment pre-integrated in a device or operating system for repairing failures or recovering data. It usually runs independently of the main system.

[0038] In this embodiment, the system boot program and the recovery system are universal basic software, which are prone to errors if burned in large quantities in advance, can realize simple functions, normally boot the system, and support automatic burning of project software.

[0039] In one embodiment, the project software includes a target system and a target application.

[0040] Specifically, the target system refers to the system corresponding to the production information (e.g., SN), which can be an embedded operating system such as Linux. The target application refers to the application corresponding to the production information (e.g., SN). Both the target system and target application corresponding to the production information are pre-stored on the server.

[0041] In this embodiment, the target system and target application are acquired by triggering the universal basic software, so that the software burning can be completed automatically and the burning content can be kept error-free.

[0042] In one embodiment, the project software includes general basic software, a target system, and a target application; Burn the project software into the memory, including: Format and burn the project software to the memory.

[0043] Specifically, the project software includes general basic software, target system and target application. It is formatted during the final burning and the project software is burned to the memory, thereby uninstalling the original general basic software. The software burning can be completed automatically without the need for production personnel to configure the project software.

[0044] In one embodiment, the memory comprises external memory.

[0045] Specifically, external memory includes, but is not limited to, EMMC (Embedded Multi Media Card), NAND FLASH (NAND-type Flash Memory), and NOR FLASH (NOR-type Flash Memory). This external memory can be pre-programmed with universal basic software using a programmer before being installed on a PCB. Once the external memory is attached to the PCB, the hardware to be programmed is obtained, and the hardware to be programmed can retrieve the production information written using the universal basic software.

[0046] In this embodiment, the memory includes an external memory, and software burning can be implemented in the external memory.

[0047] In one embodiment, traditional offline burning methods are prone to software burning errors. Online burning takes a long time when burning large-capacity storage devices and cannot be upgraded after the entire machine is assembled. The increasing number of product types leads to an increasing number of production images, and software burning errors and version inconsistencies are common during the production process. In this embodiment, a software burning method is provided to solve the problem of rework caused by software burning errors due to excessive number of projects on the same platform and untimely synchronization of multiple software versions.

[0048] Software Release Production software is divided into general basic software and project software. The general basic software package implements simple functions and can boot the system normally.

[0049] By upgrading the general basic software package to the software package of a normal project, fully automatic software burning is completed. The burned project software can be kept up to date without the need for production personnel to operate.

[0050] Universal Basic Software Package (BIOS): Contains system boot program and recovery system.

[0051] Project software package: Contains the entire system software package, including the system boot program, recovery system, normal system, and application program (APP).

[0052] like Figure 3 The figure shows a schematic diagram of the software release process in one embodiment. A common basic software image (BIOS) is created on the terminal device side, along with software packages for Project 1, Project 2, and Project N. The terminal device uploads the software to the server, which then releases the software.

[0053] Software burning like Figure 4 FIG2 is a flow chart of another embodiment of a software burning method. Online burning of universal basic software image: During the production process, online burning is uniformly used to first burn the universal basic software (BIOS) to an external storage device (EMMC, NAND FLASH, nor flash).

[0054] Production number writing: The general basic software (BIOS) is completed during PCB patching to complete the SN number writing function (SN number is used to distinguish different projects).

[0055] Insert a fixed network cable: Connect the network cable.

[0056] Device upgrade: The hardware to be burned uses the SN parameter to request the project software package download address from the server to complete the download.

[0057] Complete production software burning: partition and format the hardware to be burned (external storage device), write the project software package to the external storage device, and complete software burning.

[0058] like Figure 5 The figure shows a flow chart of a software burning method in another embodiment. The general basic software is pre-burned into a memory, and the memory is attached to a PCB board to obtain the hardware to be burned. After the hardware to be burned is turned on, it is determined whether the SN is written. If not, the SN is waited for to be written; if so, it is further determined whether the network cable is inserted. If the network cable is not inserted, the network cable is checked for access and it is again determined whether the network cable is inserted. If the network cable is inserted, the backend server is connected, the download address of the project software is requested through the SN, and the project software is downloaded from the server, thereby realizing the project software upgrade and completing the writing of the production software.

[0059] The beneficial effects of this embodiment are as follows: 1. Reduce the risk of software leakage. The production software is stored on the server, and no related images exist on the local computer.

[0060] 2. The basic software can be used for batch burning of software, without having to distinguish different projects on the same platform, reducing software errors.

[0061] 3. The software burning process is automatically upgraded without the need for production personnel to operate, ensuring the correctness of the software.

[0062] In one embodiment, a software burning method includes: Step (a1), obtaining production information written by universal basic software; the universal basic software is pre-burned into the memory; the universal basic software includes a system boot program and a recovery system.

[0063] Step (a2): accessing the local area network and requesting the project software download address from the server through the local area network. The project software download address is used to instruct the server to download the corresponding project software; the project software includes a target system and a target application.

[0064] Step (a3): receiving the project software returned by the server through the local area network.

[0065] Step (a4), burning the project software into a memory; the memory includes an external memory.

[0066] In this embodiment, the universal basic software is common to all hardware to be burned. It can be pre-burned into the memory on a large scale without distinguishing between different projects, so that simple functions such as writing production information and accessing the network can be realized through the universal basic software. The project software that obtains production information from the corresponding device through the network is burned into the memory, and is upgraded to the software of the normal project through the universal basic software, thereby realizing automatic burning of customized software, reducing software errors during downloading, and eliminating the need for production personnel to operate, thereby ensuring the correctness of software burning. It should be understood that although the above Figures 2 to 5 The steps in the flowchart are shown in sequence as indicated by arrows, and the steps (a1) to (a4) are shown in sequence as indicated by numbers, but these steps are not necessarily performed in the order indicated by arrows or numbers. Unless otherwise specified in this document, there is no strict order restriction for the execution of these steps, and these steps can be performed in other orders. In addition, Figures 2 to 5 At least part of the steps may include multiple steps or multiple stages. These steps or stages are not necessarily performed at the same time, but can be performed at different times. The order of execution of these steps or stages is not necessarily one by one, but can be performed in turn or alternately with other steps or at least part of the steps or stages in other steps. In one embodiment, a hardware to be burned is provided, comprising a memory and a processor. The memory stores a computer program, and the processor implements the steps of the above-mentioned method embodiments when executing the computer program.

[0067] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned method embodiments are implemented.

[0068] In one embodiment, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the steps of each of the above method embodiments. Those skilled in the art will appreciate that all or part of the processes in the above-described method embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes in the above-described method embodiments. Any reference to memory, storage, database, or other media used in the embodiments provided herein may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical storage. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM may be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0069] The above description is only a preferred embodiment of the present application and does not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present application.

Claims

1. A software burning method, characterized in that: The method comprises: Acquiring production information written by universal basic software; the universal basic software is pre-burned into a memory; Project software for accessing a network and obtaining the production information from corresponding equipment via the network; Burn the project software into the memory.

2. The method according to claim 1, characterized in that The project software for accessing the network and obtaining the production information from the corresponding device via the network includes: Accessing a local area network, and obtaining project software of the production information from a server through the local area network.

3. The method according to claim 2, characterized in that The project software for obtaining the production information from the server via the local area network includes: Requesting a project software download address from a server via the local area network, wherein the project software download address is used to instruct the server to download the corresponding project software; The project software returned by the server is received through the local area network.

4. The method according to claim 1, wherein The general basic software includes a system boot program and a recovery system.

5. The method according to claim 1, wherein The project software includes a target system and a target application.

6. The method according to claim 1, characterized in that The project software includes the general basic software, target system and target application; Burning the project software into the memory includes: Formatting is performed to burn the project software into the memory.

7. The method according to claim 1, characterized in that The memory includes an external memory.

8. A hardware to be burned, characterized in that, The hardware to be burned is used to implement the steps of the method according to any one of claims 1 to 7.

9. A computer-readable storage medium having a computer program stored thereon, 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.

10. A computer program product comprising 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.

Images