A system firmware flashing test method, apparatus and electronic device

Abstract

This invention discloses a system firmware flashing test method, apparatus, and electronic device. The method calls a system boot identification module to run the BOOT boot program in the bin file, which detects and judges user operations. If the recovery mode system file is correct, it loads the recovery mode system file and enters the recovery mode system. It then calls a system installation processing module to execute installation script commands, checks whether the recovery mode system has obtained an IP address. If the IP address is successfully obtained, it traverses the mounted directories, unmounts all mounted system disks, partitions and formats the system disks, and labels them. The system disk partition is mounted to a temporary directory, and the required files are downloaded from the computer. The MD5 value is verified. If the MD5 verification is successful, the downloaded files are moved to a designated directory. An SN code is generated by remotely executing a script on the computer using SSH, written to the device, and integrated testing commands are executed. This invention is highly efficient, simple, and efficient in production, and convenient for on-site maintenance.

Description

Technical Field

[0001] This invention belongs to the field of embedded system technology, specifically relating to a system firmware burning and testing method, apparatus, and electronic device. Background Technology

[0002] Embedded devices are dedicated computer devices embedded in other devices or systems. They typically have specific functions and uses and are designed to perform specific tasks. Examples include smartphones, smartwatches, electronic control systems in automobiles, and microcontrollers in home appliances.

[0003] Currently, in the firmware burning, testing, and use of embedded devices, it is often necessary to first burn the bootloader (the bootloader plays a crucial role in the computer system startup process, responsible for initializing hardware devices, loading the operating system kernel, and other critical tasks) using a programmer. After burning, a series of commands need to be entered into the bootloader, and system files need to be copied from an external USB flash drive, configurations need to be modified, and testing is required. Furthermore, if the device system is incorrectly modified, it may fail to boot normally. In this case, it is necessary to return the device to the factory or send a professional to the site to re-burn the system. This process is inefficient, cumbersome, affects production efficiency, and is troublesome for on-site repairs. Summary of the Invention

[0004] Therefore, the present invention provides a system firmware burning test method, device and electronic equipment, which solves the problems of low operation efficiency, cumbersome process, impact on production efficiency and troublesome on-site maintenance of traditional technology.

[0005] To achieve the above objectives, the present invention provides the following technical solution: Firstly, a system firmware flashing test method is provided, comprising:

[0006] The BOOT management module is invoked to package a bin file, which includes the BOOT bootloader and recovery mode system files. The bin file is then burned into the flash chip using a flash programming tool.

[0007] The system startup identification module is invoked, the BOOT boot program in the bin file is run, and the user operation is judged and detected. If the user does not manually enter the recovery mode system, the recovery mode system file is checked to see if it is correct. If the recovery mode system file is correct, the recovery mode system file is loaded and the user enters the recovery mode system.

[0008] Once the system enters recovery mode, the system installation processing module is invoked to execute the installation script command. The system checks whether it has obtained an IP address. If the IP address is successfully obtained, the mounted directories are traversed, all mounted system disks are unmounted, and the system disks are partitioned, formatted, and labeled.

[0009] Mount the system disk partition to a temporary directory, download the required files from the computer, verify the MD5 value, and after the MD5 value verification is successful, move the downloaded files from the computer to the specified directory, use SSH to remotely execute the script on the computer to generate the SN code, write the SN code into the device, and execute the integration test command.

[0010] As a preferred method for system firmware flashing test, the system startup identification module is called to run the BOOT boot program of the bin file. During the process of judging and detecting user operations, if the manual entry into the recovery mode system is not executed and the recovery mode system file is detected to be faulty, then the automatic entry into the recovery mode system is executed.

[0011] The BOOT boot program in the bin file is run. During the process of judging and detecting user operations, if the user manually enters the recovery mode system, the system will directly enter the recovery mode system.

[0012] As a preferred method for system firmware flashing test, after entering the recovery mode system, the system installation processing module is called to execute the installation script command. During the process of checking whether the recovery mode system has obtained an IP address, if the IP address acquisition fails, the installation script is exited, the operation result is returned and reported to the computer.

[0013] If the IP address is successfully obtained, iterate through the mounted directories, unmount all mounted system disks, and then erase the first 4KB of the system disk.

[0014] As a preferred method for system firmware flashing testing, after executing the integrated test command, the method further includes: calling the file resource management module to store the system firmware file; starting the file transfer protocol for the system installation processing module to obtain the system firmware file; and enabling the secure shell protocol service for the system installation processing module to remotely execute scripts and system files.

[0015] Secondly, a system firmware flashing test device is provided, comprising:

[0016] The BOOT management module is used to package bin files, which include the BOOT bootloader and recovery mode system files. The bin files are then burned into the flash chip using a flash programming tool.

[0017] The system startup identification module is used to run the BOOT boot program in the bin file, judge and detect user operations. If the user does not manually enter the recovery mode system, the system will check whether the recovery mode system file is correct. If the recovery mode system file is correct, the system will load the recovery mode system file and enter the recovery mode system.

[0018] The system installation processing module is used to execute installation script commands, check whether the recovery mode system has obtained an IP address. If the IP address is successfully obtained, it traverses the mounted directories, unmounts all mounted system disks, partitions and formats the system disks, and labels them. It is also used to mount the system disk partitions to a temporary directory, download the required files from the computer, verify the MD5 value, and after the MD5 value verification is successful, move the downloaded files from the computer to a specified directory, use SSH to remotely execute the computer script to generate an SN code, write the SN code to the device, and execute integration test commands.

[0019] As a preferred solution for the system firmware burning test device, the system startup identification module runs the BOOT boot program of the bin file and judges and detects user operations. If the user does not manually enter the recovery mode system and the recovery mode system file is detected as faulty, the user will automatically enter the recovery mode system.

[0020] The system startup identification module runs the BOOT boot program in the bin file. During the process of judging and detecting user operations, if the user manually enters the recovery mode system, the system will directly enter the recovery mode system.

[0021] As a preferred solution for the system firmware burning test device, if the IP address acquisition fails in the system installation processing module, the installation script will exit, the operation result will be returned, and the result will be reported to the computer.

[0022] The system installation processing module is also used to, if the IP address is successfully obtained, traverse the mounted directories, unmount all mounted system disks, and then erase the first 4KB of the system disk.

[0023] As a preferred option for system firmware flashing and testing devices, the following are also included:

[0024] The file resource management module is used to store system firmware files after executing integration test commands, initiate a file transfer protocol for the system installation processing module to obtain system firmware files, and enable the secure shell protocol service for the system installation processing module to remotely execute scripts and system files.

[0025] Thirdly, an electronic device is provided, comprising: a memory and a processor;

[0026] The processor and the memory communicate with each other via a bus; the memory stores program instructions that can be executed by the processor, and the processor calls the program instructions to execute a system firmware burning test method of the first aspect or any possible implementation thereof.

[0027] The beneficial effects of this invention are as follows: A BOOT management module packages a bin file, which includes a BOOT bootloader and a recovery mode system file. This bin file is then burned into the flash chip using a flash programming tool. A system boot identification module runs the BOOT bootloader within the bin file, detecting user operations. If manual entry into the recovery mode system is not performed, the system checks the correctness of the recovery mode system file. If the recovery mode system file is correct, it loads the recovery mode system file and enters the recovery mode system. A system installation processing module executes an installation script command, checking if the recovery mode system has obtained an IP address. If the IP address is successfully obtained, the system traverses the mounted directories, unmounts all mounted system disks, partitions and formats the system disks, and labels them. The system disk partition is mounted to a temporary directory. The required files are downloaded from the computer, and their MD5 values ​​are verified. If the MD5 verification passes, the downloaded files are moved to a designated directory. An SN code is generated using a script executed remotely on the computer via SSH, written to the device, and integration test commands are executed. This invention is simple to operate, highly efficient, and does not rely on dedicated equipment. Only one computer is needed to quickly and simultaneously install, deploy, and test systems on multiple devices. The files required for booting and recovery modes are stored in flash memory, preventing users from directly modifying their contents and thus preventing device bricking. When a device fails to boot normally, it can enter recovery mode for operation. Since most user operations are performed in the production system, the operation methods are familiar, and recovery mode operates identically to the production system, eliminating the need to enter an unfamiliar boot environment. Files are transferred via network port, and automated scripts are executed, enabling production personnel to quickly install, deploy, and test systems on devices. Attached Figure Description

[0028] To more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings in the following description are merely exemplary, and those skilled in the art can derive other embodiments based on the provided drawings without creative effort.

[0029] The structures, proportions, sizes, etc. illustrated in this specification are only for the purpose of assisting those skilled in the art in understanding and reading the content disclosed herein, and are not intended to limit the conditions under which the present invention can be implemented. Therefore, they have no substantial technical significance. Any modifications to the structure, changes in the proportions, or adjustments to the size, without affecting the effects and objectives that the present invention can produce, should still fall within the scope of the technical content disclosed in the present invention.

[0030] Figure 1This is a schematic diagram of a system firmware flashing and testing method provided in an embodiment of the present invention;

[0031] Figure 2 This is a schematic diagram of the technical architecture of a system firmware flashing and testing method provided in an embodiment of the present invention;

[0032] Figure 3 A flowchart of the BOOT management process in a system firmware flashing test method provided in an embodiment of the present invention;

[0033] Figure 4 This invention provides a flowchart of the system boot identification process in a system firmware flashing test method.

[0034] Figure 5 This invention provides a flowchart of the system installation process in a system firmware flashing and testing method.

[0035] Figure 6 A flowchart of file resource management in a system firmware flashing test method provided in an embodiment of the present invention;

[0036] Figure 7 This is a schematic diagram of the architecture of a system firmware burning test device provided in an embodiment of the present invention. Detailed Implementation

[0037] The following specific embodiments illustrate the implementation of the present invention. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0038] Example 1

[0039] See Figure 1 and Figure 2 Embodiment 1 of the present invention provides a system firmware flashing test method, including the following steps:

[0040] S0. Call the BOOT management module to package the bin file. The bin file includes the BOOT boot program and recovery mode system files. The bin file is burned into the flash chip using a flash programming tool.

[0041] S1. Call the system startup identification module, run the BOOT boot program of the bin file, and judge and detect the user operation. If the user does not manually enter the recovery mode system, check whether the recovery mode system file is correct. If the recovery mode system file is correct, load the recovery mode system file and enter the recovery mode system.

[0042] S2. After entering the recovery mode system, the system installation processing module is invoked to execute the installation script command. The system checks whether the recovery mode system has obtained an IP address. If the IP address is successfully obtained, the mounted directories are traversed, all mounted system disks are unmounted, the system disks are partitioned, formatted, and labeled. The system disk partition is mounted to a temporary directory, the required files are downloaded from the computer, and the MD5 value is verified. After the MD5 value verification is successful, the files downloaded from the computer are moved to the specified directory. The computer script is remotely executed using SSH to generate the SN code, the SN code is written to the device, and the integration test command is executed.

[0043] See Figure 3 In this embodiment, the specific process of step S0 for the BOOT management module includes:

[0044] S001: Package the BOOT bootloader and recovery mode system files into a bin file, then proceed to S002;

[0045] S002: Use a flash programming tool to burn the bin file into the flash chip, then proceed to S003;

[0046] S003: Chip mounting.

[0047] Specifically, the BOOT management module is responsible for the implementation of the entire BOOT area of ​​the device. The bootloader and recovery mode system are stored in a flash chip, and the corresponding BIN files are burned before the device is mounted to the PCB, which is more efficient than burning them separately with a programmer after mounting. The recovery mode system retains only basic services to reduce its size, making it easier to store in a small-capacity flash chip. System file data is stored in memory, ensuring that system files are not changed by user operations and guaranteeing the normal startup of the boot firmware.

[0048] The BOOT management module includes a simplified recovery mode system, which is more familiar to users and eliminates the need to perform operations under an unfamiliar BOOT bootloader. Compared to BOOT, it offers better interactivity and simplifies complex operations. If the system fails to boot due to misoperation in the field, users can execute `run recover` in the BOOT command line to enter recovery mode and reinstall / deploy the system.

[0049] See Figure 4 In this embodiment, step S1, the system startup identification process, includes:

[0050] S101: The system powers on and runs the BOOT boot program, then proceeds to S102;

[0051] S102: Check if you have manually entered the recovery mode system. If yes, proceed to S105; otherwise, proceed to S103.

[0052] S103: Check the recovery mode system files. If the recovery mode system files are correct, proceed to S104. If the recovery mode system files are incorrect, manually enter the recovery mode system and proceed to S105.

[0053] S104: Load recovery mode system files;

[0054] S105: Enter recovery mode system.

[0055] Specifically, the system startup identification module is responsible for the status control during system startup. When the device is powered on for the first time, the BOOT boot program will read the device system files to start. If the device system files are not detected, the system will automatically enter the recovery mode. In the recovery mode, the preset installation script will be executed to burn, deploy and configure the system. If the system is incorrectly modified later and cannot be entered normally, the system can be reinstalled and deployed in the recovery mode.

[0056] See Figure 5 In this embodiment, step S2, the system installation process, includes:

[0057] S201: Execute the installation script command, then proceed to S202;

[0058] S202: Check if the recovery mode system has obtained an IP address. If successful, proceed to S203; otherwise, proceed to S210.

[0059] S203: Traverse the mounted directories, unmount all mounted system disks, erase the first 4KB of the system disks, and proceed to S204;

[0060] S204: Partition, format, and label the system disk, then proceed to S205;

[0061] S205: Mount the system partition to a temporary directory, then proceed to S206;

[0062] S206: Download the required file from the computer, verify the MD5 value, if the verification is successful, proceed to S207, if it fails, proceed to S210;

[0063] S207: Extract the files to the corresponding directory, then proceed to S208;

[0064] S208: Use Secure Shell Protocol (SSH) to remotely execute a PC script to generate a serial number (SN) code, write the SN code into the device, and then proceed to S209.

[0065] S209: Execute integration test command, proceed to S210;

[0066] S210: Exit, return the operation results and report to the computer.

[0067] Specifically, the system installation module is responsible for IP address checks, hard drive partitioning, resource file management, and system integration testing. Upon first power-on, the device automatically enters recovery mode. The device's MAC address is randomly generated (this is done during BOOT), and the IP address is obtained via DHCP, allowing multiple devices to be flashed simultaneously. Once an IP address is obtained, the installation script is executed automatically. To prevent issues with pre-existing disk partitions, the first 4KB of data is deleted, followed by partitioning, formatting, and labeling the disks to distinguish their functions. The necessary system files are retrieved via FTP, their MD5 hashes are checked, and the files are extracted to the corresponding directories. For certain device configuration parameters requiring unique values, the installation script remotely executes the script configured on the computer using the Secure Shell protocol to generate these parameters and records the results on the computer. After system installation and deployment, the installation script calls the integration testing tool to perform a device self-test, and the results are sent to the computer via FTP for storage.

[0068] In one possible embodiment, step S3 is further included: calling the file resource management module to store the system firmware file, starting the file transfer protocol for the system installation processing module to obtain the system firmware file; and enabling the Secure Shell protocol service for the system installation processing module to remotely execute scripts and system files.

[0069] See Figure 6 Step S3, the file resource management process includes:

[0070] S301: Stores system firmware files and initiates the FTP file transfer protocol for the system installation module to retrieve system firmware files before switching to S302.

[0071] S302: Enable Secure Enclosure Protocol service, proceed to S303

[0072] S303: Provides remote execution scripts and system files for system installation modules.

[0073] Specifically, the file resource management module is responsible for the distribution and management of resource files and the generation of serial numbers. The files required for system installation and deployment are stored on the computer, which has FTP and SSH services enabled. The device connects to the computer via the network port in recovery mode to obtain the necessary files.

[0074] In summary, this embodiment of the invention calls the BOOT management module to package a bin file, which includes a BOOT bootloader and a recovery mode system file. The bin file is burned into the flash chip using a flash programming tool. The system boot identification module is then called to run the BOOT bootloader in the bin file, which checks the user's actions. If the user does not manually enter the recovery mode system, the system checks if the recovery mode system file is correct. If the recovery mode system file is correct, it loads the recovery mode system file and enters the recovery mode system. Once in the recovery mode system, the system installation processing module is called to execute the installation script command. The system checks if it has obtained an IP address. If the IP address is successfully obtained, it traverses the mounted directories, unmounts all mounted system disks, partitions and formats the system disks, and labels them. The system disk partition is mounted to a temporary directory, and the required files are downloaded from the computer. The MD5 value is verified. If the MD5 verification is successful, the downloaded files are moved to a specified directory. An SN code is generated by remotely executing a script on the computer using SSH, written to the device, and integration test commands are executed. The system utilizes a file resource management module to store system firmware files and initiates a file transfer protocol for the system installation processing module to retrieve these files. It also enables a secure shell protocol service, allowing the system installation processing module to remotely execute scripts and system files. This invention is simple to operate, highly efficient, and does not rely on dedicated equipment. Only one computer is needed to quickly and simultaneously install, deploy, and test systems on multiple devices. Files required for boot and recovery modes are stored in flash memory, preventing users from directly modifying their contents and thus preventing device bricking. When a device fails to boot normally, it can enter recovery mode for operation. Since most user operations are performed in the production system, the recovery mode operates identically to the production system, eliminating the need to navigate to an unfamiliar boot environment. File transfer via network port and automated script execution enable production personnel to quickly install, deploy, and test systems on devices.

[0075] It should be noted that the above description describes some embodiments of this disclosure. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in a different order than that shown in the above embodiments and still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0076] Example 2

[0077] See Figure 7 Embodiment 2 of the present invention also provides a system firmware burning test device, comprising:

[0078] BOOT management module 001 is used to package bin files, which include BOOT boot program and recovery mode system files. The bin files are burned into the flash chip using a flash programming tool.

[0079] The system startup identification module 002 is used to run the BOOT boot program of the bin file, judge and detect the user operation. If the user does not manually enter the recovery mode system, the system will check whether the recovery mode system file is correct. If the recovery mode system file is correct, the system will load the recovery mode system file and enter the recovery mode system.

[0080] The system installation processing module 003 is used to execute installation script commands, check whether the recovery mode system has obtained an IP address. If the IP address is successfully obtained, it traverses the mounted directories, unmounts all mounted system disks, partitions and formats the system disks, and labels them. It is also used to mount the system disk partitions to a temporary directory, download the required files from the computer, verify the MD5 value, and after the MD5 value verification is successful, move the downloaded files from the computer to a specified directory, use SSH to remotely execute the computer script to generate an SN code, write the SN code into the device, and execute integration test commands.

[0081] In this embodiment, the system startup identification module 002 runs the BOOT boot program of the bin file. During the process of judging and detecting user operations, if the manual entry into the recovery mode system is not executed and the recovery mode system file is detected to be faulty, then the automatic entry into the recovery mode system is executed.

[0082] The system startup identification module 002 runs the BOOT boot program of the bin file. During the process of judging and detecting user operations, if the user manually enters the recovery mode system, the system will directly enter the recovery mode system.

[0083] In this embodiment, if the IP address acquisition fails in the system installation processing module 003, the installation script will exit, the operation result will be returned, and the result will be reported to the computer.

[0084] The system installation processing module 003 is also used to, if the IP address is successfully obtained, traverse the mounted directories, unmount all mounted system disks, and then erase the first 4K bytes of the system disk.

[0085] This embodiment also includes:

[0086] The file resource management module 004 is used to store system firmware files after executing integration test commands, start a file transfer protocol for the system installation processing module to obtain system firmware files, and enable the secure shell protocol service for the system installation processing module to remotely execute scripts and system files.

[0087] It should be noted that the information interaction and execution process between the modules of the above-mentioned device are based on the same concept as the method embodiment in Embodiment 1 of this application, and the resulting technical effects are the same as those in the method embodiment of this application. For details, please refer to the description in the method embodiment shown above in this application, and it will not be repeated here.

[0088] Example 3

[0089] Embodiment 3 of the present invention provides an electronic device, including: a memory and a processor;

[0090] The processor and the memory communicate with each other via a bus; the memory stores program instructions that can be executed by the processor, and the processor can execute a system firmware burning test method according to Embodiment 1 or any possible implementation thereof by calling the program instructions.

[0091] Specifically, a processor can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. This memory can be integrated into the processor or located outside the processor and exist independently.

[0092] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital customer line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means.

[0093] It is obvious to those skilled in the art that the modules or steps of the present invention described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. Optionally, they can be implemented using computer-executable program code, thereby storing them in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented herein, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.

[0094] Although the present invention has been described in detail above with general descriptions and specific embodiments, modifications or improvements can be made to it, which will be obvious to those skilled in the art. Therefore, all such modifications or improvements made without departing from the spirit of the present invention fall within the scope of protection claimed by the present invention.

Claims

1. A system firmware flashing test method, characterized in that, include: The BOOT management module is invoked to package a bin file, which includes the BOOT bootloader and recovery mode system files. The bin file is then burned into the flash chip using a flash programming tool. The system startup identification module is invoked, the BOOT boot program in the bin file is run, and the user operation is judged and detected. If the user does not manually enter the recovery mode system, the system will check whether the recovery mode system file is correct. If the recovery mode system file is correct, the system will load the recovery mode system file and enter the recovery mode system. Once the system enters recovery mode, the system installation processing module is invoked to execute the installation script command. The system checks whether it has obtained an IP address. If the IP address is successfully obtained, the mounted directories are traversed, all mounted system disks are unmounted, and the system disks are partitioned, formatted, and labeled. Mount the system disk partition to a temporary directory, download the required files from the computer, verify the MD5 value, and after the MD5 value verification is successful, move the downloaded files from the computer to the specified directory, use SSH to remotely execute the script on the computer to generate the SN code, write the SN code into the device, and execute the integration test command. The system startup identification module is invoked, and the BOOT boot program in the bin file is run. During the process of judging and detecting user operations, if the manual entry into the recovery mode system is not executed and the recovery mode system file is found to be faulty, then the manual entry into the recovery mode system is executed. During the process of running the BOOT boot program in the bin file and judging user operations, if the user manually enters the recovery mode system, the user will directly enter the recovery mode system. Once the system enters recovery mode, the system installation processing module is invoked to execute the installation script command. During the process of checking whether the recovery mode system has obtained an IP address, if the IP address acquisition fails, the installation script exits, returns the operation result, and reports it to the computer. If the IP address is successfully obtained, iterate through the mounted directories, unmount all mounted system disks, and then erase the first 4KB of the system disk.

2. The system firmware flashing test method according to claim 1, characterized in that, After executing the integration test command, the process also includes calling the file resource management module to store the system firmware file, starting the file transfer protocol for the system installation processing module to obtain the system firmware file, and enabling the secure shell protocol service for the system installation processing module to remotely execute scripts and system files.

3. A system firmware burning and testing device, characterized in that, include: The BOOT management module is used to package bin files, which include the BOOT bootloader and recovery mode system files. The bin files are then burned into the flash chip using a flash programming tool. The system startup identification module is used to run the BOOT boot program in the bin file, judge and detect user operations. If the user does not manually enter the recovery mode system, the system will check whether the recovery mode system file is correct. If the recovery mode system file is correct, the system will load the recovery mode system file and enter the recovery mode system. The system installation processing module is used to execute installation script commands, check whether the recovery mode system has obtained an IP address, and if the IP address is successfully obtained, it traverses the mounted directories, unmounts all mounted system disks, partitions the system disks, formats them, and labels them. It is also used to mount the system disk partition to a temporary directory, download the required files from the computer, verify the MD5 value, and after the MD5 value verification is successful, transfer the downloaded files to the specified directory, use SSH to remotely execute the computer script to generate the SN code, write the SN code into the device, and execute the integration test command. The system starts the identification module, runs the BOOT boot program of the bin file, and judges and detects user operations. If the manual entry into the recovery mode system is not executed and the recovery mode system file is detected to be faulty, then the manual entry into the recovery mode system is executed. The system startup identification module runs the BOOT boot program of the bin file and judges and detects user operations. If the user manually enters the recovery mode system, the system will directly enter the recovery mode system. In the system installation processing module, if the IP address acquisition fails, the installation script will exit, the operation result will be returned, and the result will be reported to the computer. The system installation processing module is also used to, if the IP address is successfully obtained, traverse the mounted directories, unmount all mounted system disks, and then erase the first 4KB of the system disk.

4. The system firmware burning and testing device according to claim 3, characterized in that, Also includes: The file resource management module is used to store system firmware files after executing integration test commands and to initiate a file transfer protocol for the system installation and processing module to obtain system firmware files. Enable the Secure Shell Protocol service to allow the system's installation and processing module to remotely execute scripts and system files.

5. An electronic device, comprising: Memory and processor; The processor and the memory communicate with each other via a bus; The memory stores program instructions that can be executed by the processor, characterized in that the processor calls the program instructions to execute a system firmware burning test method according to any one of claims 1 to 2.

Images