TW202147114A - Method and apparatus and computer program product for producing solid state disk devices - Google Patents

Abstract

A method is introduced for producing solid state disks (SSDs), which is performed by a processing unit of a production host. The production host includes a device interface including first ports. Each first port is connected to one hub. Each hub includes second ports. The method includes the steps of: loading a port-mapping configuration table containing location information for indicating the second ports; comparing location information of a hardware description file with the location information of the port-mapping configuration table to determine whether each second port is connected to a SSD; displaying a graphical user interface (GUI) for showing whether each second port is connected to a SSD; and, when a SSD connecting to one second port fails to perform a card-activation process, updating the GUI for showing information about a card-activation failure has occurred in the SSD connecting to the corresponding second port. With the aforementioned comparisons therebetween, it can automatically identify ports of each hub of the production system.

Description

Method and apparatus for producing solid state hard disk and computer program product

The present invention relates to storage devices, in particular to a computer program product, method and device for producing solid state hard disks.

Solid-state drives usually need to complete the card-opening process before they can be sold, and the time spent in the card-opening process is an important issue in the production of solid-state drives. A production host can usually connect 5 to 16 solid-state drives through the ports of the device interface, and open the card for the connected solid-state drives. However, traditionally, when one of the solid-state drives fails to open the card, the production host cannot automatically know which one actually has the error, and the production personnel need to manually unplug the connected solid-state drive to confirm, elongated production time. Therefore, the present invention provides a method, apparatus and computer program product for producing a solid state hard disk, which are used to solve the above problems.

In view of this, how to alleviate or eliminate the above-mentioned deficiencies in related fields is a problem to be solved.

This specification relates to an embodiment of a method for producing a solid state hard disk, which is executed by a processing unit of a production host. The production host includes a device interface, and the device interface includes a plurality of first ports. Each first port is connected to a hub, and each hub includes a plurality of second ports. The above method includes: loading a port mapping configuration table, including position information representing each second port; comparing the position information in the hardware description file with the position information in the port mapping configuration table to determine each second port Whether a solid-state drive is connected; display a GUI on the monitor to indicate whether each second port is connected to a solid-state drive; and update when one of the connected solid-state drives in the second port fails to open the card The GUI is used to indicate the information about the failure of card opening of the solid state drive connected to the corresponding second port.

This specification also relates to a computer program product comprising program code for producing a solid state hard disk. When the processing unit of the production host executes the code, the method for producing the solid state hard disk as described above is implemented.

The present specification further relates to an apparatus for producing a solid state hard disk, comprising: the above-mentioned apparatus interface and a processing unit. The processing unit is coupled to the device interface for loading and executing the above-mentioned code to implement the above-mentioned method.

One of the advantages of the above embodiment is that, through the above comparison, it can automatically identify whether each port on each hub in the production system is connected to a solid state hard disk.

Another advantage of the above embodiment is that through the information contained in the port mapping configuration table as described above, when a certain solid state drive fails to open the card, it can automatically identify which port is connected to the solid state drive during the card opening process. An error occurred in .

Other advantages of the present invention will be explained in more detail in conjunction with the following description and drawings.

The following description is a preferred implementation manner to complete the invention, and its purpose is to describe the basic spirit of the invention, but it is not intended to limit the invention. Reference must be made to the scope of the following claims for the actual inventive content.

It must be understood that the words "comprising" and "including" used in this specification are used to indicate the existence of specific technical features, values, method steps, operation processes, elements and/or components, but do not exclude the possibility of adding More technical features, values, method steps, job processes, elements, components, or any combination of the above.

The use of words such as "first", "second", "third", etc. in the claims is used to modify the elements in the claims, and is not used to indicate that there is a priority order, a prepositional relationship between them, or an element Prior to another element, or chronological order in which method steps are performed, is only used to distinguish elements with the same name.

It must be understood that when an element is described as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element, and intervening elements may be present. In contrast, when an element is described as being "directly connected" or "directly coupled" to another element, there are no intervening elements present. Other words used to describe the relationship between elements can also be read in a similar fashion, such as "between" versus "directly interposed," or "adjacent" versus "directly adjoining," and the like.

In order to allow the production computer to automatically distinguish the Solid State Disk (SSD) connected to each port, the embodiment of the present invention divides the entire production process into two stages: the port distinguishing stage and the card opening stage. Activation) stage. Referring to FIG. 1 , in the port setting stage 110 , the training computer 140 analyzes the content of the hardware description file (Hardware Description File) in the operating system (Operating System, OS) to obtain the identification information of each physical port, such as sequence advanced Serial Advanced Technology Attachment (SATA/Peripheral Component Interconnect Express, PCIe Registries), Bus Number, Target ID, Logical Unit Number, LUN), etc., and generate a Port-mapping Configuration Table 160 accordingly. In the card opening phase 130 , the production computer 180 loads the port mapping configuration table 160 and performs the card opening procedure for a plurality of solid state drives connected to the production computer 180 . During the card opening process, if the production computer 180 finds any error message, it can identify which physical port is connected to the solid state drive with the error according to the information in the port mapping configuration table 160, and display it on the Graphical User Interface (Graphical User Interface) , GUI), which facilitates the operator and/or production computer 180 to perform error-removal processing. It should be noted here that the training computer 140 and the production computer 180 may be two computers with the same necessary software and hardware configuration, or the same computer.

Refer to Figure 2. The training system 20 includes a port-distinguishing host 210 , a hub 230 , a training solid state hard disk 250 and a display 270 . The training computer 140 shown in FIG. 1 may include a porting host 210 , a hub 230 and a display 270 . The training SSD 250 may include a flash controller and multiple flash modules. The display 270 may be a thin film transistor-liquid crystal display (Thin Film Transistor-Liquid Crystal Display, TFT-LCD Display), an organic light-emitting diode display (Organic Light-Emitting Diode, OLED Display), etc., and is displayed during the training process for engineers or The screen that the operator can watch, including the prompt text, numbers, symbols, patterns, etc., or any combination of the above.

The port-fixing host 210 can be implemented by a personal computer, a notebook computer (Laptop PC), an industrial computer (Industrial Computer), a workstation (Workstation), and the like. The porting host 210 includes a device interface 212 having a plurality of ports 214-1 to 214-4, each port can be connected to a hub, for example, the port 214-1 is connected to the hub 230. Although the device interface 212 described in FIG. 2 is only equipped with 4 ports, those skilled in the art may configure the device interface 212 with more or less ports, so that the port host 210 can be connected to more or less hubs. The present invention should not be limited thereby. The hub 230 includes a plurality of ports 232-1 to 232-4, and each port can be plugged with a training solid state drive 250, such as any one of the training solid state drives 250-1 to 250-4. It should be noted that, in order to make the description concise, when the following paragraphs use the training solid state drive 250 to describe, the structures, functions, method steps or other technical contents represented by the description can be applied to the training solid state drives 250-1 to 250-4. and any of the others. Although the hub 230 depicted in FIG. 1 has 4 ports, those skilled in the art can connect a hub with more or fewer ports to the port host 210 so that the port host 210 can be connected to more or less training Solid state hard disk, the present invention should not be limited by this.

Refer to Figure 3. Since the hub 230 is connected to a port on the device interface 212 and when the training solid state drive 250 is plugged into the hub 230, it is equivalent to physically connecting the training solid state drive 250 to the fixed port host 210, so the illustration shown in FIG. 2 is omitted in FIG. 3 . the hub 230. The porting host 210 includes a processing unit 312, which may be implemented in a variety of ways, such as using general-purpose hardware (eg, a single processor, a multiprocessor capable of parallel processing, a graphics processor, or other processor capable of computing), and When executing software and/or firmware instructions, for example, a port-distinguishing tool (Port-distinguishing Tool), an operating system (Operating System, OS), a driver (Driver), etc., to provide specified functions. The processing unit 312 can transmit commands to the training solid state drive 250 through the device interface 212 to complete the required operations.

The training solid state drive 250 includes a flash controller 330 and a flash module 350 . The flash memory module 350 provides a large amount of storage space, usually hundreds of gigabytes (Gigabytes) or even several terabytes (Terabytes), for storing large amounts of user data, such as high-resolution pictures, videos, etc. The flash controller 130 includes a host interface 332 , and the host interface 332 is coupled to the device interface 212 of the port host 210 .

In order to distinguish the ports 214-1 to 214-4 of the device interface 212 and the ports 232-1 to 232-4 of the hub 230 as shown in FIG. 2, a hardware description file needs to be provided to identify the ports 214-1 to 214-4 and The ports 232-1 to 232-4 enable the software program to know that an I/O device is connected to the port host 210 through one of the ports 214-1 to 214-4 and the ports 232-1 to 232-4. For example, the Windows Registry is a hierarchical database that stores low-level settings for use by the Windows operating system (Windows OS) and applications. Specifically, the Windows log file includes information, settings, options and other values of the hardware (eg, SATA/PCIe interface, etc.) of the port host 210 and the device (eg, solid-state drive) connected to the port host 210 . When a solid-state hard disk is connected to the fixed port host 210 through a port of the hub 230, a new subkey (Subkey) will be added to the Windows login file, and the subkey contains a plurality of values (Values), which are used for storage such as hardware Settings for identifiers, location information, manufacturer, service, etc.

An embodiment of the present invention provides a port positioning method, which is implemented when the processing unit 312 loads and executes the code of the port positioning tool. Refer to Figure 4. Taking the Windows operating system as an example, the details are as follows:

Step S410: Set the variable i=1. The variable i is used to record the sequence number of the fixed port.

Next, the process repeatedly executes a loop, including steps S420 to S480. Before each round, the operator inserted a training solid-state drive into the designated port. For example, the ports 232-1, 232-2, 232-3, and 232-4 of the hub 230 may be labeled as Port#1, Port#2, Port#3, and Port#4 in sequence. After the operator inserts the training solid state drive 250-1 into the port 232-1, the processing unit 312 executes steps S420 to S480 to assign the port Port#1. Next, after the operator inserts the training solid state drive 250-2 into the port 232-2, the processing unit 312 executes steps S420 to S480 to assign the port Port#2. This process repeats until all necessary ports are allocated.

Step S420 : Obtain the subkey (Subkey) added to the Windows login file corresponding to the newly inserted solid state hard disk. For example, the processing unit 312 can execute the Microsoft Application Programming Interface (API) function "CreateFile" to obtain the control code of the path "Enum\SCSI" in the window log file. Next, the processing unit 312 can execute the Microsoft API function "DeviceIOControl" to check whether there is a newly added subkey in the acquired control code. If there is a newly added subkey, it means that a newly added Small Computer System Interface (SCSI) device is detected, and the ClassGUID of the subkey is obtained. If there is no newly added subkey, the processing unit 312 can execute the Microsoft API function "CreateFile" to obtain the control code of the path "Enum\IDE" in the Windows log file. Next, the processing unit 312 can execute the Microsoft API function "DeviceIOControl" to check whether there is a newly added subkey in the acquired control code. If there is a newly added subkey, it means that a newly added integrated device circuit (Integrated Drive Electronics, IDE) device is detected, and the category-wide unique identification code of this subkey is obtained.

Step S430: Obtain the location information of the i-th port from the newly added subkey. For example, the processing unit 312 can execute the Microsoft API function "WINSETUPAPI SetupDiGetClassDevs" for obtaining the control code "HDEVINFO" pointing to a specific Device Information Set according to the class-wide unique identifier (obtained in step S420). The processing unit 312 can execute the Microsoft API function “WINSETUPAPI SetupDiEnumDeviceInterface” for enumerating the Device Interfaces included in the control code “HDEVINFO”, and the data of the device interface can be stored in a preset buffer in the RAM 314 . The processing unit 312 can execute the Microsoft API function "WINSETUPAPI SetupDiGetDeviceInterfaceDetail" to obtain detailed information of the device interface, including the device path (Device Path) and the location information (Location Information). The location information consists of three parts: Bus Number; Target ID; and Logical Unit Number (LUN). For example, the location information may be used to identify one of the ports 232-1 through 232-4 of the hub 230 in FIG. 2 . The processing unit 312 can interrupt the string between the second and the third pound sign (“#”, Hashtag) from the device path, and extract the last word in the string and the word before the symbol (“&”, Ampersand). element as the device path number. For example, the processing unit 312 may retrieve the device path sequence number "4&2e835db4&0" from the device path "\\?\scsi#disk&ven_wdc&prod_wd10spzx-08z10#4&2e835db4&0&000200#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}" of the SCSI device. For another example, the processing unit 312 may retrieve the device path number "5&39170d91&0" from the device path "\\?\ide#disksmi_disk________________________________q0921b__#5&39170d91&0&1.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}" of the IDE device.

Step S440: Acquire the PCI or IDE registration file of the i-th port according to the device path serial number of the i-th port. The processing unit 312 can determine whether the PCI or IDE log file is to be scanned according to the information in which path the newly added subkey is detected in step S420.

If the newly added subkey is in the path "Enum\SCSI", the processing unit 312 scans the PCI log file. For example, the processing unit 312 executes the Microsoft API function "CreateFile" to obtain the control code of the path "Enum\PCI" in the Windows log file. The processing unit 312 can execute the Microsoft API function "DeviceIOControl" to obtain all the subkeys in the control code. Next, for each subkey, referring to the technical content described in step S420, the processing unit 312 can execute the Microsoft API functions "WINSETUPAPI SetupDiGetClassDevs", "WINSETUPAPI SetupDiEnumDeviceInterface" and "WINSETUPAPI SetupDiGetDeviceInterfaceDetail" to obtain the registry value (Registry Value) "ParentIdPrifix" ”, and compare whether the registered value “ParentIdPrifix” matches the device path sequence number obtained in step S430. If it matches, it means that the subkey contains the PCI log file of the i-th port, and the processing unit S312 can execute the Microsoft API function "WINSETUPAPI SetupDiGetDeviceInterfaceDetail" to obtain the PCI log file. The processing unit 312 can interrupt the string between the second backslash (“\”, Backslash) to the last ampersand (“&”, Ampersand) from the PCI log file as the device path serial number of the PCI device. For example, the processing unit 312 may retrieve the device path sequence number "3&11583659&0" from the device path "PCI\VEN_8086&DEV_9D03&SUBSYS_225D17AA&REV_21\3&11583659&0&B8" of the PCI device.

If the newly added subkey is in the path "Enum\IDE", the processing unit 312 scans the PCIIDE log file. For example, the processing unit 312 executes the Microsoft API function "CreateFile" to obtain the control code of the path "Enum\PCIIDE" in the Windows log file. The processing unit 312 can execute the Microsoft API function "DeviceIOControl" to obtain all the subkeys in the control code. Next, for each subkey, referring to the technical content described in step S420, the processing unit 312 can execute the Microsoft API functions "WINSETUPAPI SetupDiGetClassDevs", "WINSETUPAPI SetupDiEnumDeviceInterface" and "WINSETUPAPI SetupDiGetDeviceInterfaceDetail" to obtain the login value "ParentIdPrifix", and compare Whether the registered value "ParentIdPrix" matches the device path sequence number obtained in step S430. If it matches, it means that the subkey contains the IDE log file of the i-th port, and the processing unit S312 can execute the Microsoft API function "WINSETUPAPI SetupDiGetDeviceInterfaceDetail" to obtain the IDE log file. The processing unit 312 can interrupt the character string between the second backslash (“\”, Backslash) to the last ampersand (“&”, Ampersand) from the IDE log file as the device path serial number of the IDE device. For example, the processing unit 312 may retrieve the device path number "4&1dd8ffee&0" from the device path "PCIIDE\IDEChannel\4&1dd8ffee&0&1" of the IDE device.

Step S450: Acquire a SATA or PCIe registration file according to the device path serial number of the PCI or IDE device. For example, the processing unit 312 can execute the Microsoft API function "CreateFile" to obtain the control code of the path "Enum\PCI" in the Windows log file. The processing unit 312 can execute the Microsoft API function "DeviceIOControl" to obtain all the subkeys in the control code. Next, for each subkey, referring to the technical content described in step S420, the processing unit 312 can execute the Microsoft API functions "WINSETUPAPI SetupDiGetClassDevs", "WINSETUPAPI SetupDiEnumDeviceInterface" and "WINSETUPAPI SetupDiGetDeviceInterfaceDetail" to obtain the login value "ParentIdPrifix", and compare Whether the registered value "ParentIdPrix" matches the device path sequence number obtained in step S440. If it matches, it means that the subkey contains the SATA log file of the i-th port, and the processing unit S312 can execute the Microsoft API function "WINSETUPAPI SetupDiGetDeviceInterfaceDetail" to obtain the SATA log file.

If the control code of the path "Enum\PCI" in the Windows log file cannot find a matching log file, the processing unit 312 executes the Microsoft API function "CreateFile" to obtain the control code of the path "Enum\ACPI" in the Windows log file. The processing unit 312 can execute the Microsoft API function "DeviceIOControl" to obtain all the subkeys in the control code. Next, for each subkey, referring to the technical content described in step S420, the processing unit 312 can execute the Microsoft API functions "WINSETUPAPI SetupDiGetClassDevs", "WINSETUPAPI SetupDiEnumDeviceInterface" and "WINSETUPAPI SetupDiGetDeviceInterfaceDetail" to obtain the login value "ParentIdPrifix", and compare Whether the registered value "ParentIdPrix" matches the device path sequence number obtained in step S440. If it matches, it means that this subkey contains the PCIe log file of the i-th port, and the processing unit S312 can execute the Microsoft API function "WINSETUPAPI SetupDiGetDeviceInterfaceDetail" to obtain the PCIe log file, "ACPI\PNP0A08\0". For example, a SATA or PCIe registry can be used to identify one of ports 214-1 through 214-4 of device interface 212 in FIG.

Step S460 : Store the port assignment information of the i-th port to the port mapping configuration table 160 in the RAM 314 and/or the storage unit 316 . The port setting information includes the location information obtained in step S430 and the SATA or PCIe log file obtained in step S450. Table 1 shows some examples of the port mapping configuration table 160: Table 1 port bus number target identifier logical unit number SATA/PCIe log file Port#1 0 2 0 ACPI\PNP0A08\0 Port#2 0 4 1 ACPI\PNP0A08\0 Port#3 0 6 2 ACPI\PNP0A08\0 Port#4 0 8 3 ACPI\PNP0A08\0 For example, the 1st to 4th records of the port mapping configuration table 160 respectively store the location information and the PCIe registration file of the ports Port#1 to Port#4.

Step S470: It is determined whether the fixed port operation is completed. If so, the process ends, and the port mapping configuration table 160 is completed. Otherwise, the flow proceeds to the process of step S480.

Step S480: Calculate i=i+1.

When the process ends, the port mapping configuration table 160 in the RAM 314 of the port host 210 or the storage unit 316 can be output to the production computer 180 for reference by the card opening program.

It should be noted here that, since the operator inserts the training SSDs into all the ports of the hub one by one in the preset sequence, the sequence of the location information in the port mapping configuration table 160 is consistent with the preset physical configuration of the ports of the hub. arrange.

Refer to Figure 5. The production system 50 includes a production host (Production Host) 510 , a hub 530 , solid state drives 550 - 1 to 550 - 4 and a display 570 . For each solid state drive 550 , after the flash memory controller and the flash memory module are installed on the motherboard, a card-activation process needs to be completed before they can be shipped from the factory and provided to customers. The display 570 can be a thin film transistor liquid crystal display, an organic light emitting diode display, etc., and displays a screen that can be viewed by engineers or operators during the card opening process, including prompt text, numbers, symbols, patterns, etc., or any combination of the above .

Under normal circumstances, the device interface 512 in the production host 510 and the hub 530 have the same or match the device interface 212 of the port host 210 and the hardware and software settings of the hub 230 . In order to make the description concise, when the following paragraphs use the solid-state hard disk 550 to describe, the structures, functions, method steps or other technical contents described can be applied to any of the solid-state hard disks 550-1 to 550-4 and others.

Refer to Figure 6. Since the hub 530 is connected to a port on the device interface 512 and the solid state drive 550 is plugged into the hub 530, it is equivalent to the solid state drive 550 being physically connected to the production host 510, so the hub 530 shown in FIG. 1 is omitted in FIG. 6 . The production host 510 includes a processing unit 612, which may be implemented in a variety of ways, such as using general-purpose hardware (eg, a single processor, a multiprocessor capable of parallel processing, a graphics processor, or other processor capable of computing), and When executing software and/or firmware instructions, for example, Mass Production (MP Tool), Operating System (OS), Driver (Driver), etc., provide specified functions. The processing unit 612 can issue an instruction to the device interface 512 for transmitting a vendor command (Vendor Command) to the solid-state hard disk 550 to complete the operations required in the card opening process. Vendor commands are not standard host operating commands, e.g. Universal Flash Storage (UFS), Non-Volatile Memory Express (NVMe), Open-channel Solid State Drives (Open-channel) The management commands, input and output commands, etc. defined by Solid State Disk (SSD), etc., are custom commands (Proprietary Commands) provided to the customer by the manufacturer of the solid state hard disk 550 or the flash memory controller 630 .

The production host 510 includes a storage unit 616 , which may be a hard disk (Hard Disk) or a solid-state hard disk, for storing the port mapping configuration table 160 . The production host 510 further includes a RAM 614 for performing temporary storage of data required in the card opening process, such as variables, flags, the port mapping configuration table 160 and the like.

The solid state drive 550 includes a flash memory controller 630 and a flash memory module 650 . The flash memory module 650 provides a large amount of storage space, usually hundreds of gigabytes (Gigabytes) or even several terabytes (Terabytes), for storing large amounts of user data, such as high-resolution pictures, videos, etc. The flash memory module 650 includes a control circuit and a memory array, and the memory cells in the memory array may include single-level cells (Single Level Cells, SLCs), multi-level cells (Multiple Level Cells, MLCs), triple-level cells (Triple Level Cells, MLCs) Level Cells, TLCs), Quad-Level Cells (Quad-Level Cells, QLCs), or any combination of the above.

The flash memory controller 630 includes a host interface 632, a flash memory interface 634, a volatile random access memory (VRAM) 636, a processing unit 637, a read-only memory (ROM) 638, and input and output Interface 639. The host interface 632 is coupled to the device interface 512 of the production host 510 . The flash interface (Flash Interface) 634 is coupled to the flash memory module 650, and can communicate with each other through a Double Data Rate (DDR) protocol, such as Open NAND Flash Interface (ONFI), Double Data Rate (DDR) rate switch (DDR Toggle) or other interface protocol. The processing unit 637 may be implemented in general purpose hardware as described above. The VRAM 636 stores temporary data, such as variables, flags, data tables, etc., required for performing the card opening process.

Refer to Figure 7. An embodiment of the present invention provides a card opening method, which is implemented when the processing unit 612 loads and executes the program code of the mass production tool. The method includes the following steps: loading the port mapping configuration table 160 previously generated by the port-fixing host 210, including the location information of each port in the hub 530; comparing the location information in the hardware description file with the port mapping configuration table 160 to determine whether each port in the hub 530 is connected to a solid-state hard disk; display a GUI on the display 570 to indicate whether each port in the hub 530 is connected to a solid-state hard disk; and when one of the ports is connected When the connected SSD fails to open the card, update the GUI to indicate the information that the SSD connected to the corresponding port fails to open the card. The hardware description file is provided by the operating system run by the production host 510 . Details are as follows:

Step S710: Load the port mapping configuration table 160 from the storage unit 616, and store it in the RAM 614 for quick search. The port mapping configuration table 160 may refer to an example of Table 1 or Table 2 (described in the following paragraphs).

Step S720 : Determine whether all the SATA/PCIe registration files in the port mapping configuration table 160 exist in the Windows registration file of the operating system of the production host 510 . If so, the flow continues with the processing of step S730. Otherwise, it means that the software and hardware settings of the training host 210 used to generate the port mapping configuration table 160 and the production host 510 are not the same or do not match, and the process ends.

Specifically, for each SATA log file in the port mapping configuration table 160, the processing unit 612 can execute the Microsoft API function "CreateFile" to obtain the control code of the path "Enum\PCI" in the window log file. The processing unit 612 can execute the Microsoft API function "DeviceIOControl" to obtain all the subkeys in the control code. Next, for each subkey, referring to the technical content described in step S420, the processing unit 612 can execute the Microsoft API functions "WINSETUPAPI SetupDiGetClassDevs", "WINSETUPAPI SetupDiEnumDeviceInterface" and "WINSETUPAPI SetupDiGetDeviceInterfaceDetail" to check whether the same SATA log file exists. When any SATA registration file in the port mapping configuration table 160 cannot be found in all subkeys in the control code, it represents the software and hardware settings of the training host 210 used to generate the port mapping configuration table 160 is not the same or does not match the production host 510.

In addition, for each PCIe registration file in the port mapping configuration table 160, the processing unit 612 can execute the Microsoft API function "CreateFile" to obtain the control code of the path "Enum\ACPI" in the Windows registration file. The processing unit 612 can execute the Microsoft API function "DeviceIOControl" to obtain all the subkeys in the control code. Next, for each subkey, referring to the technical content described in step S420, the processing unit 612 can execute the Microsoft API functions "WINSETUPAPI SetupDiGetClassDevs", "WINSETUPAPI SetupDiEnumDeviceInterface" and "WINSETUPAPI SetupDiGetDeviceInterfaceDetail" to check whether the same PCIe log file exists. When any PCIe registration file in the port mapping configuration table 160 cannot be found in all subkeys in the control code, it represents the software and hardware settings of the training host 210 used to generate the port mapping configuration table 160 is not the same or does not match the production host 510.

Step S730: Scan the solid state hard disk connected to the production host. For example, referring to the technical content of steps S420 and S430, the processing unit 612 can execute the Microsoft API functions "CreateFile", "DeviceIOControl", "WINSETUPAPI SetupDiGetClassDevs", "WINSETUPAPI SetupDiEnumDeviceInterface" and "WINSETUPAPI SetupDiGetDeviceInterfaceDetail" to obtain all connected production hosts 510's SCSI device and IDE device location information. Next, the processing unit 612 compares the location information of all the connected SCSI devices and IDE devices with all the location information in the port mapping configuration table 160, determines which ports on the production host 510 have been connected to the solid-state hard disk 550, and displays them on the display. The 570's Graphical User Interface (GUI) displays the detected connection results. For example, the GUI can display whether a solid-state drive is connected to each port, the location information of each port, and the card-on status of the solid-state drive connected to each port.

In some embodiments, the processing unit 612 may display on the GUI the contents of the location information of the port on the hub to which the solid state drive 550 is connected, eg, the bus number, the target identifier, the logical unit number, or any combination of the above .

In other embodiments, the processing unit 612 may further calculate the port number according to the bus number and the target identification code of the specific port, and use the port number to represent the location information of the specific port. An example formula is as follows: PN =BusN*MAX_PCI_TARGET_NUM+TargetID where PN represents the port number of a specific port, BusN represents the bus number of a specific port, TargetID represents the target ID of a specific port, MAX_PCI_TARGET is a constant, set to an integer greater than 0, for example, 48. Table 2 shows the calculation results of the location information according to the port mapping configuration table 160 of Table 1: Table 2 port port number SATA/PCIe log file Port#1 2 ACPI\PNP0A08\0 Port#2 4 ACPI\PNP0A08\0 Port#3 6 ACPI\PNP0A08\0 Port#4 8 ACPI\PNP0A08\0

Assuming that the solid state drives 550-1 to 550-4 are connected to the ports 532-1 to 532-4 of the hub 530, respectively: Referring to FIG. 8, the message boxes 810#1 to 810#4 in the GUI 800 respectively display the port P# 1 to the port number of port P#4 (as shown in Table 2) and the card open status. Blocks 810#5 to 810#16 of the GUI 800 are backslashed to indicate that ports P#5 to P#16 are not connected to any solid state drives.

It should be noted here that, if only the window registration file is searched without providing the port mapping configuration table 160 according to the embodiment of the present invention, only the position information of the ports on the hub connected to all solid-state drives can be obtained. In other words, the production host does not know the total number of ports contained in the hub, and there is no order relation between the location information searched from the Windows registry. Therefore, even if all the location information is available, there is no way to correlate the location information with the physical arrangement of ports on the hub.

Step S740: Set the variable i=1. The variable i is used to record the sequence number of card opening.

Step S750: Open a card for the solid state hard disk connected to the i-th port.

For example, in the card opening process, the processing unit 637 may load and execute the program code for processing the supplier command issued from the production host 110 from the read-only memory (Read-Only Memory, ROM) 638 (which may called vendor command processing code). In order to respond to the initialization device command sent from the production host 510, when the processing unit 637 executes the vendor command processing code, a series of tests can be performed on the flash memory module 650 through the flash memory interface 634 to find out bad blocks (Bad Blocks), bad lines (Bad Columns), etc., and generate bad block tables, bad row tables, etc. accordingly. The vendor command processing code can calculate the length of each physical page that can be used to store the Error Check and Correction (ECC Code) according to parameters such as the number of detected bad rows. The vendor command processing code can calculate the starting position of each sector (Sector) in each physical page according to the bad row table and ECC length and other information, and generate the sector starting table accordingly. The vendor command processing code can calculate the logical address block (LBA quantity) that the flash memory module 250 can store according to information such as the number of bad blocks, the number of bad rows, and the ECC length. The supplier command processing code can store the above-mentioned data table, variables and other information in the VRAM 636, and reply the initialization completion message to the production host 510 through the driver host interface 632 for notifying the mass production tool. The mass production tool may display a message that the initialization is complete on the display 570 for prompting the operator or engineer.

After the mass production tool receives the initialization completion message from the solid-state drive 650 , which may include information such as the number of LBAs that the flash memory module 650 can store, it sends a DOWNLOAD INFO supplier command to the flash memory device 650 to instruct the flash memory device 650 . The solid state drive 650 stores the initialization result in a non-volatile storage space, such as the flash memory module 650 . In response to the download information command, when the processing unit 637 executes the vendor command processing code, the data tables, variables and other information stored in the VRAM 636 can be written into the System Block of the flash memory module 650 through the flash memory interface 634 . Those skilled in the art understand that the information such as the data table and variables generated above are reference information required for future execution of the In-System Programming (ISP Code, also known as firmware). In-system code contains operations for executing host commands issued from the host, such as host read, write, erase commands, etc. Host commands are commands regulated by standard-setting organizations, such as UFS, NVMe, Open-channel SSD commands, etc. The supplier command processing code can reply to the production host 510 through the driver host interface 632 that the download information is completed, so as to notify the mass production tool. The mass production tool may display a message that the card opening is completed on the display 570 for prompting the operator or engineer. For example, the status of one of the message boxes 810#1 to 810#4 shown in FIG. 8 is changed to "completed".

However, the solid-state drive 550 may fail in one of the above card-opening processes, and the processing unit 637 can reply an appropriate error code or error message to the production host 510 through the driving host interface 632 for mass production The tool may display an error code or error message on display 570 for prompting an operator or engineer. Then, a production tool, operator, or engineer can troubleshoot the solid state drive connected to the i-th port.

Step S760: Determine whether the card is successfully opened according to the reply message of the solid state hard disk 550 connected to the i-th port. If so, the flow continues to the process of step S780. Otherwise, the flow proceeds to the process of step S770.

Step S770: Display the message that the solid state drive of the i-th port fails to open the card on the GUI. Suppose the solid state drive 550-3 fails during the card opening process: referring to FIG. 9, the message box 810#3 in the GUI 800 displays the card opening status of the port P#3 as "failed".

Step S780: Determine whether the card opening of all solid-state hard disks is completed. If so, the process ends. Otherwise, the flow proceeds to the process of step S790.

Step S790: Calculate i=i+1.

By comparing the port mapping configuration table 160 as described above with the hardware description file provided by the operating system running in the production host 510, it can be identified whether each port on each hub in the production system 50 is connected to a solid state drive. Moreover, when a solid-state hard drive fails to open the card, it can automatically identify which port is connected to the solid-state hard drive that has an error during the card-opening process.

All or part of the steps in the method of the present invention may be implemented by computer instructions, such as a specific hardware driver, firmware or software program. In addition, it can also be implemented in other types of programs. Those skilled in the art can compose the methods of the embodiments of the present invention into computer instructions, which will not be described for brevity. Computer instructions for implementing methods according to embodiments of the present invention may be stored in a suitable computer-readable medium, such as DVD, CD-ROM, USB disk, hard disk, or may be other suitable vehicles) to access the web server.

Although the above-described elements are included in FIGS. 2 , 3 , 5 and 6 , it is not excluded that more other additional elements can be used to achieve better technical effects without departing from the spirit of the invention. In addition, although the flowcharts of FIG. 4 and FIG. 7 are executed in the specified order, those skilled in the art can modify the order of these steps under the premise of achieving the same effect without violating the spirit of the invention. Therefore, The present invention is not limited to using only the sequence described above. In addition, those skilled in the art can also integrate several steps into one step, or in addition to these steps, perform more steps sequentially or in parallel, and the present invention is not limited thereby.

Although the present invention is described using the above embodiments, it should be noted that these descriptions are not intended to limit the present invention. On the contrary, this invention covers modifications and similar arrangements obvious to those skilled in the art. Therefore, the scope of the appended claims is to be construed in the broadest manner so as to encompass all obvious modifications and similar arrangements.

110: Porting stage 130: Card opening stage 140: Train the computer 160: Port mapping configuration table 180: Production Computers 20: Training the system 210: fixed port host 212: Device Interface 214-1~214-4, 232-1~232-4: port 230: Hub 250, 250-1~250-4: Training SSD 270: Monitor 312: Processing unit 314: Random Access Memory 316: Storage Unit 330: Flash Controller 332: Host Interface 350: Flash Module S410~S480: Method steps 50: Production System 510: Production host 512: Device Interface 514-1~514-4, 532-1~532-4: port 530: Hub 550, 550-1~550-4: Solid State Disk 570: Display 612,637: Processing unit 614: Random Access Memory 616: Storage Unit 632: host interface 634: Flash interface 636: Volatile random access memory 638: read-only memory 650: Flash Module S710~S790: method steps 800: Graphical User Interface 810#1~810#16: message box

FIG. 1 is a schematic diagram of a production stage according to an embodiment of the present invention.

FIG. 2 is a schematic diagram of a training system according to an embodiment of the present invention.

3 is a block diagram of a ported host and a training solid state drive according to an embodiment of the present invention.

FIG. 4 is a flowchart of a method for port determination according to an embodiment of the present invention.

5 is a schematic diagram of a production system according to an embodiment of the present invention.

FIG. 6 is a block diagram of a production host and a solid state hard disk according to an embodiment of the present invention.

FIG. 7 is a flowchart of a card opening method according to an embodiment of the present invention.

8 and 9 are schematic diagrams of graphical user interfaces according to embodiments of the present invention.

S710~S790: method steps

Claims (13)

A method for producing a solid state hard disk is performed by a processing unit of a production host, wherein the production host includes a device interface, the device interface includes a plurality of first ports, each of the first ports is connected to a hub, and each The above-mentioned hub includes a plurality of second ports, and the above-mentioned method includes: Loading a port mapping configuration table containing location information representing each of the second ports described above; Comparing location information in a hardware description file with location information in the port mapping configuration table to determine whether each of the second ports is connected to a solid state drive, wherein the hardware description file is an operation run by the production host provided by the system; displaying on a display a graphical user interface for indicating whether each of the second ports is connected to a solid state drive; and When the SSD connected to one of the second ports fails to open the card, the GUI is updated to indicate the information that the SSD connected to the corresponding second port fails to open the card. The method for producing a solid-state hard disk as claimed in claim 1, wherein the sequence of the location information in the port mapping configuration table is consistent with the default physical arrangement of the second port of the hub. The method for producing a solid-state hard disk according to claim 1, wherein the operating system is a Windows operating system, and the hardware description file is a Windows login file. The method for producing a solid-state hard disk according to claim 3, wherein the port mapping configuration table includes a plurality of registration files associated with the first port, and the method includes: Determine whether all the login files in the above-mentioned port mapping configuration table exist in the above-mentioned window login file; When all the registration files in the port mapping configuration table exist in the window registration file, compare the location information in the hardware description file with the location information in the port mapping configuration table to determine each of the second ports whether a solid state drive is connected; and When any one of the above-mentioned registration files in the above-mentioned port mapping configuration table does not exist in the above-mentioned window registration file, the card opening operation of the solid-state hard disk is ended. The method for producing a solid-state hard disk according to claim 1, wherein the graphical user interface displays the content of the location information of the second port to which the solid-state hard disk is connected. The method for producing a solid-state hard disk according to claim 1, wherein the graphical user interface displays the port number of the second port to which the solid-state hard disk is connected, and the port number is calculated using the following formula: PN=BusN*MAX_PCI_TARGET_NUM+TargetID PN represents the port number of a specific second port, BusN represents the bus number of the specific second port, TargetID represents the target identification code of the specific second port, and MAX_PCI_TARGET is a constant, set to an integer greater than 0. A computer program product, comprising program code for producing a solid-state hard disk, wherein, when a processing unit of a production host executes the above-mentioned program code, the production of the solid-state hard disk according to any one of claims 1 to 6 is implemented Methods. An apparatus for producing solid state hard disks, comprising: a device interface including a plurality of first ports, wherein each of the first ports is connected to a hub, and each of the hubs includes a plurality of second ports; and a processing unit, coupled to the above-mentioned device interface, for loading a port mapping configuration table from a storage unit, including location information representing each of the above-mentioned second ports; comparing the location information in a hardware description file with the above-mentioned The location information in the port mapping configuration table is used to determine whether each of the second ports is connected to a solid-state hard disk, wherein the hardware description file is provided by an operating system running on the device; a graphical user interface is displayed on a display, using information indicating whether each of the second ports is connected to a solid-state hard disk; and when one of the second ports is connected to a solid-state disk that fails to open the card, update the graphical user interface to indicate the corresponding second port The connected solid-state drive has failed to open the card. The device for producing a solid-state hard disk as claimed in claim 8, wherein the sequence of the location information in the port mapping configuration table conforms to the default physical arrangement of the second port of the hub. The device for producing a solid-state hard disk according to claim 8, wherein the operating system is a Windows operating system, and the hardware description file is a Windows login file. The device for producing a solid-state hard disk according to claim 10, wherein the port mapping configuration table includes a plurality of registration files associated with the first port, and the processing unit is configured to determine the port mapping configuration table. Whether all log files exist in the above window log file; when all log files in the above port mapping configuration table exist in the above window log file, compare the location information in the above hardware description file with the above port mapping configuration table determine whether each of the second ports is connected to a solid-state hard disk; and when any one of the above-mentioned registration files in the above-mentioned port mapping configuration table does not exist in the above-mentioned window registration file, end the card-opening operation of the solid-state hard disk. The device for producing a solid-state hard disk according to claim 8, wherein the graphical user interface displays the content of the location information of the second port to which the solid-state hard disk is connected. The device for producing a solid-state hard disk according to claim 8, wherein the graphical user interface displays the port number of the second port to which the solid-state hard disk is connected, and the port number is calculated using the following formula: PN=BusN*MAX_PCI_TARGET_NUM+TargetID PN represents the port number of a specific second port, BusN represents the bus number of the specific second port, TargetID represents the target identification code of the specific second port, and MAX_PCI_TARGET is a constant, set to an integer greater than 0.

Images