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

Abstract

The present invention discloses an embedded storage chip mass production device and method 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 contains privately defined mass production progress data, and the command verification module is used to implement a checksum header generation, reverse code verification, and hardware response mechanism. The present invention optimizes efficiency: CMD10 is responded to directly by hardware, eliminating the need for frequent operating system intervention and reducing interrupt processing time; provides excellent compatibility: eMMC private commands are encapsulated through SCSI commands, adapting to common card reader hardware; and provides high reliability: the reverse code verification of the verification mechanism ensures correct command transmission.

Description

TECHNICAL FIELD

[0001] The application 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 suitable for the scene of batch production through a USB to eMMC card reader. BACKGROUND

[0002] In the prior art, when mass producing embedded storage chips (such as eMMC), the Host usually needs to rely on frequent underlying interrupt triggering to obtain device states (such as mass production progress, error codes, etc.) when converting the eMMC protocol, which results in low efficiency and high resource occupancy, especially when processing high-concurrency mass production tasks, which significantly affects performance. SUMMARY

[0003] In order to solve the defects and deficiencies existing in the prior art, the application provides an embedded storage chip mass production device and method based on SCSI and eMMC protocol conversion, which has the following efficiency optimization: CMD10 is directly responded by hardware, without frequent intervention of the operating system, reducing interrupt processing time; good compatibility: encapsulating eMMC private commands through SCSI commands, adapting to ordinary card reader hardware; high reliability: verification mechanism (such as reverse code verification) ensures error-free command transmission.

[0004] To achieve the above purpose, the application provides the following technical scheme: 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 state query module and a command verification module; the USB communication protocol layer of the SCSI-eMMC private command mapping module uses 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 to realize verification header generation, reverse code verification and hardware response mechanism.

[0005] A mass production method of an embedded storage chip mass production device based on SCSI and eMMC protocol conversion, comprising the following steps:

[0006] S1. Initialization phase: after device initialization, read eMMC basic information (CSD, CID, EXTCSD, etc.), verify compatibility (CMD8, CMD9, standard CMD10), configure private command interface, and bind the mapping relationship between SCSI commands and eMMC commands;

[0007] S2. SCSI private command conversion mechanism: transmit a custom instruction header (reference storage device agreement structure) through SCSI282A command WRITE10 or READ10 to trigger eMMC private command logic;

[0008] S3. Non-standard CMD10 status query: redefining eMMC CMD10 command as a status query instruction directly responded by hardware, containing private mass production progress information or error code, instead of CID reading function in standard protocol.

[0009] Preferably, the step S2 further comprises protocol conversion logic: embedding CMD23+CMD25 and storage device agreed instruction header in SCSIWRITE10 command to generate eMMC private write command CMD23+CMD25; when sending SCSIREAD10 command, encapsulating as eMMC private read command CMD24+CMD23+CMD18, and ensuring data transmission integrity through verification mechanism reverse code verification.

[0010] Preferably, the hardware triggering mechanism in the step S3 is as follows: after receiving SCSI command, the controller directly returns CMD10 query result through eMMC master hardware, avoiding kernel interruption.

[0011] Preferably, the specific steps of the private command read process in the step S2 are as follows:

[0012] 1) The host sends SCSI282AWRITE10 command, and the conversion device generates eMMC CMD17 / CMD18 request with a custom instruction header;

[0013] 2) The device parses SCSI command and converts it into eMMC private write operation CMD23+CMD25;

[0014] 3) The host sends SCSI282AREAD10 command, and the conversion device generates eMMC CMD17 / CMD18 request to directly return mass production progress data to the host buffer;

[0015] 4) This process is used for LLF related data transmission.

[0016] Preferably, the specific steps of the private command write process in the step S2 are as follows:

[0017] 1) The host sends SCSI282AWRITE10 command with a custom instruction header;

[0018] 2) The device parses SCSI command and converts it into eMMC private write operation CMD23+CMD25;

[0019] 3) The host obtains corresponding private command data;

[0020] 4) This process is used for LLF related data transmission.

[0021] Preferably, the progress query process in step S3 is as follows: a SCSI private command is sent, the conversion device generates an eMMC CMD10 related request, progress / error feedback is performed through a communication protocol agreed by the storage device and the host, [0, 100] is the production progress, greater than 100 is a production related ErrCode, and the error position corresponding to the production can be queried through a list. The related register is returned by hardware in real time, and the underlying firmware does not need to respond to related interrupts, thereby affecting the execution efficiency.

[0022] Compared with the prior art, the beneficial effects of the present application are:

[0023] 1. Efficiency optimization: CMD10 is directly responded by hardware, without frequent intervention of the operating system, and the interrupt processing time is reduced.

[0024] 2. Good compatibility: the eMMC private command is encapsulated through the SCSI command, and the ordinary card reader hardware is adapted.

[0025] 3. High reliability: the check mechanism (such as the inverse code verification) ensures that the command transmission is error-free. BRIEF DESCRIPTION OF DRAWINGS

[0026] Figure 1 The figure is a logical block diagram of the SCSI-eMMC protocol conversion in the present application and a non-standard CMD10 state query flowchart. DETAILED DESCRIPTION

[0027] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present application.

[0028] Embodiment 1: An embedded storage chip production device based on SCSI and eMMC protocol conversion, comprising: a SCSI-eMMC private command mapping module, a non-standard CMD10 state query module and a command check module; the USB communication protocol layer of the SCSI-eMMC private command mapping module uses SCSI standard, the CMD10 command response content of the non-standard CMD10 state query module is private defined production progress data, and the command check module is used for implementing check head generation, inverse code verification and hardware response mechanism.

[0029] Embodiment 2: A production method of an embedded storage chip production device based on SCSI and eMMC protocol conversion, as shown in Figure 1 The core steps include:

[0030] 1. Initialization phase: after the device is initialized, read the eMMC basic information (CSD, CID, EXTCSD, etc.), verify compatibility (CMD8, CMD9, standard CMD10).

[0031] 2. Configure the mapping relationship between SCSI command and eMMC command.

[0032] 3. SCSI private command conversion mechanism: transmit custom instruction header (reference storage device agreement structure) through SCSI 282A command WRITE10 or READ10 to trigger eMMC private command logic.

[0033] Protocol conversion logic: embed the storage device agreed instruction header in SCSI WRITE10 command to generate eMMC private write command CMD23+CMD25.

[0034] When sending SCSI READ10 command, encapsulate it as eMMC private read command CMD24+CMD23+CMD18, and verify the data transmission integrity through the reverse code verification mechanism.

[0035] Non-standard CMD10 state query: redefine eMMC CMD10 command as a state query instruction directly responded by hardware, which contains private mass production progress information or error code, instead of the CID reading function in the standard protocol.

[0036] Hardware triggering mechanism: the controller receives SCSI command and directly returns CMD10 query result through eMMC master hardware to avoid kernel interruption.

[0037] Figure 1 Data refers to: the mass production data that the host needs to obtain, such as progress, abnormal information, and error type.

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

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

[0040] Private protocol CMD (private command protocol command) is used to define the private communication instruction of the conversion device and the host.

[0041] Public protocol CMD read / write (public command read / write) is used to define the standard public command of the conversion device and the host.

[0042] eMMC protocol: protocol instruction for device and eMMC storage to interact.

[0043] Storage device: for storing data, the mcu on the storage device needs to be mass produced first, and the device is composed of storage master and storage medium (such as NAND Flash).

[0044] LLF flow refers to: bottom layer storage device mass production flow.

[0045] Private command CMD10RSP, standard CMD10 in eMMC protocol is used to obtain CID, which indicates private usage to obtain relevant information of bottom layer LLF flow.

[0046] Embodiment 3 mass production progress query flow is as follows:

[0047] Private command read flow 1. The host sends SCSI282A WRITE10 command, and the conversion device generates eMMC CMD17 / CMD18 request, with a custom instruction header. 2. The device parses the SCSI command and converts it into eMMC private write operation CMD23+CMD25. 3. The host sends SCSI282A READ10 command, and the conversion device generates eMMC CMD17 / CMD18 request, and directly returns the mass production progress data to the host buffer. 4. This flow is used for LLF related data transfer.

[0048] Private command write flow 1. The host sends SCSI282A WRITE10 command, with a custom instruction header. 2. The device parses the SCSI command and converts it into eMMC private write operation CMD23+CMD25. 3. The host gets the corresponding private command data 4. This flow is used for LLF related data transfer.

[0049] Query flow: send SCSI private command, and the conversion device generates eMMC CMD10 related request, and the progress / error feedback is carried out through the communication protocol agreed by the storage device and the host, [0, 100] is the mass production progress, and greater than 100 is the mass production related ErrCode, which can be queried through the list to obtain the error position of the corresponding mass production. The relevant register is returned by hardware in real time, and there is no need for the bottom layer firmware to respond to the relevant interruption, which affects the execution efficiency.

[0050] Finally, it should be noted that: the above only for the preferred embodiments of the present application, and not for limiting the present application, although the present application has been described in detail with reference to the foregoing embodiments, for those skilled in the art, it still can modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacement for part of the technical features. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. A method for mass production of embedded storage chips based on SCSI and eMMC protocol conversion, characterized by: The mass production equipment used in this mass production method includes: 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 check header generation, inverse code verification, and hardware response mechanism; The mass production method includes the following steps: S1. Initialization phase: After the device is initialized, it reads basic eMMC information, verifies compatibility, configures the private command interface, and binds the mapping relationship between SCSI commands and eMMC commands. S2. SCSI private command conversion mechanism: Transmits a custom instruction header via the SCSI282A command WRITE10 or READ10 to trigger the eMMC private command logic; S3. Non-standard CMD10 status query: The eMMCCMD10 command is redefined as a status query instruction that the hardware directly responds to. The content contains proprietary mass production progress information or error codes, replacing the CID reading function in the standard protocol. The specific steps of the private command reading process in step S2 are as follows: 1) The host sends a SCSI282AWRITE10 command, and the conversion device generates an eMMCCMD17 / CMD18 request with a custom instruction header. 2) The device parses the SCSI command and converts it into the eMMC private write operation CMD23+CMD25; 3) The host sends a SCSI282AREAD10 command, and the conversion device generates an eMMCCMD17 / CMD18 request and directly returns the mass production progress data to the host buffer; 4) This process is used for LLF related data transmission; The specific steps of the private command writing process in step S2 are as follows: 1) The host sends a SCSI282AWRITE10 command with a custom instruction header; 2) The device parses the SCSI command and converts it into the eMMC private write operation CMD23+CMD25; 3) The host obtains the corresponding private command data; 4) This process is used for LLF related data transmission.

2. The method for mass production of embedded storage chips based on SCSI and eMMC protocol conversion according to claim 1, characterized in that: The step S2 also includes protocol conversion logic: CMD23+CMD25 is embedded in the SCSIWRITE10 command and the storage device agreed instruction header is generated to generate the eMMC private write command CMD23+CMD25; when the SCSIREAD10 command is sent, it is encapsulated as the eMMC private read command CMD24+CMD23+CMD18, and the data transmission integrity is ensured by the verification mechanism reverse code verification.

3. The method for mass production of embedded storage chips based on SCSI and eMMC protocol conversion according to claim 1, characterized in that: The hardware trigger mechanism in step S3 is as follows: after receiving the SCSI command, the controller directly returns the CMD10 query result through the eMMC master hardware to avoid kernel interruption.

4. The method for mass production of embedded storage chips based on SCSI and eMMC protocol conversion according to claim 1, characterized in that: The mass production progress query process in step S3 is as follows: a SCSI private command is sent, the conversion device generates an eMMCCMD10 related request, and progress / error feedback is provided 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 represent mass production-related ErrCodes. The error location corresponding to the mass production can be queried through a list, and the query of the relevant registers is returned by the hardware in real time, without the need for the underlying firmware to respond to related interrupts, which affects execution efficiency.

Images