A solid state disk detection method, system, device and storage medium

Abstract

The application discloses a solid state disk detection method, system and device and a storage medium, and is applied to the field of solid state disk detection. Related instructions are sent to a micro control unit (MCU) through a data transmission interface, hard disk information obtained by the MCU is acquired, the hard disk information is sent to a background center, and a feedback result obtained by the background center according to the hard disk information is acquired. Through the above method, whether the solid state disk is inserted in a server or not, personnel can collect, report and analyze the hard disk state or realize firmware upgrading of the hard disk through a standard data cable and a personal electronic device installed with a related APP, and remote operation of the background personnel is supported. The solid state disk does not need to be connected with the server and manually detected, is not limited by the environment such as the server and the technical level of the front-line personnel, and the detection efficiency of the solid state disk is greatly improved.

Description

Technical Field

[0001] This application relates to the field of solid-state drive (SSD) testing, and in particular to a SSD testing method, system, apparatus, and storage medium. Background Technology

[0002] With the development of social informatization, the installed capacity of solid-state drives (SSDs) is increasing, and their application scenarios are becoming more and more widespread. Faced with complex installation environments, the probability of SSD failures is also increasing, making it more important to locate hard drive failures, obtain fault information, and upgrade firmware.

[0003] Currently, the main method to solve the above technical problems is to manually connect the solid-state drive (SSD) to the server, locate the SSD failure, obtain fault information, or upgrade the firmware. However, it is difficult to locate the fault information when the server is not working or malfunctioning. In addition, manual means are limited, and the efficiency of SSD status analysis and firmware upgrade is greatly reduced by the limitations of the server environment and the technical level of front-line personnel.

[0004] In view of the above problems, finding a solution to these technical problems is a problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0005] The purpose of this application is to provide a method, system, device, and storage medium for testing solid-state drives (SSDs).

[0006] Currently, the main method for testing solid-state drives (SSDs) is to manually connect the SSD to the server, locate the SSD fault, obtain fault information, or upgrade the firmware. However, this method is difficult to locate fault information when the server is not working or malfunctioning. Furthermore, manual methods are limited by the server environment and the technical level of frontline personnel, which greatly reduces the efficiency of SSD status analysis and firmware upgrades.

[0007] To address the aforementioned issues, this application provides a solid-state drive (SSD) detection method. This method sends relevant commands to a microcontroller unit (MCU) via a data transmission interface, obtains SSD information from the MCU, and then sends this information to a backend center. The backend center then provides feedback based on the SSD information. Using this method, regardless of whether the SSD is installed on a server, personnel can conveniently collect, report, and analyze SSD status, or perform firmware upgrades, using a standard data cable and a personal electronic device with a relevant app installed. Furthermore, it supports remote manual operation from the backend. This method is not limited by server environments or the technical skills of frontline personnel, significantly improving the efficiency of SSD status analysis and firmware upgrades.

[0008] To address the aforementioned technical problems, this application provides a solid-state drive (SSD) testing method. The SSD includes a controller, a memory, a data transfer interface, an MCU, and a data selector. The MCU is connected to the data transfer interface, and the data selector is used to control the connection between the controller and the MCU and the memory. The method includes:

[0009] Send relevant instructions to the MCU via the data transmission interface;

[0010] Obtain the hard disk information stored in the memory obtained by the MCU;

[0011] Analyze the hard drive information and obtain the corresponding analysis results.

[0012] Preferably, there are two memories: a status information memory and a firmware memory.

[0013] There are two data selectors: a first data selector and a second data selector.

[0014] The first data selector is used to control the connection between the main controller and the MCU and the status information memory, and the second data selector is used to control the connection between the main controller and the MCU and the firmware memory.

[0015] Preferably, sending relevant instructions to the MCU via the data transmission interface includes:

[0016] Send fault analysis commands to the MCU via the data transmission interface;

[0017] Obtain the status information acquired by the MCU and the hard disk status information stored in the memory;

[0018] Send hard drive status information to the backend center;

[0019] Retrieve and display the solution obtained from the backend center based on the hard drive status information.

[0020] Preferably, the step of the MCU acquiring the hard disk status information stored in the hard disk status information memory includes:

[0021] Determine whether the main controller is using the status information storage;

[0022] If not, then connect to the status information storage and obtain the hard disk status information;

[0023] If so, then request the use of the status information memory and determine whether the main controller allows the MCU to use the status information memory;

[0024] If permitted, connect to the status information storage and obtain the hard disk status information;

[0025] If not allowed, return to the step of determining whether the master controller uses the status information memory.

[0026] Preferably, sending relevant instructions to the MCU via the data transmission interface includes:

[0027] Send firmware upgrade commands to the MCU via the data transmission interface;

[0028] The MCU retrieves the current firmware version information stored in the firmware memory on the hard drive.

[0029] Send the current firmware version information of the hard drive to the backend center;

[0030] Retrieve the latest firmware version retrieved by the backend center based on the current firmware version information of the hard drive;

[0031] The latest firmware version is sent to the MCU via the data transmission interface.

[0032] Preferably, the step of the MCU obtaining the current firmware version information of the hard disk stored in the firmware memory includes:

[0033] Determine whether the main controller uses firmware storage;

[0034] If not, then connect to the firmware storage and obtain the current firmware version information of the hard drive;

[0035] If so, then request the use of firmware memory and determine whether the main controller allows the MCU to use firmware memory;

[0036] If permitted, connect to the firmware storage and obtain the current firmware version information of the hard drive;

[0037] If not allowed, return to the step of determining whether the main controller uses firmware storage.

[0038] Preferably, before sending relevant instructions to the MCU via the data transmission interface, the process further includes:

[0039] Determine if the server is supplying power to the MCU normally;

[0040] If so, proceed directly to the step of sending relevant instructions to the MCU via the data transmission interface;

[0041] If not, power on the MCU and confirm the connection status before proceeding to the step of sending relevant instructions to the MCU through the data transmission interface.

[0042] To address the aforementioned technical problems, this application also provides a solid-state drive (SSD) testing system, comprising:

[0043] The transmitting module is used to send relevant instructions to the MCU through the data transmission interface;

[0044] The acquisition module is used to acquire the hard disk information stored in the memory obtained by the MCU;

[0045] The analysis module is used to analyze hard drive information and obtain corresponding analysis results.

[0046] To address the aforementioned technical problems, this application also provides a solid-state drive testing device, including a memory for storing computer programs;

[0047] A processor is used to implement the steps of the solid-state drive detection method described above when executing computer programs.

[0048] To address the aforementioned technical problems, this application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the solid-state drive detection method described above.

[0049] The solid-state drive (SSD) detection method provided in this application sends relevant commands to an MCU (Microcontroller Unit) via a data transmission interface, obtains SSD information from the MCU, sends this information to a backend center, and receives feedback results from the backend center based on the SSD information. Using this method, regardless of whether the SSD is installed on a server, personnel can conveniently collect, report, and analyze SSD status, or perform firmware upgrades, using a standard data cable and a personal electronic device with a relevant app installed. It also supports remote manual operation from the backend. It is not limited by server environments or the technical skills of frontline personnel, greatly improving the efficiency of SSD status analysis and firmware upgrades.

[0050] This application also provides a solid-state drive testing system, apparatus, and computer-readable storage medium, which correspond to the above-described method and therefore have the same beneficial effects as the above-described method. Attached Figure Description

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

[0052] Figure 1 A flowchart of a solid-state drive testing method provided in this application;

[0053] Figure 2 A schematic diagram of a solid-state drive system provided in this application;

[0054] Figure 3 This is a structural diagram of a solid-state drive testing system provided in this application;

[0055] Figure 4This is a structural diagram of a solid-state drive testing device provided in another embodiment of this application. Detailed Implementation

[0056] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the protection scope of this application.

[0057] The core of this application is to provide a solid-state drive (SSD) testing method, system, device, and storage medium.

[0058] Currently, the main method for testing solid-state drives (SSDs) is to manually connect the SSD to the server, locate the SSD fault, obtain fault information, or upgrade the firmware. However, this method is difficult to locate fault information when the server is not working or malfunctioning. Furthermore, manual methods are limited by the server environment and the technical level of frontline personnel, which greatly reduces the efficiency of SSD status analysis and firmware upgrades.

[0059] The solid-state drive (SSD) detection method provided in this application sends relevant commands to an MCU (Microcontroller Unit) via a data transmission interface, obtains SSD information from the MCU, sends this information to a backend center, and receives feedback results from the backend center based on the SSD information. Using this method, regardless of whether the SSD is installed on a server, personnel can conveniently collect, report, and analyze SSD status, or perform firmware upgrades, using a standard data cable and a personal electronic device with a relevant app installed. It also supports remote manual operation from the backend. It is not limited by server environments or the technical skills of frontline personnel, greatly improving the efficiency of SSD status analysis and firmware upgrades.

[0060] To enable those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0061] Figure 1 A flowchart of a solid-state drive (SSD) testing method provided in this application is shown, wherein the SSD includes a controller, a memory, a data transfer interface, an MCU, and a data selector. The MCU is connected to the data transfer interface, and the data selector is used to control the connection between the controller and the MCU and the memory, respectively. Figure 1 As shown, the method includes:

[0062] S10: Send relevant instructions to the MCU via the data transmission interface;

[0063] It should be noted that when acquiring the status information of the solid-state drive, the relevant instructions need to be sent to the MCU through the data transmission interface of the current electronic device. This application embodiment does not limit the functionality of the electronic device, as long as it can install the relevant APP. This application embodiment does not limit the type of data transmission interface, nor does it limit whether the data transmission interface can perform functions other than data transmission, such as power supply. This application embodiment does not limit the type and specific content of the relevant instructions sent; the relevant instructions can be, but are not limited to, fault detection instructions, firmware upgrade instructions, etc.

[0064] S11: Obtain the hard disk information stored in the memory obtained by the MCU;

[0065] It should be noted that after the aforementioned instructions are transmitted to the solid-state drive (SSD), its MCU will obtain the relevant hard drive information stored in the corresponding memory according to the instructions, and transmit the hard drive information to the corresponding electronic device through the data transmission interface. The electronic device can then obtain the hard drive information stored in the memory. This application embodiment does not limit the method by which the MCU obtains the hard drive information stored in the memory, nor does it limit the number or type of memory, nor does it limit the type or specific content of the hard drive information; it can be obtained according to the relevant instructions.

[0066] S12: Analyze the hard drive information and obtain the corresponding analysis results.

[0067] It should be noted that the acquired hard drive information is analyzed and processed to obtain corresponding analysis results. This application does not specify a particular method for analyzing and processing the hard drive information; it can be processed directly on the electronic device or uploaded to the corresponding APP's backend investment center for processing. This application's embodiments are not limited to only one processing method for different hard drive information and can be selected according to the actual situation.

[0068] As can be seen, the method provided in this application sends relevant instructions to the MCU through a data transmission interface, obtains the hard drive information acquired by the MCU, sends the hard drive information to the back-end center, and obtains the feedback results obtained by the back-end center based on the hard drive information. Through this method, regardless of whether the solid-state drive is installed on the server, personnel can conveniently collect, report, and analyze the hard drive status, or perform firmware upgrades, using a standard data cable and a personal electronic device with a relevant APP installed. It also supports remote manual operation from the back-end. It is not limited by server environments or the technical level of front-line personnel, greatly improving the efficiency of solid-state drive status analysis and firmware upgrades.

[0069] Based on the above embodiments, this application provides a preferred embodiment, wherein there are two memories, namely a status information memory and a firmware memory;

[0070] There are two data selectors: a first data selector and a second data selector.

[0071] The first data selector is used to control the connection between the main controller and the MCU and the status information memory, and the second data selector is used to control the connection between the main controller and the MCU and the firmware memory.

[0072] It should be noted that this application provides a preferred method of setting up a solid-state drive status information storage for solid-state drive status information, setting up a firmware information storage for firmware upgrade information, and setting up two data selectors (MUX), such as... Figure 2 As shown, Figure 2 This application provides a schematic diagram of a solid-state drive (SSD) system, including a controller and a combined power supply area. The combined power supply refers to the automatic switching between the power supply to the electronic device and the power supply to the SSD system when the electronic device is connected to a mobile phone via a cable. The switching logic is as follows: when the server's power supply to the SSD is abnormal, it switches to power supply to the electronic device; when the server's power supply to the SSD is normal, it supplies power to the SSD system. This power supply includes: memory 1, memory 2, MCU, MUX1, and MUX2. Memory 1 stores basic information such as SSD capacity and serial number, as well as fault states during operation (i.e., the aforementioned status information memory). Memory 2 stores the SSD firmware (i.e., the aforementioned solid-state information memory). A data selector acts as a switch, used for switching between the MCU bus and the controller bus, controlled by the MCU. MUX1 switches whether the aforementioned status information memory is connected to the MCU or the controller, and MUX2 switches whether the aforementioned firmware memory is connected to the MCU or the controller. This application's embodiments are not limited to only including the aforementioned two types of data selectors and two types of memories, nor are they limited to only the aforementioned connection methods. This application's embodiments do not limit the specific switching methods.

[0073] As can be seen, the method provided in this application sends relevant instructions to the MCU through a data transmission interface, obtains the hard drive information acquired by the MCU, sends the hard drive information to the back-end center, and obtains the feedback results obtained by the back-end center based on the hard drive information. Through this method, regardless of whether the solid-state drive is installed on the server, personnel can conveniently collect, report, and analyze the hard drive status, or perform firmware upgrades, using a standard data cable and a personal electronic device with a relevant APP installed. It also supports remote manual operation from the back-end. It is not limited by server environments or the technical level of front-line personnel, greatly improving the efficiency of solid-state drive status analysis and firmware upgrades.

[0074] Based on the above embodiments, this application provides a preferred embodiment in which relevant instructions are sent to the MCU via a data transmission interface, including:

[0075] Send fault analysis commands to the MCU via the data transmission interface;

[0076] Obtain the status information acquired by the MCU and the hard disk status information stored in the memory;

[0077] Send hard drive status information to the backend center;

[0078] Retrieve and display the solution obtained from the backend center based on the hard drive status information.

[0079] It should be noted that, for solid-state drive (SSD) fault analysis, the fault analysis command is first sent to the MCU within the SSD via a data transmission interface. Upon receiving the command, the MCU retrieves the SSD's status information. The electronic device then retrieves this status information from the MCU and uploads it to the backend center. The backend center analyzes the status information and ultimately returns a solution to the electronic device for display. This application does not limit the method by which the MCU retrieves the hard drive status information, and this application is not limited to only the aforementioned analysis command.

[0080] As can be seen, the method provided in this application sends relevant instructions to the MCU through a data transmission interface, obtains the hard drive information acquired by the MCU, sends the hard drive information to the back-end center, and obtains the feedback results obtained by the back-end center based on the hard drive information. Through this method, regardless of whether the solid-state drive is installed on the server, personnel can conveniently collect, report, and analyze the hard drive status and analyze hard drive faults using a standard data cable and a personal electronic device with a relevant APP installed, and it also supports remote manual operation in the back-end. It is not limited by the server environment or the technical level of front-line personnel, greatly improving the efficiency of solid-state drive status analysis and firmware upgrades.

[0081] Based on the above embodiments, this application provides a preferred embodiment in which the step of the MCU acquiring the hard disk status information stored in the hard disk status information memory includes:

[0082] Determine whether the main controller is using the status information storage;

[0083] If not, then connect to the status information storage and obtain the hard disk status information;

[0084] If so, then request the use of the status information memory and determine whether the main controller allows the MCU to use the status information memory;

[0085] If permitted, connect to the status information storage and obtain the hard disk status information;

[0086] If not allowed, return to the step of determining whether the master controller uses the status information memory.

[0087] It should be noted that when the MCU needs to obtain hard disk status information, it must retrieve the corresponding status information from the memory. First, it must determine whether the main controller is using the status information memory. If the main controller is not using the status information memory, the MCU can directly connect to the status information memory and obtain the hard disk status information. If the main controller is currently connected to the status information memory, the MCU must determine whether the main controller allows the MCU to use the status information memory. If the MCU does not allow it, it must continue to determine whether the main controller is connected to the status information memory until it can connect. The embodiments of this application are not limited to only the above-described connection method and can be modified according to actual circumstances.

[0088] As can be seen, the method provided in this application sends relevant instructions to the MCU through a data transmission interface, obtains the hard drive information acquired by the MCU, sends the hard drive information to the back-end center, and obtains the feedback results obtained by the back-end center based on the hard drive information. Through this method, regardless of whether the solid-state drive is installed on the server, personnel can conveniently collect, report, and analyze the hard drive status and analyze hard drive faults using a standard data cable and a personal electronic device with a relevant APP installed, and it also supports remote manual operation in the back-end. It is not limited by the server environment or the technical level of front-line personnel, greatly improving the efficiency of solid-state drive status analysis and firmware upgrades.

[0089] Based on the above embodiments, this application provides a preferred embodiment in which sending relevant instructions to the MCU through a data transmission interface includes:

[0090] Send firmware upgrade commands to the MCU via the data transmission interface;

[0091] The MCU retrieves the current firmware version information stored in the firmware memory on the hard drive.

[0092] Send the current firmware version information of the hard drive to the backend center;

[0093] Retrieve the latest firmware version retrieved by the backend center based on the current firmware version information of the hard drive;

[0094] The latest firmware version is sent to the MCU via the data transmission interface.

[0095] It should be noted that when upgrading the firmware of a solid-state drive (SSD), the firmware upgrade command is first sent to the MCU (Microcontroller Unit) within the SSD via a data transmission interface. Upon receiving the command, the MCU retrieves the current firmware version information from the SSD. The electronic device then obtains this information from the MCU and uploads it to the backend center. The backend center analyzes the status information of the firmware version, retrieves the latest firmware version, and finally sends the latest firmware version to the MCU via the data transmission interface. This application does not limit the method by which the MCU obtains the current firmware version information, and this application is not limited to the analysis command described above.

[0096] As can be seen, the method provided in this application sends relevant instructions to the MCU through a data transmission interface, obtains the hard drive information acquired by the MCU, sends the hard drive information to the back-end center, and obtains the feedback results obtained by the back-end center based on the hard drive information. Through this method, regardless of whether the solid-state drive is installed on the server, personnel can conveniently collect, report, and analyze the hard drive status and upgrade the hard drive firmware version using a standard data cable and a personal electronic device with a relevant APP installed. It also supports remote manual operation in the back-end. It is not limited by the server environment or the technical level of front-line personnel, greatly improving the efficiency of solid-state drive status analysis and firmware upgrades.

[0097] Based on the above embodiments, this application provides a preferred embodiment in which the step of the MCU obtaining the current firmware version information of the hard disk stored in the firmware memory includes:

[0098] Determine whether the main controller uses firmware storage;

[0099] If not, then connect to the firmware storage and obtain the current firmware version information of the hard drive;

[0100] If so, then request the use of firmware memory and determine whether the main controller allows the MCU to use firmware memory;

[0101] If permitted, connect to the firmware storage and obtain the current firmware version information of the hard drive;

[0102] If not allowed, return to the step of determining whether the main controller uses firmware storage.

[0103] It should be noted that when the MCU needs to obtain the current firmware version information, it must retrieve the corresponding firmware version information from the memory. First, it must determine whether the main controller is using the firmware memory. If the main controller is not using the firmware memory, the MCU can directly connect to the firmware memory and obtain the current firmware version information. If the main controller is connected to the firmware memory, the MCU must determine whether the main controller allows the MCU to use the firmware memory. If the MCU does not allow it, it must continue to determine whether the main controller is connected to the firmware memory until a connection can be established. The embodiments of this application are not limited to only the above-described connection method and can be modified according to actual circumstances.

[0104] As can be seen, the method provided in this application sends relevant instructions to the MCU through a data transmission interface, obtains the hard drive information acquired by the MCU, sends the hard drive information to the back-end center, and obtains the feedback results obtained by the back-end center based on the hard drive information. Through this method, regardless of whether the solid-state drive is installed on the server, personnel can conveniently collect, report, and analyze the hard drive status and upgrade the hard drive firmware version using a standard data cable and a personal electronic device with a relevant APP installed. It also supports remote manual operation in the back-end. It is not limited by the server environment or the technical level of front-line personnel, greatly improving the efficiency of solid-state drive status analysis and firmware upgrades.

[0105] Based on the above embodiments, this application provides a preferred embodiment, which further includes the following before sending relevant instructions to the MCU through the data transmission interface:

[0106] Determine if the server is supplying power to the MCU normally; if so, proceed directly to the step of sending relevant instructions to the MCU through the data transmission interface; if not, supply power to the MCU and confirm the connection status before proceeding to the step of sending relevant instructions to the MCU through the data transmission interface.

[0107] As can be seen, the method provided in this application embodiment first determines whether the circuit of the solid-state drive is powered normally before sending data to the solid-state drive. If the power supply is not normal, the solid-state drive is powered before the transmission command is transmitted, so as to avoid the failure of the transmission command in the absence of power supply, which greatly improves the efficiency of solid-state drive status analysis and firmware upgrade.

[0108] From the perspective of functional modules Figure 3 A structural diagram of a solid-state drive testing system provided in this application is shown below. Figure 3 As shown, the system includes:

[0109] The sending module 30 is used to send relevant instructions to the MCU through the data transmission interface;

[0110] The acquisition module 31 is used to acquire the hard disk information stored in the memory obtained by the MCU;

[0111] Analysis module 32 is used to analyze hard disk information and obtain corresponding analysis results.

[0112] Since the embodiments of the system part correspond to the embodiments of the method part, please refer to the description of the embodiments of the method part for the embodiments of the system part, and they will not be repeated here.

[0113] The solid-state drive testing system provided in this embodiment corresponds to the solid-state drive testing method described above, and therefore has the same beneficial effects as the method described above.

[0114] Figure 4 This is a structural diagram of a solid-state drive testing device provided in another embodiment of this application, as shown below. Figure 4 As shown, the solid-state drive testing device includes: a memory 20 for storing computer programs;

[0115] The processor 21 is used to execute computer programs to implement the steps of the solid-state drive detection method mentioned in the above embodiments.

[0116] The solid-state drive testing device provided in this embodiment may include, but is not limited to, smartphones, tablets, laptops, or desktop computers.

[0117] The processor 21 may include one or more processing cores, such as a quad-core processor or an octa-core processor. The processor 21 may be implemented using at least one of the following hardware forms: Digital Signal Processor (DSP), Field-Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). The processor 21 may also include a main processor and a coprocessor. The main processor, also known as the Central Processing Unit (CPU), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, the processor 21 may integrate a Graphics Processing Unit (GPU), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, the processor 21 may also include an Artificial Intelligence (AI) processor, which is used to handle computational operations related to machine learning.

[0118] The memory 20 may include one or more computer-readable storage media, which may be non-transitory. The memory 20 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In this embodiment, the memory 20 is used to store at least the following computer program 201, which, after being loaded and executed by the processor 21, is capable of implementing the relevant steps of the solid-state drive detection method disclosed in any of the foregoing embodiments. In addition, the resources stored in the memory 20 may also include an operating system 202 and data 203, and the storage method may be temporary or permanent storage. The operating system 202 may include Windows, Unix, Linux, etc. The data 203 may include, but is not limited to, the data in the solid-state drive detection method.

[0119] In some embodiments, the solid-state drive testing device may further include a display screen 22, an input / output interface 23, a communication interface 24, a power supply 25, and a communication bus 26.

[0120] Those skilled in the art will understand that Figure 4 The structure shown does not constitute a limitation on the solid-state drive testing device and may include more or fewer components than shown.

[0121] The solid-state drive testing device provided in this application includes a memory and a processor. When the processor executes a program stored in the memory, it can implement the following method: solid-state drive testing method.

[0122] Finally, this application also provides an embodiment corresponding to a computer-readable storage medium. The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps described in the above method embodiments.

[0123] It is understood that if the methods in the above embodiments are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and executes all or part of the steps of the methods in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0124] The foregoing provides a detailed description of a solid-state drive (SSD) testing method, system, apparatus, and storage medium provided in this application. The various embodiments in the specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section. It should be noted that those skilled in the art can make several improvements and modifications to this application without departing from the principles of this application, and these improvements and modifications also fall within the protection scope of the claims of this application.

[0125] It should also be noted that, in this specification, relational terms such as "first" and "second" are used only 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 the element.

Claims

1. A method for detecting solid-state drives, characterized in that, The solid-state drive (SSD) includes a controller, memory, a data transfer interface, an MCU, and a data selector. The MCU is connected to the data transfer interface, and the data selector is used to control the connection between the controller, the MCU, and the memory. The MCU is a built-in unit of the SSD, and it is connected to a personal electronic device via the data transfer interface. This method is applied to a personal electronic device and includes: The relevant instructions are sent to the MCU through the data transmission interface; The MCU acquires the hard disk information stored in the memory; the hard disk information includes hard disk status information and firmware version information. The hard drive information is analyzed and the corresponding analysis results are obtained.

2. The solid-state drive testing method according to claim 1, characterized in that, The memory consists of two parts: a status information memory and a firmware memory. There are two data selectors, namely a first data selector and a second data selector; The first data selector is used to control the connection between the main controller and the MCU and the status information memory, respectively, and the second data selector is used to control the connection between the main controller and the MCU and the firmware memory, respectively.

3. The solid-state drive testing method according to claim 2, characterized in that, Sending relevant instructions to the MCU through the data transmission interface includes: The fault analysis command is sent to the MCU through the data transmission interface; Obtain the hard disk status information stored in the status information memory acquired by the MCU; Send the hard drive status information to the backend center; The solution obtained by the backend center based on the hard drive status information is retrieved and displayed.

4. The solid-state drive testing method according to claim 3, characterized in that, The steps for the MCU to obtain the hard disk status information stored in the hard disk status information memory include: Determine whether the main controller is using the status information memory; If not, then connect the status information storage and obtain the hard disk status information; If so, then request the use of the status information memory and determine whether the main controller allows the MCU to use the status information memory; If permitted, the status information storage is connected and the hard disk status information is obtained; If not allowed, return to the step of determining whether the master controller uses the status information memory.

5. The solid-state drive testing method according to claim 2, characterized in that, Sending relevant instructions to the MCU through the data transmission interface includes: The firmware upgrade command is sent to the MCU through the data transmission interface; The MCU obtains the current firmware version information of the hard disk stored in the firmware memory; Send the current firmware version information of the hard drive to the backend center; Obtain the latest firmware version retrieved by the backend center based on the current firmware version information of the hard drive; The latest version firmware is sent to the MCU through the data transmission interface.

6. The solid-state drive testing method according to claim 5, characterized in that, The steps for the MCU to obtain the current firmware version information of the hard disk stored in the firmware memory include: Determine whether the main controller uses the firmware memory; If not, then connect to the firmware storage and obtain the current firmware version information of the hard disk; If so, then request the use of the firmware memory and determine whether the main controller allows the MCU to use the firmware memory; If permitted, the firmware storage is connected and the current firmware version information of the hard disk is obtained; If not allowed, return to the step of determining whether the main controller uses the firmware memory.

7. The solid-state drive testing method according to any one of claims 1 to 6, characterized in that, Before sending the relevant instructions to the MCU through the data transmission interface, the following steps are also included: Determine whether the server is supplying power to the MCU normally; If so, proceed directly to the step of sending relevant instructions to the MCU through the data transmission interface; If not, then power on the MCU and confirm the connection status before proceeding to the step of sending relevant instructions to the MCU through the data transmission interface.

8. A solid-state drive (SSD) testing system, characterized in that, The solid-state drive (SSD) includes a controller, memory, a data transfer interface, an MCU, and a data selector. The MCU is connected to the data transfer interface, and the data selector is used to control the connection between the controller, the MCU, and the memory. The MCU is a built-in unit of the SSD and is connected to personal electronic devices via the data transfer interface. The sending module is used to send relevant instructions to the MCU through the data transmission interface; The acquisition module is used to acquire the hard disk information stored in the memory obtained by the MCU; the hard disk information includes hard disk status information and firmware version information; The analysis module is used to analyze the hard drive information and obtain the corresponding analysis results.

9. A solid-state drive testing device, characterized in that, Includes memory used to store computer programs; A processor, configured to implement the steps of the solid-state drive detection method as described in any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the solid-state drive detection method as described in any one of claims 1 to 7.

Images