Link anomaly detection and recovery method during firmware burning

Abstract

The invention discloses a link anomaly detection and recovery method during firmware burning, which relates to the technical field of solid-state storage, and comprises the following steps: S1, a host sequentially sends different preset commands to SSD (Solid State Disk) equipment for burning operation; s2, correspondingly and sequentially judging whether different preset commands are successfully executed or not by the host; s3, if so, judging that the SSD equipment is burnt successfully; if not, the host detects whether the SSD equipment exists or not; s4, if yes, the S1 is executed repeatedly until the number of times of repeating the S1 exceeds a preset number threshold, and it is judged that the link is abnormal; if not, the preset external device is used for operating the SSD device according to the preset rule, and the host detects whether the SSD device exists or not; s5, if yes, repeating the S1 until the number of times of repeating the S1 exceeds a preset number threshold, and judging that the link is abnormal; and if not, judging that the link is abnormal or the SSD equipment has a problem. According to the invention, detection and recovery of link abnormity are completed through an automatic process, manpower resources in a burning process are saved, and faults caused by manual operation errors are avoided.

Description

Technical Field

[0001] This invention relates to the field of solid-state storage technology, and in particular to a method for detecting and recovering from link anomalies during firmware burning. Background Technology

[0002] Currently, hard drive programming is a key step in the manufacturing and maintenance of storage devices. In the production process of hard drives, firmware programming is a necessary step to write the underlying program of the controller chip into the internal storage unit of the device.

[0003] In existing technologies, hard drive production relies on manual operation, which has problems such as low efficiency, low fault tolerance, and poor batch consistency. The process requires manual connection of each device to the programmer and manual input of firmware files. This is prone to errors due to operational mistakes, such as incorrect firmware versions or writing failures, which can lead to device recognition failures and abnormal performance. Summary of the Invention This invention provides a method for detecting and recovering link anomalies during firmware flashing, in order to solve the technical problems of low efficiency and easy error caused by reliance on manual operation in related technologies.

[0004] This invention provides a method for detecting and recovering from link anomalies during firmware flashing, comprising the following steps: Step S1: The host sequentially sends different preset commands to the SSD device to perform the burning operation; Step S2: The host sequentially checks whether the different preset commands have been executed successfully. Step S3: If all are true, the SSD device is determined to have been successfully burned; otherwise, the host detects whether the SSD device exists. Step S4: If yes, repeat step S1 until the number of repetitions of step S1 exceeds the preset threshold, and determine that the link is abnormal; if no, use a preset external device to perform preset rule operations on the SSD device, and the host detects whether the SSD device exists. Step S5: If yes, repeat step S1 until the number of times step S1 is repeated exceeds the preset threshold, then determine that the link is abnormal; if no, determine that the link is abnormal or that the SSD device has a problem.

[0005] In some embodiments, before the host sequentially sends different preset commands to the SSD device to perform the burning operation, the following steps are included: Use a USB to PCIe adapter to connect the SSD to the host computer. One side of the USB to PCIe adapter has a USB interface, which is used to connect to the host computer. The other side of the USB to PCIe adapter has a PCIe interface, which is used to connect the SSD to the host computer.

[0006] In some embodiments, if not, performing preset rule operations on the SSD device using a preset external device includes: Use preset external devices to perform removal, power-off, power-on, and loading operations on the SSD device.

[0007] In some embodiments, the removal operation of the SSD device using a preset external device includes: The SSD device is removed using the host's standard system protocols and connection methods.

[0008] In some embodiments, the step of using a preset external device to power down the SSD device includes: Power-off operation of the PCIe slot is performed through the proprietary protocol of the bridge chip in the USB to PCIe fixture.

[0009] In some embodiments, the step of powering on the SSD device using a preset external device includes: The PCIe slot is powered on via a proprietary protocol of the bridge chip in the USB-to-PCIe fixture.

[0010] In some embodiments, the loading operation of the SSD device using a preset external device includes: The SSD device is loaded using the host's standard system protocols and connection methods.

[0011] In some embodiments, if the condition is yes, step S1 is repeated until the number of repetitions of step S1 exceeds a preset threshold. After determining that the link is abnormal, the following steps are included: Perform removal, power-down, power-on, and loading operations on both the USB interface and the SSD device.

[0012] In some embodiments, step S1, in which the host sequentially sends different preset commands to the SSD device to perform a burning operation, includes: The preset commands include at least the PCIE ADMIN command, the DOWNLOAD command, and the SSD reboot command.

[0013] In some embodiments, if the condition is yes, step S1 is repeated until the number of repetitions of step S1 exceeds a preset threshold, and a link anomaly is determined, including: The preset threshold number of times is five.

[0014] The beneficial effects of the technical solution provided by this invention include: This invention provides a method for detecting and recovering from link anomalies during firmware flashing. The method includes the following steps: S1, the host sequentially sends different preset commands to the SSD device for flashing; S2, the host sequentially checks whether the different preset commands were executed successfully; S3, if all commands were executed successfully, the SSD device is determined to have been successfully flashed; otherwise, the host checks whether the SSD device exists; S4, if the command is executed successfully, step S1 is repeated until the number of repetitions exceeds a preset threshold, at which point a link anomaly is determined; otherwise, a preset external device is used to perform operations on the SSD device according to preset rules, and the host checks whether the SSD device exists; S5, if the command is executed successfully, step S1 is repeated until the number of repetitions exceeds a preset threshold, at which point a link anomaly is determined; otherwise, a link anomaly or a problem with the SSD device is determined. This invention reduces manual intervention during the detection and recovery of problems during hard drive flashing, saving manpower and avoiding software errors caused by human error. Attached Figure Description

[0015] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0016] Figure 1 This is a flowchart illustrating a method for detecting and recovering link anomalies during firmware flashing, provided in an embodiment of the present invention. Detailed Implementation To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. 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.

[0017] This invention provides a method for detecting and recovering from link anomalies during firmware burning, which can solve the technical problem that manual operation is labor-intensive and prone to errors when problems occur during SSD device burning.

[0018] See Figure 1 As shown, this embodiment of the invention provides a method for detecting and recovering from link anomalies during firmware flashing, including the following steps: Step S1: The host sequentially sends different preset commands to the SSD device to perform the burning operation; Step S2: The host sequentially checks whether the different preset commands have been executed successfully. Step S3: If all are true, the SSD device is determined to have been successfully burned; otherwise, the host detects whether the SSD device exists. Step S4: If yes, repeat step S1 until the number of repetitions of step S1 exceeds the preset threshold, and determine that the link is abnormal; if no, use a preset external device to perform preset rule operations on the SSD device, and the host detects whether the SSD device exists. Step S5: If yes, repeat step S1 until the number of times step S1 is repeated exceeds the preset threshold, then determine that the link is abnormal; if no, determine that the link is abnormal or that the SSD device has a problem.

[0019] In the SSD device burning process, this invention first sends a preset command set in the burning process. If the preset command fails to execute, it checks whether the SSD device is properly connected. If it is not properly connected, it retests whether it is properly connected after removing, powering off, powering on, and loading operations. If it is still not connected, it is determined that the link or the SSD device is faulty. The judgment and recovery process does not require human intervention, saving human resources and avoiding faults caused by human operation errors.

[0020] In an optional embodiment, before the host sequentially sends different preset commands to the SSD device to perform the burning operation, it includes: Use a USB to PCIe adapter to connect SSD devices to the host. One side of the USB to PCIe adapter has a USB interface, which is connected to the host via a dual USB cable. The other side of the USB to PCIe adapter has a PCIe interface, which is used to connect various SSD devices. The other side of the USB to PCIe adapter has multiple PCIe interfaces, allowing multiple SSD devices to be connected simultaneously.

[0021] By using a USB-to-PCIe adapter to connect SSD devices and the host in a one-to-many manner, a single host can connect to multiple SSD devices and perform firmware burning operations simultaneously, greatly improving the efficiency of firmware burning.

[0022] In an optional embodiment, the step of using a preset external device to perform preset rule operations on the SSD device includes: The preset external devices can be freely selected according to the different protocols used for connection. The selected external devices can be used to perform removal, power-off, power-on, and loading operations on the SSD device.

[0023] By using preset external devices to perform removal, power-off, power-on, and loading operations to reconnect the SSD device, link failures caused by connection problems are eliminated. External devices replace manual labor, improving the efficiency of the inspection stage and avoiding SSD device failures or damage caused by improper manual operation.

[0024] In an optional embodiment, the removal operation of the SSD device using a preset external device includes: Use the default external device to remove the SSD device according to the system standard protocol and PCIe interface connection method provided by the host.

[0025] By using external devices to remove the SSD device according to the system's standard protocol, hardware damage to the SSD device caused by direct physical removal is avoided, the success rate of firmware burning is improved, and firmware burning costs are saved.

[0026] In an optional embodiment, the step of using a preset external device to power down the SSD device includes: Using a pre-set external device, the USB interface is used as a control channel. The bridge chip parses the private protocol instructions and performs a safe and contactless power-off operation on the PCIe slot directly through the private protocol of the bridge chip of the USB to PCIe fixture.

[0027] By using the proprietary protocol of the bridge chip in the USB-to-PCIe fixture to power off the SSD device, the risk of electrostatic discharge or short circuit that may be caused by manual power-on operation in the traditional operation process is avoided, and the SSD device or PCIe interface is prevented from being burned out due to improper operation.

[0028] In an optional embodiment, the step of powering on the SSD device using a preset external device includes: Using a preset external device, the USB interface is used as a control channel. The bridge chip parses the private protocol instructions and performs a smooth and controllable power-on operation on the PCIe slot through the private protocol of the bridge chip of the USB to PCIe fixture.

[0029] Reduce manual intervention, speed up the power-on process for SSD devices, reduce the time required for each burning process, and avoid the risk of electrostatic discharge or short circuit that may be caused by manual power-on in traditional operation processes, preventing SSD devices or PCIe interfaces from being burned out due to improper operation.

[0030] In an optional embodiment, the loading operation of the SSD device using a preset external device includes: The SSD device is loaded using a preset external device according to the system standard protocol and PCIe interface connection method provided by the host.

[0031] By using an external device to load the SSD according to the system's standard protocol, hardware damage caused by errors resulting from direct physical connection is avoided, thus improving the success rate of firmware burning and saving firmware burning costs.

[0032] In an optional embodiment, if the condition is yes, step S1 is repeated until the number of repetitions of step S1 exceeds a preset threshold. After determining that the link is abnormal, the following steps are included: If an SSD device on a certain channel repeatedly encounters command errors, it is determined that the USB interface and PCIe interface of the USB to PCIe fixture need to be removed, powered off, powered on, and loaded using preset external devices to resolve the link anomaly.

[0033] When an SSD device on a certain channel repeatedly encounters command errors, a power-off operation is performed on both the USB interface and the SSD device to resolve link errors that cannot be repaired by power-off alone via software, and to prevent the burning process from failing due to problems with the physical connection of the USB interface.

[0034] In an optional embodiment, step S1, in which the host sequentially sends different preset commands to the SSD device to perform a burning operation, includes: The preset commands include at least the PCIE ADMIN command, the DOWNLOAD command, and the SSD reboot command. First, the PCIE ADMIN command is executed to start the host burning program and prepare for the burning process. Then, the DOWNLOAD command is executed to start burning the firmware, downloading and burning the corresponding FW file to the SSD device to unlock the SSD device. Finally, the SSD reboot command is executed, and after rebooting, it is checked whether the SSD device can be detected on the channel.

[0035] By setting up PCIE ADMIN, DOWNLOAD, and SSD reboot commands, the process of burning SSD devices is standardized and automated. Compared with the traditional manual burning method, it is simpler and more intuitive. The standardized operation method requires less professional training for operators and makes it easier to detect anomalies in the subsequent stage.

[0036] In an optional embodiment, if the step is to repeat step S1 until the number of repetitions of step S1 exceeds a preset threshold, the method further includes setting the preset threshold to five times. By setting a threshold, the programming process is prevented from entering an infinite loop, thus improving programming efficiency and avoiding resource waste.

[0037] In the description of this invention, it should be noted that the terms "upper," "lower," etc., indicating the orientation or positional relationship are based on the orientation or positional relationship shown in the accompanying drawings, and are only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the invention. Unless otherwise expressly specified and limited, the terms "installed," "connected," and "linked" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication between two elements. For those skilled in the art, the specific meaning of the above terms in this invention can be understood according to the specific circumstances.

[0038] It should be noted that in this invention, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0039] The above description is merely a specific embodiment of the present invention, enabling those skilled in the art to understand or implement the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the present invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features of the invention herein.

Claims

1. A method for detecting and recovering from link anomalies during firmware flashing, characterized in that, Includes the following steps: Step S1: The host sequentially sends different preset commands to the SSD device to perform the burning operation; Step S2: The host sequentially checks whether the different preset commands have been executed successfully. Step S3: If all are true, the SSD device is determined to have been successfully burned; otherwise, the host detects whether the SSD device exists. Step S4: If yes, repeat step S1 until the number of repetitions of step S1 exceeds the preset threshold, and determine that the link is abnormal; if no, use a preset external device to perform preset rule operations on the SSD device, and the host detects whether the SSD device exists. Step S5: If yes, repeat step S1 until the number of times step S1 is repeated exceeds the preset threshold, then determine that the link is abnormal; if no, determine that the link is abnormal or that the SSD device has a problem.

2. The method for detecting and recovering link anomalies during firmware burning according to claim 1, wherein before the host sequentially sends different preset commands to the SSD device to perform the burning operation, it includes: Use a USB to PCIe adapter to connect the SSD to the host computer. One side of the USB to PCIe adapter has a USB interface, which is used to connect to the host computer. The other side of the USB to PCIe adapter has a PCIe interface, which is used to connect the SSD to the host computer.

3. The method for detecting and recovering link anomalies during firmware flashing according to claim 2, wherein if not, the operation of the SSD device using a preset external device according to preset rules includes: Use preset external devices to perform removal, power-off, power-on, and loading operations on the SSD device.

4. The method for detecting and recovering link anomalies during firmware flashing according to claim 2, wherein the step of removing the SSD device using a preset external device includes: The SSD device is removed using the host's standard system protocols and connection methods.

5. The method for detecting and recovering link anomalies during firmware burning according to claim 2, wherein the step of using a preset external device to power down the SSD device includes: Power-off operation of the PCIe slot is performed through the proprietary protocol of the bridge chip in the USB to PCIe fixture.

6. The method for detecting and recovering link anomalies during firmware burning according to claim 2, wherein the step of powering on the SSD device using a preset external device includes: The PCIe slot is powered on via a proprietary protocol of the bridge chip in the USB-to-PCIe fixture.

7. The method for detecting and recovering link anomalies during firmware flashing according to claim 2, wherein the step of using a preset external device to perform a loading operation on the SSD device includes: The SSD device is loaded using the host's standard system protocols and connection methods.

8. A method for detecting and recovering link anomalies during firmware flashing according to claim 2, wherein if so, step S1 is repeated until the number of repetitions of step S1 exceeds a preset threshold, and after determining that the link is abnormal, the method includes: Perform removal, power-down, power-on, and loading operations on both the USB interface and the SSD device.

9. The method for detecting and recovering link anomalies during firmware burning according to claim 1, wherein step S1, the host sequentially sends different preset commands to the SSD device to perform the burning operation, includes: The preset commands include at least the PCIE ADMIN command, the DOWNLOAD command, and the SSD reboot command.

10. A method for detecting and recovering link anomalies during firmware flashing according to claim 8, wherein if so, step S1 is repeated until the number of repetitions of step S1 exceeds a preset threshold, and a link anomaly is determined, comprising: The preset threshold number of times is five.

Images