Chip verification methods, systems, equipment and storage media
By generating verification scenario information and determining the mapping relationship of the scenarios to be tested, and combining test result information and semantic input information, the problem of uncertain coverage of scenarios to be tested in chip verification is solved, thereby improving the accuracy and efficiency of chip verification.
Patent Information
- Application Number
- CN202611316299.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-27
- Publication Date
- 2026-11-17
AI Technical Summary
In the chip verification stage, determining whether the preset test scenarios are fully covered is a technical problem that urgently needs to be solved.
By acquiring the specifications and verification planning information of the design under test, verification scenario information is generated, including the scenario identifier of the test scenario and the mapping relationship between test cases. Test cases are executed and test result information and semantic input information are generated. The mapping relationship information is combined to determine whether the test scenario is covered by the current test.
This enables verification of whether the preset test scenarios are fully covered, improving the accuracy and efficiency of chip verification.
Smart Images

Figure CN123117008A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of chip technology, specifically to a chip verification method, system, device, and storage medium. Background Technology
[0002] Chip verification is a key step in the front-end design process of digital chips. It involves simulating the chip's actual operating environment, running the chip based on pre-designed test cases, and verifying the correctness of the chip's functions based on the chip's operating results.
[0003] However, in the chip verification stage, how to determine whether the preset test scenarios are fully covered is a technical problem that urgently needs to be solved in this field. Summary of the Invention
[0004] In view of this, embodiments of this application provide a chip verification method, system, device, and storage medium to confirm whether a preset test scenario is fully covered.
[0005] To achieve the above objectives, the embodiments of this application provide the following technical solutions.
[0006] In a first aspect, embodiments of this application provide a chip verification method, including: Obtain the specification information and verification plan information of the design under test; wherein, the design under test is used to perform tests in the test scenario; Based on the specification information and the verification planning information, verification scenario information is generated, wherein the verification scenario information includes at least mapping relationship information for indicating the mapping relationship between scenario identifiers and test cases; Execute the test cases corresponding to the design under test, and generate test result information and semantic input information for each test case; the semantic input information includes at least test case identifier and scenario identifier; Based on the test result information, the semantic input information, and the mapping relationship information, it is determined whether each scenario to be tested is covered by the current test.
[0007] Optionally, determining whether each scenario to be tested is covered by the current test based on the test result information, the semantic input information, and the mapping relationship information includes: Based on the test result information and the semantic input information, the current test evidence for the corresponding scenario to be tested is determined; the current test evidence includes one or more of the observed test cases, semantic states, and scenario states. Based on the mapping relationship information and the current test evidence, it is determined whether each scenario to be tested is covered by the current test.
[0008] Optionally, determining the current test evidence for the corresponding test scenario based on the test result information and the semantic input information specifically involves: Based on the test results and semantic input information, a coverage summary file is generated. The coverage summary file includes the current test evidence for the corresponding test scenario and the judgment result for the test scenario.
[0009] Optionally, determining whether each scenario to be tested is covered by the current test based on the mapping relationship information and the current test evidence specifically involves comparing and analyzing the mapping relationship information with the current test evidence to determine whether the scenario to be tested is covered by the current test. The comparative analysis includes determining the intersection between the test case mapping and the observed test cases, and determining the absence or failure of the scenario state.
[0010] Optionally, the step of generating verification scenario information based on the specification information and the verification planning information further includes: generating assertion plan information associated with the scenario identifier based on the specification information and the verification planning information; In the step of executing the test cases corresponding to the design under test and generating test result information and semantic input information for each test case, the hit, pass or failure results of the corresponding scenario under test are also updated in the assertion plan information. In the step of determining the current test evidence for the corresponding test scenario based on the test result information and the semantic input information, the current test evidence for the corresponding test scenario is also determined based on the assertion plan information; the current test evidence includes the assertion state. In the step of comparing and analyzing the mapping relationship information with the current test evidence to determine whether the scenario to be tested is covered by the current test, the comparison and analysis also includes the judgment of anomalies in the assertion state.
[0011] Optionally, the step of executing test cases corresponding to the design under test and generating test result information and semantic input information corresponding to each test case may further include testing the design under test using a parameter matrix expansion method. The step of determining the current test evidence for the corresponding test scenario based on the test result information and the semantic input information includes: reading the parameter matrix summary and taking the parameter row that satisfies the corresponding scenario constraint as the matrix evidence in the current test evidence; In the step of comparing and analyzing the mapping relationship information with the current test evidence to determine whether the scene under test is covered by the current test, the comparison and analysis further includes determining the matching relationship between the matrix evidence and the mapping relationship information or scene constraints; wherein, when the scene under test lacks test evidence of test cases, if there is matrix evidence that matches the scene under test, then the scene under test is marked as having only matrix evidence.
[0012] Optionally, after the steps of executing the test cases corresponding to the design under test and generating test result information and semantic input information corresponding to each test case, the method further includes: Based on the test result information, the semantic input information, and the mapping relationship information, semantic tracking information including a test case view and a scenario view is generated. The test case view is used to record the execution status, associated scenarios, and semantic records of each test case, while the scenario view is used to record the declared test cases, observed test cases, and semantic records of each scenario to be tested.
[0013] Optionally, the specification information of the design under test is obtained from the intermediate specification representation file corresponding to the chip design during the self-verification process. The intermediate specification representation file is a carrier for carrying intermediate information of the chip design verification process. The verification planning information includes one or more of the following: scenario granularity, planned coverage points, candidate test cases, and assertion requirements. The intermediate representation file includes one or more fields from the following: interface name, transaction type, timing event, expected behavior, and constraints.
[0014] Optionally, generating verification scenario information based on the specification information and the verification planning information includes: Based on the specification information and the verification planning information, a mapping relationship is established between the scenario identifier and the test cases of the scenario to be tested; Generate verification scenario information that includes mapping information indicating the mapping relationship between scenario identifiers and test cases for the scenario under test.
[0015] Optionally, the verification scenario information includes a use case mapping field, a scenario identifier field, a scenario intent field, an event sequence field, and an expected behavior field. The use case mapping field records the mapping relationship information; the scenario identifier field records the identifier of the scenario under test; the scenario intent field records the test intent of the scenario under test; the event sequence field records the sequence of high-level events occurring during scenario execution; and the expected behavior field records the internal state and external output conditions that the design under test should meet after the test case execution is completed.
[0016] Optionally, the semantic input information further includes a run identifier, execution status, and result summary; wherein, the run identifier is a globally unique identifier assigned to the execution of the verification test, the execution status is used to indicate the stage of the verification test, and the result summary is used to record the conclusive information of the verification test execution.
[0017] Secondly, embodiments of this application also provide a chip verification system, including: The information acquisition module is used to acquire the specification information and verification plan information of the design under test; wherein, the design under test is used to perform testing in the test scenario; The information generation module is used to generate verification scenario information based on the specification information and the verification planning information. The verification scenario information includes at least mapping relationship information indicating the mapping relationship between the scenario identifier and the test case. The test execution module is used to execute the test cases corresponding to the design under test, generate test result information and semantic input information for each test case; the semantic input information includes at least test case identifier and scenario identifier; The result determination module is used to determine whether each scenario to be tested is covered by the current test based on the test result information, the semantic input information, and the mapping relationship information.
[0018] Optionally, the information generation module is further configured to generate semantic tracking information including a test case view and a scenario view based on the test result information, the semantic input information, and the mapping relationship information. The test case view is used to record the execution status, associated scenarios, and semantic records of each test case, while the scenario view is used to record the declared test cases, observed test cases, and semantic records of each scenario to be tested.
[0019] Thirdly, this application also provides a chip verification device, which includes a memory and a processor; the memory stores a computer program, and when the computer program is executed by the processor, it implements the chip verification method provided in this application.
[0020] Fourthly, embodiments of this application also provide a storage medium storing a computer program, which, when executed by a processor, implements the loading method of the chip verification system provided in embodiments of this application.
[0021] This application provides a chip verification method, system, device, and storage medium. The method includes: acquiring specification information and verification planning information of a design under test (DUT); wherein the DUT is used to perform tests in a test scenario; generating verification scenario information based on the specification information and the verification planning information, wherein the verification scenario information includes at least mapping relationship information indicating the mapping relationship between a scenario identifier and test cases; executing test cases corresponding to the DUT, generating test result information and semantic input information corresponding to each test case; wherein the semantic input information includes at least a test case identifier and a scenario identifier; and determining whether each test scenario is covered by the current test based on the test result information, the semantic input information, and the mapping relationship information.
[0022] As can be seen, the embodiments of this application establish a preset mapping relationship between the scene identifier of the scene to be tested and the test cases in the step of generating verification scene information. Then, after executing the corresponding test cases, the test result information obtained from the test and the semantic input information of each test case are combined to confirm whether the scene to be tested is covered by the current test, thereby realizing the confirmation of whether the preset scene to be tested is completely covered. Attached Figure Description
[0023] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.
[0024] Figure 1 This is an optional flowchart illustrating the chip verification method provided in an embodiment of this application; Figure 2 A schematic diagram of an optional process for step S130 provided in an embodiment of this application; Figure 3 This is another optional flowchart illustrating the chip verification method provided in the embodiments of this application; Figure 4 This is an optional structural diagram of the chip verification system provided in an embodiment of this application. Detailed Implementation
[0025] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0026] As described in the background section, in the chip verification stage, how to determine whether the preset test scenario is fully covered is a technical problem that urgently needs to be solved in this field.
[0027] Specifically, in the chip design verification process, it is typically necessary to execute pre-designed test cases on the design under test (DUT) in a preset test environment based on a verification plan, thereby achieving test scenario coverage for the DUT. The DUT is usually configured with multiple test scenarios. However, in specific chip design verification processes, especially those based on distributed scripts and multi-directory maintenance, the complexity of the verification process, the dispersion of corresponding test information, and the potential adjustments to the verification methods and processes as intermediate results occur can make it impossible to determine whether the planned test scenarios have been completely covered in the final test results.
[0028] In view of this, embodiments of this application provide a chip verification method, system, device, and storage medium. The method includes: acquiring specification information and verification planning information of a design under test (DUT); wherein the DUT is used to perform tests in a test scenario; generating verification scenario information based on the specification information and the verification planning information, wherein the verification scenario information includes at least mapping relationship information indicating the mapping relationship between a scenario identifier and test cases; executing test cases corresponding to the DUT, generating test result information and semantic input information corresponding to each test case; wherein the semantic input information includes at least a test case identifier and a scenario identifier; and determining whether each test scenario is covered by the current test based on the test result information, the semantic input information, and the mapping relationship information.
[0029] As can be seen, the embodiments of this application establish a preset mapping relationship between the scene identifier of the scene to be tested and the test cases in the step of generating verification scene information. Then, after executing the corresponding test cases, the test result information obtained from the test and the semantic input information of each test case are combined to confirm whether the scene to be tested is covered by the current test, thereby realizing the confirmation of whether the preset scene to be tested is completely covered.
[0030] The chip verification scheme provided in the embodiments of this application will now be described in detail.
[0031] In one alternative implementation, refer to Figure 1 The illustrated schematic diagram shows an optional flowchart of a chip verification method provided in an embodiment of this application. The chip verification method provided in this embodiment may include: Step S100: Obtain the specification information and verification plan information of the design to be tested; The Design Under Test (DUT) is used to perform tests in the test scenarios to verify its functionality. It should be noted that in a specific verification testing process, there are usually multiple test scenarios to verify one or more functions of the DUT from multiple perspectives.
[0032] The specification information of the design under test can be obtained from the intermediate specification representation file corresponding to the chip design during the self-verification process. The intermediate specification representation file can be understood as a carrier for carrying intermediate information of the chip design verification process, and thus can serve as a transition file for transferring data between different stages or different tools in the verification process.
[0033] In a preferred implementation, the intermediate representation file is an intermediate representation file (such as spec_ir) obtained by normalizing the source specification file or imported RTL description. This intermediate representation file may include fields such as interface name, transaction type, timing event, expected behavior, and constraints.
[0034] The verification planning information is used to indicate information such as verification objectives and scope, verification strategies and methods, coverage and completion criteria, verification plan documents and examples. In specific implementations, the verification planning information may include one or more of the following: scenario granularity, planned coverage points, candidate test cases, and assertion requirements.
[0035] It is understood that during the chip verification process, the specification information and verification plan information are existing information, and can be obtained by querying or retrieving relevant documents.
[0036] Step S110: Generate verification scenario information based on the specification information and the verification planning information; The verification scenario information includes at least mapping relationship information that indicates the mapping relationship between the scenario identifier and the test cases; In a preferred implementation, the verification scenario information can be loaded based on a verification scenario file. Accordingly, this step can be achieved by generating a verification scenario file containing the verification scenario information. There can be multiple verification scenario information entries, and each entry can correspond one-to-one with a planned test scenario. In a specific example, the verification scenario information can be scenario records, with one scenario record corresponding to one test scenario.
[0037] The verification scenario information may include mapping relationship information, which indicates the mapping relationship between the scenario identifier and test cases of the scenario under test. In a specific implementation, this step can first establish a mapping relationship between the scenario identifier and test cases of the scenario under test based on the specification information and the verification planning information, and then generate verification scenario information including the mapping relationship information.
[0038] In a further optional implementation, the verification scenario information may include a test case mapping (linked_testcases) field, which records the mapping relationship information. In some examples, the verification scenario information may further include fields such as scenario identifier (scenario_id), scenario intent (scenario_intent), event sequence (events), and expected behavior (expected_behavior), used to record corresponding verification process information. The scenario identifier field records the identifier of the scenario to be tested; the scenario intent field records the test intent of the scenario to be tested; the event sequence field records the sequence list of high-level events occurring during scenario execution, which can be used to define the execution flow of test cases; the expected behavior field records the conditions that the internal state and external output of the design under test should meet after the test cases are executed, which can be used to define the judgment criteria for whether the scenario to be tested passes.
[0039] In the specific implementation, scene identifiers can be implemented using scene numbers, scene codes, or other scene identifiers, as long as they are consistently referenced during scene declaration, test execution, and result aggregation.
[0040] In a further optional implementation, this step may further generate assertion plan information associated with the scenario identifier based on the specification information and the verification plan information.
[0041] In a specific implementation, the assertion plan information can be an assertion plan file. Specifically, the assertion plan information may include signals to be checked, timing windows to be checked, triggering conditions to be checked, and expected results; wherein, the signals to be checked are the signals that the design under test needs to check in the verification process, the timing windows to be checked are the timing windows that the design under test needs to check in the verification process, the triggering conditions to be checked are the triggering conditions that the design under test needs to check in the verification process, and the expected results are the results that the design under test expects in the verification process.
[0042] Step S120: Execute the test cases corresponding to the design under test, and generate test result information and semantic input information for each test case; The test result information refers to the result information obtained after executing the design under test. The semantic input information can also be referred to as a semantic input record, semantic trajectory, or stimulus semantic log in specific examples.
[0043] Specifically, the semantic input information is used to instruct the verification environment to perform a structured, traceable description and archiving of the stimuli applied to the design under test at the transaction-level behavior level. The semantic input information includes at least test case identifiers and scenario identifiers, thereby identifying the test cases and scenarios involved in the testing process in subsequent steps. In a specific implementation, the semantic input information can be a semantic input record. Furthermore, the semantic input information may include a runtime identifier, execution status, and result summary.
[0044] In addition to using JSON files, semantic input information can also be implemented using other structured record formats, as long as the correspondence between test case identifiers, scenario identifiers, execution status, and result summaries can be maintained.
[0045] The run identifier refers to a globally unique identifier assigned to the verification test execution, used to accurately locate and reference relevant data for this run in the database, logs, and toolchain; the execution status refers to the stage identifier of the verification test in its life cycle, used to reflect whether the verification environment itself has completed the preset startup, stimulus application, and shutdown processes; the result summary refers to the conclusive information obtained from the verification test execution.
[0046] It is understandable that by generating test result information and corresponding semantic input information for each test case, an information basis is provided for subsequent determination of whether the scenario is covered.
[0047] In a further optional implementation, where assertion plan information exists, this step further updates the hit, pass, or failure result of the corresponding test scenario in the assertion plan information.
[0048] It should be noted that during the execution of test cases, testing of some scenarios under test can also be performed using parameter matrix expansion. Specifically, testing of some scenarios under test can be performed without separately written test cases, but by parameter matrices (such as configuration matrices and state transition matrices) rotating through the parameters. When generating the coverage summary, the parameter matrix summary is read, and the parameter rows that satisfy the scenario constraints are recorded as matrix evidence, providing supplementary evidence for scenarios lacking test case evidence. In other words, the parameter matrix expansion can systematically define, generate, and cover the functional scenarios and parameter combinations of the chip using structured parameter matrices (such as configuration matrices and state transition matrices).
[0049] Step S130: Based on the test result information, the semantic input information, and the mapping relationship information, determine whether each scenario to be tested is covered by the current test; It is understandable that the mapping relationship information obtained in the aforementioned steps can be used to associate the scene under test with the corresponding test result information and semantic input information, thereby enabling the confirmation of whether the scene under test is covered.
[0050] In the optional implementation, refer to Figure 2 The illustrated optional flowchart for step S130 shows that this step can be implemented based on the following process: Step S131: Based on the test result information and the semantic input information, determine the current test evidence for the corresponding test scenario; The current test evidence refers to the test data corresponding to the current test process. Accordingly, based on this current test evidence, it can be determined whether the corresponding scenario under test is covered. In a specific implementation, the current test evidence for the scenario under test may include one or more of the following: observed test cases, semantic status, and scenario status. Observed test cases indicate the number of test cases whose execution results have been successfully captured and recorded, the semantic status records the execution status of the verification scenario at the high-level behavioral level, and the scenario status indicates whether the scenario under test is covered.
[0051] When assertion plan information exists, the current test evidence in this step can further determine the current test evidence for the corresponding test scenario based on the assertion plan information. Specifically, the current test evidence can further include the assertion status, which is used to indicate the inspection results of assertions in the design under test.
[0052] Specifically, this step can generate a coverage summary file based on the test result information and the semantic input information. The coverage summary file can include the current test evidence for the corresponding scenario to be tested. In a further example, the coverage summary file can further include the judgment result of the scenario to be tested, which can be, for example, covered, failed, or missing.
[0053] Understandably, by judging the results of the scenario under test, three scenario states—covered, failed, and missing—can be determined, providing status indications for scenario-level verification evidence. The judgment result is a scenario-level state directly summarized from the results of this execution, and it is distinct from the consistency verification result obtained subsequently based on the comparison of declaration mapping relationships.
[0054] Furthermore, by aggregating scenario results and assertion results in the same coverage summary file, the integration of the result evidence chain can be improved. Assertion results are used to verify the iteration process; when an assertion fails, the iteration returns until the assertion result is satisfied. The summary of assertion results for each test case is also part of the evidence chain and serves as one of the evaluation criteria for the verification results.
[0055] In a further optional implementation, if there is a process of testing the design under test by expanding the parameter matrix during the execution of the test cases corresponding to the design under test, the parameter matrix summary can be read further, and the parameter row that satisfies the corresponding scenario constraints can be used as the matrix evidence in the current test evidence.
[0056] Step S132: Based on the mapping relationship information and the current test evidence, determine whether each scenario to be tested is covered by the current test; After determining the current test evidence corresponding to the test scenario, it can be determined whether the scenario to be tested is covered by the current test. Understandably, when there are multiple scenarios to be tested, it is also possible to determine whether each scenario is covered by the current test.
[0057] In a specific implementation, the mapping relationship information generated in the aforementioned steps, which indicates the mapping relationship between the scenario identifier and the test cases, can be compared and analyzed with the current test evidence to determine whether the scenario under test is covered by the current test.
[0058] In a specific example, the mapping relationship information can be the linked_testcases set corresponding to each scenario. The corresponding comparison analysis can include the intersection judgment of the test case mapping linked_testcases and the observed test cases observed_testcases, the missing or failed scenario status scenario_status judgment, and then output the consistency verification result. The consistency verification result is used to indicate whether each scenario under test is covered by the current test.
[0059] In implementations that include assertion plan information, the comparative analysis may further include anomaly detection of the assertion status (assertion_status).
[0060] In a further optional implementation, when testing the design under test using the parameter matrix expansion method in the testing step, the comparative analysis described in this step may also include determining the matching relationship between matrix evidence and mapping relationship information or scenario constraints. If test evidence for test cases is missing in the scenario under test, and if there is matrix evidence that matches the scenario under test, then the scenario under test is marked as having only matrix evidence.
[0061] It should be noted that the comparative analysis can also be understood as consistency verification. By performing consistency verification between the test case mapping linked_testcases and the observed test cases, scenario status, assertion status, and other current test evidence, scenarios that lack current test evidence, have mapping mismatches, or are only supplemented by parameter matrices can be identified.
[0062] In further optional implementations, refer to Figure 3 Another alternative flowchart of the chip verification method shown may include, after step S120: Step S200: Based on the test result information, the semantic input information, and the mapping relationship information, generate semantic tracking information including a test case view and a scenario view; The test case view can be used to record the execution status, associated scenarios, and semantic records of each test case, while the scenario view can be used to record the declared test cases, observed test cases, and semantic records of each scenario under test. In implementations with assertion plan information, the scenario view may also include assertion results.
[0063] In a specific implementation, the semantic tracking information can be loaded into a semantic tracking file. Accordingly, this step can generate a semantic tracking file based on the test result information, the semantic input information, and the mapping relationship information. The semantic tracking file includes the semantic tracking information.
[0064] In a specific example, this step can create an execution status index for test result information based on test cases, and group semantic input information based on test cases and scenario identifiers, thereby forming semantic tracking information that includes test case views and scenario views.
[0065] In a preferred implementation, step S200 may be executed before step S130, while step S131 may confirm the test execution status based on the test case view in the semantic tracking information, and confirm the current test evidence for the corresponding test scenario based on the scenario view.
[0066] Understandably, by generating semantic tracking information based on the mapping relationship between scenario identifiers and corresponding tests, a unified tracking chain can be established for the scenario under test, test cases, and scenario results. Furthermore, by bidirectionally aggregating test result information and semantic input information, and forming test case views and scenario views respectively, it is possible to avoid judging whether a scenario has been covered solely based on the test pass status.
[0067] As can be seen, by establishing a mapping relationship between scenario identifiers and test cases, the embodiments of this application can incorporate scenario declarations and test execution evidence of the verification process into the same tracing thread. Furthermore, by establishing an execution status index by testcase and aggregating semantic input records by scenario_id, a semantic tracing file with both testcase and scene views is formed. This allows the testcase view to confirm the test execution status and the scene view to confirm the current scenario evidence.
[0068] Understandably, the scene view inverts and aggregates the execution results with test cases as the primary key into a set of evidence with scene identifiers as the primary key (which may include declared test cases, observed test cases, semantic records, and optional assertion results for each scene). This is the direct data source for confirming the "current evidence of the scene" in consistency verification, thereby avoiding the need to judge whether the scene has been covered based solely on the test pass status.
[0069] In a further embodiment, this application provides a chip verification system, referring to... Figure 4 The diagram shows an optional architecture for a chip verification system. (See diagram for example.) Figure 4 As shown, the chip verification system includes: The information acquisition module 200 is used to acquire the specification information and verification plan information of the design under test; wherein, the design under test is used to perform testing in the test scenario; The information generation module 210 is used to generate verification scenario information based on the specification information and the verification planning information. The verification scenario information includes at least mapping relationship information indicating the mapping relationship between the scenario identifier and the test case. The test execution module 220 is used to execute the test cases corresponding to the design under test, and generate test result information and semantic input information corresponding to each test case; the semantic input information includes at least test case identifier and scenario identifier; The result determination module 230 is used to determine whether each test scenario is covered by the current test based on the test result information, the semantic input information, and the mapping relationship information.
[0070] Optionally, the result determination module 230 is used to determine whether each test scenario is covered by the current test based on the test result information, the semantic input information, and the mapping relationship information, including: Based on the test result information and the semantic input information, the current test evidence for the corresponding scenario to be tested is determined; the current test evidence includes one or more of the observed test cases, semantic states, and scenario states. Based on the mapping relationship information and the current test evidence, it is determined whether each scenario to be tested is covered by the current test.
[0071] Optionally, the result determination module 230 is used to determine the current test evidence corresponding to the test scenario based on the test result information and the semantic input information, specifically: Based on the test results and semantic input information, a coverage summary file is generated. The coverage summary file includes the current test evidence for the corresponding test scenario and the judgment result for the test scenario.
[0072] Optionally, the result determination module 230 is used to determine whether each scenario to be tested is covered by the current test based on the mapping relationship information and the current test evidence. Specifically, it performs a comparative analysis based on the mapping relationship information and the current test evidence to determine whether the scenario to be tested is covered by the current test. The comparative analysis includes determining the intersection between the test case mapping and the observed test cases, and determining the absence or failure of the scenario state.
[0073] Optionally, the step of generating verification scenario information based on the specification information and the verification planning information by the information generation module 210 further includes: generating assertion plan information associated with the scenario identifier based on the specification information and the verification planning information. The test execution module 220 is used to execute the test cases corresponding to the design under test, generate test result information and semantic input information corresponding to each test case. In the process, it also updates the hit, pass or failure results of the corresponding test scenario in the assertion plan information. The result determination module 230, in the step of determining the current test evidence for the corresponding test scenario based on the test result information and the semantic input information, further determines the current test evidence for the corresponding test scenario based on the assertion plan information; the current test evidence includes the assertion state; The result determination module 230 is used to perform a comparative analysis based on the mapping relationship information and the current test evidence to determine whether the scene to be tested is covered by the current test. The comparative analysis also includes anomaly judgment of the assertion state.
[0074] Optionally, the test execution module 220, in the step of executing test cases corresponding to the design under test and generating test result information and semantic input information corresponding to each test case, further includes testing the design under test using a parameter matrix expansion method. The result determination module 230 is used to determine the current test evidence for the corresponding test scenario based on the test result information and the semantic input information. The step includes: reading the parameter matrix summary and taking the parameter row that satisfies the corresponding scenario constraint as the matrix evidence in the current test evidence. The result determination module 230 is used to perform a comparative analysis based on the mapping relationship information and the current test evidence to determine whether the scene under test is covered by the current test. The comparative analysis further includes determining the matching relationship between the matrix evidence and the mapping relationship information or scene constraints. Wherein, when the scene under test lacks test evidence of test cases, if there is matrix evidence that matches the scene under test, then the scene under test is marked as having only matrix evidence.
[0075] Optionally, the specification information of the design under test is obtained from the intermediate specification representation file corresponding to the chip design during the self-verification process. The intermediate specification representation file is a carrier for carrying intermediate information of the chip design verification process. The verification planning information includes one or more of the following: scenario granularity, planned coverage points, candidate test cases, and assertion requirements. The intermediate representation file includes one or more fields from the following: interface name, transaction type, timing event, expected behavior, and constraints.
[0076] Optionally, the information generation module 210 is used to generate verification scenario information based on the specification information and the verification planning information, including: Based on the specification information and the verification planning information, a mapping relationship is established between the scenario identifier and the test cases of the scenario to be tested; Generate verification scenario information that includes mapping information indicating the mapping relationship between scenario identifiers and test cases for the scenario under test.
[0077] Optionally, the verification scenario information includes a use case mapping field, a scenario identifier field, a scenario intent field, an event sequence field, and an expected behavior field. The use case mapping field records the mapping relationship information; the scenario identifier field records the identifier of the scenario under test; the scenario intent field records the test intent of the scenario under test; the event sequence field records the sequence of high-level events occurring during scenario execution; and the expected behavior field records the internal state and external output conditions that the design under test should meet after the test case execution is completed.
[0078] Optionally, the information generation module 210 is further configured to generate semantic tracking information including a test case view and a scenario view based on the test result information, the semantic input information, and the mapping relationship information. The test case view is used to record the execution status, associated scenarios, and semantic records of each test case, while the scenario view is used to record the declared test cases, observed test cases, and semantic records of each scenario to be tested.
[0079] Optionally, the semantic input information further includes a run identifier, execution status, and result summary; wherein, the run identifier is a globally unique identifier assigned to the execution of the verification test, the execution status is used to indicate the stage of the verification test, and the result summary is used to record the conclusive information of the verification test execution.
[0080] This application also provides a chip verification device, including a memory and a processor; the memory stores a computer program, which, when executed by the processor, implements the chip verification method provided in this application.
[0081] This application also provides a storage medium that stores a computer program, which, when executed by a processor, implements the loading method of the chip verification system provided in this application.
[0082] The foregoing describes multiple embodiment schemes provided by the embodiments of this application. The optional methods described in each embodiment scheme can be combined and cross-referenced with each other without conflict, thereby extending to a variety of possible embodiment schemes. These can all be considered as the embodiment schemes disclosed and published by the embodiments of this application.
[0083] While the embodiments disclosed above are described in this application, this application is not limited thereto. Any person skilled in the art can make various modifications and alterations without departing from the spirit and scope of this application; therefore, the scope of protection of this application should be determined by the scope defined in the claims.
Claims
1. A chip verification method, characterized in that, include: Obtain the specification information and verification plan information of the design under test; wherein, the design under test is used to perform tests in the test scenario; Based on the specification information and the verification planning information, verification scenario information is generated, wherein the verification scenario information includes at least mapping relationship information for indicating the mapping relationship between scenario identifiers and test cases; Execute the test cases corresponding to the design under test, and generate test result information and semantic input information for each test case; the semantic input information includes at least test case identifier and scenario identifier; Based on the test result information, the semantic input information, and the mapping relationship information, it is determined whether each scenario to be tested is covered by the current test.
2. The chip verification method according to claim 1, characterized in that, The step of determining whether each scenario to be tested is covered by the current test based on the test result information, the semantic input information, and the mapping relationship information includes: Based on the test result information and the semantic input information, the current test evidence for the corresponding scenario to be tested is determined; the current test evidence includes one or more of the observed test cases, semantic states, and scenario states. Based on the mapping relationship information and the current test evidence, it is determined whether each scenario to be tested is covered by the current test.
3. The chip verification method according to claim 2, characterized in that, The step of determining the current test evidence for the corresponding test scenario based on the test result information and the semantic input information specifically involves: Based on the test results and semantic input information, a coverage summary file is generated. The coverage summary file includes the current test evidence for the corresponding test scenario and the judgment result for the test scenario.
4. The chip verification method according to claim 2, characterized in that, The step of determining whether each scenario to be tested is covered by the current test based on the mapping relationship information and the current test evidence specifically involves comparing and analyzing the mapping relationship information with the current test evidence to determine whether the scenario to be tested is covered by the current test. The comparative analysis includes determining the intersection between the test case mapping and the observed test cases, and determining the absence or failure of the scenario state.
5. The chip verification method according to claim 4, characterized in that, The step of generating verification scenario information based on the specification information and the verification planning information further includes: generating assertion plan information associated with the scenario identifier based on the specification information and the verification planning information. In the step of executing the test cases corresponding to the design under test and generating test result information and semantic input information for each test case, the hit, pass or failure results of the corresponding scenario under test are also updated in the assertion plan information. In the step of determining the current test evidence for the corresponding test scenario based on the test result information and the semantic input information, the current test evidence for the corresponding test scenario is also determined based on the assertion plan information; the current test evidence includes the assertion state. In the step of comparing and analyzing the mapping relationship information with the current test evidence to determine whether the scenario to be tested is covered by the current test, the comparison and analysis also includes the judgment of anomalies in the assertion state.
6. The chip verification method according to claim 4, characterized in that, The step of executing test cases corresponding to the design under test and generating test result information and semantic input information for each test case also includes testing the design under test using a parameter matrix expansion method. The step of determining the current test evidence for the corresponding test scenario based on the test result information and the semantic input information includes: reading the parameter matrix summary and taking the parameter row that satisfies the corresponding scenario constraint as the matrix evidence in the current test evidence; In the step of comparing and analyzing the mapping relationship information with the current test evidence to determine whether the scene under test is covered by the current test, the comparison and analysis further includes determining the matching relationship between the matrix evidence and the mapping relationship information or scene constraints; wherein, when the scene under test lacks test evidence of test cases, if there is matrix evidence that matches the scene under test, then the scene under test is marked as having only matrix evidence.
7. The chip verification method according to claim 1, characterized in that, After the steps of executing the test cases corresponding to the design under test, generating test result information and semantic input information for each test case, the method further includes: Based on the test result information, the semantic input information, and the mapping relationship information, semantic tracking information including a test case view and a scenario view is generated. The test case view is used to record the execution status, associated scenarios, and semantic records of each test case, while the scenario view is used to record the declared test cases, observed test cases, and semantic records of each scenario to be tested.
8. The chip verification method according to claim 1, characterized in that, The specification information of the design under test is obtained from the intermediate specification representation file corresponding to the chip design during the self-verification process. The intermediate specification representation file is a carrier for carrying intermediate information of the chip design verification process. The verification planning information includes one or more of the following: scenario granularity, planned coverage points, candidate test cases, and assertion requirements. The intermediate representation file includes one or more fields from the following: interface name, transaction type, timing event, expected behavior, and constraints.
9. The chip verification method according to claim 1, characterized in that, The step of generating verification scenario information based on the specification information and the verification planning information includes: Based on the specification information and the verification planning information, a mapping relationship is established between the scenario identifier and the test cases of the scenario to be tested; Generate verification scenario information that includes mapping information indicating the mapping relationship between scenario identifiers and test cases for the scenario under test.
10. The chip verification method according to claim 1, characterized in that, The verification scenario information includes a use case mapping field, a scenario identifier field, a scenario intent field, an event sequence field, and an expected behavior field. The use case mapping field is used to record the mapping relationship information; the scenario identifier field is used to record the identifier of the scenario to be tested; the scenario intent field is used to record the test intent of the scenario to be tested; the event sequence field is used to record the sequence list of high-level events that occur during scenario execution; and the expected behavior field is used to record the internal state and external output conditions that the design under test should meet after the test case is executed.
11. The chip verification method according to claim 1, characterized in that, The semantic input information also includes a running identifier, an execution status, and a result summary; wherein, the running identifier is a globally unique identifier assigned to the execution of the verification test, the execution status is used to indicate the stage of the verification test, and the result summary is used to record the conclusive information of the verification test execution.
12. A chip verification system, characterized in that, include: The information acquisition module is used to acquire the specification information and verification plan information of the design under test; wherein, the design under test is used to perform testing in the test scenario; The information generation module is used to generate verification scenario information based on the specification information and the verification planning information. The verification scenario information includes at least mapping relationship information indicating the mapping relationship between the scenario identifier and the test case. The test execution module is used to execute the test cases corresponding to the design under test, generate test result information and semantic input information for each test case; the semantic input information includes at least test case identifier and scenario identifier; The result determination module is used to determine whether each scenario to be tested is covered by the current test based on the test result information, the semantic input information, and the mapping relationship information.
13. The chip verification system according to claim 12, characterized in that, The information generation module is further configured to generate semantic tracking information, including a test case view and a scenario view, based on the test result information, the semantic input information, and the mapping relationship information. The test case view is used to record the execution status, associated scenarios, and semantic records of each test case, while the scenario view is used to record the declared test cases, observed test cases, and semantic records of each scenario to be tested.
14. A chip verification device, characterized in that, It includes a memory and a processor; the memory stores a computer program, which, when executed by the processor, implements the chip verification method as described in any one of claims 1-11.
15. A storage medium, characterized in that, The storage medium stores a computer program, which, when executed by a processor, implements the chip verification method as described in any one of claims 1-11.
