Efficient DFT implementation method and system based on script control

Abstract

The invention relates to the technical field of testability design, in particular to an efficient DFT implementation method and system based on script control, and the method comprises the steps: receiving a to-be-recognized step parameter and a to-be-recognized module parameter, judging whether the to-be-recognized step parameter is a preset step parameter, if the to-be-recognized step parameter is a link insertion step parameter, carrying out link insertion operation to obtain a link insertion folder, and if the to-be-recognized step parameter is a link insertion step parameter, carrying out link insertion operation; and if the to-be-identified step parameters are verification step parameters, performing formal verification operation to obtain a verification folder, if the to-be-identified step parameters are test step parameters, performing test excitation generation operation to obtain a test folder, and if the to-be-identified step parameters are not preset step parameters, generating an input error signal. According to the invention, the efficient operation of the DFT implementation process can be realized, and the efficiency and accuracy of the DFT process are improved.

Description

Technical Field

[0001] The present invention relates to the technical field of design for testability, and in particular to an efficient DFT implementation method and system based on script control. Background Art

[0002] Design for testability (DFT) is a common method for detecting chip defects. By adding DFT scan logic to the chip design, such as scan chains and built-in self-test circuits, the controllability and observability of the internal nodes of the chip can be enhanced, thereby detecting defects caused by the manufacturing process. To ensure the smooth progress of DFT testing, before the chip is tested on the bench, the following three points must be ensured: the scan chain is successfully inserted, the original chip function is not changed after the chain is inserted, and the test stimulus can be generated normally according to the netlist after the chain is inserted. These three points correspond to the following three steps: DFT scan chain insertion, Formality formal verification, and Tmax test stimulus generation. These steps together ensure the effective implementation of DFT design.

[0003] In the existing DFT implementation process, a large number of modules need to be implemented separately for DFT, and the implementation method of each module is different, which makes the existing DFT implementation process operation more cumbersome. First, each implementation step needs to run independently, and each has an independent proprietary script. When the same step is executed on different modules, the script needs to be changed twice according to the characteristics of the module, resulting in a cumbersome implementation process and difficult unified management. This not only increases the complexity of DFT implementation work, but also reduces the implementation efficiency. In addition, due to the lack of a unified scheduling and control mechanism between the steps, information omissions and duplication of work may occur in the DFT implementation process, which further affects the accuracy and efficiency of DFT implementation. Summary of the invention

[0004] The present invention provides an efficient DFT implementation method and system based on script control, the main purpose of which is to achieve efficient operation of the DFT implementation process and improve the efficiency and accuracy of the DFT process.

[0005] To achieve the above object, the present invention provides an efficient DFT implementation method based on script control, comprising:

[0006] Receiving parameters of a step to be identified and parameters of a module to be identified, wherein the parameters of the step to be identified and the parameters of the module to be identified are input by a user;

[0007] Determine whether the step parameters to be identified are preset step parameters, where the preset step parameters include insertion step parameters, verification step parameters, and test step parameters;

[0008] If the step parameter to be identified is a plug-in chain step parameter, the module parameter to be identified is recorded as a plug-in chain module parameter, and based on the plug-in chain step parameter and the plug-in chain module parameter, a plug-in chain operation is performed to obtain a plug-in chain folder;

[0009] If the step parameter to be identified is a verification step parameter, the module parameter to be identified is recorded as a verification module parameter, and a formal verification operation is performed based on the verification step parameter and the verification module parameter to obtain a verification folder;

[0010] If the step parameter to be identified is a test step parameter, the module parameter to be identified is recorded as a test module parameter, and based on the test step parameter and the test module parameter, a test stimulus generation operation is performed to obtain a test folder;

[0011] If the step parameter to be identified is not a preset step parameter, an input error signal is generated, and an efficient DFT implementation based on script control is completed based on the input error signal, the insertion chain folder, the verification folder and the test folder.

[0012] Optionally, performing a plug-in operation based on the plug-in step parameters and the plug-in module parameters to obtain a plug-in folder includes:

[0013] Using the plug-in module parameters, set the preset parameterized path as the plug-in module dedicated path;

[0014] Determine a plug-in chain dedicated script library based on the dedicated path of the plug-in chain module, wherein the plug-in chain dedicated script library includes: a signal link and constraint script, a dedicated print report script, a scan mode setting script, a non-scan unit protection script and a clock gating constraint script;

[0015] The plug-in operation is performed based on the plug-in dedicated script library and the preset plug-in public script library to obtain the plug-in folder.

[0016] Optionally, the plug-in chain common script library includes: running core number control script, report file and intermediate file output path control script, netlist reading script, RTL reading script, process library reading script, print format parameter control script, plug-in chain and clock gating style parameter selection script, special mode parameter control script, special mode instruction control script, plug-in chain control script and DRC check control script.

[0017] Optionally, the plug-in operation is performed based on the plug-in dedicated script library and the preset plug-in public script library to obtain the plug-in folder, including:

[0018] Set up the plug-in chain configuration environment based on running the core count control script and the process library reading script;

[0019] In the plug-in chain configuration environment, the plug-in chain operation file is read according to the netlist read-in script or the RTL read-in script, wherein the plug-in chain operation file includes: an RLT code file or a plug-in chain netlist file;

[0020] Based on the plug-in chain public script library, the original plug-in chain report folder and the original plug-in chain result folder are obtained;

[0021] Use the DRC check control script to perform DRC check and obtain the pre-chaining test report;

[0022] According to the signal link and constraint script, the dedicated print report script, the scan mode setting script, the non-scan unit protection script, the clock gating constraint script, the print format parameter control script, the plug-in and clock gating style parameter selection script and the plug-in control script, the plug-in operation is performed, and after the plug-in operation is completed, a DRC check is performed to obtain a post-plug-in test report;

[0023] The chain insertion operation file is stored in the original chain insertion report folder to obtain a chain insertion report folder, and the pre-chain insertion test report and the post-chain insertion test report are stored in the original chain insertion result folder to obtain a chain insertion result folder;

[0024] The insertion chain report folder and the insertion chain result folder are summarized to obtain the original insertion chain folder, the insertion chain execution date is obtained, and the original insertion chain folder is named based on the insertion chain execution date, the insertion chain step parameters and the insertion chain module parameters to obtain the insertion chain folder.

[0025] Optionally, the obtaining of the original plug-in report folder and the original plug-in result folder based on the plug-in common script library includes:

[0026] Based on the report file and intermediate file output path control script, set the print report path and comparison point path;

[0027] The printing report path is set to a preset report folder to obtain an original plug-in report folder;

[0028] If a special plug-in chain is included in the plug-in chain module corresponding to the plug-in chain module parameters, a special printing path is set based on the special mode parameter control script and the special mode instruction control script, and the comparison point path and the special printing path are set in a preset result folder to obtain the original plug-in chain result folder.

[0029] Optionally, performing a formal verification operation based on the verification step parameters and the verification module parameters to obtain a verification folder includes:

[0030] Using the verification module parameters, set the parameterized path to the verification module-specific path;

[0031] Determine a verification module database based on the verification module dedicated path, wherein the verification module database includes: a pre-chaining netlist, a post-chaining netlist, and a comparison point file;

[0032] Determine a verification common script library for the verification step parameters, wherein the verification common script library includes: a core count control script, a report file and intermediate file output path control script, a netlist read-in script, an RTL read-in script, a comparison point file read-in script, a process library read-in script, and an execution comparison instruction control script;

[0033] Formal verification is performed according to the verification common script library and the verification module database to obtain a verification folder.

[0034] Optionally, performing formal verification according to the verification common script library and the verification module database to obtain a verification folder includes:

[0035] Set up the verification configuration environment based on running the core count control script and the process library reading script;

[0036] In the verification configuration environment, according to the netlist reading script, the RTL reading script and the comparison point file reading script, the verification operation file is read in the verification module database, wherein the verification operation file includes: a netlist file before chain insertion, a netlist file after chain insertion and a comparison point file;

[0037] Based on the report file and the intermediate file output path control script, the original verification report folder and the original verification result folder are obtained;

[0038] Use the execution comparison instruction control script to perform formal verification and obtain a formal verification report;

[0039] The verification operation file is stored in the original verification report folder to obtain a verification report folder, and the formal verification report is stored in the original verification result folder to obtain a verification result folder;

[0040] The verification report folder and the verification result folder are aggregated to obtain an original verification folder, the verification execution date is obtained, and based on the verification execution date, verification step parameters and verification module parameters, the original verification folder is named to obtain a verification folder.

[0041] Optionally, the test stimulus generation operation is performed based on the test step parameters and the test module parameters to obtain a test folder, including:

[0042] Using the test module parameters, setting the parameterized path as a test module-specific path;

[0043] Determine a test-specific database based on the test module-specific path, wherein the test-specific database includes: a pre-chaining netlist, a post-chaining netlist, a constraint file, and a protocol file, and the protocol file includes scan chain information;

[0044] Determine a test common script library for the test step parameters, wherein the test common script library includes: a core count control script, a report file and intermediate file output path control script, a netlist read-in script, a protocol file read-in script, a TetraMAX work environment setting script, a TetraMAX model building script, a stimulus generation parameter control script, a boundary constraint read-in control script, a DRC check control script, a stimulus generation control script, and a coverage analysis control script;

[0045] The test stimulus generation operation is performed according to the test common script library and the test dedicated database to obtain a test folder.

[0046] Optionally, performing a test stimulus generation operation according to the test common script library and the test dedicated database to obtain a test folder includes:

[0047] Set up the test configuration environment based on running the core count control script and the process library reading script;

[0048] Under the test configuration environment, reading the test netlist file, the test protocol file and the test constraint file into the test-specific database according to the netlist reading script, the protocol file reading script and the boundary constraint reading control script respectively;

[0049] Based on the report file and the intermediate file output path control script, the original test report folder, the original test result folder and the original test constraint folder are obtained;

[0050] According to the DRC check control script, perform DRC detection to obtain a test DRC report;

[0051] Set test vector parameters based on TetraMAX working environment setting script, TetraMAX model building script and stimulus generation parameter control script;

[0052] Generate a stimulus test report according to the test vector parameters and by generating a stimulus control script and a coverage analysis control script;

[0053] The test netlist file is stored in the original test report folder to obtain a test report folder, the test protocol file and the test constraint file are stored in the original test constraint folder to obtain a test constraint folder, and the stimulus test report and the test DRC report are stored in the original test result folder to obtain a test result folder;

[0054] The test report folder, the test constraint folder and the test result folder are aggregated to obtain an original test folder, the test execution date is acquired, and based on the test execution date, the test step parameters and the test module parameters, the original test folder is named to obtain a test folder.

[0055] To achieve the above object, the present invention also provides an efficient DFT implementation system based on script control, comprising:

[0056] A plug-in operation execution module, used for recording the module parameters to be identified as plug-in module parameters when the step parameters to be identified are plug-in step parameters, and performing a plug-in operation based on the plug-in step parameters and the plug-in module parameters to obtain a plug-in folder;

[0057] A formal verification execution module, used for recording the module parameters to be identified as verification module parameters when the step parameters to be identified are verification step parameters, and performing a formal verification operation based on the verification step parameters and the verification module parameters to obtain a verification folder;

[0058] A test stimulus generation module, used for recording the module parameters to be identified as test module parameters when the step parameters to be identified are test step parameters, and performing a test stimulus generation operation based on the test step parameters and the test module parameters to obtain a test folder;

[0059] The control module is used to generate an input error signal when the step parameter to be identified is not a preset step parameter, and to complete an efficient DFT implementation based on script control based on the input error signal, the insertion chain folder, the verification folder and the test folder.

[0060] In order to solve the above problem, the present invention further provides an electronic device, the electronic device comprising:

[0061] A memory storing at least one instruction;

[0062] The processor executes the instructions stored in the memory to implement the above-mentioned efficient DFT implementation method based on script control.

[0063] In order to solve the above problem, the present invention also provides a computer-readable storage medium, in which at least one instruction is stored. The at least one instruction is executed by a processor in an electronic device to implement the above-mentioned efficient DFT implementation method based on script control.

[0064] The present invention solves the problem described in the background technology. The present invention first receives the parameters of the step to be identified and the parameters of the module to be identified input by the user. This user-driven parameter input method enables the DFT process to be dynamically adjusted according to specific needs, thereby adapting to different design scenarios and goals. Then, the present invention realizes the unified deployment of different steps and different modules by matching and judging the parameters of the step to be identified with the preset step parameters. This process not only simplifies the traditional DFT operation process, but also reduces manual intervention and error probability. In the steps corresponding to the matched parameters of the step to be identified, the present invention further performs specific operations on the module parameters to realize the splitting and modularization of the DFT implementation control script. This modular design greatly improves the operating efficiency of the DFT implementation process, and also makes each step more It is clearer, more independent, and easier to manage and maintain. In addition, the method of the present invention is applicable to various modules, which further simplifies the operating steps of the existing DFT process and significantly improves the efficiency of DFT operations. The present invention processes the scripts and data corresponding to different steps in a proprietary manner, so that when a new data module is incorporated, the necessary script or configuration modifications can be minimized, which not only ensures the efficiency of the DFT implementation process, but also improves the efficiency and accuracy of DFT control. Finally, the present invention standardizes the folders generated by each step, such as the insertion link folder, the verification folder, and the test folder, and stamps them with timestamps. This measure not only improves the simplicity of version control, but also enhances the traceability and reliability of file management, and further improves the overall efficiency of the DFT implementation process. Therefore, the present invention can realize the efficient operation of the DFT implementation process and improve the efficiency and accuracy of the DFT process. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] Figure 1 A flowchart of an efficient DFT implementation method based on script control provided by an embodiment of the present invention;

[0066] Figure 2 A functional module diagram of an efficient DFT implementation system based on script control provided by an embodiment of the present invention;

[0067] Figure 3 A schematic diagram of the structure of an electronic device for implementing the efficient DFT implementation method based on script control provided by an embodiment of the present invention.

[0068] Description of reference numerals:

[0069] 1. Electronic device; 10. Processor; 11. Memory; 12. Bus; 100. Efficient DFT implementation system based on script control; 101. User parameter receiving module; 102. Insert chain operation execution module; 103. Formal verification execution module; 104. Test stimulus generation module; 105. Control module.

[0070] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0071] It should be understood that the specific embodiments described herein are only used to explain the present invention, and are not used to limit the present invention.

[0072] The embodiment of the present application provides an efficient DFT implementation method based on script control. The execution subject of the efficient DFT implementation method based on script control includes but is not limited to at least one of the electronic devices such as a server, a terminal, etc. that can be configured to execute the method provided by the embodiment of the present application. In other words, the efficient DFT implementation method based on script control can be executed by software or hardware installed on a terminal device or a server device, and the software can be a blockchain platform. The server includes but is not limited to: a single server, a server cluster, a cloud server or a cloud server cluster, etc.

[0073] Reference Figure 1 FIG. 1 is a flow chart of an efficient DFT implementation method based on script control provided by an embodiment of the present invention. In this embodiment, the efficient DFT implementation method based on script control includes:

[0074] S1. Receive parameters of a step to be identified and parameters of a module to be identified, wherein the parameters of the step to be identified and the parameters of the module to be identified are input by a user.

[0075] It can be understood that the step parameter to be identified refers to the specific step name in the testability design (DFT) input by the user, and the module parameter to be identified refers to the module name input by the user for the specific testability design.

[0076] Exemplarily, the parameters of the step to be identified and the parameters of the module to be identified input by the user are: insertion chain step parameters and module A, respectively, indicating that the user needs to perform the insertion chain operation in DFT in module A.

[0077] S2. Determine whether the step parameters to be identified are preset step parameters, where the preset step parameters include insertion step parameters, verification step parameters, and test step parameters.

[0078] It can be understood that the preset step parameters refer to the specific step parameter names in the DFT steps set manually, which include: insertion chain step parameters, verification step parameters and test step parameters, among which, the insertion chain step parameters refer to the step name of performing the DFT scan chain insertion operation in the DFT step, the verification step parameters refer to the step name of performing the Formality formal verification operation in the DFT step, and the test step parameters refer to the step name of performing the Tmax test stimulus generation operation in the DFT step.

[0079] S3. If the step parameter to be identified is a plug-in chain step parameter, the module parameter to be identified is recorded as a plug-in chain module parameter, and a plug-in chain operation is performed based on the plug-in chain step parameter and the plug-in chain module parameter to obtain a plug-in chain folder.

[0080] It can be understood that when the parameters of the step to be identified are the plug-in chain step parameters, it means that the user wants to perform a plug-in chain operation on the input module at this time, that is, the module parameters to be identified at this time are plug-in chain module parameters. The plug-in chain operation refers to inserting a scan chain into the chip netlist without changing the chip logic function. The plug-in chain folder refers to the folder obtained after the plug-in chain operation, which contains the netlist file and result file obtained in the plug-in chain operation.

[0081] In detail, the insert chain operation is performed based on the insert chain step parameters and the insert chain module parameters to obtain the insert chain folder, including:

[0082] Using the plug-in module parameters, set the preset parameterized path as the plug-in module dedicated path;

[0083] Determine a plug-in chain dedicated script library based on the dedicated path of the plug-in chain module, wherein the plug-in chain dedicated script library includes: a signal link and constraint script, a dedicated print report script, a scan mode setting script, a non-scan unit protection script and a clock gating constraint script;

[0084] The plug-in operation is performed based on the plug-in dedicated script library and the preset plug-in public script library to obtain the plug-in folder.

[0085] It should be explained that the parameterized path refers to a path containing input parameters, the plug-in module-specific path refers to a parameterized path after the plug-in module parameters are set, and setting the preset parameterized path as the plug-in module-specific path refers to replacing the input parameters in the parameterized path with the plug-in module parameters. The replaced parameterized path is the plug-in module-specific path, and the file where the plug-in module-specific path is located contains a plug-in-specific script library, wherein the plug-in-specific script library refers to the script used for the plug-in step, and the scripts in the plug-in-specific script library should be written by professionals.

[0086] Furthermore, the signal link and constraint script refers to a script used to define and link scan chain signals, and the special print report refers to a script used to generate a report with special printing requirements for a specific module in the chain insertion step, wherein the specific module and the special printing requirements are set manually. The scan mode setting script refers to a script used to define the DFT chain insertion style or special scan mode, wherein the special scan mode is, for example, the OCC mode. The non-scan unit protection script refers to a script used to protect non-scan chain units in the simulation netlist, thereby preventing these units from being affected by the scan chain insertion operation during the chain insertion process. The clock gating constraint script refers to a script used to define and apply clock gating constraints.

[0087] It can be understood that the said plug-in common library refers to a common script library applicable to the plug-in step, wherein the common script library is a script library common to the plug-in step, the formal verification step and the stimulus generation step, and the scripts in the script library are manually written.

[0088] In detail, the plug-in chain common script library includes: running core number control script, report file and intermediate file output path control script, netlist reading script, RTL reading script, process library reading script, print format parameter control script, plug-in chain and clock gating style parameter selection script, special mode parameter control script, special mode instruction control script, plug-in chain control script and DRC check control script.

[0089] It can be understood that the running core number control script refers to a script for setting the maximum number of cores for parallel tasks. The report file and intermediate file output path control script refers to a script for defining the output path of the report file and the intermediate file, such as: DFT report, intermediate netlist, etc. The netlist reading script, RTL reading script and process library reading script refer to the script for loading the netlist file, the script for loading the RLT code file and the script for loading the process library respectively. The print format parameter control script refers to a script for defining the print format of the report and file, which ensures that the generated file meets the specified format requirements. The insertion chain and clock gating style parameter selection script refers to a script for configuring the style and parameters of scan chain insertion and clock gating. The special mode parameter control script refers to a script for defining and configuring the parameters of the special DFT mode, wherein the special DFT mode is, for example, OCC mode, compressed scan mode, etc. The special mode instruction control script refers to a script for generating and managing instructions for the special DFT mode. The insertion chain control script refers to a script for managing and executing scan chain insertion operations, such as: controlling the scan chain insertion process, configuring the parameters of the scan chain, generating the netlist after the scan chain is inserted, etc. The DRC check control script refers to a script used to perform a design rule check (DRC), for example, controlling the process of the DRC check, generating a DRC check report, etc.

[0090] In detail, the plug-in operation is performed based on the plug-in dedicated script library and the preset plug-in public script library to obtain the plug-in folder, including:

[0091] Set up the plug-in chain configuration environment based on running the core count control script and the process library reading script;

[0092] In the plug-in chain configuration environment, the plug-in chain operation file is read according to the netlist read-in script or the RTL read-in script, wherein the plug-in chain operation file includes: an RLT code file or a plug-in chain netlist file;

[0093] Based on the plug-in chain public script library, the original plug-in chain report folder and the original plug-in chain result folder are obtained;

[0094] Use the DRC check control script to perform DRC check and obtain the pre-chaining test report;

[0095] According to the signal link and constraint script, the dedicated print report script, the scan mode setting script, the non-scan unit protection script, the clock gating constraint script, the print format parameter control script, the plug-in and clock gating style parameter selection script and the plug-in control script, the plug-in operation is performed, and after the plug-in operation is completed, a DRC check is performed to obtain a post-plug-in test report;

[0096] The chain insertion operation file is stored in the original chain insertion report folder to obtain a chain insertion report folder, and the pre-chain insertion test report and the post-chain insertion test report are stored in the original chain insertion result folder to obtain a chain insertion result folder;

[0097] The insertion chain report folder and the insertion chain result folder are summarized to obtain the original insertion chain folder, the insertion chain execution date is obtained, and the original insertion chain folder is named based on the insertion chain execution date, the insertion chain step parameters and the insertion chain module parameters to obtain the insertion chain folder.

[0098] It should be explained that the plug-in configuration environment refers to the number of running cores, common parameters and process libraries, the original plug-in report folder refers to a folder that can store report files during the plug-in process, the original plug-in result folder refers to a folder that can store result files during the plug-in process, the pre-plug-in test report refers to a test report obtained after performing a DRC check before plug-in, and the pre-plug-in test report contains a netlist file. The post-plug-in test report refers to a test report obtained after performing a DRC check after plug-in, and the post-plug-in test report contains a netlist file. The plug-in report folder refers to the original plug-in folder containing the plug-in operation file, and the plug-in result folder refers to a folder containing the pre-plug-in test report and the post-plug-in test report. The plug-in execution date refers to the date on which the plug-in operation is currently executed, and the naming of the original plug-in folder refers to naming the file name in the following manner: plug-in step parameters-plug-in module parameters-plug-in execution date.

[0099] In detail, the original plug-in report folder and the original plug-in result folder are obtained based on the plug-in common script library, including:

[0100] Based on the report file and intermediate file output path control script, set the print report path and comparison point path;

[0101] The printing report path is set to a preset report folder to obtain an original plug-in report folder;

[0102] If a special plug-in chain is included in the plug-in chain module corresponding to the plug-in chain module parameters, a special printing path is set based on the special mode parameter control script and the special mode instruction control script, and the comparison point path and the special printing path are set in a preset result folder to obtain the original plug-in chain result folder.

[0103] It is understandable that the print report path refers to the file path where the report file is stored in the insertion chain step. The comparison point path refers to the file path where the comparison point file and the result file are stored in the insertion chain step, wherein the result file is, for example, a DRC test report, etc. The report folder refers to a folder where the report file can be stored, and the folder is an empty folder. The special insertion chain refers to a special insertion chain set manually, such as an OCC insertion chain, etc. The dedicated print path refers to the file path where the result file obtained by executing the special insertion chain is stored. The result folder refers to a folder where the result file can be stored, and the folder is an empty folder.

[0104] It should be explained that the difference between the original plug-in report folder and the report folder is that although the original plug-in report folder is also an empty folder, the folder has a print report path set up, that is, when a report file is generated, the report file will be directly stored in the original plug-in report file according to the print report path.

[0105] S4. If the step parameters to be identified are verification step parameters, the module parameters to be identified are recorded as verification module parameters, and a formal verification operation is performed based on the verification step parameters and the verification module parameters to obtain a verification folder.

[0106] It can be understood that the formal verification operation refers to the logical consistency verification of the netlist before and after the DFT scan chain is inserted. The verification folder refers to the folder obtained after the formal verification operation.

[0107] In detail, the formal verification operation is performed based on the verification step parameters and the verification module parameters to obtain a verification folder, including:

[0108] Using the verification module parameters, set the parameterized path to the verification module-specific path;

[0109] Determine a verification module database based on the verification module dedicated path, wherein the verification module database includes: a pre-chaining netlist, a post-chaining netlist, and a comparison point file;

[0110] Determine a verification common script library for the verification step parameters, wherein the verification common script library includes: a core count control script, a report file and intermediate file output path control script, a netlist read-in script, an RTL read-in script, a comparison point file read-in script, a process library read-in script, and an execution comparison instruction control script;

[0111] Formal verification is performed according to the verification common script library and the verification module database to obtain a verification folder.

[0112] It can be understood that the verification module dedicated path refers to the parameterized path after the verification module parameters are set. The step of setting the parameterized path as the verification module dedicated path by using the verification module parameters is the same as the step of setting the preset parameterized path as the verification module dedicated path by using the insertion chain module parameters, and will not be repeated here. The verification module database refers to the file library corresponding to the verification module dedicated path. The insertion chain netlist and the post-insertion chain netlist refer to the netlist file before the insertion chain and the netlist file after the insertion chain of the module corresponding to the verification module parameters in the insertion chain step respectively. The comparison point file refers to the comparison point file obtained in the insertion chain step. The execution comparison instruction control script refers to the script for performing the design comparison operation in the formal verification step. The verification public script library refers to the public script library applicable to the formal verification step.

[0113] In detail, the formal verification is performed according to the verification common script library and the verification module database to obtain a verification folder, including:

[0114] Set up the verification configuration environment based on running the core count control script and the process library reading script;

[0115] In the verification configuration environment, according to the netlist reading script, the RTL reading script and the comparison point file reading script, the verification operation file is read in the verification module database, wherein the verification operation file includes: a netlist file before chain insertion, a netlist file after chain insertion and a comparison point file;

[0116] Based on the report file and the intermediate file output path control script, the original verification report folder and the original verification result folder are obtained;

[0117] Use the execution comparison instruction to control the script to perform formal verification and obtain a formal verification report;

[0118] The verification operation file is stored in the original verification report folder to obtain a verification report folder, and the formal verification report is stored in the original verification result folder to obtain a verification result folder;

[0119] The verification report folder and the verification result folder are aggregated to obtain an original verification folder, the verification execution date is obtained, and based on the verification execution date, verification step parameters and verification module parameters, the original verification folder is named to obtain a verification folder.

[0120] It is understandable that the verification configuration environment refers to the number of running cores, common parameters and process libraries in the formal verification step. The original verification report folder refers to a folder that can store report files in the formal verification process, and the original verification result folder refers to a folder that can store result files in the formal verification process. The formal verification report refers to the result report obtained after formal verification. The verification report folder refers to the original verification report folder after storing the verification operation file, and the verification result folder refers to the original verification result folder after storing the formal verification report. The verification execution date refers to the date when the formal verification operation is performed. The step of naming the original verification folder is the same as the above-mentioned step of naming the original plug-in chain folder, which will not be repeated here.

[0121] S5. If the step parameter to be identified is a test step parameter, the module parameter to be identified is recorded as a test module parameter, and based on the test step parameter and the test module parameter, a test stimulus generation operation is performed to obtain a test folder.

[0122] It can be understood that the test stimulus generation operation refers to an operation for generating test stimulus, which can help designers quickly verify problems in the scan chain so as to shorten the design verification cycle. The test folder refers to a folder obtained after the test stimulus generation operation, and the test stimulus operation can be performed using the Tmax tool, wherein the full name of Tmax is TetraMAX, which is developed by Synopsys and is a tool for automatically generating test stimulus for DFT, which has multiple functions such as test vector generation, fault simulation and coverage analysis.

[0123] In detail, the test stimulus generation operation is performed based on the test step parameters and the test module parameters to obtain a test folder, including:

[0124] Using the test module parameters, setting the parameterized path as a test module-specific path;

[0125] Determine a test-specific database based on the test module-specific path, wherein the test-specific database includes: a pre-chaining netlist, a post-chaining netlist, a constraint file, and a protocol file, and the protocol file includes scan chain information;

[0126] Determine a test common script library for the test step parameters, wherein the test common script library includes: a core count control script, a report file and intermediate file output path control script, a netlist read-in script, a protocol file read-in script, a TetraMAX work environment setting script, a TetraMAX model building script, a stimulus generation parameter control script, a boundary constraint read-in control script, a DRC check control script, a stimulus generation control script, and a coverage analysis control script;

[0127] The test stimulus generation operation is performed according to the test common script library and the test dedicated database to obtain a test folder.

[0128] It is understandable that the test module dedicated path refers to the parameterized path after the test module parameters are set. The test dedicated database refers to the file library corresponding to the test module dedicated path. The test public script library refers to the public script library applicable to the test stimulus generation operation.

[0129] In detail, the test stimulus generation operation is performed according to the test common script library and the test dedicated database to obtain a test folder, including:

[0130] Set up the test configuration environment based on running the core count control script and the process library reading script;

[0131] Under the test configuration environment, reading the test netlist file, the test protocol file and the test constraint file into the test-specific database according to the netlist reading script, the protocol file reading script and the boundary constraint reading control script respectively;

[0132] Based on the report file and the intermediate file output path control script, the original test report folder, the original test result folder and the original test constraint folder are obtained;

[0133] According to the DRC check control script, perform DRC detection to obtain a test DRC report;

[0134] Set test vector parameters based on TetraMAX working environment setting script, TetraMAX model building script and stimulus generation parameter control script;

[0135] Generate a stimulus test report according to the test vector parameters and by generating a stimulus control script and a coverage analysis control script;

[0136] The test netlist file is stored in the original test report folder to obtain a test report folder, the test protocol file and the test constraint file are stored in the original test constraint folder to obtain a test constraint folder, and the stimulus test report and the test DRC report are stored in the original test result folder to obtain a test result folder;

[0137] The test report folder, the test constraint folder and the test result folder are aggregated to obtain an original test folder, the test execution date is acquired, and based on the test execution date, the test step parameters and the test module parameters, the original test folder is named to obtain a test folder.

[0138] It should be explained that the test configuration environment refers to the number of running cores, common parameters and process libraries. The original test report folder refers to a folder that can be used to store report files in the test stimulus generation operation, the original test result folder refers to a folder that can be used to store result files in the test stimulus generation operation, and the original test constraint folder refers to a folder that can be used to store constraint files and protocol files in the test stimulus generation operation. The test DRC report refers to a test report obtained after DRC detection. The test vector parameters refer to the generation parameters when the test vector is generated later, and the stimulus test includes refers to the report obtained after the test vector generation is completed. The test includes folder refers to the original test report folder after the test netlist file has been stored, the test constraint folder refers to the folder where the test protocol file and the test constraint file have been stored, and the test result folder refers to the original test result folder where the stimulus test includes and the test DRC report have been stored. The test execution date refers to the date on which the test stimulus generation operation is executed. The step of naming the original test folder is the same as the step of naming the original plug-in chain folder mentioned above, and will not be repeated here.

[0139] S6. If the step parameter to be identified is not a preset step parameter, an input error signal is generated, and an efficient DFT implementation based on script control is completed based on the input error signal, the insertion chain folder, the verification folder and the test folder.

[0140] It is clear that when the parameters of the step to be identified are not the parameters of the predicted step, it means that the user input is incorrect, and an input error signal should be generated to inform the user that the parameter input is incorrect. The DFT operation files are managed uniformly through the plug-in folder, verification folder and test folder. At the same time, these folders will standardize the execution results and stamp them with timestamps to facilitate subsequent version control, thereby simplifying the operation process of traditional DFT.

[0141] The present invention solves the problem described in the background technology. The present invention first receives the parameters of the step to be identified and the parameters of the module to be identified input by the user. This user-driven parameter input method enables the DFT process to be dynamically adjusted according to specific needs, thereby adapting to different design scenarios and goals. Then, the present invention realizes the unified deployment of different steps and different modules by matching and judging the parameters of the step to be identified with the preset step parameters. This process not only simplifies the traditional DFT operation process, but also reduces manual intervention and error probability. In the steps corresponding to the matched parameters of the step to be identified, the present invention further performs specific operations on the module parameters to realize the splitting and modularization of the DFT implementation control script. This modular design greatly improves the operating efficiency of the DFT implementation process, and also makes each step more It is clearer, more independent, and easier to manage and maintain. In addition, the method of the present invention is applicable to various modules, which further simplifies the operating steps of the existing DFT process and significantly improves the efficiency of DFT operations. The present invention processes the scripts and data corresponding to different steps in a proprietary manner, so that when a new data module is incorporated, the necessary script or configuration modifications can be minimized, which not only ensures the efficiency of the DFT implementation process, but also improves the efficiency and accuracy of DFT control. Finally, the present invention standardizes the folders generated by each step, such as the insertion link folder, the verification folder, and the test folder, and stamps them with timestamps. This measure not only improves the simplicity of version control, but also enhances the traceability and reliability of file management, and further improves the overall efficiency of the DFT implementation process. Therefore, the present invention can realize the efficient operation of the DFT implementation process and improve the efficiency and accuracy of the DFT process.

[0142] like Figure 2 , which is a functional module diagram of an efficient DFT implementation system based on script control provided by an embodiment of the present invention.

[0143] The efficient DFT implementation system 100 based on script control of the present invention can be installed in an electronic device. According to the functions implemented, the efficient DFT implementation system 100 based on script control can include a user parameter receiving module 101, a plug-in operation execution module 102, a formal verification execution module 103, a test stimulus generation module 104 and a control module 105. The module of the present invention can also be called a unit, which refers to a series of computer program segments that can be executed by an electronic device processor and can complete fixed functions, which are stored in the memory of the electronic device.

[0144] The user parameter receiving module 101 is used to receive parameters of the step to be identified and parameters of the module to be identified, wherein the parameters of the step to be identified and the parameters of the module to be identified are input by the user;

[0145] The plug-in operation execution module 102 is used for recording the module parameters to be identified as plug-in module parameters when the step parameters to be identified are plug-in step parameters, and performing a plug-in operation based on the plug-in step parameters and the plug-in module parameters to obtain a plug-in folder;

[0146] The formal verification execution module 103 is used for recording the module parameters to be identified as verification module parameters when the step parameters to be identified are verification step parameters, and performing a formal verification operation based on the verification step parameters and the verification module parameters to obtain a verification folder;

[0147] The test stimulus generating module 104 is used to record the module parameters to be identified as test module parameters when the step parameters to be identified are test step parameters, and perform a test stimulus generating operation based on the test step parameters and the test module parameters to obtain a test folder.

[0148] The control module 105 is used to generate an input error signal when the step parameter to be identified is not a preset step parameter, and to complete an efficient DFT implementation based on script control based on the input error signal, the insertion chain folder, the verification folder and the test folder.

[0149] In detail, each module in the script-controlled efficient DFT implementation system 100 in the embodiment of the present invention is used in the same manner as described above. Figure 1 The same technical means as the efficient DFT implementation method based on script control described in , and can produce the same technical effects, will not be repeated here.

[0150] like Figure 3 FIG. 1 is a schematic diagram of the structure of an electronic device for implementing an efficient DFT implementation method based on script control provided by an embodiment of the present invention.

[0151] The electronic device 1 may include a processor 10, a memory 11 and a bus 12, and may also include a computer program stored in the memory 11 and executable on the processor 10, such as a program for an efficient DFT implementation method based on script control.

[0152] The memory 11 includes at least one type of readable storage medium, and the readable storage medium includes flash memory, mobile hard disk, multimedia card, card-type memory (for example, SD or DX memory, etc.), magnetic memory, disk, optical disk, etc. In some embodiments, the memory 11 may be an internal storage unit of the electronic device 1, such as a mobile hard disk of the electronic device 1. In other embodiments, the memory 11 may also be an external storage device of the electronic device 1, such as a plug-in mobile hard disk, a smart memory card (Smart Media Card, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), etc. equipped on the electronic device 1. Further, the memory 11 also includes an internal storage unit of the electronic device 1 and an external storage device. The memory 11 can not only be used to store application software and various types of data installed in the electronic device 1, such as the code of the efficient DFT implementation method program based on script control, but also be used to temporarily store data that has been output or is to be output.

[0153] The processor 10 may be composed of an integrated circuit in some embodiments, for example, a single packaged integrated circuit, or a plurality of packaged integrated circuits with the same or different functions, including one or more central processing units (CPUs), microprocessors, digital processing chips, graphics processors, and combinations of various control chips, etc. The processor 10 is the control core (Control Unit) of the electronic device, and uses various interfaces and lines to connect various components of the entire electronic device, and executes or executes programs or modules (such as script-based efficient DFT implementation method programs, etc.) stored in the memory 11, and calls data stored in the memory 11 to execute various functions of the electronic device 1 and process data.

[0154] The bus 12 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus 12 may be divided into an address bus, a data bus, a control bus, etc. The bus 12 is configured to realize connection and communication between the memory 11 and at least one processor 10, etc.

[0155] Figure 3 Only an electronic device with components is shown, and those skilled in the art will understand that Figure 3The structure shown does not constitute a limitation on the electronic device 1, and may include fewer or more components than shown in the figure, or combine certain components, or arrange the components differently.

[0156] For example, although not shown, the electronic device 1 may also include a power source (such as a battery) for supplying power to each component. Preferably, the power source may be logically connected to the at least one processor 10 through a power management system, so that the power management system can realize functions such as charging management, discharging management, and power consumption management. The power source may also include any components such as one or more DC or AC power sources, recharging systems, power failure detection circuits, power converters or inverters, and power status indicators. The electronic device 1 may also include a variety of sensors, Bluetooth modules, Wi-Fi modules, etc., which will not be repeated here.

[0157] Furthermore, the electronic device 1 may also include a network interface. Optionally, the network interface may include a wired interface and / or a wireless interface (such as a WI-FI interface, a Bluetooth interface, etc.), which is generally used to establish a communication connection between the electronic device 1 and other electronic devices.

[0158] Optionally, the electronic device 1 may further include a user interface, which may be a display, an input unit (such as a keyboard), or a standard wired interface or a wireless interface. Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, and an OLED (Organic Light-Emitting Diode) touch device. The display may also be appropriately referred to as a display screen or a display unit, which is used to display information processed in the electronic device 1 and to display a visual user interface.

[0159] The script-controlled efficient DFT implementation method program stored in the memory 11 of the electronic device 1 is a combination of multiple instructions. When running in the processor 10, it can achieve:

[0160] Receiving parameters of a step to be identified and parameters of a module to be identified, wherein the parameters of the step to be identified and the parameters of the module to be identified are input by a user;

[0161] Determine whether the step parameters to be identified are preset step parameters, where the preset step parameters include insertion step parameters, verification step parameters, and test step parameters;

[0162] If the step parameter to be identified is a plug-in chain step parameter, the module parameter to be identified is recorded as a plug-in chain module parameter, and based on the plug-in chain step parameter and the plug-in chain module parameter, a plug-in chain operation is performed to obtain a plug-in chain folder;

[0163] If the step parameter to be identified is a verification step parameter, the module parameter to be identified is recorded as a verification module parameter, and a formal verification operation is performed based on the verification step parameter and the verification module parameter to obtain a verification folder;

[0164] If the step parameter to be identified is a test step parameter, the module parameter to be identified is recorded as a test module parameter, and based on the test step parameter and the test module parameter, a test stimulus generation operation is performed to obtain a test folder;

[0165] If the step parameter to be identified is not a preset step parameter, an input error signal is generated, and an efficient DFT implementation based on script control is completed based on the input error signal, the insertion chain folder, the verification folder and the test folder.

[0166] Specifically, the specific implementation method of the processor 10 for the above instructions can refer to Figures 1 to 3 The description of the relevant steps in the corresponding embodiments will not be repeated here.

[0167] Furthermore, if the module / unit integrated in the electronic device 1 is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. The computer-readable storage medium can be volatile or non-volatile. For example, the computer-readable medium can include: any entity or system capable of carrying the computer program code, a recording medium, a USB flash drive, a mobile hard disk, a magnetic disk, an optical disk, a computer memory, and a read-only memory (ROM).

[0168] The present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor of an electronic device, the computer program can implement:

[0169] Receiving parameters of a step to be identified and parameters of a module to be identified, wherein the parameters of the step to be identified and the parameters of the module to be identified are input by a user;

[0170] Determine whether the step parameters to be identified are preset step parameters, where the preset step parameters include insertion step parameters, verification step parameters, and test step parameters;

[0171] If the step parameter to be identified is a plug-in chain step parameter, the module parameter to be identified is recorded as a plug-in chain module parameter, and based on the plug-in chain step parameter and the plug-in chain module parameter, a plug-in chain operation is performed to obtain a plug-in chain folder;

[0172] If the step parameter to be identified is a verification step parameter, the module parameter to be identified is recorded as a verification module parameter, and a formal verification operation is performed based on the verification step parameter and the verification module parameter to obtain a verification folder;

[0173] If the step parameter to be identified is a test step parameter, the module parameter to be identified is recorded as a test module parameter, and based on the test step parameter and the test module parameter, a test stimulus generation operation is performed to obtain a test folder;

[0174] If the step parameter to be identified is not a preset step parameter, an input error signal is generated, and an efficient DFT implementation based on script control is completed based on the input error signal, the insertion chain folder, the verification folder and the test folder.

[0175] In the several embodiments provided by the present invention, it should be understood that the disclosed devices, systems and methods can be implemented in other ways. For example, the system embodiments described above are only illustrative, and actual implementation may have other division methods.

[0176] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0177] In addition, each functional module in each embodiment of the present invention may be integrated into one processing unit, each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional modules.

[0178] It is obvious to those skilled in the art that the present invention is not limited to the details of the above exemplary embodiments, and that the present invention can be implemented in other specific forms without departing from the spirit or essential characteristics of the present invention.

[0179] Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the preferred embodiments, those skilled in the art should understand that the technical solution of the present invention can be modified or replaced by equivalents without departing from the spirit and scope of the technical solution of the present invention.

Claims

1. An efficient DFT implementation method based on script control, characterized in that: The method comprises: Receiving parameters of a step to be identified and parameters of a module to be identified, wherein the parameters of the step to be identified and the parameters of the module to be identified are input by a user; Determine whether the step parameters to be identified are preset step parameters, where the preset step parameters include insertion step parameters, verification step parameters, and test step parameters; If the step parameter to be identified is a plug-in chain step parameter, the module parameter to be identified is recorded as a plug-in chain module parameter, and based on the plug-in chain step parameter and the plug-in chain module parameter, a plug-in chain operation is performed to obtain a plug-in chain folder; If the step parameter to be identified is a verification step parameter, the module parameter to be identified is recorded as a verification module parameter, and a formal verification operation is performed based on the verification step parameter and the verification module parameter to obtain a verification folder; If the step parameter to be identified is a test step parameter, the module parameter to be identified is recorded as a test module parameter, and based on the test step parameter and the test module parameter, a test stimulus generation operation is performed to obtain a test folder; If the step parameter to be identified is not a preset step parameter, an input error signal is generated, and an efficient DFT implementation based on script control is completed based on the input error signal, the insertion chain folder, the verification folder and the test folder.

2. The efficient DFT implementation method based on script control as claimed in claim 1, characterized in that: The insert chain operation is performed based on the insert chain step parameters and the insert chain module parameters to obtain the insert chain folder, including: Using the plug-in module parameters, set the preset parameterized path as the plug-in module dedicated path; Determine a plug-in chain dedicated script library based on the dedicated path of the plug-in chain module, wherein the plug-in chain dedicated script library includes: a signal link and constraint script, a dedicated print report script, a scan mode setting script, a non-scan unit protection script and a clock gating constraint script; The plug-in operation is performed based on the plug-in dedicated script library and the preset plug-in public script library to obtain the plug-in folder.

3. The efficient DFT implementation method based on script control as claimed in claim 2, characterized in that: The plug-in chain public script library includes: running core number control script, report file and intermediate file output path control script, netlist reading script, RTL reading script, process library reading script, print format parameter control script, plug-in chain and clock gating style parameter selection script, special mode parameter control script, special mode instruction control script, plug-in chain control script and DRC check control script.

4. The efficient DFT implementation method based on script control as claimed in claim 3, characterized in that: The plug-in operation is performed based on the plug-in dedicated script library and the preset plug-in public script library to obtain the plug-in folder, including: Set up the plug-in chain configuration environment based on running the core count control script and the process library reading script; In the plug-in chain configuration environment, the plug-in chain operation file is read according to the netlist read-in script or the RTL read-in script, wherein the plug-in chain operation file includes: an RLT code file or a plug-in chain netlist file; Based on the plug-in chain public script library, the original plug-in chain report folder and the original plug-in chain result folder are obtained; Use the DRC check control script to perform DRC check and obtain the pre-chaining test report; According to the signal link and constraint script, the dedicated print report script, the scan mode setting script, the non-scan unit protection script, the clock gating constraint script, the print format parameter control script, the plug-in and clock gating style parameter selection script and the plug-in control script, the plug-in operation is performed, and after the plug-in operation is completed, a DRC check is performed to obtain a post-plug-in test report; The chain insertion operation file is stored in the original chain insertion report folder to obtain a chain insertion report folder, and the pre-chain insertion test report and the post-chain insertion test report are stored in the original chain insertion result folder to obtain a chain insertion result folder; The insertion chain report folder and the insertion chain result folder are summarized to obtain the original insertion chain folder, the insertion chain execution date is obtained, and the original insertion chain folder is named based on the insertion chain execution date, the insertion chain step parameters and the insertion chain module parameters to obtain the insertion chain folder.

5. The efficient DFT implementation method based on script control as claimed in claim 4, characterized in that: The method of obtaining the original plug-in chain report folder and the original plug-in chain result folder based on the plug-in chain public script library includes: Based on the report file and intermediate file output path control script, set the print report path and comparison point path; The printing report path is set to a preset report folder to obtain an original plug-in report folder; If a special plug-in chain is included in the plug-in chain module corresponding to the plug-in chain module parameters, a special printing path is set based on the special mode parameter control script and the special mode instruction control script, and the comparison point path and the special printing path are set in a preset result folder to obtain the original plug-in chain result folder.

6. The efficient DFT implementation method based on script control as claimed in claim 1, characterized in that: The method performs a formal verification operation based on the verification step parameters and the verification module parameters to obtain a verification folder, including: Using the verification module parameters, set the parameterized path to the verification module-specific path; Determine a verification module database based on the verification module dedicated path, wherein the verification module database includes: a pre-chaining netlist, a post-chaining netlist, and a comparison point file; Determine a verification common script library for the verification step parameters, wherein the verification common script library includes: a core count control script, a report file and intermediate file output path control script, a netlist read-in script, an RTL read-in script, a comparison point file read-in script, a process library read-in script, and an execution comparison instruction control script; Formal verification is performed according to the verification common script library and the verification module database to obtain a verification folder.

7. The efficient DFT implementation method based on script control as claimed in claim 6, characterized in that: The method of performing formal verification according to the verification common script library and the verification module database to obtain a verification folder includes: Set up the verification configuration environment based on running the core count control script and the process library reading script; In the verification configuration environment, according to the netlist reading script, the RTL reading script and the comparison point file reading script, the verification operation file is read in the verification module database, wherein the verification operation file includes: a netlist file before chain insertion, a netlist file after chain insertion and a comparison point file; Based on the report file and the intermediate file output path control script, the original verification report folder and the original verification result folder are obtained; Use the execution comparison instruction control script to perform formal verification and obtain a formal verification report; The verification operation file is stored in the original verification report folder to obtain a verification report folder, and the formal verification report is stored in the original verification result folder to obtain a verification result folder; The verification report folder and the verification result folder are aggregated to obtain an original verification folder, the verification execution date is obtained, and based on the verification execution date, verification step parameters and verification module parameters, the original verification folder is named to obtain a verification folder.

8. The method for realizing efficient DFT based on script control as claimed in claim 1, characterized in that: The test stimulus generation operation is performed based on the test step parameters and the test module parameters to obtain a test folder, including: Using the test module parameters, setting the parameterized path as a test module-specific path; Determine a test-specific database based on the test module-specific path, wherein the test-specific database includes: a pre-chaining netlist, a post-chaining netlist, a constraint file, and a protocol file, and the protocol file includes scan chain information; Determine a test common script library for the test step parameters, wherein the test common script library includes: a core count control script, a report file and intermediate file output path control script, a netlist read-in script, a protocol file read-in script, a TetraMAX work environment setting script, a TetraMAX model building script, a stimulus generation parameter control script, a boundary constraint read-in control script, a DRC check control script, a stimulus generation control script, and a coverage analysis control script; The test stimulus generation operation is performed according to the test common script library and the test dedicated database to obtain a test folder.

9. The method for realizing efficient DFT based on script control as claimed in claim 8, characterized in that: The step of performing a test stimulus generation operation according to the test common script library and the test dedicated database to obtain a test folder includes: Set up the test configuration environment based on running the core count control script and the process library reading script; Under the test configuration environment, reading the test netlist file, the test protocol file and the test constraint file into the test-specific database according to the netlist reading script, the protocol file reading script and the boundary constraint reading control script respectively; Based on the report file and the intermediate file output path control script, the original test report folder, the original test result folder and the original test constraint folder are obtained; According to the DRC check control script, perform DRC detection to obtain a test DRC report; Set test vector parameters based on TetraMAX working environment setting script, TetraMAX model building script and stimulus generation parameter control script; Generate a stimulus test report according to the test vector parameters and by generating a stimulus control script and a coverage analysis control script; The test netlist file is stored in the original test report folder to obtain a test report folder, the test protocol file and the test constraint file are stored in the original test constraint folder to obtain a test constraint folder, and the stimulus test report and the test DRC report are stored in the original test result folder to obtain a test result folder; The test report folder, the test constraint folder and the test result folder are aggregated to obtain an original test folder, the test execution date is acquired, and based on the test execution date, the test step parameters and the test module parameters, the original test folder is named to obtain a test folder.

10. A system using the script-controlled efficient DFT implementation method according to claim 1, characterized in that: The system comprises: A user parameter receiving module, used for receiving parameters of the step to be identified and parameters of the module to be identified, wherein the parameters of the step to be identified and the parameters of the module to be identified are both input by the user; A plug-in operation execution module, used for recording the module parameters to be identified as plug-in module parameters when the step parameters to be identified are plug-in step parameters, and performing a plug-in operation based on the plug-in step parameters and the plug-in module parameters to obtain a plug-in folder; A formal verification execution module, used for recording the module parameters to be identified as verification module parameters when the step parameters to be identified are verification step parameters, and performing a formal verification operation based on the verification step parameters and the verification module parameters to obtain a verification folder; A test stimulus generation module, used for recording the module parameters to be identified as test module parameters when the step parameters to be identified are test step parameters, and performing a test stimulus generation operation based on the test step parameters and the test module parameters to obtain a test folder; The control module is used to generate an input error signal when the step parameter to be identified is not a preset step parameter, and to complete an efficient DFT implementation based on script control based on the input error signal, the insertion chain folder, the verification folder and the test folder.

Images