Method, device and equipment for programming solid state disk and medium

Abstract

The invention provides a method, a device, equipment and a medium for programming a solid state disk, which can be applied to the technical field of hard disk programming. The method for programming the solid state disk comprises the following steps: acquiring a bus number and a hard disk capacity of the solid state disk; according to the hard disk capacity, determining a target capacity parameter by using a capacity mapping relationship stored in the shared server, the capacity mapping relationship representing an association relationship between a plurality of predetermined hard disk capacities and a plurality of predetermined capacity parameters; according to the target capacity parameters, target capacity firmware is obtained from a predetermined capacity firmware integration package stored in the shared server, and the predetermined capacity firmware integration package comprises predetermined capacity firmware with multiple capacities; and based on the bus number, programming the target capacity firmware into the solid state disk to obtain a target solid state disk.

Description

Technical Field

[0001] The present application relates to the technical field of hard disk burning and programming, and more specifically to a method, device, equipment and medium for burning and programming a solid state hard disk. Background Art

[0002] Before using the SSD to store, read and write data in the server, you need to first burn the capacity firmware into the SSD. SSDs and capacity firmware usually correspond one to one. When using capacity firmware that does not match the SSD to burn it, the SSD will fail to burn or even be damaged. Summary of the invention

[0003] In view of the above problems, the present application provides a method, apparatus, device and medium for burning a solid state drive.

[0004] According to the first aspect of the present application, a method for burning a solid-state hard disk is provided, comprising: obtaining a bus number and a hard disk capacity of the solid-state hard disk; determining a target capacity parameter according to the hard disk capacity using a capacity mapping relationship stored in a shared server, wherein the capacity mapping relationship represents an association relationship between a plurality of predetermined hard disk capacities and a plurality of predetermined capacity parameters; obtaining a target capacity firmware from a predetermined capacity firmware integrated package stored in a shared server according to the target capacity parameter, wherein the predetermined capacity firmware integrated package includes predetermined capacity firmware having a plurality of capacities; and burning the target capacity firmware into the solid-state hard disk based on the bus number to obtain a target solid-state hard disk.

[0005] The second aspect of the present application provides a device for burning a solid-state hard disk, including: a first acquisition module, used to obtain the bus number and hard disk capacity of the solid-state hard disk; a determination module, used to determine the target capacity parameter according to the hard disk capacity using the capacity mapping relationship stored in a shared server, wherein the capacity mapping relationship represents the association between multiple predetermined hard disk capacities and multiple predetermined capacity parameters; a second acquisition module, used to obtain the target capacity firmware from the predetermined capacity firmware integrated package stored in the shared server according to the target capacity parameter, wherein the predetermined capacity firmware integrated package includes predetermined capacity firmware with multiple capacities; a burning module, used to burn the target capacity firmware into the solid-state hard disk based on the bus number to obtain the target solid-state hard disk.

[0006] The third aspect of the present application provides an electronic device, comprising: one or more processors; a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the steps of the above method.

[0007] The fourth aspect of the present application also provides a computer-readable storage medium on which a computer program or instruction is stored. When the computer program or instruction is executed by a processor, the steps of the above method are implemented.

[0008] The fifth aspect of the present application also provides a computer program product, including a computer program or instructions, which implement the steps of the above method when the above computer program or instructions are executed by a processor.

[0009] According to the embodiment of the present application, the bus number and hard disk capacity of the solid-state hard disk are first obtained, so that the hard disk capacity can be used as the basic reference for selecting the matching target capacity firmware. The bus number is convenient for accurately locating the solid-state hard disk to be burned even in batches, thereby improving the burning efficiency and burning quality of the solid-state hard disk when burning alone or in batches. Then, using the capacity mapping relationship pre-constructed based on the association between the predetermined hard disk capacity and the predetermined capacity parameter and stored in the shared server, the target capacity parameter corresponding only to the hard disk capacity is determined from the mapping relationship bridge according to the hard disk capacity, and the target capacity parameter is used as a parameter instruction or parameter identifier to extract the target capacity firmware.

[0010] According to the embodiments of the present application, according to the target capacity parameters, the target capacity firmware is obtained from a unified predetermined capacity firmware integrated package stored in a shared server and containing predetermined capacity firmware of multiple capacities, so that in the process of obtaining the target capacity firmware, it is possible to search and obtain the target capacity firmware that matches the solid-state drive without traversing all firmware files in the shared server, thereby improving the efficiency of obtaining the target capacity firmware, avoiding omissions and occupying large resources when traversing multiple firmware files during the acquisition process, improving the accuracy and stability of obtaining the target capacity firmware, and reducing the resource cost during the burning process. Finally, based on the pre-acquired bus number, the solid-state drive to be burned is located, and the target capacity firmware that matches the solid-state drive is burned into the solid-state drive, so as to obtain a target solid-state drive with a high success rate and effectiveness of burning, thereby improving the burning efficiency and burning quality of the solid-state drive during burning. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The above contents and other objects, features and advantages of the present application will become more clear through the following description of the embodiments of the present application with reference to the accompanying drawings.

[0012] Figure 1 An application scenario diagram of the method, apparatus, device and medium for burning a solid-state hard disk according to an embodiment of the present application is shown.

[0013] Figure 2 A flow chart of a method for programming a solid state drive according to an embodiment of the present application is shown.

[0014] Figure 3 A schematic diagram of multiple burning files containing interception identifiers according to an embodiment of the present application is shown.

[0015] Figure 4 A schematic diagram of programming a solid state drive according to an embodiment of the present application is shown.

[0016] Figure 5 A schematic diagram of replacing and updating a predetermined capacity firmware integration package according to an embodiment of the present application is shown.

[0017] Figure 6 A schematic diagram of adding and updating a predetermined capacity firmware integration package according to an embodiment of the present application is shown.

[0018] Figure 7 A schematic diagram of adding and updating a predetermined capacity firmware integration package according to another embodiment of the present application is shown.

[0019] Figure 8 A schematic diagram is shown of replacing and updating a predetermined capacity firmware integrated package containing multiple sub-packages according to an embodiment of the present application.

[0020] Fig. 9 A structural block diagram of a device for programming a solid state drive according to an embodiment of the present application is shown.

[0021] Fig.10 A block diagram of an electronic device suitable for implementing a method for programming a solid state drive according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0022] Below, embodiments of the present application will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present application. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present application. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present application.

[0023] The terms used herein are only for describing specific embodiments and are not intended to limit the present application. The terms "include", "comprising", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0024] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.

[0025] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0026] In the process of implementing the concept of the present invention, it is found through research that before using the solid state drive to store, read and write data in the server, the capacity firmware needs to be burned into the solid state drive. The solid state drive and the capacity firmware usually correspond one to one. When the capacity firmware that does not correspond to the solid state drive is used to burn it, the solid state drive will fail to burn or even be damaged.

[0027] In view of this, an embodiment of the present application provides a method for burning a solid-state hard disk, obtaining the bus number and hard disk capacity of the solid-state hard disk; according to the hard disk capacity, determining the target capacity parameter using the capacity mapping relationship stored in a shared server, wherein the capacity mapping relationship represents the association between multiple predetermined hard disk capacities and multiple predetermined capacity parameters; according to the target capacity parameter, obtaining the target capacity firmware from a predetermined capacity firmware integrated package stored in the shared server, wherein the predetermined capacity firmware integrated package includes predetermined capacity firmware with multiple capacities; based on the bus number, burning the target capacity firmware to the solid-state hard disk to obtain the target solid-state hard disk.

[0028] Figure 1 An application scenario diagram of the method, apparatus, device and medium for burning a solid-state hard disk according to an embodiment of the present application is shown.

[0029] like Figure 1 As shown, the application scenario according to this embodiment may include a first solid state drive 101, a second solid state drive 102, a third solid state drive 103, a network 104, and a server 105. The network 104 is used to provide a medium for a communication link between the first solid state drive 101, the second solid state drive 102, the third solid state drive 103, and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or optical fiber cables, etc.

[0030] The user can use the first solid state drive 101 , the second solid state drive 102 , and the third solid state drive 103 to interact with the server 105 through the network 104 to send device information of the solid state drives to the server 105 .

[0031] The server 105 may be a server that uses firmware to burn the first solid-state drive 101, the second solid-state drive 102, and the third solid-state drive 103. For example, the capacity firmware or functional firmware is used to burn the capacity or function of the first solid-state drive 101, the second solid-state drive 102, and the third solid-state drive 103, respectively, and the burning result is fed back and displayed. The server 105 can also reset the first solid-state drive 101, the second solid-state drive 102, and the third solid-state drive 103 in the card slot by restarting, so that the first solid-state drive 101, the second solid-state drive 102, and the third solid-state drive 103 can perform normal storage, reading, writing, and other operations.

[0032] It should be noted that the method for burning a solid-state hard disk provided in the embodiment of the present application can generally be performed by the server 105. Accordingly, the device for burning a solid-state hard disk provided in the embodiment of the present application can generally be set in the server 105. The method for burning a solid-state hard disk provided in the embodiment of the present application can also be performed by a server or server cluster that is different from the server 105 and can communicate with the first solid-state hard disk 101, the second solid-state hard disk 102, the third solid-state hard disk 103 and / or the server 105. Correspondingly, the device for burning a solid-state hard disk provided in the embodiment of the present application can also be set in a server or server cluster that is different from the server 105 and can communicate with the first solid-state hard disk 101, the second solid-state hard disk 102, the third solid-state hard disk 103 and / or the server 105.

[0033] It should be understood that Figure 1 The number of solid state drives, networks, and servers in the embodiment is only for illustration purposes. Any number of terminal devices, networks, and servers may be provided as required.

[0034] The following will be based on Figure 1 The scene described by Figure 2~Figure 8 The method for burning a solid state hard disk in an embodiment of the application is described in detail.

[0035] Figure 2 A flow chart of a method for programming a solid state drive according to an embodiment of the present application is shown.

[0036] like Figure 2 As shown, the method for programming a solid state drive in this embodiment includes operations S210 to S240.

[0037] In operation S210, a bus number and hard disk capacity of the solid state hard disk are obtained.

[0038] According to an embodiment of the present application, a server may include multiple hard disk slots, each of which may be inserted with a solid-state hard disk that complies with the service agreement. Each hard disk slot may have a bus number corresponding to it, and the solid-state hard disk to be burned may be located by the bus number of the hard disk slot. When batch burning multiple solid-state hard disks, the bus number may be used to determine the solid-state hard disk being burned, the solid-state hard disk to be burned, the solid-state hard disk that has been burned successfully, etc.

[0039] According to an embodiment of the present application, a solid state drive may be a storage device. In the process of preparing the solid state drive, the hard disk capacity of the solid state drive may be determined. When the solid state drive is inserted into the hard disk slot, the server may obtain the hardware capacity of the solid state drive in the current slot.

[0040] In operation S220, a target capacity parameter is determined according to the hard disk capacity using a capacity mapping relationship stored in the shared server. The capacity mapping relationship represents an association relationship between a plurality of predetermined hard disk capacities and a plurality of predetermined capacity parameters.

[0041] According to an embodiment of the present application, the target capacity parameter may represent a parameter instruction or a parameter identifier for obtaining the capacity firmware of the solid state drive from a predetermined capacity firmware integrated package.

[0042] According to an embodiment of the present application, based on the association between the predetermined hard disk capacity and the predetermined capacity parameters, a capacity mapping relationship can be pre-constructed and stored in a shared server or shared file. For example, a shared file or service platform such as FTP (File Transfer Protocol), Samba (SMB / CIFS), or NFS (Network File System) can be pre-built to store the capacity mapping relationship, so that the capacity mapping relationship can be directly called to determine the target capacity parameters during burning.

[0043] In operation S230, the target capacity firmware is acquired from the predetermined capacity firmware integrated package stored in the shared server according to the target capacity parameter. The predetermined capacity firmware integrated package may include predetermined capacity firmware having multiple capacities.

[0044] According to an embodiment of the present application, the capacity of each predetermined capacity firmware is different from each other. In the predetermined capacity firmware integrated package, the predetermined capacity firmwares of multiple capacities can be sorted at will. For example, the sorting order is 0.96T predetermined capacity firmware-15.36T predetermined capacity firmware-1.6T predetermined capacity firmware-3.2T predetermined capacity firmware-3.84T predetermined capacity firmware.

[0045] According to the embodiments of the present application, the hard disk capacity of the solid-state hard disk and the capacity firmware used during burning are in one-to-one correspondence, that is, the data volume of the hard disk capacity of the solid-state hard disk and the capacity firmware used during burning are equal, so that the solid-state hard disk can only be burned successfully when the capacity firmware equal to the hard disk capacity of the solid-state hard disk is used for burning, otherwise the burning will fail. For example, when using the 0.96T capacity firmware to burn a solid-state hard disk with a hard disk capacity of 0.96T, the burning can be successful; when using the 1.6T capacity firmware to burn a solid-state hard disk with a hard disk capacity of 0.96T, it prompts that the burning failed.

[0046] According to an embodiment of the present application, multiple predetermined capacity firmware and multiple functional firmware of multiple capacities may be pre-existing in a shared server, and only multiple predetermined capacity firmware of multiple capacities are extracted from the firmware containing various functions and types, and processed to form a predetermined capacity firmware integrated package that only includes capacity firmware. This reduces firmware files and avoids high matching risks and high burning failure rates caused by errors such as missing files or confusing files when matching capacity firmware. At the same time, in the process of constructing a predetermined capacity firmware integrated package, a relationship between multiple predetermined capacity firmware and capacity parameters is established, and the capacity firmware can be determined according to the capacity parameters during burning.

[0047] In operation S240, the target capacity firmware is burned into the solid state drive based on the bus number to obtain a target solid state drive.

[0048] According to the embodiment of the present application, the bus number is used to confirm and verify whether the solid-state drive to be burned is correct, and the target capacity firmware is burned into the solid-state drive corresponding to the bus number, thereby avoiding the problem of wrong burning or missed burning. In the case of batch burning, the bus number of each solid-state drive can be used to avoid burning confusion and further improve the quality of batch burning.

[0049] According to the embodiment of the present application, the bus number and hard disk capacity of the solid-state hard disk are first obtained, so that the hard disk capacity can be used as the basic reference for selecting the matching target capacity firmware. The bus number is convenient for accurately locating the solid-state hard disk to be burned even in batches, thereby improving the burning efficiency and burning quality of the solid-state hard disk when burning alone or in batches. Then, using the capacity mapping relationship pre-constructed based on the association between the predetermined hard disk capacity and the predetermined capacity parameter and stored in the shared server, the target capacity parameter corresponding only to the hard disk capacity is determined from the mapping relationship bridge according to the hard disk capacity, and the target capacity parameter is used as a parameter instruction or parameter identifier to extract the target capacity firmware.

[0050] According to the embodiments of the present application, according to the target capacity parameters, the target capacity firmware is obtained from a unified predetermined capacity firmware integrated package stored in a shared server and containing predetermined capacity firmware of multiple capacities, so that in the process of obtaining the target capacity firmware, it is possible to search and obtain the target capacity firmware that matches the solid-state drive without traversing all firmware files in the shared server, thereby improving the efficiency of obtaining the target capacity firmware, avoiding omissions and occupying large resources when traversing multiple firmware files during the acquisition process, improving the accuracy and stability of obtaining the target capacity firmware, and reducing the resource cost during the burning process. Finally, based on the pre-acquired bus number, the solid-state drive to be burned is located, and the target capacity firmware that matches the solid-state drive is burned into the solid-state drive, so as to obtain a target solid-state drive with a high success rate and effectiveness of burning, thereby improving the burning efficiency and burning quality of the solid-state drive during burning.

[0051] According to an embodiment of the present application, before obtaining the target capacity firmware from the predetermined capacity firmware integrated package, the predetermined capacity firmware integrated package can be pre-constructed in the shared server. Specifically, the predetermined capacity firmware integrated package can be constructed in the following manner:

[0052] According to an embodiment of the present application, a plurality of predetermined capacity firmwares having different capacities are obtained.

[0053] According to an embodiment of the present application, a plurality of predetermined capacity firmwares with different capacities may be stored in the server, for example, 0.96T predetermined capacity firmware, 1.6T predetermined capacity firmware, and 1.92T predetermined capacity firmware.

[0054] According to an embodiment of the present application, multiple predetermined capacity firmwares are compiled respectively to obtain multiple burning files corresponding to the multiple predetermined capacity firmwares, and the burning files have the same data volume as the predetermined capacity firmwares.

[0055] According to an embodiment of the present application, further, a method of compiling a plurality of predetermined capacity firmwares respectively to obtain a plurality of burning files corresponding to the plurality of predetermined capacity firmwares includes the following operations:

[0056] According to an embodiment of the present application, a plurality of predetermined capacity firmwares are compiled respectively to obtain a plurality of capacity files corresponding to the plurality of predetermined capacity firmwares.

[0057] According to an embodiment of the present application, multiple capacity files are all binary files.

[0058] According to an embodiment of the present application, fields in multiple capacity files are marked respectively according to multiple interception identifiers to obtain multiple burning files.

[0059] According to an embodiment of the present application, the interception identifier may include a start identifier and an end identifier. Marking the fields in the capacity file using the end identifier may include inserting an end identifier such as a binary form before, in the middle, or after the field, and may also include marking a certain character in all fields so that the character can appear luminous, bold, or other significant marks without changing the meaning. Further, when marking the fields in the capacity file using the start identifier, the start identifier needs to be located before all the fields of the capacity firmware, or located on the first character of all the fields of the capacity firmware; when marking the fields in the capacity file using the end identifier, the start identifier needs to be located after all the fields of the capacity firmware, or located on the last character of all the fields of the capacity firmware.

[0060] According to the embodiment of the present application, each burning file contains an interception identifier, and the interception identifiers in each burning file are different from each other. Through different interception identifiers, it is convenient to establish mapping and other connections with multiple predetermined capacity parameters.

[0061] According to an embodiment of the present application, the compiled capacity files are marked by using interception identifiers to facilitate the establishment of a mapping relationship between the identifiers in each capacity file and the predetermined capacity parameters, so that the accurate capacity firmware can be located according to the relevant capacity parameters.

[0062] Figure 3 A schematic diagram of multiple burning files containing interception identifiers according to an embodiment of the present application is shown.

[0063] like Figure 3 As shown, it includes multiple burning files containing interception identifiers and different capacities, each interception identifier is located at the front of a different field, that is, a start identifier, by adding an arrow and a binary parameter identifier before the first character in the field, for example, adding an arrow and a binary parameter 0100 before the first character in the field of a 3.2T burning file, thereby establishing a connection between multiple burning files and multiple predetermined capacity parameters.

[0064] According to an embodiment of the present application, a plurality of burning files are compressed respectively to obtain a plurality of compressed burning files and attribute information of the plurality of compressed burning files.

[0065] According to an embodiment of the present application, when the interception identifier includes a start identifier, the method of compressing multiple burning files respectively to obtain multiple compressed burning files and attribute information of multiple compressed burning files also includes the following operations:

[0066] According to an embodiment of the present application, a predetermined field of the programming file is marked according to the verification mark to obtain an intermediate programming file. The predetermined field represents a field located after the start mark.

[0067] According to an embodiment of the present application, the verification marks used to mark the predetermined fields of the burning file can be the same. In the process of compressing the burning file, if the compression is normal, the position of the interception mark in the burning file will not change, but if there is a compression error such as garbled characters, the position of the start mark in the burning file may be confused or lost. Therefore, a verification mark can be introduced and inserted into the field after the start mark, or a certain character in the field after the mark can be marked so that the character can appear with significant marks such as luminous and bold without changing the meaning, to help determine whether the current compression is correct and improve the generation accuracy of the predetermined capacity firmware integrated package.

[0068] According to an embodiment of the present application, the intermediate burning file is compressed to obtain an intermediate compressed burning file.

[0069] According to an embodiment of the present application, the intermediate compressed burning file is verified according to the relative position between the verification mark and the start mark of the intermediate compressed burning file to obtain a second verification result.

[0070] According to an embodiment of the present application, when the verification mark of the intermediate compressed burning file is located after the start mark, the second verification result can represent a pass; otherwise, the second verification result can represent a fail.

[0071] According to an embodiment of the present application, when the second verification result indicates passing, the intermediate compressed burning file is determined as the compressed burning file.

[0072] According to an embodiment of the present application, when the second verification result characterizes failure, the intermediate burning file with compression error is located, and operations such as re-compression, re-labeling, and regeneration of the binary burning file are performed on it.

[0073] According to an embodiment of the present application, in the case where the interception mark includes a termination mark, the field of the burning file located before the termination mark is marked according to the verification mark to obtain an intermediate burning file, and the intermediate burning file is compressed to obtain an intermediate compressed burning file, and the intermediate compressed burning file is verified according to the relative position between the verification mark and the termination mark of the intermediate compressed burning file. In the case where the verification mark of the intermediate compressed burning file is located before the termination mark, the second verification result can be characterized as a pass; in the case where the verification mark of the intermediate compressed burning file is located after the termination mark or the termination mark is not identified, the second verification result can be characterized as a fail. Therefore, in the case where the second verification result indicates a pass, the intermediate compressed burning file is determined as a compressed burning file.

[0074] According to an embodiment of the present application, after determining to obtain a plurality of compressed burning files, the attribute information of each compressed burning file is obtained. The attribute information of the compressed burning file may include the size of the compressed burning file, but is not limited thereto.

[0075] According to an embodiment of the present application, multiple compressed burning files and multiple attribute information are packaged to obtain a firmware integrated package of a predetermined capacity.

[0076] According to the embodiment of the present application, during the packaging process, the data content in the compressed burning file will not change in order, but the order between multiple compressed burning files will be disrupted. Therefore, before packaging, the interception mark of the compressed burning file and the attribute information matching it can be associated in advance, so that the compressed burning file, the attribute information and the interception mark can achieve a three-way match, avoid confusion and mixing, improve the orderliness of the files in the predetermined capacity firmware integration package, the robustness, stability and generation accuracy of the predetermined capacity firmware integration package, thereby improving the accuracy of obtaining the target capacity firmware during the application process.

[0077] According to an embodiment of the present application, before the target capacity parameter is determined using the capacity mapping relationship, the capacity mapping relationship may be pre-constructed in a shared server or a shared file.

[0078] According to an embodiment of the present application, a first mapping sub-relationship is established based on the association relationship between multiple predetermined hard disk capacities and multiple predetermined capacity firmwares.

[0079] According to an embodiment of the present application, the association relationship between multiple predetermined capacity firmware and multiple predetermined capacity parameters builds a second mapping sub-relationship. For example, the predetermined capacity parameter can be represented by -c. When -c is 0, the predetermined capacity firmware of 0.96T is obtained; when -c is 1, the predetermined capacity firmware of 1.6T is obtained; when -c is 2, the predetermined capacity firmware of 1.92T is obtained; when -c is 3, the predetermined capacity firmware of 3.2T is obtained; when -c is 4, the predetermined capacity firmware of 3.84T is obtained; when -c is 5, the predetermined capacity firmware of 6.4T is obtained; when -c is 6, the predetermined capacity firmware of 7.68T is obtained; when -c is 7, the predetermined capacity firmware of 12.8T is obtained; when -c is 8, the predetermined capacity firmware of 15.36T is obtained.

[0080] According to an embodiment of the present application, a method for determining a target capacity parameter based on a hard disk capacity by using a capacity mapping relationship stored in a shared server includes the following operations:

[0081] According to an embodiment of the present application, the capacity mapping relationship includes a first mapping sub-relationship and a second mapping sub-relationship.

[0082] According to an embodiment of the present application, the capacity information of the capacity firmware corresponding to the hard disk capacity is determined according to the first mapping sub-relationship.

[0083] According to an embodiment of the present application, based on the capacity information of the capacity firmware, the target capacity parameter is determined according to the second mapping sub-relationship.

[0084] For example, the hard disk capacity of the solid state drive is 0.96T. According to the first mapping sub-relationship, the capacity information of the capacity firmware is determined to be 0.96T. Based on the capacity information of the capacity firmware being 0.96T, according to the second mapping sub-relationship, the target capacity parameter -c is determined to be 0.

[0085] According to an embodiment of the present application, in the process of building the second mapping sub-relationship, multiple predetermined capacity parameters and multiple interception identifiers can be matched one by one, and the association between capacity parameters-interception identifier-capacity firmware can be established, so that the target capacity firmware can be obtained from the predetermined capacity firmware integrated package based on the capacity parameters.

[0086] According to the embodiment of the present application, the first mapping sub-relationship and the second mapping sub-relationship are established based on the association between hard disk capacity-capacity firmware-capacity parameters. Therefore, the target capacity parameter of the solid state drive can be determined when the hard disk capacity is known, and based on the association between the predetermined capacity firmware integrated package-capacity parameters, when the target capacity parameters are obtained, it is equivalent to obtaining the accurate parameter identification for extracting the corresponding capacity firmware in the predetermined capacity firmware integrated package, so that each link is related to each other and there is a one-to-one mapping connection, so that when the solid state drives are burned in large quantities, the matching error rate is reduced, and the acquisition accuracy and stability of the target capacity firmware of each solid state drive are improved.

[0087] According to an embodiment of the present application, according to the target capacity parameter, a method for obtaining target capacity firmware from a predetermined capacity firmware integrated package stored in a shared server includes the following operations:

[0088] According to an embodiment of the present application, a firmware integration package of a predetermined capacity is retrieved from the firmware storage space of a shared server.

[0089] According to an embodiment of the present application, a target interception identifier and target attribute information corresponding to the target capacity parameter are determined according to the target capacity parameter.

[0090] According to the embodiment of the present application, by pre-building the association between the capacity parameter and the interception identifier, the target interception identifier can be determined first according to the target capacity parameter, and then the size information of the corresponding target compressed burning file can be determined based on the target interception identifier.

[0091] According to an embodiment of the present application, target capacity firmware is obtained from a predetermined capacity firmware integrated package based on a target interception identifier and target attribute information.

[0092] According to an embodiment of the present application, further, from the predetermined capacity firmware integrated package, according to the target interception identifier and the target attribute information, the method for obtaining the target capacity firmware includes the following operations:

[0093] According to an embodiment of the present application, a target compressed burning file is obtained from a predetermined capacity firmware integrated package based on a target interception identifier and target attribute information.

[0094] According to an embodiment of the present application, the position of the target interception identifier is first determined from the predetermined capacity firmware integrated package. When the target interception identifier is the starting identifier, based on the size information of the target compressed burning file in the target attribute information and according to the marking method, with the starting identifier as the starting point, a compressed burning file of a size equal to the size information of the target compressed burning file is intercepted as the target compressed burning file.

[0095] For example, if the start identifier is inserted into the capacity file during the marking process, it is necessary to erase the start identifier in advance before intercepting the compressed burning file of the same size as the size information of the target compressed burning file, and then intercept the compressed burning file, or based on the size of the target compressed burning file and the number of characters of the start identifier, intercept multiple compressed burning files in the predetermined capacity firmware integrated package, and then erase the start identifier in the intercepted compressed burning file to obtain the target compressed burning file.

[0096] According to an embodiment of the present application, during the interception process, it is also possible to determine whether the next character carries an interception identifier or whether the next character is an interception identifier when the last character is intercepted, thereby helping to determine whether the interception of the current compressed burning file is accurate.

[0097] According to an embodiment of the present application, the target compressed burning file is decompressed to obtain the target burning file.

[0098] According to an embodiment of the present application, the target burning file is decompiled to obtain the first capacity firmware. The target burning file is a binary file.

[0099] According to an embodiment of the present application, based on the hard disk capacity, the capacity information of the first capacity firmware is verified to obtain a first verification result.

[0100] According to an embodiment of the present application, based on the hard disk capacity, the first capacity firmware obtained after decompilation is capacity checked. When the hard disk capacity is consistent with the capacity information of the first capacity firmware, the first check result is confirmed to be passed; otherwise, the first check result is confirmed to be failed.

[0101] According to an embodiment of the present application, when the first verification result indicates passing, the first capacity firmware is determined to be the target capacity firmware.

[0102] According to the embodiment of the present application, when the first verification result does not pass, the target capacity parameter of the current solid-state drive can be reconfirmed or the target compressed burning file can be intercepted and other operations can be performed until the first verification result passes. Further, a verification number threshold for the first verification can be set, and when the first verification is repeated for a number greater than the threshold on the same solid-state drive, an alarm can be issued to the server.

[0103] According to an embodiment of the present application, according to the target capacity parameter, the target interception identifier and target attribute information corresponding to the target capacity parameter are determined, and then from the predetermined capacity firmware integrated package, according to the target interception identifier and the target attribute information, the target compressed burning file is obtained, and it is decompressed and decompiled to obtain a first capacity firmware, and then based on the hard disk capacity, the capacity information of the first capacity firmware is verified to obtain a first verification result, and the first capacity firmware is determined to be the target capacity firmware according to the first verification result, so as to obtain the target capacity firmware uniquely corresponding to the solid-state hard disk based on the association between the capacity parameter-interception identifier-attribute information-compressed burning file, and at the same time, in the process of obtaining the target capacity firmware uniquely corresponding to the solid-state hard disk, repeated verification and verification are performed to improve the integrity and accuracy of the obtained target capacity firmware under multi-dimensional verification, so that when the target capacity firmware is used to burn the solid-state hard disk, it can be burned successfully, thereby improving the burning efficiency.

[0104] According to the embodiments of the present application, when batch burning of multiple solid-state hard drives, the multiple solid-state hard drives can determine the target capacity parameters of each other based on their respective hard drive capacities and bus numbers in a single thread, and based on the established association between capacity parameters-interception identifiers-attribute information-compressed burning files, utilize multiple target capacity parameters to determine the target capacity firmware of each solid-state hard drive one by one without affecting each other. There is no need to traverse multiple firmware files from the server, thus avoiding omissions when traversing multiple firmware files and occupying large resources, improving the accuracy and stability of obtaining the target capacity firmware, and reducing resource costs.

[0105] According to the embodiment of the present application, when batch burning multiple solid-state hard disks, the bus numbers with the same hard disk capacity can also be marked according to the same hard disk capacity. For solid-state hard disks with the same hard disk capacity, it is only necessary to obtain the target capacity firmware once, and then burn the marked bus number with the obtained target capacity firmware, so as to avoid confusion caused by cross-acquisition in the predetermined capacity firmware integrated package and repeatedly obtain the same target capacity firmware, thereby improving the burning efficiency during batch burning and the accuracy of obtaining the target capacity firmware.

[0106] According to an embodiment of the present application, the program can be programmed using the burn command (nvme burn -c) (-b) (fw-path) is used to burn batches of solid-state drives, where (nvme burn -c) can represent the target capacity parameters, -b can represent the bus number and hard disk capacity, and fw-path can represent a shared file or shared server.

[0107] According to an embodiment of the present application, the method for burning a solid state drive further includes:

[0108] According to an embodiment of the present application, the server into which the target solid state drive is inserted is powered off to initialize the server.

[0109] According to an embodiment of the present application, the server is powered on and the target capacity firmware in the target solid-state drive is activated to enable the target solid-state drive to perform read and write operations.

[0110] According to the embodiments of the present application, considering that the server often has related running services while burning the solid-state hard disk, the server can be powered on and off during non-business operation so that the target solid-state hard disk can perform read and write operations.

[0111] Figure 4 A schematic diagram of programming a solid state drive according to an embodiment of the present application is shown.

[0112] like Figure 4As shown, three solid-state hard disks are inserted into the target server 407, and the bus number and hard disk capacity of each solid-state hard disk are obtained 401. For example, the bus number of the first solid-state hard disk is 1, and the hard disk capacity is 1.6T; the bus number of the first solid-state hard disk is 2, and the hard disk capacity is 3.84T; the bus number of the first solid-state hard disk is 3, and the hard disk capacity is 12.8T. The target capacity parameter of each solid-state hard disk is determined by using the capacity mapping relationship 402 stored in the shared server. For example, the target capacity parameter -c of the first solid-state hard disk is 1, the target capacity parameter -c of the second solid-state hard disk is 4, and the target capacity parameter -c of the third solid-state hard disk is 7. Based on the relationship between the capacity parameter and the interception identifier, the binary form of the interception identifier 403 of the target capacity parameter is determined from the predetermined capacity firmware integration package stored in the shared server. For example, the binary form of -c is 1 is 0001, the binary form of -c is 4 is 0100, and the binary form of -c is 7 is 0111. The target burning files 404 of the three solid-state hard disks are obtained. The target burning files 404 of the three solid state drives are decompiled to obtain the target capacity firmware 405 of each solid state drive. Based on the bus number, the target capacity firmware 405 is burned into the corresponding solid state drives to obtain three target solid state drives 406. The target server 407 with the three target solid state drives 406 inserted is powered on and off so that each target solid state drive 406 can perform read and write operations.

[0113] According to an embodiment of the present application, the method for burning a solid state drive further includes:

[0114] According to an embodiment of the present application, an update compressed burning file and update attribute information of the update compressed burning file are obtained according to the update capacity firmware.

[0115] According to the embodiments of the present application, the update capacity firmware is subjected to the above operations such as interception identification marking, compilation, and compression to obtain an update compressed burning file and its update attribute information.

[0116] According to an embodiment of the present application, based on the update capacity firmware, a target update strategy is determined from multiple predetermined update strategies, and the multiple predetermined update strategies include at least one of a strategy for replacing the predetermined capacity firmware in a predetermined capacity firmware integrated package and a strategy for adding an update capacity firmware to the predetermined capacity firmware integrated package, but are not limited to this.

[0117] According to an embodiment of the present application, based on a target update strategy, the predetermined capacity firmware integrated package is updated to obtain an updated predetermined capacity firmware integrated package.

[0118] According to an embodiment of the present application, further, based on the target update strategy, the predetermined capacity firmware integrated package is updated to obtain an updated predetermined capacity firmware integrated package. The method includes the following operations:

[0119] According to an embodiment of the present application, when the target update strategy is to replace the predetermined capacity firmware in the predetermined capacity firmware integrated package, the compressed burning file and attribute information corresponding to the updated compressed burning file are queried from the predetermined capacity firmware integrated package based on the interception identifier.

[0120] For example, if the updated capacity firmware is 6.4T, the target capacity parameter of the 6.4T predetermined capacity firmware is queried from the capacity mapping relationship, thereby determining the interception mark 0101 of the 6.4T predetermined capacity firmware. Then, the compressed burning file and attribute information at the location of the interception mark 0101 are queried from the predetermined capacity firmware integrated package.

[0121] According to an embodiment of the present application, the compressed burning file and the attribute information are replaced with the updated compressed burning file and the updated attribute information to obtain an updated predetermined capacity firmware integrated package.

[0122] According to an embodiment of the present application, after replacing with the updated compressed burning file and updating the attribute information, it is necessary to synchronously update the cutoff mark corresponding to the predetermined capacity parameter of the predetermined capacity firmware. For example, the interception mark in the 6.4T updated compressed burning file is the first character marked in yellow. After replacing with the 6.4T updated compressed burning file and updating the attribute information, it is necessary to replace the original cutoff mark 0101 with the first character marked in yellow.

[0123] Figure 5 A schematic diagram of replacing and updating a predetermined capacity firmware integration package according to an embodiment of the present application is shown.

[0124] like Figure 5 As shown, the 6.4T predetermined capacity firmware in the predetermined capacity firmware integrated package needs to be updated. When the interception identifier is inserted before the first character of the compressed burning file of the 6.4T predetermined capacity firmware, there is no need to erase the interception identifier 0101. According to the interception identifier 0101, the position of the compressed burning file of the 6.4T predetermined capacity firmware is located, and the 6.4T updated compressed burning file is used to replace it.

[0125] According to an embodiment of the present application, when the target update strategy is a strategy of adding an update capacity firmware to a predetermined capacity firmware integrated package, when performing the (i+1)th round of update:

[0126] According to an embodiment of the present application, when i+1 is less than a predetermined threshold, the predetermined capacity firmware integrated package obtained by the i-th round update is determined as the predetermined capacity firmware sub-package of the i+1th round. The predetermined capacity firmware integrated package of the i-th round includes the predetermined capacity firmware sub-package of the previous i-1 rounds, where i is a positive integer.

[0127] According to an embodiment of the present application, when the target update policy is a replacement policy, the update round when the target update policy is added may not be included, that is, when the target update policy is a replacement policy, there is no need to consider the round and the update may be directly replaced.

[0128] According to an embodiment of the present application, the predetermined capacity firmware sub-package of the i+1th round, the updated compressed burning file of the i+1th round and the updated attribute information of the i+1th round are packaged to obtain an updated predetermined capacity firmware integrated package.

[0129] According to an embodiment of the present application, after the predetermined capacity firmware integrated package is updated, the cutoff mark corresponding to the predetermined capacity parameter of the predetermined capacity firmware needs to be synchronously updated.

[0130] According to an embodiment of the present application, when i+1 is less than a predetermined threshold, the predetermined capacity firmware integrated package obtained by the i-th round of update is determined as the predetermined capacity firmware sub-package of the i+1th round, and the predetermined capacity firmware sub-package of the i+1th round, the updated compressed burning file of the i+1th round, and the updated attribute information of the i+1th round are packaged to obtain an updated predetermined capacity firmware integrated package. In this way, the predetermined capacity firmware integrated package can be quickly updated, and during the update process, the acquisition of the original capacity firmware will not be affected, and the burning and updating can be carried out simultaneously, thereby improving the burning efficiency and the updating efficiency. When it is necessary to add capacity firmware, by limiting the update rounds, it is equivalent to limiting the sub-packages contained in the predetermined capacity firmware integrated package, so that the structure in the predetermined capacity firmware integrated package is simple.

[0131] Figure 6 A schematic diagram of adding and updating a predetermined capacity firmware integration package according to an embodiment of the present application is shown.

[0132] like Figure 6 As shown, taking the predetermined threshold of 8 as an example, when i+1 is less than the predetermined threshold, the updated predetermined capacity firmware integrated package is obtained. The predetermined capacity firmware integrated package obtained by the second round of update is determined as the predetermined capacity firmware sub-package of the third round (the second predetermined capacity firmware sub-package), and is packaged with the updated compressed burning file in the third round to obtain the updated predetermined capacity firmware integrated package. At the same time, the second round of predetermined capacity firmware integrated package includes: the 0th predetermined capacity firmware sub-package obtained by the first round of update, and the 1st predetermined capacity firmware sub-package obtained by the second round of update.

[0133] According to an embodiment of the present application, when i+1 is greater than or equal to a predetermined threshold, multiple compressed burning files and multiple attribute information in a predetermined capacity firmware integration package obtained by the i-th round of update are obtained.

[0134] According to an embodiment of the present application, when i+1 is greater than or equal to a predetermined threshold, the compressed burning files of all original capacity firmware in the predetermined capacity firmware integrated package are disassembled from the integrated package.

[0135] According to an embodiment of the present application, multiple compressed burning files, multiple attribute information, the updated compressed burning files of the i+1th round, and the updated attribute information of the i+1th round are packaged to obtain an updated predetermined capacity firmware integrated package.

[0136] According to an embodiment of the present application, the compressed burning file of the original capacity firmware and the updated compressed burning file are packaged together to obtain an updated predetermined capacity firmware integrated package.

[0137] According to an embodiment of the present application, when i+1 is greater than or equal to a predetermined threshold, multiple compressed burning files and multiple attribute information in the predetermined capacity firmware integrated package obtained in the i-th round of update are obtained, and all compressed burning files and attribute information are packaged to obtain an updated predetermined capacity firmware integrated package, so that the predetermined capacity firmware integrated package can be quickly updated and the structure within the predetermined capacity firmware integrated package can be concise.

[0138] According to an embodiment of the present application, when i+1 is less than a predetermined threshold, multiple sub-package identifiers can be used to mark each predetermined capacity firmware sub-package in each round of update, and at the same time, the sub-package identifier is associated with the capacity size of all capacity firmware in the predetermined capacity firmware sub-package. In the case of containing multiple predetermined capacity firmware sub-packages, there is no need to first determine the target capacity parameter. The first mapping sub-relationship can be used to first determine the capacity information of the capacity firmware according to the hard disk capacity, and then the target predetermined capacity firmware sub-package is determined using the capacity information and from multiple sub-package identifiers. Thus, the selection range of the target capacity parameter can be narrowed, and in the predetermined capacity firmware integrated package, the range of the target capacity firmware is determined according to the cutoff identifier. Based on the selection range of the current target capacity parameter and the hard disk capacity, the target capacity parameter and the corresponding cutoff identifier are determined, and then the target capacity firmware is directly determined from the cutoff identifier. The scope of the target capacity firmware is obtained. Thus, in the case of multiple rounds of capacity firmware updates to the predetermined capacity firmware integrated package, the predetermined capacity firmware sub-package where the target capacity firmware is located can be found more efficiently and quickly, further reducing the resource cost used in the burning process, and improving the accuracy and stability of obtaining the target capacity firmware.

[0139] Figure 7 A schematic diagram of adding and updating a predetermined capacity firmware integration package according to another embodiment of the present application is shown.

[0140] like Figure 7As shown, taking the predetermined threshold of 3 as an example, when i+1 is greater than or equal to the predetermined threshold, all files in the predetermined capacity firmware integration package obtained after the third round of update need to be disassembled and packaged together with the 18.94T update compression and burning file of the fourth round of update to obtain the predetermined capacity firmware integration package after the fourth round of update.

[0141] Figure 8 A schematic diagram is shown of replacing and updating a predetermined capacity firmware integrated package containing multiple sub-packages according to an embodiment of the present application.

[0142] like Figure 8 As shown, since the target update strategy is a replacement strategy, it can be excluded from the update round when the target update strategy is added. Therefore, the 6.4T compressed burning file corresponding to the 6.4T update compressed burning file can be directly queried according to the interception identifier 0101, and the 6.4T compressed burning file can be replaced with the 6.4T update compressed burning file to obtain the updated predetermined capacity firmware integrated package.

[0143] Based on the above method for burning a solid state hard disk, the present application also provides a device for burning a solid state hard disk. Fig. 9 The device is described in detail.

[0144] Fig. 9 A structural block diagram of a device for programming a solid state drive according to an embodiment of the present application is shown.

[0145] like Fig. 9 As shown, the apparatus for programming a solid state drive in this embodiment includes: a first acquisition module 910 , a determination module 920 , a second acquisition module 930 and a programming module 940 .

[0146] The first acquisition module 910 is used to acquire the bus number and hard disk capacity of the solid state hard disk. In one embodiment, the first acquisition module 910 can be used to perform the operation S210 described above, which will not be repeated here.

[0147] The determination module 920 is used to determine the target capacity parameter according to the hard disk capacity using the capacity mapping relationship stored in the shared server, wherein the capacity mapping relationship represents the association relationship between multiple predetermined hard disk capacities and multiple predetermined capacity parameters. In one embodiment, the determination module 920 can be used to perform the operation S220 described above, which will not be repeated here.

[0148] The second acquisition module 930 is used to acquire the target capacity firmware from the predetermined capacity firmware integrated package stored in the shared server according to the target capacity parameter, wherein the predetermined capacity firmware integrated package includes predetermined capacity firmware with multiple capacities. In one embodiment, the second acquisition module 930 can be used to perform the operation S230 described above, which will not be repeated here.

[0149] The burning module 940 is used to burn the target capacity firmware into the solid state drive based on the bus number to obtain the target solid state drive. In one embodiment, the burning module 940 can be used to perform the operation S240 described above, which will not be repeated here.

[0150] According to an embodiment of the present application, the device for burning a solid state hard disk in this embodiment further includes: a power-off module and a power-on module.

[0151] The power-off module is used to power off the server into which the target solid state drive is inserted, so as to initialize the server.

[0152] The power-on module is used to power on the server and activate the target capacity firmware in the target solid-state hard disk so that the target solid-state hard disk can perform read and write operations.

[0153] According to an embodiment of the present application, the apparatus for burning a solid state hard disk in this embodiment further includes: an obtaining module, a determining strategy module and an updating module.

[0154] The obtaining module is used to obtain the update compression burning file and the update attribute information of the update compression burning file according to the update capacity firmware.

[0155] A policy determination module is used to determine a target update policy from a plurality of predetermined update policies according to the update capacity firmware, wherein the plurality of predetermined update policies include at least one of a policy for replacing the predetermined capacity firmware in a predetermined capacity firmware integrated package and a policy for adding an update capacity firmware to the predetermined capacity firmware integrated package.

[0156] The update module is used to update the predetermined capacity firmware integrated package based on the target update strategy to obtain an updated predetermined capacity firmware integrated package.

[0157] According to an embodiment of the present application, any multiple modules of the first acquisition module 910, the determination module 920, the second acquisition module 930 and the burning module 940 can be combined into one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present application, at least one of the first acquisition module 910, the determination module 920, the second acquisition module 930 and the burning module 940 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware and firmware or in a suitable combination of any of them. Alternatively, at least one of the first acquisition module 910, the determination module 920, the second acquisition module 930 and the burning module 940 may be at least partially implemented as a computer program module, and when the computer program module is executed, a corresponding function may be performed.

[0158] Fig.10 A block diagram of an electronic device suitable for implementing a method for programming a solid state drive according to an embodiment of the present application is shown.

[0159] like Fig.10 As shown, the electronic device according to the embodiment of the present application includes a processor 1001, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 1002 or the program loaded from the storage part 1008 to the random access memory (RAM) 1003. The processor 1001 may include, for example, a general-purpose microprocessor (such as a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (for example, an application-specific integrated circuit (ASIC)), etc. The processor 1001 may also include an onboard memory for caching purposes. The processor 1001 may include a single processing unit or multiple processing units for performing different actions of the method flow according to the embodiment of the present application.

[0160] In RAM 1003, various programs and data required for the operation of the electronic device are stored. The processor 1001, ROM 1002 and RAM 1003 are connected to each other via a bus 1004. The processor 1001 performs various operations of the method flow according to the embodiment of the present application by executing the program in ROM 1002 and / or RAM 1003. It should be noted that the program can also be stored in one or more memories other than ROM 1002 and RAM 1003. The processor 1001 can also perform various operations of the method flow according to the embodiment of the present application by executing the program stored in the one or more memories.

[0161] According to an embodiment of the present application, the electronic device may further include an input / output (I / O) interface 1005, which is also connected to the bus 1004. The electronic device may further include one or more of the following components connected to the input / output (I / O) interface 1005: an input portion 1006 including a keyboard, a mouse, etc.; an output portion 1007 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 1008 including a hard disk, etc.; and a communication portion 1009 including a network interface card such as a LAN card, a modem, etc. The communication portion 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to the input / output (I / O) interface 1005 as needed. A removable medium 1011, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 1010 as needed, so that a computer program read therefrom is installed into the storage portion 1008 as needed.

[0162] The present application also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present application is implemented.

[0163] According to an embodiment of the present application, the computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, it may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device. For example, according to an embodiment of the present application, the computer-readable storage medium may include the ROM 1002 and / or RAM 1003 described above and / or one or more memories other than ROM 1002 and RAM 1003.

[0164] The embodiment of the present application also includes a computer program product, which includes a computer program, and the computer program includes a program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the method for burning a solid state drive provided in the embodiment of the present application.

[0165] The computer program executes the above functions defined in the system / device of the embodiment of the present application when the processor 1001 executes the computer program. According to the embodiment of the present application, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0166] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 1009, and / or installed from the removable medium 1011. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0167] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 1009, and / or installed from the removable medium 1011. When the computer program is executed by the processor 1001, the above functions defined in the system of the embodiment of the present application are performed. According to the embodiment of the present application, the system, device, means, module, unit, etc. described above can be implemented by a computer program module.

[0168] According to an embodiment of the present application, the program code for executing the computer program provided by the embodiment of the present application can be written in any combination of one or more programming languages, and specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, such as Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or completely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (e.g., using an Internet service provider to connect through the Internet).

[0169] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the above-mentioned module, program segment or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0170] It will be appreciated by those skilled in the art that the features described in the various embodiments of the present application may be combined and / or combined in a variety of ways, even if such combinations or combinations are not explicitly described in the present application. In particular, without departing from the spirit and teachings of the present application, the features described in the various embodiments of the present application may be combined and / or combined in a variety of ways. All of these combinations and / or combinations fall within the scope of the present application.

[0171] The embodiments of the present application are described above. However, these embodiments are only for the purpose of illustration, and are not intended to limit the scope of the present application. Although each embodiment is described above, this does not mean that the measures in each embodiment cannot be used in combination advantageously. Without departing from the scope of the present application, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present application.

Claims

1. A method for burning a solid state hard disk, characterized in that: The method comprises: Get the bus number and hard disk capacity of the solid state drive; Determining a target capacity parameter according to the hard disk capacity using a capacity mapping relationship stored in a shared server, wherein the capacity mapping relationship represents an association relationship between a plurality of predetermined hard disk capacities and a plurality of predetermined capacity parameters; According to the target capacity parameter, obtaining the target capacity firmware from a predetermined capacity firmware integrated package stored in the shared server, wherein the predetermined capacity firmware integrated package includes predetermined capacity firmware having multiple capacities; Based on the bus number, the target capacity firmware is burned into the solid state drive to obtain a target solid state drive.

2. The method according to claim 1, characterized in that The capacity mapping relationship includes a first mapping sub-relationship and a second mapping sub-relationship; The determining the target capacity parameter according to the hard disk capacity by using the capacity mapping relationship stored in the shared server includes: Determining the capacity information of the capacity firmware corresponding to the hard disk capacity according to the first mapping sub-relationship, wherein the first mapping sub-relationship represents the association relationship between the plurality of the predetermined hard disk capacities and the plurality of the predetermined capacity firmwares; Based on the capacity information of the capacity firmware, the target capacity parameter is determined according to the second mapping sub-relationship, wherein the second mapping sub-relationship represents an association relationship between a plurality of the predetermined capacity firmwares and a plurality of the predetermined capacity parameters.

3. The method according to claim 1, characterized in that: The step of obtaining the target capacity firmware from a predetermined capacity firmware integration package stored in the shared server according to the target capacity parameter includes: Retrieving the firmware integration package of the predetermined capacity from the firmware storage space of the shared server; According to the target capacity parameter, determining a target interception identifier and target attribute information corresponding to the target capacity parameter; The target capacity firmware is obtained from the predetermined capacity firmware integrated package according to the target interception identifier and the target attribute information.

4. The method according to claim 3, characterized in that The step of acquiring the target capacity firmware from the predetermined capacity firmware integrated package according to the target interception identifier and the target attribute information includes: From the predetermined capacity firmware integrated package, according to the target interception identifier and the target attribute information, obtaining a target compressed burning file; Decompressing the target compressed burning file to obtain the target burning file; Decompiling the target burning file to obtain a first capacity firmware; Based on the hard disk capacity, verify the capacity information of the first capacity firmware to obtain a first verification result; When the first verification result indicates passing, the first capacity firmware is determined to be the target capacity firmware.

5. The method according to claim 1, characterized in that The predetermined capacity firmware integration package is constructed in the following manner: Acquire a plurality of the predetermined capacity firmwares having different capacities; Compiling the plurality of the predetermined capacity firmwares respectively to obtain a plurality of burning files corresponding to the plurality of the predetermined capacity firmwares, wherein the burning files have the same data volume as the predetermined capacity firmwares; Compressing the plurality of burning files respectively to obtain a plurality of compressed burning files and attribute information of the plurality of compressed burning files; The plurality of compressed burning files and the plurality of attribute information are packaged to obtain the predetermined capacity firmware integrated package.

6. The method according to claim 5, characterized in that The step of compiling the plurality of predetermined capacity firmwares respectively to obtain a plurality of burning files corresponding to the plurality of predetermined capacity firmwares comprises: Compiling the plurality of predetermined capacity firmwares respectively to obtain a plurality of capacity files corresponding to the plurality of predetermined capacity firmwares; According to a plurality of interception identifiers, the fields in a plurality of the capacity files are marked respectively to obtain a plurality of the burning files.

7. The method according to claim 5, characterized in that The interception mark includes the start mark; The method of compressing the plurality of burning files respectively to obtain a plurality of compressed burning files and attribute information of the plurality of compressed burning files includes: Marking a predetermined field of the programming file according to the verification mark to obtain an intermediate programming file, wherein the predetermined field represents a field located after the start mark; Compressing the intermediate burning file to obtain an intermediate compressed burning file; Verifying the intermediate compressed burning file according to the relative position between the verification mark of the intermediate compressed burning file and the start mark to obtain a second verification result; When the second verification result indicates passing, the intermediate compressed burning file is determined as the compressed burning file.

8. The method according to claim 1, characterized in that The method further comprises: Powering off the server into which the target solid state drive is inserted, so as to initialize the server; The server is powered on to activate the target capacity firmware in the target solid state drive, so that the target solid state drive can perform read and write operations.

9. The method according to claim 1, characterized in that: The method further comprises: According to the update capacity firmware, an update compression burning file and update attribute information of the update compression burning file are obtained; Determining a target update strategy from a plurality of predetermined update strategies according to the update capacity firmware, wherein the plurality of predetermined update strategies include at least one of a strategy for replacing the predetermined capacity firmware in the predetermined capacity firmware integrated package and a strategy for adding the update capacity firmware to the predetermined capacity firmware integrated package; Based on the target update strategy, the predetermined capacity firmware integrated package is updated to obtain an updated predetermined capacity firmware integrated package.

10. The method according to claim 9, characterized in that In the case where the target update strategy is a strategy for replacing the predetermined capacity firmware in the predetermined capacity firmware integrated package, The method of updating the predetermined capacity firmware integrated package based on the target update strategy to obtain an updated predetermined capacity firmware integrated package includes: According to the interception identifier, querying the compressed burning file and attribute information corresponding to the updated compressed burning file from the predetermined capacity firmware integrated package; The compressed burning file and the attribute information are replaced with the updated compressed burning file and the updated attribute information to obtain an updated predetermined capacity firmware integrated package.

11. The method according to claim 9, characterized in that In the case where the target update strategy is a strategy of adding the update capacity firmware to the predetermined capacity firmware integrated package, The updating of the predetermined capacity firmware integrated package based on the target update strategy to obtain the updated predetermined capacity firmware integrated package includes performing the (i+1) round of updating in the following manner: If i+1 is less than a predetermined threshold, the predetermined capacity firmware integrated package obtained by the i-th round update is determined as the predetermined capacity firmware sub-package of the i+1th round, wherein the predetermined capacity firmware integrated package of the i-th round includes the predetermined capacity firmware sub-package of the previous i-1th round, and i is a positive integer; The predetermined capacity firmware sub-package of the i+1th round, the updated compressed burning file of the i+1th round and the updated attribute information of the i+1th round are packaged to obtain an updated predetermined capacity firmware integrated package.

12. The method according to claim 11, characterized in that The method further comprises: When i+1 is greater than or equal to the predetermined threshold, obtaining a plurality of compressed burning files and a plurality of attribute information in a predetermined capacity firmware integrated package obtained by the i-th round of update; The plurality of compressed burning files, the plurality of attribute information, the updated compressed burning files of the (i+1)th round, and the updated attribute information of the (i+1)th round are packaged to obtain the updated predetermined capacity firmware integrated package.

13. A device for burning a solid state hard disk, characterized in that: The device comprises: A first acquisition module is used to acquire the bus number and hard disk capacity of the solid state hard disk; a determination module, configured to determine a target capacity parameter according to the hard disk capacity by using a capacity mapping relationship stored in a shared server, wherein the capacity mapping relationship represents an association relationship between a plurality of predetermined hard disk capacities and a plurality of predetermined capacity parameters; A second acquisition module is used to acquire the target capacity firmware from a predetermined capacity firmware integrated package stored in the shared server according to the target capacity parameter, wherein the predetermined capacity firmware integrated package includes predetermined capacity firmware with multiple capacities; The burning module is used to burn the target capacity firmware into the solid state drive based on the bus number to obtain a target solid state drive.

14. An electronic device comprising: one or more processors; a memory for storing one or more computer programs, It is characterized in that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 12.

15. A computer-readable storage medium having a computer program or instruction stored thereon, characterized in that: When the computer program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 12 are implemented.

Images