TWI745997B - 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 device for producing solid hard disk and computer program product

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

The solid state drive usually needs to complete the card opening procedure before it can be sold out of the factory, and the time consumed by the card opening procedure is an important issue in the production of the solid state hard drive. A production host can usually connect 5 to 16 solid state drives through the port of the device interface, and open the card of the connected solid state drive. However, traditionally, when one of the solid state drives fails to open the card, the production host cannot automatically know which one actually has an error, and the production personnel need to manually unplug the connected solid state drive to confirm and extend it. Time for production.

Therefore, the present invention provides a method, device, and computer program product for producing a solid state hard disk to solve the above-mentioned problems.

In view of this, how to reduce or eliminate the deficiencies in the above-mentioned related fields is indeed 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 the processing unit of the 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 multiple second ports. The above method includes: loading the port mapping configuration table, which contains the location information representing each second port; comparing the location information in the hardware description file with the location information in the port mapping configuration table to determine each second port Whether to connect a solid state drive; display the graphical user interface on the monitor, use In the information indicating whether each second port is connected to the solid state drive; and when the solid state drive connected to one of the second ports fails to open the card, the graphical user interface is updated to indicate the solid state drive connected to the corresponding second port Information about the card opening failure of the hard disk.

This manual also relates to a computer program product, which contains the program code used to produce solid state drives. When the processing unit of the production host executes the program code, the method for producing the solid state drive as described above is implemented.

This specification also relates to a device for producing solid-state hard disks, including: the above-mentioned device interface and a processing unit. The processing unit is coupled to the device interface, and is used to load and execute the above-mentioned program 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 drive.

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, it can automatically identify which port is connected to the solid state drive in the process of opening the card. An error occurred in.

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

110: fixed port stage

130: card opening stage

140: training computer

160: Port mapping configuration table

180: production computer

20: Training 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 solid state drive

270: display

312: Processing Unit

314: Random Access Memory

316: storage unit

330: Flash Controller

332: Host Interface

350: Flash memory 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 drive

570: display

612,637: processing unit

614: Random Access Memory

616: storage unit

632: Host Interface

634: flash memory interface

636: Volatile Random Access Memory

638: Read Only Memory

650: Flash memory 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.

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

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

Fig. 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 drive 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.

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

The following descriptions are preferred implementations for completing the invention, and their purpose is to describe the basic spirit of the invention, but not to limit the invention. The actual content of the invention must refer to the following Scope of claims.

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

Words such as "first", "second", and "third" used in the claims are used to modify the elements in the claims, and are not used to indicate that there is a precedence, prerequisite relationship, or an element. Prior to another element, or the chronological order of execution of method steps, 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 other elements, and intervening elements may appear. Conversely, when an element is described as being "directly connected" or "directly coupled" to another element, there are no intervening elements. Other terms used to describe the relationship between elements can also be interpreted in a similar manner, such as "between" versus "directly between", or "adjacent" versus "directly adjacent" and so on.

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: Port Distinguishing stage and Card opening stage. Activation) stage. Referring to FIG. 1, in the port determination 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 serial advanced Technology Attachment/Fast Peripheral Component Interconnect Express (Serial Advanced Technology Attachment, SATA/Peripheral Component Interconnect Express, PCIe Registries), Bus Number, Target ID, Logical Unit Number, LUN) and so on, based on which a Port-mapping Configuration Table 160 is generated. In the card opening stage 130, the production computer 180 loads the port mapping configuration table 160, and the production computer 180 is connected for multiple connections Perform the card opening procedure for the solid state drive. During the card opening process, if the production computer 180 finds any error messages, the port mapping configuration table 160 can be used to identify which physical port is connected to the solid state drive that has an error, and display it on the Graphical User Interface (Graphical User Interface). , GUI), which is beneficial to the operator and/or the production computer 180 to perform error elimination 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 drive 250, and a display 270. The training computer 140 described in FIG. 1 may include a fixed-port host 210, a hub 230 and a display 270. The training solid state drive 250 may include a flash memory controller and a plurality of flash memory modules. The display 270 can be a Thin Film Transistor-Liquid Crystal Display (TFT-LCD Display), an Organic Light-Emitting Diode (OLED Display), etc., which can be displayed during the training process for engineers or The screen that the operator can watch, including prompt text, numbers, symbols, patterns, etc., or any combination of the above.

The fixed port host 210 can be implemented by a personal computer, a laptop PC, an industrial computer, a workstation, or the like. The fixed-port host 210 includes a device interface 212 with a plurality of ports 214-1 to 214-4, and 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 can equip the device interface 212 with more or fewer ports, so that the fixed-port host 210 can connect to more or fewer hubs. The present invention should not be limited by this. The hub 230 includes a plurality of ports 232-1 to 232-4, and each port can be plugged into 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 instructions concise, when the following paragraphs use the training solid state drive 250 to describe, it means that the structure, function, method steps or other technical content of the description can be applied to the training solid state drive 250-1 to 250-4 And others Any one of them. Although the hub 230 described in FIG. 1 has 4 ports, those skilled in the art can connect a hub with more or fewer ports to the fixed-port host 210, so that the fixed-port host 210 can be connected to more or less training. For solid state drives, 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 training the solid state drive 250 physically connected to the fixed port host 210, so the figure 2 shown in Figure 3 is omitted The hub 230. The fixed-port host 210 includes a processing unit 312, which can be implemented in a variety of ways, such as using general-purpose hardware (for example, a single processor, multiple processors with parallel processing capabilities, graphics processors, or other processors with computing capabilities), and When executing software and/or firmware commands, for example, Port-distinguishing Tool (Port-distinguishing Tool), Operating System (OS), Driver, etc., provide specified functions. The processing unit 312 can send 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 memory controller 330 and a flash memory module 350. The flash memory module 350 provides a large amount of storage space, usually hundreds of gigabytes (Gigabytes), or even several terabytes (Terabytes), used to store a large amount of user data, such as high resolution Pictures, videos, etc. The flash memory controller 130 includes a host interface 332, and the host interface 332 is coupled to the device interface 212 of the fixed-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 input/output device is connected to the fixed port host 210 through one of the ports 214-1 to 214-4 and the ports 232-1 to 232-4 when the software program is executed. For example, the Windows Registry is a hierarchical database that stores low-level settings and is used for Windows operating systems (Windows OS) and applications. In detail, the Windows registry file includes the hardware of the fixed-port host 210 (such as SATA/PCIe interface, etc.) and the device connected to the fixed-port host 210 (such as a solid state drive) Information, settings, options, and other values for. When a solid state drive is connected to the fixed-port host 210 through a port of the hub 230, a new subkey (Subkey) will be added to the window registry file. The subkey contains multiple values (Values) for storage such as hardware Setting values for identification code, location information, manufacturer, service, etc.

The embodiment of the present invention provides a port determination method, which is implemented when the processing unit 312 loads and executes the program code of the port determination tool. Refer to Figure 4. Taking the Windows operating system as an example, the detailed description is as follows: Step S410: Set the variable i=1. The variable i is used to record the serial number of the fixed port.

Then, the process repeatedly executes a loop, including steps S420 to S480. Before each round is executed, the operator inserts 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 sequentially labeled Port#1, Port#2, Port#3, and Port#4. 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 set the port Port#1. Then, 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 set the port Port#2. This process will be repeated until the necessary ports have been fixed.

Step S420: Obtain the subkey corresponding to the newly inserted solid-state drive added to the window registration file. 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 Windows registry 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 class GUID of this 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 login file. Next, the processing unit 312 can execute the Microsoft API function "DeviceIOControl" to check whether the acquired control code is Are there any newly added subkeys? If there is a newly added subkey, it means that a newly added Integrated Drive Electronics (IDE) device is detected, and then the category global 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", which is used to obtain the control code "HDEVINFO-" pointing to a specific Device Information Set according to the category global unique identification code (obtained in step S420). The processing unit 312 can execute the Microsoft API function "WINSETUPAPI SetupDiEnumDeviceInterface" for listing the device interfaces (Device Interfaces) contained in the control code "HDEVINFO". The data of the device interfaces can be stored in the preset buffer in the RAM 314. The processing unit 312 can execute the Microsoft API function "WINSETUPAPI SetupDiGetDeviceInterfaceDetail" for obtaining detailed data of the device interface, including the device path (Device Path) and location information (Location Information). The location information includes three parts: Bus Number; Target ID; and Logical Unit Number (LUN). For example, the location information can be used to identify one of the ports 232-1 to 232-4 of the hub 230 in FIG. 2. The processing unit 312 can interrupt the string between the second to the third hashtag ("#", Hashtag) from the device path, and extract the last word before the ampersand ("&", Ampersand) in the string Yuan as the device path number. For example, the processing unit 312 can retrieve the device path serial 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 can retrieve the device path serial number "5" from the IDE device's device path "\\?\ide#disksmi_disk____q0921b_#5&39170d91&0&1.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}".

Step S440: Obtain 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 registry file to be scanned is based on 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 registration 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 registry file. The processing unit 312 can execute the Microsoft API function "DeviceIOControl" to obtain all the subkeys in the control code. Then, 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 "ParentIdPrifix" ", and compare whether the registered value "ParentIdPrifix" matches the device path serial number obtained in step S430. If it matches, it means that this subkey contains the PCI registration file of the i-th port, and the processing unit 312 can execute the Microsoft API function "WINSETUPAPI SetupDiGetDeviceInterfaceDetail" to obtain the PCI registration file. The processing unit 312 can interrupt the string from the second backslash ("\", Backslash) to the last ampersand ("&", Ampersand) from the PCI registration file as the device path serial number of the PCI device. For example, the processing unit 312 can retrieve the device path serial 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 registration 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 window registration file. The processing unit 312 can execute the Microsoft API function "DeviceIOControl" to obtain all the subkeys in the control code. Then, 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 “ParentIdPrifix”, and compare whether the registry value “ParentIdPrifix” matches the device path serial number obtained in step S430. If they match, it means that this subkey contains the IDE login of the i-th port. The processing unit S312 can execute the Microsoft API function "WINSETUPAPI SetupDiGetDeviceInterfaceDetail" to obtain the IDE login file. The processing unit 312 can interrupt the IDE login file from the second backslash ("\", Backslash) to the last and the symbol ("& ", Ampersand), as the device path serial number of the IDE device. For example, the processing unit 312 can retrieve the device path serial number "4&1dd8ffee&0" from the device path "PCIIDE\IDEChannel\4&1dd8ffee&0&1" of the IDE device.

Step S450: Obtain the 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 "ParentIdPrifix" matches the device path serial number obtained in step S440. If it matches, it means that this subkey contains the SATA registry file of the i-th port, and the processing unit S312 can execute the Microsoft API function "WINSETUPAPI SetupDiGetDeviceInterfaceDetail" to obtain the SATA registry file.

If the control code of the path “Enum\PCI” in the window registry file cannot find a matching registry file, the processing unit 312 executes the Microsoft API function “CreateFile” to obtain the control code of the path “Enum\ACPI” in the window registry file. The processing unit 312 can execute the Microsoft API function "DeviceIOControl" to obtain all the subkeys in the control code. Then, for each With reference 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 the login value "ParentIdPrifix" Whether it matches the device path serial number obtained in step S440. If it matches, it means that this subkey contains the PCIe registration file of the i-th port, and the processing unit S312 can execute the Microsoft API function "WINSETUPAPI SetupDiGetDeviceInterfaceDetail" to obtain the PCIe registration file, "ACPI\PNP0A08\0". For example, the SATA or PCIe registry file can be used to identify one of the ports 214-1 to 214-4 of the device interface 212 in FIG. 2.

Step S460: Store the fixed port information of the i-th port in the RAM 314 and/or the port mapping configuration table 160 in the storage unit 316. The port information includes the location information obtained in step S430 and the SATA or PCIe registration file obtained in step S450. Table 1 shows some examples of port mapping configuration table 160:

For example, the first to fourth records of the port mapping configuration table 160 respectively store the location information of the ports Port#1 to Port#4 and the PCIe registration file.

Step S470: Determine whether the port assignment is completed. If it is, the process ends, and the port mapping configuration table 160 is created. Otherwise, the flow continues with the processing of step S480.

Step S480: Calculate i=i+1.

When the process ends, the port mapping in RAM 314 or storage unit 316 of fixed port host 210 The configuration table 160 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 solid-state drive into all ports of the hub one by one in the preset order, the order of the position information in the port mapping configuration table 160 matches the default physical of the hub port. arrange.

Refer to Figure 5. The production system 50 includes a production host 510, a hub 530, solid state drives 550-1 to 550-4, and a display 570. For each solid-state hard disk 550, after the flash memory controller and flash memory module are installed on the motherboard, the card activation process (Card-activation Process) needs to be completed before it can be shipped and provided to customers. The display 570 can be a thin-film transistor liquid crystal display, an organic light-emitting diode display, etc. It displays images that can be viewed by engineers or operators during the card opening process, including prompt texts, 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 fixed-port host 210, and the hardware and software settings of the hub 230. In order to make the description concise, when the solid state drive 550 is used for description in the following paragraphs, it means that the structure, function, method steps or other technical content of the description can be applied to any of the solid state drives 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 that the solid state drive 550 is physically connected to the production host 510, so the hub 530 shown in FIG. 1 is omitted in FIG. The production host 510 includes a processing unit 612, which can be implemented in a variety of ways, such as using general-purpose hardware (for example, a single processor, multiple processors with parallel processing capabilities, graphics processors or other processors with computing capabilities), and When executing software and/or firmware commands, for example, mass production tools (Mass Production, MP Tool), operating systems (OS), drivers, etc., provide specified functions. The processing unit 612 can issue a command to the device interface 512 for sending a vendor command (Vendor Command) to the solid state drive 550 to complete the operations required in the card opening process. Vendor commands are not standard host operation commands, for example, Universal Flash memory storage (Universal Flash Storage, UFS), fast non-volatile memory (Non-Volatile Memory Express, NVMe), open-channel solid state disk (Open-channel Solid State Disk, SSD) and other defined management commands, input and output commands, etc., but by Proprietary Commands (Proprietary Commands) provided by the manufacturer of the solid state drive 550 or the flash memory controller 630 to the customer.

The production host 510 includes a storage unit 616, which can be a hard disk or a solid state disk, and is used to store the port mapping configuration table 160. The production host 510 further includes a RAM 614, which is used to execute temporary storage data required in the card opening process, such as variables, flags, port mapping configuration table 160, and so on.

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), used to store a large amount of user data, such as high resolution Pictures, videos, etc. The flash memory module 650 includes a control circuit and a memory array. The memory cells in the memory array can include single level cells (SLCs), multiple level cells (MLCs) and triple level cells (Triple). Level Cells, TLCs), 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 the Double Data Rate (DDR) communication protocol, for example, Open NAND Flash Interface (ONFI), double data Rate switch (DDR Toggle) or other interface communication protocol. The processing unit 637 may be implemented by general-purpose hardware as described above. The VRAM 636 stores the temporary data needed in the card opening process, such as variables, flags, and data tables.

Refer to Figure 7. The 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. This method includes the following steps: load the port mapping configuration table 160 previously generated by the ported host 210, which contains the location information of each port in the hub 530; compare 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 drive; display a GUI on the display 570 to indicate whether each port in the hub 530 is connected to a solid state drive; and when one of the ports is connected When the connected solid-state drive fails to open the card, the GUI is updated to indicate the information that the solid-state drive connected to the corresponding port has failed to open the card. The hardware description file is provided by the operating system run by the production host 510. The detailed description is 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 can refer to the example of Table 1 or Table 2 (which will be described in the following paragraphs).

Step S720: Determine whether all the SATA/PCIe registration files of the port mapping configuration table 160 exist in the window registration file of the operating system of the production host 510. If yes, 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.

In detail, for each SATA registry 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 registry. The processing unit 612 can execute the Microsoft API function "DeviceIOControl" to obtain all the subkeys in the control code. Then, 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 login file exists. When any SATA registry file in the port mapping configuration table 160 cannot be found in all the subkeys in this control code, it represents the software and hardware settings of the training host 210 used to generate the port mapping configuration table 160 It 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 window 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 login file exists. When any PCIe registration file in the port mapping configuration table 160 cannot be found in all the subkeys in this control code, it represents the hardware and software settings of the training host 210 used to generate the port mapping configuration table 160 It is not the same or does not match the production host 510.

Step S730: Scan the solid state drive connected to the production host. For example, referring to the technical content of steps S420 and S430, the processing unit 612 can execute Microsoft API functions "CreateFile", "DeviceIOControl", "WINSETUPAPI SetupDiGetClassDevs", "WINSETUPAPI SetupDiEnumDeviceInterface" and "WINSETUPAPI SetupDiGetDeviceInterfaceDetail" to obtain all connected production hosts Location information of 510 SCSI devices and IDE devices. Then, the processing unit 612 compares the location information of all connected SCSI devices and IDE devices with all the location information in the port mapping configuration table 160, and determines which ports on the production host 510 have been connected to the solid state drive 550, and 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 open card status of the solid state drive connected to each port.

In some embodiments, the processing unit 612 can display the location information of the port on the hub to which the solid state drive 550 is connected on the GUI, for example, the bus number, the target identification code, the logical unit number, or any combination of the above .

In other embodiments, the processing unit 612 may further calculate the port number (Port Number) based on the bus number and target ID of a specific port, and use the port number to represent the location information of the specific port. The 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 identification code of the specific port, MAX_PCI_TARGET is a constant, set to an integer greater than 0, for example, 48. Table 2 shows the calculation result of the location information according to the port mapping configuration table 160 of Table 1:

Assume that the solid state drives 550-1 to 550-4 are respectively connected to the ports 532-1 to 532-4 of the hub 530: referring to Figure 8, the message boxes 810#1 to 810#4 in the graphical user interface 800 respectively display port P# Port number from 1 to port P#4 (as shown in Table 2) and card opening status. The boxes 810#5 to 810#16 of the graphical user interface 800 use backslashes to indicate that the 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 as described in the embodiment of the present invention, only the location information of the ports on the hubs to which all solid state drives are connected can be obtained. In other words, the production host does not know the total number of ports included in the hub, and there is no order relationship that can be referenced among the location information searched from the window registry. Therefore, even if all the location information is obtained, it cannot be related to the physical arrangement of the 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 drive connected to the i-th port.

For example, in the card opening process, the processing unit 637 can load and execute the program code (which can also Called the supplier command processing code). In order to respond to the initialization device command sent from the production host 510, the processing unit 637 can perform a series of tests on the flash memory module 650 through the flash memory interface 634 when executing the supplier command processing code to find bad blocks and bad lines. (Bad Columns) and so on, and generate bad block tables, bad row tables and so on. The supplier command processing code can calculate the length of each physical page that can be used to store the Error Check and Correction (ECC Code) based on the number of detected bad rows and other parameters. The supplier command processing code can calculate the starting position of each sector in each physical page based on 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 650 can store based on information such as the number of bad blocks, the number of bad rows, and the length of the ECC. The supplier command processing code can store the above-mentioned data tables, 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 the initialization completion message on the display 570 to prompt the operator or engineer.

After the mass production tool receives the initialization completion message from the solid state drive 650, it can include information such as the number of LBAs that the flash memory module 650 can store, and sends a supplier command for downloading information (DOWNLOAD INFO) to the flash memory device 650 for instructions The solid state drive 650 stores the initialization result in a non-volatile storage space, such as the flash memory module 650. In order to respond to the download information command, the processing unit 637 can write the data table, variables and other information stored in the VRAM 636 into the system block of the flash memory module 650 through the flash memory interface 634 when executing the supplier command processing code. Those skilled in the art understand that the data tables, variables and other information generated above are reference information needed for future execution of the In-System Programming (ISP Code, also referred to as firmware). The code in the system contains the operations used to execute the host command sent from the host, for example Such as host read, write, erase commands, etc. The host command is a command regulated by a standard-setting organization, such as UFS, NVMe, and Open-channel SSD commands. The supplier's command processing code can reply to the production host 510 through the driver host interface 632 with the completion of the download information, for notifying the mass production tool. The mass production tool can display the card opening completion message on the display 570 for prompting the operator or engineer. For example, change the status of one of the message boxes 810#1 to 810#4 shown in FIG. 8 to "completed".

However, the solid state drive 550 may fail in a certain operation in the card opening process as described above, and the processing unit 637 can reply an appropriate error code or error message to the production host 510 through the drive host interface 632 for mass production. The tool can display an error code or error message on the display 570 for prompting the operator or engineer. Then, mass production tools, operators, or engineers can perform error troubleshooting operations on 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 drive 550 connected to the i-th port. If so, the flow continues with the processing of step S780. Otherwise, the flow continues with the processing of step S770.

Step S770: A message indicating that the card opening of the i-th port of the solid state drive failed to be opened is displayed on the GUI. Assume that the solid state drive 550-3 fails during the card opening process: referring to FIG. 9, the message box 810#3 in the graphical user interface 800 shows that the card opening status of the port P#3 is "failed".

Step S780: It is judged whether the card opening of all the solid state hard disks is completed. If it is, the process ends. Otherwise, the flow continues with the processing 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 is possible to identify whether each port on each hub in the production system 50 is connected to a solid state drive. Moreover, when a certain solid-state drive fails to open the card, it can automatically identify which port the solid-state drive is connected to in the process of opening the card.

All or part of the steps in the method of the present invention can be implemented by computer instructions, such as specific hardware drivers, firmware programs, or software programs. In addition, it can also be implemented in other types of programs. Those skilled in the art can write the method of the embodiment of the present invention as The computer instructions are not described for the sake of brevity. The computer instructions implemented according to the method of the embodiment of the present invention can be stored in a suitable computer readable medium, such as DVD, CD-ROM, USB disk, hard disk, and can also be placed on a network (such as the Internet, or Other appropriate vehicles).

Although FIG. 2, FIG. 3, FIG. 5, and FIG. 6 include the above-described elements, it does not rule out that, without violating the spirit of the invention, more other additional elements are used to achieve better technical effects. In addition, although the flowcharts in Figures 4 and 7 are executed in the specified order, those skilled in the art can modify the sequence of these steps on 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 that are obvious to those skilled in the art. Therefore, the scope of applied claims must be interpreted in the broadest way to include all obvious modifications and similar settings.

S710~S790: method steps

Claims (13)

A method for producing a solid state drive is executed 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 hub includes a plurality of second ports, and the method includes: loading a port mapping configuration table containing location information representing each of the second ports; comparing the location information in a hardware description file with the port mapping group The position information in the status table is used to determine whether each of the second ports is connected to a solid state drive, wherein the hardware description file is provided by an operating system running on the production host; a graphical user interface is displayed on a display to indicate Information about whether each of the second ports is connected to a solid state drive; and when the solid state drive connected to one of the second ports fails to open the card, update the graphical user interface to indicate that the corresponding second port is connected Information about the card opening failure of the solid state drive. The method for producing a solid state drive according to claim 1, wherein the sequence of the position information in the port mapping configuration table matches the default physical arrangement of the second port of the hub. The method for producing a solid state drive according to claim 1, wherein the operating system is a windows operating system, and the hardware description file is a windows registry file. The method for producing a solid state drive 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: determining all the registrations in the port mapping configuration table File exists in the above-mentioned window registry file; when all the registry files in the above-mentioned port mapping configuration table exist in the above-mentioned window registry file, compare Determine whether each of the second ports is connected to a solid-state drive based on the location information in the hardware description file and the location information in the port mapping configuration table; and when any one of the above-mentioned registration files in the port mapping configuration table If it does not exist in the above-mentioned window registration file, the solid-state drive card opening operation is ended. The method for producing a solid state drive 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 drive is connected. The method for producing a solid state drive according to claim 1, wherein the graphic user interface displays the port number of the second port to which the solid state drive 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 above specific second port, TargetID represents the target identification code of the above specific second port, and MAX_PCI_TARGET is a constant, set to an integer greater than 0. A computer program product, comprising a program code for the production of 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 claim items 1 to 6 is implemented Methods. A device for producing a solid state drive, 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 Connected to the above device interface, used to load a port mapping configuration table from a storage unit, including location information representing each of the above second ports; compare the location information in a hardware description file with the above port mapping configuration table To determine whether each of the above-mentioned second ports is connected to a solid-state drive, and the above-mentioned hardware description file is determined by the above-mentioned The operating system provided by the device is provided; a graphical user interface is displayed on a display to indicate whether each of the above-mentioned second ports is connected to the solid state drive; and when one of the above-mentioned second ports is connected to the solid state drive When the card opening fails, the above-mentioned graphical user interface is updated to indicate the information of the card opening failure of the solid-state hard disk connected to the corresponding second port. The device for producing a solid-state hard disk according to claim 8, wherein the sequence of the position information in the port mapping configuration table matches 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 registry file. The device for producing a solid state drive 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 used to determine the port mapping configuration table Whether all registry files exist in the above window registry file; when all registry files in the above port mapping configuration table exist in the above window registry file, compare the location information in the above hardware description file with the above port mapping configuration table To determine whether each of the second ports is connected to a solid state drive; 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 solid-state drive opening operation is terminated. 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 disk is connected. The device for producing a solid-state hard disk according to claim 8, wherein the above-mentioned graphical user interface displays the port number of the above-mentioned second port to which the solid-state disk is connected, and the above-mentioned port number uses the following Formula calculation: PN=BusN*MAX_PCI_TARGET_NUM+TargetID PN represents the port number of a specific second port, BusN represents the bus number of the above specific second port, TargetID represents the target identification code of the above specific second port, and MAX_PCI_TARGET is a constant, Set to an integer greater than 0.

Images