Code coverage rate filtering file generation method, system and equipment and medium

By obtaining the design information to be tested and filtering configuration information, the target code coverage filter file is generated, which solves the problem of low efficiency in generating coverage filter files in large-scale and system-level design, and realizes automated coverage filter files Generate, improving chip verification efficiency.

CN119046239APending Publication Date: 2024-11-29SHANDONG YUNHAI GUOCHUANG CLOUD COMPUTING EQUIP IND INNOVATION CENT CO LTD

Patent Information

Application Number
CN202411045973.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-31
Publication Date
2024-11-29

AI Technical Summary

Technical Problem

Existing chip verification tools have performance and efficiency limitations when dealing with large-scale, system-level, and complex designs to be tested. Especially when generating coverage filter files, they need to manually add filter statements, and cannot adapt to the current module level. Transfer to system-level verification workflow.

Method used

By obtaining the design information to be tested and filtering configuration information, including path hierarchy information, signal statement location, filtering rules and target function options, the target code coverage filter file is generated, and the merge, split and inheritance functions are supported, and the filter file is automatically determined and generated. .

Benefits of technology

It improves the efficiency of the generation of coverage filter files, adapts to large-scale, system-level, and complex designs to be tested, simplifies the chip verification process, and improves verification efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119046239A_ABST
    Figure CN119046239A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of chip verification, and mainly relates to a code coverage rate filtering file generation method, system and device and a medium, and the method comprises the steps: obtaining to-be-tested design information; the to-be-tested design information comprises path level information and a signal statement position; the path hierarchical information is used for indicating a hierarchical structure of the to-be-tested design; obtaining filtering configuration information, wherein the filtering configuration information comprises a filtering rule and / or a target function option; the target function options comprise a merging option, a splitting option and an inheriting option; and according to the filtering configuration information, the path level information and the signal statement position, generating a target code coverage rate filtering file. According to the embodiment of the invention, the method is suitable for an application scene of cooperative verification of a large-scale, system-level and complex to-be-tested design, and improves the efficiency of chip verification.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of chip verification technology, and mainly to a method, system, device and medium for generating a code coverage filter file. Background Art

[0002] Chip verification is an important part of the chip development process. As the scale of chips grows, the complexity of chip verification also increases. There are many different ways to measure whether the verification results are reliable. One of the most important is coverage analysis. Simulation tools in the current industry all have coverage collection and filtering functions. Taking the most common VCS tool (Verilog Compiler Simulator, a simulation tool) as an example, when paired with debugging platforms such as DVE (Debugging and Verification Environment) or Verdi (Visual Environment for Reverse Debugging), it can provide strong support for coverage analysis. These tools can display coverage results through a graphical interface, helping engineers quickly locate uncovered code areas, and also provide coverage filtering functions.

[0003] Although relevant coverage analysis tools play an important role in chip front-end verification, they still have performance and efficiency limitations when dealing with large-scale, system-level, and complex DUTs. For example, when performing module-level verification on large-scale, system-level, and complex DUTs, technicians can only add filter statements one by one manually, which is not suitable for the current module-level to system-level verification workflow commonly used in the industry. Therefore, how to generate filter files to improve verification efficiency is a difficult problem that needs to be solved. Summary of the invention

[0004] One of the purposes of the present application is to propose a method for generating a code coverage filter file to solve or at least partially solve the problems in the related art. The second purpose of the present application is to provide a code coverage filter file generation system, the third purpose of the present application is to provide an electronic device, and the fourth purpose of the present application is to provide a medium.

[0005] In order to achieve the above purpose, the technical solution of this application is as follows:

[0006] A method for generating a code coverage filtering file, comprising:

[0007] Acquire the design information to be tested; the design information to be tested includes: path hierarchy information and signal statement position; the path hierarchy information is used to indicate the hierarchical structure of the design to be tested;

[0008] Acquire filtering configuration information, the filtering configuration information including: filtering rules and / or target function options; the target function options including: merging options, splitting options, and inheritance options;

[0009] According to the filtering configuration information, the target code coverage filtering file is generated based on the path hierarchy information and the signal statement position.

[0010] Optionally, the filtering configuration information includes: target function options;

[0011] The step of generating a target code coverage filtering file according to the filtering configuration information, the path hierarchy information and the signal statement position includes:

[0012] In a case where the filtering configuration information includes the merging option, obtaining a plurality of filtering files to be merged;

[0013] The filter files to be merged are merged according to the path hierarchy information and the signal statement positions to generate a target code coverage filter file.

[0014] Optionally, generating a target code coverage filter file according to the filtering configuration information, the path hierarchy information and the signal statement position includes:

[0015] In the case where the filtering configuration information includes the splitting option, obtaining the identifiers of the filtering file to be split and the target module;

[0016] The target code coverage filter file of the target module is split out from the filter file to be split according to the path hierarchy information, the signal statement position, and the identifier.

[0017] Optionally, generating a target code coverage filter file according to the filtering configuration information, the path hierarchy information and the signal statement position includes:

[0018] In the case where the filtering configuration information includes the inheritance option, obtaining an inherited filtering file and an inheriting filtering file;

[0019] According to the path hierarchy information and the signal statement position, the filter statement in the inherited filter file is formatted;

[0020] A target code coverage filter file is generated according to the format-converted filter statement and the inherited filter file.

[0021] Optionally, the filtering configuration information includes: filtering rules;

[0022] The step of generating a target code coverage filtering file according to the filtering configuration information, the path hierarchy information and the signal statement position includes:

[0023] According to the filtering rules, based on the path hierarchy information and the signal statement position, determining the signals to be filtered in the design information to be tested;

[0024] Generate a corresponding filtering statement according to the signal to be filtered;

[0025] The filtering statements are summarized to generate a target code coverage filtering file.

[0026] Optionally, the filtering configuration information includes: filtering rules and target function options;

[0027] The step of generating a target code coverage filtering file according to the filtering configuration information, the path hierarchy information and the signal statement position includes:

[0028] According to the filtering rules, based on the path hierarchy information and the signal statement position, determining the signals to be filtered in the design information to be tested;

[0029] Generate a corresponding filtering statement according to the signal to be filtered;

[0030] Summarizing the filtering statements to generate a first filtering file;

[0031] In the case where the target function option is the merge option or the inheritance option, generating a target code coverage filter file according to the first filter file and the second filter file; wherein the second filter file is a file uploaded by a user through an input interface in a filter configuration page;

[0032] When the target functional option is the split option, a target code coverage filter file is generated according to the first filter file.

[0033] Optionally, obtaining the design information to be tested includes:

[0034] Obtain the design file to be tested according to the address information of the design to be tested submitted through the user interface;

[0035] The design information to be tested is determined according to the design file to be tested.

[0036] A code coverage filtering file generation system, comprising:

[0037] A first acquisition unit is used to acquire information of the design to be tested; the information of the design to be tested includes: path hierarchy information and signal statement positions; the path hierarchy information is used to indicate the hierarchical structure of the design to be tested;

[0038] A second acquisition unit is used to acquire filtering configuration information, wherein the filtering configuration information includes: filtering rules and / or target function options; the target function options include: merging options, splitting options, and inheritance options;

[0039] A generating unit is used to generate a target code coverage filtering file according to the filtering configuration information, the path hierarchy information and the signal statement position.

[0040] An electronic device comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned method for generating a code coverage filter file when executing the computer program.

[0041] A non-volatile storage medium stores a computer program, which, when executed by a processor, implements the above-mentioned method for generating a code coverage filter file.

[0042] Beneficial effects of this application:

[0043] In the present application, by obtaining the design information to be tested; the design information to be tested includes: path hierarchy information and signal statement position; the path hierarchy information is used to indicate the hierarchical structure of the design to be tested; obtaining the filtering configuration information, the filtering configuration information includes: filtering rules and / or target function options; the target function options include: merging options, splitting options, and inheritance options; according to the filtering configuration information, according to the path hierarchy information and the signal statement position, a target code coverage filtering file is generated. Since the filtering configuration information may include filtering rules and / or target function options, the content to be filtered can be automatically determined from the design information to be tested according to the filtering rules in the filtering configuration information configured by the user to generate a corresponding filtering file; or according to the target function options in the filtering configuration information, according to the path hierarchy and signal statement position of the design to be tested, the filtering statements are merged or split or inherited to generate a corresponding filtering file, which is suitable for various chip verification application scenarios. In this way, the system can output a code coverage filtering file suitable for user needs for large-scale, system-level, and complex designs to be tested, which improves the generation efficiency of the filtering file, thereby facilitating the improvement of chip verification efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0045] Figure 1is a flow chart of a method for generating a code coverage filter file in an embodiment of the present application;

[0046] Figure 2 It is a schematic diagram of the framework of the code coverage filtering file generation system described in one embodiment of the present application.

[0047] Among them, 200 is a code coverage filtering file generation system, 201 is a first acquisition unit, 202 is a second acquisition unit, and 203 is a generation unit. DETAILED DESCRIPTION

[0048] The following will describe the implementation methods of the present application with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present application from the contents disclosed in this specification. The present application can also be implemented or applied through other different specific implementation methods, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present application. It should be understood that the preferred embodiments are only for illustrating the present application, not for limiting the scope of protection of the present application.

[0049] The code coverage filter file is the coverage filter file of the code. The technical solution of the present application is applied to the code coverage filter file generation system, which is configured with a filter configuration page. In the filter configuration page, a variety of preset filter conditions or filter rules are deployed for users to choose. So that according to the user's selection, the signal statements to be filtered are automatically screened out from the design information to be tested, thereby automatically generating a filter file. The user can analyze the coverage of the chip verification according to the filter file. At the same time, the code coverage filter file generation system also provides functional options for splitting, merging or inheriting existing filter files. If the user selects a certain function option in the filter configuration page, and based on actual needs, inputs the filter file required for processing by the function, the input filter file can be processed accordingly in the code coverage filter file generation system to output the filter file required by the user. In this way, the verification efficiency can be improved for large-scale, system-level, and complex designs to be tested.

[0050] Specifically, refer to Figure 1 , Figure 1 This is a flow chart of a method for generating a code coverage filter file in one embodiment of the present application. In one embodiment of the present application, the method for generating a code coverage filter file can be performed in the following steps:

[0051] Step S101, obtaining the design information to be tested;

[0052] The design information to be tested includes: path hierarchy information and signal statement location;

[0053] The path hierarchy information is used to indicate the hierarchical structure of the design to be tested.

[0054] Specifically, the design to be tested is the internal design of the chip, and the design to be tested information is the specific content of the design to be tested. The hierarchical structure of the design to be tested may include system level, subsystem level, module level, submodule level, etc. According to the path hierarchy information, the various hierarchical structures of the design to be tested, as well as the association relationship of each level and the corresponding module name and other information can be determined. Each module includes multiple signal statements, and the signal statements in each hierarchy can be determined by the position of the signal statements. In this way, after obtaining the design to be tested information, the specific internal structure of the design to be tested can be known, so that the system can generate a filter file for the design to be tested.

[0055] In a feasible implementation manner, the obtaining the design information to be tested includes:

[0056] Obtain the design file to be tested according to the address information of the design to be tested submitted through the user interface;

[0057] The design information to be tested is determined according to the design file to be tested.

[0058] Specifically, the system front end can display a user interface so that the user can input the address of the design file to be tested based on the user interface, so that the system can obtain the design file to be tested according to the address information of the design file to be tested submitted by the user interface; based on the file to be tested, perform structure and content analysis, identify modules, branches, statements, etc. one by one, so as to obtain the design information to be tested.

[0059] In this implementation, for different design files to be tested, the design information to be tested can be automatically identified, so as to output the filter file in a targeted manner later, thereby improving the user experience.

[0060] Step S102, obtaining filtering configuration information, the filtering configuration information including: filtering rules and / or target function options; the target function options including: merging options, splitting options, and inheritance options.

[0061] Specifically, after the user enters the filtering configuration information and submits it on the system filtering configuration page, the system can obtain the filtering configuration information. The filtering configuration information may include: filtering rules and / or target function options.

[0062] In this embodiment, different automatic filtering rules are provided for different code coverage categories. The filtering rules include preset filtering rules and custom filtering rules. That is, the system can preset some filtering rules: for example, different automatic filtering rules are provided for different code coverage categories to generate filtering files. In actual applications, users can also add custom filtering rules.

[0063] For example, it automatically filters the dangling bits on ports due to misaligned bit widths, automatically filters ports with fixed connections, automatically filters ports with "XXX" in their names, automatically filters all branch coverage related to the name "XXX" (here XXX is user-defined), etc. It also supports other filtering based on regular matching rules.

[0064] At the same time, for common general interfaces, this application also provides proprietary function filtering. Taking the AMBA (Advanced Microcontroller Bus Architecture) protocol interface as an example, after inputting the function configuration parameters of the AMBA interface of the current module to be tested, all redundant interfaces, bit widths, functions, and code coverage related to the above input functions, such as burst transfer, lock transfer, outstanding transfer, secure transfer, redundant data line bit width, redundant address line bit width, etc., can be filtered. When these general components and protocols are integrated in the system, but these additional functions are not needed due to various practical application requirements, they can be filtered with one click, without the need for users to manually filter signals one by one by consulting relevant documents. In this way, there is no need for users to manually enter filter statements, which improves the efficiency of generating filter files.

[0065] At the same time, in this embodiment, the filtering configuration information also includes target function options, such as a merge option, a split option, and an inheritance option. Specifically, the function corresponding to the merge option is: merging multiple filter files. The function corresponding to the split option is: splitting a filter file into multiple ones. For example, splitting the content required by the user from a filter file. The function corresponding to the inheritance option is: inheriting the filter statements in a filter file to another filter file. The system provides users with the choice of target function options, which can be adapted to large-scale, system-level, and complex designs to be tested. In the process of collaborative verification, the filter files required by the user can be generated with high adaptability based on this target function option. For example, this embodiment is suitable for application scenarios such as converting from module-level verification to system-level verification, multiple users simultaneously verifying a design to be tested, and distributed filter file maintenance. It should be noted that only one function option can be selected at a time.

[0066] Step S103: Generate a target code coverage filtering file according to the filtering configuration information, the path hierarchy information and the signal statement position.

[0067] Specifically, based on the filter configuration information, the user can know which parts of the design to be tested need to be filtered, or which functions to use to process the existing filter files. At this time, the corresponding operations are performed according to the path hierarchy information and the signal statement location (the specific content inside the chip to be tested), and finally, the target code coverage filter file required by the user can be output.

[0068] In this embodiment, by obtaining the design information to be tested; the design information to be tested includes: path hierarchy information and signal statement position; the path hierarchy information is used to indicate the hierarchical structure of the design to be tested; obtaining the filtering configuration information, the filtering configuration information includes: filtering rules and / or target function options; the target function options include: merging options, splitting options, and inheritance options; according to the filtering configuration information, according to the path hierarchy information and the signal statement position, a target code coverage filtering file is generated. Since the filtering configuration information may include filtering rules and / or target function options, the content to be filtered can be automatically determined from the design information to be tested according to the filtering rules in the filtering configuration information configured by the user to generate a corresponding filtering file; or according to the target function options in the filtering configuration information, according to the path hierarchy and signal statement position of the design to be tested, the filtering statements are merged, split, or inherited to generate a corresponding filtering file. In this way, the system can output a code coverage filtering file suitable for user needs for large-scale, system-level, and complex designs to be tested, which improves the generation efficiency of the filtering file, thereby facilitating the improvement of chip verification efficiency.

[0069] In one embodiment of the present application, the filtering configuration information includes: filtering rules, and the above step S103, according to the filtering configuration information, generates a target code coverage filtering file according to the path hierarchy information and the signal statement position, which may specifically include:

[0070] According to the filtering rules, based on the path hierarchy information and the signal statement position, the signals to be filtered in the design information to be tested are determined; according to the signals to be filtered, corresponding filtering statements are generated; and the filtering statements are summarized to generate a target code coverage filtering file.

[0071] Specifically, when the filtering configuration information only includes filtering rules, the signals to be filtered in the design information to be tested are determined according to the filtering rules, path hierarchy information and signal statement positions. According to the signals to be filtered, corresponding filtering statements are generated, thereby generating a target code coverage filtering file.

[0072] For example, the design under test is a common AHB2AXI functional module, whose function is to process the input AHB (Advanced High-performance Bus) data and convert it into AXI (Advanced Extensible Interface) data output with the same frequency.

[0073] During module-level verification, this module does not have lock transfer and secure transfer functions, and the relevant information is input into the filtering script. After sorting, the information input into the script is shown in Table 1:

[0074] AMBA Function Enable / Width AHB ADDR 32 AHB RDATA 32 AHB WDATA 32 AHB LOCK 0 AHB SECURE 0 …… …… ……

[0075] Table 1

[0076] In Table 1, the properties of the AHB interface of this module have the following characteristics: the address and data bit widths are both 32 bits, and lock transfer and secure transfer are not supported. Therefore, the filtering script automatically filters the code coverage of AHB address lines and data lines that exceed 32 bits, as well as the code coverage of ports related to lock transfer and secure transfer, and automatically generates coverage filtering statements as follows (only statements related to the functions mentioned above are shown):

[0077] CHECKSUM: "24935457903511233536"

[0078] INSTANCE:ahb2axi_top_tb.th.dut_inst

[0079] Toggle hlock_o "nethlock_o"

[0080] Toogle hprot_o "net hprot_o[3:0]"

[0081] …………

[0082] In this embodiment, when the filtering configuration information only includes filtering rules, a target code coverage filtering file is quickly generated according to the filtering rules, which is also suitable for large-scale, system-level, and complex designs to be tested, thereby improving user experience.

[0083] Optionally, after entering the system-level verification, if similar signals at different levels appear: for example, the "hprot" signal mentioned above is passed to the top level of other modules through the bus, and the signal "ahb2ahb_target_hlock_i" with a name slightly different from the module-level signal appears, which also needs to be filtered. Then you can use the regular matching filtering function in the automatic filtering to automatically filter the signals that meet the "ahb2axi_*_hlock_*" regular matching formula. Not only that, each filter statement will automatically add the user's ID at the end to mark who provided the filter, so that if an incorrect filter occurs, it is easy to trace the source. The system will also check whether there is a conflict every time a merge occurs. If a conflict occurs in different files to be merged, the conflict will be recorded in the debug log for users to review and solve these conflicts in a targeted manner.

[0084] In one embodiment of the present application, the filter configuration information input by the user includes target function options. In a feasible implementation, the above step S103 generates a target code coverage filter file according to the filter configuration information, the path hierarchy information and the signal statement position, which may specifically include:

[0085] In the case where the filtering configuration information includes the merging option, a plurality of filter files to be merged are obtained; and according to the path hierarchy information and the signal statement positions, the filter files to be merged are merged to generate a target code coverage filter file.

[0086] Specifically, when the user selects a target function option through the filter configuration page, a corresponding input box is displayed below the corresponding selection control of the selected target function option to prompt the user to select the path of the filter file to be executed. In this way, the user can select the corresponding filter file to be processed according to his own needs.

[0087] If the filter configuration information includes a merge option, that is, multiple filter files need to be merged, the filter files to be merged can be obtained, and these filter files to be merged are merged according to the path hierarchy information and the signal statement position to generate a target code coverage filter file.

[0088] When merging, different filter rules for the same statement can be recorded in the debug log, which is used to integrate the coverage filter files distributed to each verification leader in system-level verification or subsystem-level verification.

[0089] In this embodiment, when the filtering configuration information includes a merge option, that is, merging is performed based on user input files, so that the module-level filter files can be merged to generate a global system-level filter file to achieve resource integration, thereby improving the verification efficiency of the design to be tested.

[0090] In another feasible implementation manner, the above step S103, according to the filtering configuration information, the path hierarchy information and the signal statement position, generates a target code coverage filtering file, which may specifically include:

[0091] When the filtering configuration information includes a split option, the identifiers of the filter file to be split and the target module are obtained; and the target code coverage filter file of the target module is split from the filter file to be split according to the path hierarchy information, the signal statement position and the identifier.

[0092] Specifically, if the filtering configuration information includes a split option, the file is split according to the identifier of the filter file to be split and the target module previously input by the user to obtain the target code coverage filter file. For example, based on the identifier of the target module (such as name, number, etc.), combined with the path hierarchy information and the signal statement position and the identifier, the relevant filter statement of the target module is found from the filter file to be split, so that the module-level filter file can be obtained.

[0093] In this embodiment, when the filtering configuration information includes a split option, the required filtering file is generated according to the file to be split and the target module identifier input by the user. In this way, the module-level filtering file can be split from the global system-level filtering file to facilitate the collaborative verification of the technical personnel. At this time, there is no need to load the global system-level filtering file, and only the module-level filtering file needs to be concerned. In this way, the verification efficiency of the design to be tested is improved.

[0094] In another feasible implementation manner, the above step S103, according to the filtering configuration information, the path hierarchy information and the signal statement position, generates a target code coverage filtering file, which may specifically include:

[0095] In the case where the filtering configuration information includes the inheritance option, an inherited filtering file and an inheriting filtering file are obtained; the filtering statements in the inherited filtering file are formatted according to the path hierarchy information and the signal statement positions; and a target code coverage filtering file is generated according to the format-converted filtering statements and the inheriting filtering file.

[0096] Specifically, if the filter configuration information includes an inheritance option, the filter file input by the user is obtained. There are at least two filter files input by the user, a child filter file (inherited filter file) and a parent filter file (inheriting filter file). The parent-child relationship does not represent an inclusion relationship, but can be regarded as a high-low relationship in the hierarchical structure. For example, when using the inheritance function to convert the filter statements in the child filter file (inherited filter file), the filter statements to be inherited are determined based on the path hierarchy information and the signal statement position, and are converted based on the writing format of the level in the parent filter file (inheriting filter file), and then the converted filter statements are migrated to the parent filter file. This inheritance can be the inheritance of a structurally low-level (such as a module-level) filter file to a high-level (such as a system-level) filter file.

[0097] When the user completes the module-level verification and wants to send the module-level coverage filter file to the system-level verification, the inheritance function can be directly enabled to avoid the incompatibility of the filter file caused by the different module-level and system-level hierarchical structures. For example, using the design to be tested in Table 1 above, after the user turns on the inheritance function and enters the module name "ahb2axi", the system script will automatically modify the relevant hierarchical structure in the module-level filter file to the system-level hierarchy.

[0098] The following shows the modified filter statement:

[0099] CHECKSUM: "28138111884115267657"

[0100] INSTANCE:soc_top_tb_th.cpu_subsys_top.ahb2axi_top.th

[0101] Toggle hlock_o"net hlock_o"

[0102] Toogle hprot_o "net hprot_o[3:0]"

[0103] …………

[0104] It can be seen that the "INSTANCE" and "CHECKSUM" containing the hierarchical structure information of the design to be tested have been automatically modified to adapt to the system-level hierarchical structure. In this way, module-level verification engineers can quickly migrate to the system-level verification work environment.

[0105] Following the above implementation, optionally, when the filter configuration information includes the inheritance option, when generating the target code coverage filter file, the inheriting filter file and the inherited filter file among these filter files can be determined according to the priority of each filter file input by the user; the filter statement in the inherited filter file is formatted according to the format in the inheriting filter file; and the converted filter statement is inherited to the inheriting filter file. That is, in this implementation, such inheritance can be the inheritance of a filter file with a low priority to a filter file with a high priority. And its priority can be determined according to the user ID carried by the filter file. For example, the higher the authority corresponding to the user, the higher the priority of its filter file. In this way, the inheriting and inherited filter files can be further determined based on the priority of each filter file, so as to identify and confirm the filter file and avoid misoperation.

[0106] In this embodiment, based on the configuration of the target function options, the filter file input by the user and associated with the design to be tested is processed accordingly, which can improve the adaptability of the filter file generation and meet the application scenarios of distributed maintenance coverage filter files. In this way, there is no need for technicians to manually add filter statements one by one for personalized designs to be tested, which improves the efficiency of filter file generation and thus improves the efficiency of chip verification.

[0107] In one embodiment of the present application, the filtering configuration information includes: filtering rules and target function options, and the above step S103 generates a target code coverage filtering file according to the filtering configuration information, the path hierarchy information and the signal statement position, which may specifically include:

[0108] According to the filtering rules, based on the path hierarchy information and the signal statement position, the signals to be filtered in the design information to be tested are determined; according to the signals to be filtered, corresponding filtering statements are generated; the filtering statements are summarized to generate a first filtering file; when the target function option is a merge option or an inheritance option, a target code coverage filtering file is generated according to the first filtering file and the second filtering file; wherein the second filtering file is a file uploaded by the user through the input interface in the filtering configuration page; when the target function option is a split option, a target code coverage filtering file is generated according to the first filtering file.

[0109] Specifically, referring to the above two embodiments, when the filtering configuration information includes filtering rules and target function options, the first filtering file can be generated according to the filtering rules, path hierarchy information and signal statement positions. Each filtering statement in the first filtering file carries a comment, indicating whether this filtering statement is a result of automatic filtering, the automatic filtering rule corresponding to this filtering statement, and the time when this filtering statement was added, so as to facilitate subsequent tracing processing.

[0110] After the first filter file is generated, if the target function option is a merge option or an inheritance option, the first filter file is regarded as one of the filter files that need to be processed by the merge or inheritance function by default. Then, based on the first filter file and the second filter file, a target code coverage filter file is generated. The second filter file can be a file automatically generated by the system before, or it can be a filter file manually written by a technician. It can be understood that if it is a merge option, the first filter file and the second filter file are merged to generate a target code coverage filter file; if it is an inheritance option, the first filter file and the second filter file are in an inheritance and inheritance relationship, for example, the filter statement in the first filter file is inherited to the second filter file, thereby generating a target code coverage filter file.

[0111] If the target function option is a split option, the first filter file is assumed to be the file to be split, so that the split is performed according to the first filter file and the identifier of the target module input by the user to generate a target code coverage filter file.

[0112] In this embodiment, a technical solution is provided in which filtering configuration information includes both filtering rules and target function options. A filtering file can be generated based on the filtering rules, and then the filtering file can be processed with corresponding functions according to the target function options. In this way, the efficiency of generating filtering files can be improved, thereby improving the efficiency of chip verification.

[0113] Based on the same or similar technical concept, in one embodiment of the present application, a code coverage filter file generation system is also provided. Figure 2 , Figure 2 Schematic diagram of the framework of the code coverage filtering file generation system described in one embodiment of the present application. Figure 2 As shown, the code coverage filtering file generation system 200 includes:

[0114] The first acquisition unit 201 is used to acquire the design information to be tested; the design information to be tested includes: path hierarchy information and signal statement positions; the path hierarchy information is used to indicate the hierarchical structure of the design to be tested; the signal statement positions are used to determine the signal statements in each hierarchical structure;

[0115] The second acquisition unit 202 is used to acquire filtering configuration information, wherein the filtering configuration information includes: filtering rules and / or target function options; the target function options include: merging options, splitting options, and inheritance options;

[0116] The generating unit 203 is used to generate a target code coverage filtering file according to the filtering configuration information, the path hierarchy information and the signal statement position.

[0117] In this embodiment, by obtaining the design information to be tested; the design information to be tested includes: path hierarchy information and signal statement position; the path hierarchy information is used to indicate the hierarchical structure of the design to be tested, that is, the specific content inside the design to be tested can be understood through the design information to be tested; the filtering configuration information is obtained, and the filtering configuration information includes: filtering rules and / or target function options; the target function options include: merging options, splitting options, and inheritance options; according to the filtering configuration information, according to the path hierarchy information and the signal statement position, a target code coverage filtering file is generated. Since the filtering configuration information may include filtering rules and / or target function options, the content to be filtered can be automatically determined from the design information to be tested according to the filtering rules in the filtering configuration information configured by the user to generate a corresponding filtering file; or according to the target function options in the filtering configuration information, according to the path hierarchy and signal statement position of the design to be tested, the filtering statements are merged, split, or inherited to generate a corresponding filtering file. In this way, the system can output a code coverage filtering file suitable for user requirements for large-scale, system-level, and complex designs to be tested, which improves the generation efficiency of the filtering file, thereby facilitating the improvement of chip verification efficiency.

[0118] In the present application, the description of the system embodiment is relatively short, and specific details can be referred to the above method embodiment, which will not be repeated here.

[0119] In one embodiment of the present application, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the above-mentioned code coverage filtering file method when executing the computer program.

[0120] In one embodiment of the present application, a non-volatile storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the code coverage filtering file method as described in the above embodiment is implemented.

[0121] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0122] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, devices, or computer program products. Therefore, the embodiments of the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the embodiments of the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0123] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, terminal devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing terminal device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0124] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing terminal device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0125] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device so that a series of operating steps are executed on the computer or other programmable terminal device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable terminal device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0126] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present application.

[0127] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or terminal device including the elements.

[0128] The above is a detailed introduction to a code coverage filter file generation method, system, device and medium provided. Specific examples are used in this article to illustrate the principles and embodiments of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea. At the same time, for general technical personnel in this field, according to the idea of ​​the present application, there will be changes in the specific embodiments and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A method for generating a code coverage filter file, characterized in that: The method comprises: Acquire the design information to be tested; the design information to be tested includes: path hierarchy information and signal statement position; the path hierarchy information is used to indicate the hierarchical structure of the design to be tested; Acquire filtering configuration information, the filtering configuration information including: filtering rules and / or target function options; the target function options including: merging options, splitting options, and inheritance options; According to the filtering configuration information, the target code coverage filtering file is generated based on the path hierarchy information and the signal statement position.

2. The method according to claim 1, characterized in that: The filtering configuration information includes: target function options; The step of generating a target code coverage filtering file according to the filtering configuration information, the path hierarchy information and the signal statement position includes: In a case where the filtering configuration information includes the merging option, obtaining a plurality of filtering files to be merged; The filter files to be merged are merged according to the path hierarchy information and the signal statement positions to generate a target code coverage filter file.

3. The method according to claim 2, characterized in that The step of generating a target code coverage filtering file according to the filtering configuration information, the path hierarchy information and the signal statement position includes: In the case where the filtering configuration information includes the splitting option, obtaining the identifiers of the filtering file to be split and the target module; The target code coverage filter file of the target module is split out from the filter file to be split according to the path hierarchy information, the signal statement position, and the identifier.

4. The method according to claim 2, characterized in that: The step of generating a target code coverage filtering file according to the filtering configuration information, the path hierarchy information and the signal statement position includes: In the case where the filtering configuration information includes the inheritance option, obtaining an inherited filtering file and an inheriting filtering file; According to the path hierarchy information and the signal statement position, the filter statement in the inherited filter file is formatted; A target code coverage filter file is generated according to the format-converted filter statement and the inherited filter file.

5. The method according to claim 1, characterized in that The filtering configuration information includes: filtering rules; The step of generating a target code coverage filtering file according to the filtering configuration information, the path hierarchy information and the signal statement position includes: According to the filtering rules, based on the path hierarchy information and the signal statement position, determining the signals to be filtered in the design information to be tested; Generate a corresponding filtering statement according to the signal to be filtered; The filtering statements are summarized to generate a target code coverage filtering file.

6. The method according to claim 1, characterized in that The filtering configuration information includes: filtering rules and target function options; The step of generating a target code coverage filtering file according to the filtering configuration information, the path hierarchy information and the signal statement position includes: According to the filtering rules, based on the path hierarchy information and the signal statement position, determining the signals to be filtered in the design information to be tested; Generate a corresponding filtering statement according to the signal to be filtered; Summarizing the filtering statements to generate a first filtering file; In the case where the target function option is the merge option or the inheritance option, generating a target code coverage filter file according to the first filter file and the second filter file; wherein the second filter file is a file uploaded by a user through an input interface in a filter configuration page; When the target function option is the split option, a target code coverage filter file is generated according to the first filter file.

7. The method according to claim 1, characterized in that The obtaining of the design information to be tested includes: Obtain the design file to be tested according to the address information of the design to be tested submitted through the user interface; The design information to be tested is determined according to the design file to be tested.

8. A code coverage filter file generation system, characterized in that: The system comprises: A first acquisition unit is used to acquire information of the design to be tested; the information of the design to be tested includes: path hierarchy information and signal statement positions; the path hierarchy information is used to indicate the hierarchical structure of the design to be tested; A second acquisition unit is used to acquire filtering configuration information, wherein the filtering configuration information includes: filtering rules and / or target function options; the target function options include: merging options, splitting options, and inheritance options; A generating unit is used to generate a target code coverage filtering file according to the filtering configuration information, the path hierarchy information and the signal statement position.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method for generating a code coverage filter file according to any one of claims 1 to 7 is implemented.

10. A non-volatile storage medium, characterized in that: A computer program is stored thereon, and when the program is executed by a processor, the method for generating a code coverage filter file as described in any one of claims 1 to 7 is implemented.

Citation Information

Patent Citations

  • Chip code coverage rate delivery method and system

    CN109800176A

  • Coverage rate filtering file generation method and device, equipment and medium

    CN114706785A

  • Coverage rate data processing method and device, computer equipment and storage medium

    CN115437905A

  • Service cluster test method and device, storage medium and program product

    CN118227255A

  • Code coverage rate testing method and device, terminal and storage medium

    CN118331887A

Cited By

  • Universal merging method of coverage rate data, electronic equipment and storage medium

    CN121503362A