An efficient chip production method

Abstract

The present invention provides an efficient chip production method, which configures the program files corresponding to all processing steps of the chip to be processed into an updating mobile disk. When the program files in the test frame need to be updated, the updating mobile disk is inserted into the test frame, and the program files are updated to the test frame through the boot program of the threshold on the test frame. The user is supported to select the program file of the current process for execution in the form of a menu. During the entire process, the program file update does not require professional implementation, and ordinary users can select it through the menu, which reduces the execution difficulty and improves the execution efficiency.

Description

Technical Field

[0001] The present invention relates to the technical field of chip production and testing, and in particular to an efficient chip production method. Background Art

[0002] Chips go through multiple steps during production, such as binding, burning, and testing, and each step requires a different program file. To improve production efficiency, a test rack is typically used. The program files for the corresponding steps are stored in the test rack's memory, and chips of the same model are placed in the same test rack, allowing simultaneous burning, testing, and other operations on multiple chips. However, because different chip models have different contact arrangements, the corresponding test point locations and chip sizes vary, requiring different test racks for each chip and making them incompatible. In practice, if M types of chips need to be tested simultaneously, and each chip requires N steps, the number of test racks required is M x N. This requires a significant amount of space to house the test racks, resulting in significant waste of space. Furthermore, frequent chip removal and assembly reduces work efficiency and increases the probability of chip damage.

[0003] In order to reduce and improve the test efficiency, the solution commonly adopted in the existing technology is to move each chip that needs to change the test process together with the test rack to the server where the program file is stored, and replace the program file in each test rack through a burner connected to the server without replacing the test rack; however, this method is also time-consuming and labor-intensive, and replacing the program files in the test rack requires professional personnel to operate, which is very inconvenient and affects the overall execution efficiency of chip processing. Summary of the Invention

[0004] In order to solve the problem in the prior art that, for different chip processing procedures, it is necessary to frequently replace the program files in the test rack, which affects the overall execution efficiency of chip processing, the present invention provides an efficient chip production method, which can complete all processes requiring the use of the test rack without frequently moving the test rack, and can complete the replacement of program files corresponding to different processes without the need for specialized technicians, thereby greatly improving the execution efficiency.

[0005] The technical solution of the present invention is as follows: an efficient chip production method, characterized in that it includes the following steps:

[0006] S1: Construct a processing program directory, wherein the processing program directory includes: a primary directory and a secondary directory, wherein the secondary directory is set under the primary directory;

[0007] The name of the first-level directory is the chip name of the chip to be processed;

[0008] The names of the secondary directories are respectively the names of all the processing steps of the chip to be processed; the program files corresponding to each step are placed in the corresponding secondary directory;

[0009] S2: putting the processing program directory into the root directory of the U disk, and making the directory information of the processing program directory into a configuration file and putting it into the root directory of the U disk to make a mobile disk for updating;

[0010] S3: Setting a boot program in the control chip of the test stand;

[0011] S4: placing the chip to be processed on the test rack;

[0012] When the program file in the test rack needs to be updated, the update removable disk is inserted into the test rack;

[0013] S5: After the test rack is powered on after being shut down, the boot program will scan the USB interface. If the update removable disk is found, step S7 will be executed; otherwise, step S6 will be executed.

[0014] S6: The boot program detects the file storage area of ​​the test rack;

[0015] If there is a program file in the file storage area, step S8 is implemented;

[0016] Otherwise, stop working and issue a warning message;

[0017] S7: Compare the file version in the update removable disk with the file version in the file storage area;

[0018] If the file storage area is empty, or the file version in the update removable disk is updated, copy or replace the updated program file in the update removable disk to the test rack file area; implement step S8;

[0019] Otherwise, perform step S8;

[0020] S8: The boot program reads the configuration file in the test rack file area and displays all secondary directory names in a menu format;

[0021] S9: Reading the user's selection on the menu, decrypting the corresponding program file in the test rack file area according to the secondary directory name selected by the user, and copying the decrypted program file to the storage area of ​​the control chip of the test rack;

[0022] S10: The boot program jumps to the first address of the storage area of ​​the control chip, starts the program file, and guides the operation of subsequent processing steps.

[0023] It is further characterized by:

[0024] In step S1, before storing the program files in the secondary directory, each program file needs to be named; the name of the program file includes: directory information, version information, and CRC checksum information;

[0025] In step S5, when the boot program detects the USB interface of the test stand, it determines whether the update removable disk is present through the configuration file;

[0026] When the boot program detects that there is a USB disk on the USB interface and the configuration file exists in the USB disk, it is determined that the update removable disk is found;

[0027] The configuration file includes a chip model field. When the boot program scans the update removable disk and finds the configuration file, it reads the chip model field in the update removable disk and compares it with the model of the chip to be processed. If the two are inconsistent, a warning is issued and subsequent operations are stopped.

[0028] In step S7, it is determined whether the file version in the update removable disk has been updated, and the following steps are performed:

[0029] b1: comparing the configuration file in the test rack file area with the configuration file in the update removable disk;

[0030] If the two configuration files are exactly the same, go to step b3;

[0031] Otherwise, determine that all files are updated and implement step b2;

[0032] b2: Overwriting all program files and configuration files in the update mobile disk to the test rack file area;

[0033] b3: Read the program files in the test rack file area one by one, and find the program files in the corresponding secondary directory in the update mobile disk according to the directory information in the file name;

[0034] b4: Compare the version information in the two program file names;

[0035] If the version information of the program file in the test rack file area is different from the version information of the program file in the update removable disk, it is determined that the single program file has been updated, and step b5 is implemented;

[0036] Otherwise, go to step b6;

[0037] b5: copy the program files in the update removable disk to the corresponding secondary directory in the test rack file area to overwrite the original files; execute step b6;

[0038] b6: cyclically executing steps b3 to b5 until all program files in the test rack file area are compared, and then stopping the operation;

[0039] It also includes a CRC check process, which specifically includes the following steps:

[0040] c1: the boot program copies each program file from the update removable disk to the secondary directory of the test rack file area, and then reads the copied program file, which is recorded as a file to be verified;

[0041] c2: Perform CRC check calculation on the file to be checked to obtain: the value to be checked;

[0042] c3: Compare the value to be checked with the CRC check information in the file name of the file to be checked;

[0043] If the two are consistent, it means the program file is updated successfully;

[0044] Otherwise, the boot program issues a warning message indicating update failure;

[0045] In step S1, the program file corresponding to each process is encrypted and then placed in the corresponding secondary directory;

[0046] The test frame file area is implemented based on an external storage chip.

[0047] The present invention provides an efficient chip production method, which configures the program files corresponding to all processing steps of the chip to be processed into an updating mobile disk. When the program files in the test frame need to be updated, the updating mobile disk is inserted into the test frame, and the program files are updated to the test frame through the boot program of the threshold on the test frame. The user is supported to select the program file of the current process for execution in the form of a menu. During the whole process, the update of the program file does not require the implementation of professional personnel, and ordinary users can select it through the menu, which reduces the execution difficulty and improves the execution efficiency. At the same time, when the file version in the updating mobile disk is updated, the update of the program file is also automatically completed through the boot program, further improving the operation efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] Figure 1 This is a schematic diagram of the workflow of the boot program in this application;

[0049] Figure 2 Update the flowchart for the program file;

[0050] Figure 3 A diagram showing the resource allocation structure for the test rack file area. DETAILED DESCRIPTION

[0051] like Figure 1 As shown, the present invention includes an efficient chip production method, which includes the following steps.

[0052] S1: Build a processing program directory, which includes a primary directory and a secondary directory, with the secondary directory being located under the primary directory.

[0053] The name of the first-level directory is the chip name of the chip to be processed;

[0054] The secondary directories are named after all the processing procedures of the chip to be processed; the program files corresponding to each procedure are placed in the corresponding secondary directory.

[0055] Before storing a program file in a secondary directory, each program file needs to be named; the program file name includes directory information, version information, and CRC checksum information. In the technical solution of this application, the basic information of the program file is recorded by the program file name for subsequent calculations, eliminating the need to set up additional fields to store the basic information of the program file, saving system space. At the same time, during calculations, the data fields used for calculations can be found by reading the program file name, reducing the complexity of the calculations.

[0056] The configuration file includes a chip model field. When the boot program scans the mobile disk for updates and finds the configuration file, it reads the chip model field in the mobile disk for updates and compares it with the model of the chip to be processed. If the two are inconsistent, a warning is issued and subsequent operations are stopped. Because different models of chips have different chip contact arrangements, the corresponding test point positions and chip sizes are different, so the test racks for each chip are different, so the test racks are not compatible with each other. In this application, the chip model field is set in the configuration file to prevent the occurrence of program file copy errors, thereby avoiding the problem of damage to the tool or the chip being misoperated, resulting in a decrease in yield. At the same time, the boot program automatically compares the model in the configuration file with the chip model preset in the test rack, which also improves execution efficiency.

[0057] The program files, configuration files, and program file information corresponding to each process are all stored in the form of binary files. In step S1, the program files corresponding to each process are encrypted and then placed in the corresponding secondary directory, reducing the possibility of file tampering and avoiding the problem of program file leakage.

[0058] S2: Put the processing program directory into the root directory of the U disk, and make the directory information of the processing program directory into a configuration file and put it into the root directory of the U disk to make it: a mobile disk for updating.

[0059] S3: Set the boot program in the control chip of the test stand.

[0060] S4: Place the chip to be processed on the test rack;

[0061] When the program files in the test frame need to be updated, the mobile disk for updating is inserted into the test frame.

[0062] Specific times when files in the test rack need to be updated include: placing a program file into the test rack for the first time after initialization, or updating the content of a program file generated by a subsequent process.

[0063] S5: After the test rack is powered on again after being shut down, the boot program will scan the USB interface. If a removable disk for updating is found, step S7 will be executed; otherwise, step S6 will be executed.

[0064] When the boot program detects the USB interface of the test frame, it determines whether there is a mobile disk for update through the configuration file;

[0065] When the boot program detects that there is a USB disk on the USB interface and there is a configuration file in the USB disk, it is determined that a mobile disk for update is found.

[0066] S6: The boot program detects the file storage area of ​​the test frame;

[0067] If there is a program file in the file storage area, step S8 is implemented;

[0068] Otherwise, the machine stops working and issues a warning message.

[0069] S7: Compare the file version in the update removable disk with the file version in the file storage area;

[0070] If the file storage area is empty, or the file version in the update removable disk is updated, the updated program file in the update removable disk is copied or replaced into the test rack file area; step S8 is implemented;

[0071] Otherwise, execute step S8.

[0072] like Figure 2 As shown, in step S7, it is determined whether the file version in the update removable disk has been updated, and the following steps are performed:

[0073] b1: Compare the configuration file in the test rack file area with the configuration file in the update removable disk;

[0074] If the two configuration files are exactly the same, go to step b3;

[0075] Otherwise, determine that all files are updated and implement step b2;

[0076] b2: Overwrite all program files and configuration files in the update removable disk to the test rack file area;

[0077] b3: Read the program files in the test rack file area one by one, and find the program file in the corresponding secondary directory in the mobile disk for update according to the directory information in the file name;

[0078] b4: Compare the version information in the two program file names;

[0079] If the version information of the program file in the test rack file area is different from the version information of the program file in the update removable disk, or in a specific implementation, the version information can be digitally marked and the size of the version data can be judged to determine whether a version update has occurred, then it is determined that the single file has been updated and step b5 is implemented;

[0080] Otherwise, go to step b6;

[0081] b5: Copy the program files in the update removable disk to the corresponding secondary directory in the test rack file area to overwrite the original files; proceed to step b6;

[0082] b6: Loop through steps b3 to b5 until all program files in the test rack file area are compared, and then stop the operation.

[0083] The technical solution of this application also includes a CRC check process, which specifically includes the following steps:

[0084] c1: The boot program copies each program file from the update removable disk to the secondary directory of the test bench file area, and then reads the copied program file, which is recorded as the file to be verified;

[0085] c2: Perform CRC check calculation on the file to be checked and obtain the value to be checked;

[0086] c3: Compare the value to be checked with the CRC checksum information in the file name to be checked;

[0087] If the two are consistent, it means the program file is updated successfully;

[0088] Otherwise, the boot program issues a warning message indicating that the update failed.

[0089] In this application, CRC check is used to ensure the integrity of program files, effectively reducing the risk of errors in program copying or saving.

[0090] S8: The boot program reads the configuration file in the test rack file area and displays all secondary directory names in menu form. The menu information is displayed on the LCD screen.

[0091] like Figure 3 Figure 2 shows the resource allocation structure of the test rack's file area. The file directory information in the configuration file includes information for programs A through E. Based on the file directory information in the configuration file, the boot program generates a menu displayed on the test rack's LCD screen, displaying the program information for programs A through E for the user to select. The menu displays the names of both the primary and secondary directories, allowing the operator to easily select a program for a specific chip type and function using a single keystroke.

[0092] S9: Read the user's selection on the menu, decrypt the corresponding program file in the test rack file area according to the secondary directory name selected by the user, and copy it to the flash storage area of ​​the control chip of the test rack.

[0093] During specific implementation, menu information is displayed on the LCD screen, and the user selects the required program file through the buttons on the test stand and presses the confirmation button. The boot program decrypts the program in the test stand file area and copies the decrypted program to the flash storage area of ​​the test stand control chip. Usually, the test stand file area on the test stand is implemented in the form of an external memory chip (such as a flash memory chip with model W25Q128). The number of entries in the menu generated by the boot program is related to the number of programs in the processing process and the storage capacity of the external memory chip. In specific applications, an external memory chip of appropriate capacity can be selected as needed to adapt it to the number of program files and the menu size. By implementing the test stand file area through an external memory chip, the volume of the test stand file area can be flexibly increased or decreased according to the needs of the process, thereby controlling the overall cost. At the same time, in this application, the program files stored in the test stand file area are encrypted, and the program files are only decrypted when the boot program copies the program files to the microcontroller, thereby preventing direct reading of the external memory chip, which may lead to program leakage.

[0094] S10: The boot program jumps to the first address of the storage area of ​​the control chip, starts the program file, and guides the operation of subsequent processing steps.

[0095] After using the technical solution of the present invention, after the test stand is powered on, the boot program first checks whether the update mobile disk based on the U disk is inserted. If the test stand is inserted with the update mobile disk, it checks whether there is a program that needs to be updated through the program file information. If it is found that there is a program that needs to be updated, the latest program is copied to the area of ​​the test stand file area where the original program is located; if the program does not need to be updated or the update mobile disk is not inserted, the boot program forms a menu system by loading the configuration file and displays it on the LCD screen of the test stand; the operator selects the required program by pressing a button, and the boot program decrypts the program in the test stand file area and copies it to the fixed area of ​​the single-chip microcomputer. The boot program jumps to the first address of the area and starts the program. In this application, the program used is first encrypted and saved in the external memory chip of the test stand board. The boot program selects the corresponding program through the menu, so that the switching program does not need to attach other hardware such as burners, and the operator can freely change the program by himself, and the method is simple and direct. Not only can the operator switch the test stand program simply and efficiently, but the number of test stands can be effectively reduced, saving costs. And it greatly improves operating efficiency.

Claims

1. An efficient chip production method, characterized in that: It includes the following steps: S1: Construct a processing program directory, wherein the processing program directory includes: a primary directory and a secondary directory, wherein the secondary directory is set under the primary directory; The name of the first-level directory is the chip name of the chip to be processed; The names of the secondary directories are respectively the names of all the processing steps of the chip to be processed; the program files corresponding to each step are placed in the corresponding secondary directory; S2: putting the processing program directory into the root directory of the U disk, and making the directory information of the processing program directory into a configuration file and putting it into the root directory of the U disk to make a mobile disk for updating; S3: Set the boot program in the control chip of the test stand; S4: placing the chip to be processed on the test rack; When the program file in the test rack needs to be updated, the update removable disk is inserted into the test rack; S5: After the test rack is powered on after being shut down, the boot program will scan the USB interface. If the update removable disk is found, step S7 will be executed; otherwise, step S6 will be executed. S6: The boot program detects the file storage area of ​​the test rack; If there is a program file in the file storage area, step S8 is implemented; Otherwise, stop working and issue a warning message; S7: Compare the file version in the update removable disk with the file version in the file storage area; If the file storage area is empty, or the file version in the update removable disk is updated, copy or replace the updated program file in the update removable disk to the test rack file area; implement step S8; Otherwise, perform step S8; S8: The boot program reads the configuration file in the test rack file area and displays all secondary directory names in a menu format; S9: Reading the user's selection on the menu, decrypting the corresponding program file in the test rack file area according to the secondary directory name selected by the user, and copying the decrypted program file to the storage area of ​​the control chip of the test rack; S10: The boot program jumps to the first address of the storage area of ​​the control chip, starts the program file, and guides the operation of subsequent processing steps.

2. The efficient chip production method according to claim 1, characterized in that: In step S1, before storing the program files in the secondary directory, each program file needs to be named; The name of the program file includes: directory information, version information, and CRC check information.

3. The efficient chip production method according to claim 1, characterized in that: In step S5, when the boot program detects the USB interface of the test stand, it determines whether the update removable disk is present through the configuration file; When the boot program detects that there is a U disk on the USB interface and the configuration file exists in the U disk, it is determined that the update mobile disk is found.

4. The efficient chip production method according to claim 1, characterized in that: The configuration file includes a chip model field. When the boot program scans the update mobile disk and finds the configuration file, it reads the chip model field in the update mobile disk and compares it with the model of the chip to be processed. If the two are inconsistent, a warning is issued and subsequent operations are stopped.

5. The efficient chip production method according to claim 2, characterized in that: In step S7, it is determined whether the file version in the update removable disk has been updated, and the following steps are performed: b1: comparing the configuration file in the test rack file area with the configuration file in the update removable disk; If the two configuration files are exactly the same, go to step b3; Otherwise, determine that all files are updated and implement step b2; b2: Overwriting all program files and configuration files in the update mobile disk to the test rack file area; b3: Read the program files in the test rack file area one by one, and find the program files in the corresponding secondary directory in the update mobile disk according to the directory information in the file name; b4: Compare the version information in the two program file names; If the version information of the program file in the test rack file area is different from the version information of the program file in the update removable disk, it is determined that the single program file has been updated, and step b5 is implemented; Otherwise, go to step b6; b5: copy the program files in the update removable disk to the corresponding secondary directory in the test rack file area to overwrite the original files; execute step b6; b6: Execute steps b3 to b5 in a loop until all program files in the test rack file area are compared, and then stop the operation.

6. The efficient chip production method according to claim 2, characterized in that: It also includes a CRC check process, which specifically includes the following steps: c1: the boot program copies each program file from the update removable disk to the secondary directory of the test rack file area, and then reads the copied program file, which is recorded as a file to be verified; c2: Perform CRC check calculation on the file to be checked to obtain: the value to be checked; c3: Compare the value to be checked with the CRC check information in the file name of the file to be checked; If the two are consistent, it means the program file is updated successfully; Otherwise, the boot program issues a warning message indicating update failure.

7. The efficient chip production method according to claim 1, characterized in that: In step S1, the program file corresponding to each process is encrypted and then placed in the corresponding secondary directory.

8. The efficient chip production method according to claim 1, characterized in that: The test frame file area is implemented based on an external storage chip.

Images