Embedded storage chip mass production device and method based on SCSI and eMMC protocol conversion

Abstract

The invention discloses an embedded storage chip mass production device and method based on SCSI and eMMC protocol conversion. The embedded storage chip mass production device comprises an SCSI-eMMC private command mapping module, a non-standard CMD10 state query module and a command verification module. The USB communication protocol layer of the SCSI-eMMC private command mapping module uses an SCSI standard, the CMD10 command response content of the non-standard CMD10 state query module is private defined mass production progress data, and the command verification module is used for realizing verification head generation, anti-code verification and hardware response mechanism. According to the method, the efficiency is optimized, the CMD10 is directly responded by hardware, frequent intervention of an operating system is not needed, and the interrupt processing time is shortened; the compatibility is good; an eMMC private command is packaged through an SCSI command to adapt to common card reader hardware; and the anti-code verification of the verification mechanism ensures that the command transmission is errorless.

Description

Technical Field

[0001] The present invention belongs to the technical field of embedded storage chip production, and particularly relates to an embedded storage chip mass production device and method based on SCSI and eMMC protocol conversion, which is applicable to the scenario of batch production through a USB to eMMC card reader. Background Art

[0002] In the prior art, when mass-producing embedded storage chips (such as eMMC), when converting from the Host to the eMMC protocol, it is usually necessary to rely on frequent low-level interrupt triggers to obtain device status (such as mass production progress, error codes, etc.), resulting in low efficiency and high resource occupancy. Especially when dealing with high-concurrency mass production tasks, the performance is significantly affected. Summary of the Invention

[0003] In order to solve the above-mentioned defects and deficiencies in the prior art, the present invention provides an embedded storage chip mass production device and method based on SCSI and eMMC protocol conversion, with optimized efficiency: CMD10 is directly responded by hardware, without the need for frequent intervention of the operating system, reducing the interrupt processing time; good compatibility: encapsulating eMMC private commands through SCSI commands to adapt to ordinary card reader hardware; high reliability: a verification mechanism (such as inverse code verification) ensures error-free command transmission.

[0004] To achieve the above object, the present invention provides the following technical solution: An embedded storage chip mass production device based on SCSI and eMMC protocol conversion, comprising: a SCSI-eMMC private command mapping module, a non-standard CMD10 status query module, and a command verification module; the USB communication protocol layer of the SCSI-eMMC private command mapping module uses the SCSI standard, the CMD10 command response content of the non-standard CMD10 status query module is privately defined mass production progress data, and the command verification module is used to implement verification header generation, inverse code verification, and hardware response mechanism.

[0005] A mass production method for an embedded storage chip mass production device based on SCSI and eMMC protocol conversion, comprising the following steps: S1. Initialization stage: After the device is initialized, read the eMMC basic information (CSD, CID, EXTCSD, etc.), verify compatibility (CMD8, CMD9, standard CMD10), configure the private command interface, and bind the mapping relationship between SCSI commands and eMMC commands; S2. SCSI private command conversion mechanism: Transmit a custom instruction header (refer to the storage device convention structure) through the SCSI282A command WRITE10 or READ10 to trigger the eMMC private command logic; S3. Non-standard CMD10 status query: Redefine the eMMC CMD10 command as a status query instruction directly responded by hardware, the content of which includes private mass production progress information or error codes, replacing the CID reading function in the standard protocol.

[0006] Preferably, the step S2 further includes a protocol conversion logic: Embed CMD23 + CMD25 and a storage device convention instruction header in the SCSI WRITE10 command to generate an eMMC private write command CMD23 + CMD25; when sending the SCSI READ10 command, encapsulate it as an eMMC private read command CMD24 + CMD23 + CMD18, and ensure the integrity of data transmission through the anti-code verification of the verification mechanism.

[0007] Preferably, the hardware trigger mechanism in the step S3 is as follows: After receiving the SCSI command, the controller directly returns the CMD10 query result through the eMMC main control hardware to avoid kernel interruption.

[0008] Preferably, the specific steps of the private command read process in the step S2 are as follows: 1) The host sends a SCSI282A WRITE10 command, and the conversion device generates an eMMC CMD17 / CMD18 request with a custom instruction header attached. 2) The device parses the SCSI command and converts it into an eMMC private write operation CMD23 + CMD25. 3) The host sends a SCSI282A READ10 command, and the conversion device generates an eMMC CMD17 / CMD18 request and directly returns the mass production progress data to the host buffer. 4) This process is used for LLF-related data transfer.

[0009] Preferably, the specific steps of the private command write process in the step S2 are as follows: 1) The host sends a SCSI282A WRITE10 command with a custom instruction header attached. 2) The device parses the SCSI command and converts it into an eMMC private write operation CMD23 + CMD25. 3) The Host obtains the corresponding private command data. 4) This process is used for LLF-related data transfer.

[0010] Preferably, the mass production progress query process in step S3 is as follows: Send SCSI private commands, convert the device to generate eMMC CMD10-related requests, and perform progress / error feedback through the communication protocol agreed upon by the storage device and the Host. [0, 100] represents the mass production progress, and values greater than 100 are mass production-related ErrCodes. The error location corresponding to the mass production can be queried through a list. Querying the relevant registers is returned in real time by the hardware without the need for the underlying firmware to perform relevant interrupt responses, which affects the execution efficiency.

[0011] Compared with the prior art, the beneficial effects of the present invention are as follows: 1. Efficiency optimization: CMD10 is directly responded to by the hardware without the need for frequent intervention by the operating system, reducing the interrupt handling time; 2. Good compatibility: Encapsulate eMMC private commands through SCSI commands to adapt to the hardware of ordinary card readers; 3. High reliability: The verification mechanism (such as inverse code verification) ensures error-free command transmission. Description of the Drawings

[0012] Figure 1 It is the logic block diagram of the SCSI-eMMC protocol conversion and the flowchart of the non-standard CMD10 status query in the present invention. Detailed Embodiments

[0013] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0014] Embodiment 1 An embedded storage chip mass production device based on SCSI and eMMC protocol conversion includes: an SCSI-eMMC private command mapping module, a non-standard CMD10 status query module, and a command verification module; the USB communication protocol layer of the SCSI-eMMC private command mapping module uses the SCSI standard, the CMD10 command response content of the non-standard CMD10 status query module is privately defined mass production progress data, and the command verification module is used to implement the generation of verification headers, inverse code verification, and hardware response mechanisms.

[0015] Embodiment 2 A mass production method for an embedded storage chip mass production device based on SCSI and eMMC protocol conversion, as Figure 1 shown, its core steps include:

[0016] 1. Initialization phase: After the device is initialized, the basic information of the eMMC (CSD, CID, EXTCSD, etc.) is read, and compatibility is verified (CMD8, CMD9, standard CMD10).

[0017] 2. Configure the private command interface and bind the mapping relationship between SCSI commands and eMMC commands.

[0018] 3. SCSI private command conversion mechanism: The custom instruction header (refer to the storage device convention structure) is transmitted through the SCSI282A command WRITE10 or READ10 to trigger the eMMC private command logic.

[0019] Protocol conversion logic: The instruction header agreed upon with the storage device is embedded in the SCSI WRITE10 command to generate the eMMC private write command CMD23 + CMD25.

[0020] When sending the SCSI READ10 command, it is encapsulated as the eMMC private read command CMD24 + CMD23 + CMD18, and the integrity of data transmission is ensured through the anti-code verification of the check mechanism.

[0021] Non-standard CMD10 status query: The eMMC CMD10 command is redefined as a status query instruction directly responded by the hardware, and the content includes private mass production progress information or error codes, replacing the CID reading function in the standard protocol.

[0022] Hardware trigger mechanism: After the controller receives the SCSI command, it directly returns the CMD10 query result through the eMMC main control hardware to avoid kernel interruption.

[0023] Figure 1 The data in the middle refers to: the mass production data that the host needs to obtain, such as progress, exception information, error type.

[0024] The USB protocol refers to: The SCSI standard is used in the USB communication protocol layer.

[0025] The role of the conversion device (protocol conversion device) is as follows: Since not all hosts, such as PCs, can directly send eMMC-related protocol commands, a protocol conversion device is needed to convert devices supported by the PC, such as USB, into eMMC protocol commands.

[0026] Private protocol CMD (private command protocol command), used for private communication instructions defined by the conversion device and the host.

[0027] Public protocol CMD read / write (public command read / write), used for standard public commands defined by the conversion device and the host.

[0028] eMMC protocol: Protocol instructions for the interaction between a device and an eMMC storage.

[0029] Storage device: Used to store data. The MCU on the storage device needs to be mass-produced first. The device consists of a storage main control + a storage medium (such as NAND Flash).

[0030] The LLF process refers to: The mass production process of the underlying storage device.

[0031] Private command CMD10RSP. The standard CMD10 in the eMMC protocol is used to obtain the CID. Here, it represents the private usage to obtain information related to the underlying LLF Flow.

[0032] Example 3 The mass production progress query process is as follows: Private command read process 1. The host sends a SCSI282AWRITE10 command, and the conversion device generates an eMMCCMD17 / CMD18 request, attaching a custom instruction header. 2. The device parses the SCSI command and converts it into an eMMC private write operation CMD23 + CMD25. 3. The host sends a SCSI282AREAD10 command, and the conversion device generates an eMMCCMD17 / CMD18 request, directly returning the mass production progress data to the host buffer. 4. This process is used for LLF-related data transfer.

[0033] Private command write process 1. The host sends a SCSI282AWRITE10 command, attaching a custom instruction header. 2. The device parses the SCSI command and converts it into an eMMC private write operation CMD23 + CMD25. 3. The Host obtains the corresponding private command data. 4. This process is used for LLF-related data transfer.

[0034] Query process: Send a SCSI private command, and the conversion device generates an eMMCCMD10-related request. Progress / error feedback is carried out through the communication protocol agreed upon by the storage device and the Host. [0, 100] is the mass production progress, and greater than 100 is the mass production-related ErrCode. The error location of the corresponding mass production can be queried through a list. The relevant registers for query are returned in real time by the hardware, without the need for the underlying firmware to perform relevant interrupt responses, which affects the execution efficiency.

[0035] Finally, it should be noted that: The above are only the preferred embodiments of the present invention and are not used to limit the present invention. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements for some of the technical features. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims

1. An embedded storage chip mass production device based on SCSI and eMMC protocol conversion, characterized in that: Including: SCSI-eMMC private command mapping module, non-standard CMD10 status query module and command verification module; The USB communication protocol layer of the SCSI-eMMC private command mapping module uses the SCSI standard. The CMD10 command response content of the non-standard CMD10 status query module is privately defined mass production progress data. The command verification module is used to implement checksum generation, one's complement verification and hardware response mechanism.

2. A mass production method for an embedded storage chip mass production device based on SCSI and eMMC protocol conversion as described in claim 1, characterized in that: Including the following steps: S1. Initialization stage: After the device is initialized, read the eMMC basic information, verify the compatibility, configure the private command interface, and bind the mapping relationship between SCSI commands and eMMC commands; S2. SCSI private command conversion mechanism: Transmit a custom instruction header through the SCSI282A command WRITE10 or READ10 to trigger the eMMC private command logic; S3. Non-standard CMD10 status query: Redefine the eMMC CMD10 command as a status query instruction directly responded by the hardware, and the content includes private mass production progress information or error codes, replacing the CID reading function in the standard protocol.

3. The mass production method of the embedded storage chip mass production device based on SCSI and eMMC protocol conversion according to claim 2, characterized in that: The step S2 also includes a protocol conversion logic: Embed CMD23+CMD25 and a storage device agreement instruction header in the SCSI WRITE10 command to generate an eMMC private write command CMD23+CMD25; When sending the SCSI READ10 command, encapsulate it as an eMMC private read command CMD24+CMD23+CMD18, and ensure the integrity of data transmission through one's complement verification of the verification mechanism.

4. The mass production method of the embedded storage chip mass production device based on SCSI and eMMC protocol conversion according to claim 2, characterized in that: The hardware trigger mechanism in the step S3 is as follows: After the controller receives the SCSI command, directly return the CMD10 query result through the eMMC main control hardware to avoid kernel interruption.

5. The mass production method of the embedded storage chip mass production device based on the SCSI and eMMC protocol conversion according to claim 2, characterized in that: The specific steps of the private command read process in the step S2 are as follows: 1) The host sends a SCSI282A WRITE10 command, and the conversion device generates an eMMC CMD17 / CMD18 request with a custom instruction header attached. 2) The device parses the SCSI command and converts it into an eMMC private write operation CMD23+CMD25; 3) The host sends a SCSI282A READ10 command, and the conversion device generates an eMMC CMD17 / CMD18 request and directly returns the mass production progress data to the host buffer; 4) This process is used for LLF-related data transfer.

6. The mass production method of the embedded storage chip mass production device based on the SCSI and eMMC protocol conversion according to claim 2, characterized in that: The specific steps of the private command write process in the step S2 are as follows: 1) The host sends a SCSI282A WRITE10 command with a custom instruction header attached; 2) The device parses the SCSI command and converts it into an eMMC private write operation CMD23+CMD25; 3) The Host obtains the corresponding private command data; 4) This process is used for LLF-related data transfer.

7. The mass production method of the mass production equipment of the embedded storage chip based on the SCSI and eMMC protocol conversion according to claim 2, wherein: The mass production progress query process in step S3 is as follows: Send a SCSI private command, convert the device to generate an eMMC CMD10 related request, and perform progress / error feedback through the communication protocol agreed upon by the storage device and the Host. [0, 100] represents the mass production progress, and a value greater than 100 represents a mass production related ErrCode. The error location corresponding to the mass production can be queried through a list. The relevant register is returned in real time by the hardware, and no relevant interrupt response is required from the underlying firmware, which affects the execution efficiency.

Images