Test scenario generation device, verification specification generation device, program, and verification device

The test scenario generation device automates the conversion of verification specifications into test scenarios using identification symbols and condition information, enhancing the efficiency of logic design verification for semiconductor integrated circuits.

JP2024165608APending Publication Date: 2024-11-28MITSUBISHI ELECTRIC ENG CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023081940
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-18
Publication Date
2024-11-28

AI Technical Summary

Technical Problem

The conventional method of converting verification specifications into test scenarios for semiconductor integrated circuits is manually performed by a test engineer, which is time-consuming and inefficient.

Method used

A test scenario generation device that utilizes verification specification data with identification symbols to automatically generate test scenarios by associating condition information with processing types, referencing a database to output test scenarios efficiently.

Benefits of technology

Improves the efficiency of logic design verification by automating the conversion of verification specifications into test scenarios, reducing manual effort and time.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024165608000001_ABST
    Figure 2024165608000001_ABST
Patent Text Reader

Abstract

To provide a test scenario generation device and the like that improve efficiency of logical design verification.SOLUTION: A test scenario generation device comprises: a verification specification acquisition section for acquiring verification specification data which contains verification specification character strings divided by identifying codes, and in which verification specification sentences per processing in logical design verification of a semiconductor integrated circuit are described; a condition acquisition section for acquiring condition information containing information in which an identifying code and a use condition related to the use of a verification specification character string are associated with each other, and containing information in which a verification specification character string and a kind of processing in logical design verification are associated with each other; a constituent extraction section for outputting verification specification information containing a verification specification character string, a use condition, and a processing kind, per processing, by using the verification specification data and the condition information; and a test scenario output section for outputting a scenario that is generated according to the use condition and the processing kind, and that contains a test scenario character string corresponding to the verification specification character string, by using the information and referring to a DB in which verification specification character strings and test scenario character strings are stored in beforehand.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to a test scenario generation technique for generating test scenarios for verifying semiconductor integrated circuits. [Background technology]

[0002] In the development stage of a semiconductor integrated circuit, logic design verification is performed to verify the logic design data of the semiconductor integrated circuit (LSI). The logic design data is expressed as HDL source code written in a Hardware Description Language (HDL), and logic design verification is performed using test scenarios written in HDL. In the conventional technology, in logical design verification, a tester writes and converts a test scenario using HDL based on information related to a verification specification in a verification specification document received by the tester.

[0003] Incidentally, Patent Document 1 discloses a "test method for semiconductor integrated circuits" that uses conditions such as voltage, current, impedance, and output load. Specifically, the "test method for semiconductor integrated circuits" of Patent Document 1 employs a "standard test library database" (1) that is a database of "plurality of data libraries in which test procedures are set for each operating mode," a "product operation specification database" (3) that stores "operation specifications such as the operating voltage and operating frequency of the semiconductor integrated circuit to be tested," and a "test sequence database" (4) that stores "program modules" that are "written in a program language specific to the tester." Using the test library and individual test conditions (such as voltage, current, impedance, and output load) specified by the designer of the semiconductor integrated circuit, a test engineer can select a test library from a standard test library database (1), select values ​​such as voltage, current, impedance, and output load that correspond to the individual test conditions from a product operation specification database (3), and select and use a program module from a test sequence database (4) based on the selected information to convert it into a test program. According to Patent Document 1, "Testing Method for Semiconductor Integrated Circuits," "The designer of a semiconductor integrated circuit need only provide test engineers with test specifications that combine test libraries and individual test conditions. The test engineers can convert the test specifications into test programs and obtain the desired test programs." [Prior art documents] [Patent documents]

[0004] [Patent Document 1] International Patent Publication No. 2004 / 023554 Summary of the Invention [Problem to be solved by the invention]

[0005] In conventional technology, the process of converting verification specifications into test scenarios in logical design verification is performed manually by a tester, which tends to take a long time and is therefore inefficient. The semiconductor integrated circuit testing method described in Patent Document 1 is a testing method that uses conditions such as voltage, current, impedance, and output load, and a test engineer selects them from a database in accordance with the test specifications and converts them into a test program, so it cannot solve the problems related to the logic design verification described above.

[0006] The present disclosure is intended to solve the above-mentioned problems, and has an object to make it possible to improve the efficiency of logic design verification. [Means for solving the problem]

[0007] The test scenario generation device according to the present disclosure comprises: a verification specification acquisition unit that acquires verification specification data describing a verification specification for each process in a logic design verification of a semiconductor integrated circuit, the verification specification including a verification specification character string separated by an identification symbol; a condition acquiring unit that acquires condition information including information associating the identification symbol with a use condition related to use of the verification specification character string, and information associating the verification specification character string with a type of processing in the logic design verification; a component extraction unit that uses the verification specification data and the condition information to output, for each process, verification specification information including the verification specification character string, the use condition, and the type of the process; a test scenario output unit that uses the verification specification information to refer to a database that prestores verification specification strings and test scenario strings, and outputs a test scenario that includes the test scenario strings that correspond to the verification specification strings, the test scenario being generated according to the use conditions and the type of processing; Equipped with: Effect of the Invention

[0008] The present disclosure provides an advantage in that it is possible to improve the efficiency of logic design verification. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram showing an example of a configuration according to a first embodiment for implementing the present disclosure. [Diagram 2] FIG. 2 is a flowchart illustrating an example of a test scenario generation process in the configuration according to the first embodiment of the present disclosure. [Diagram 3] FIG. 3 is a flowchart illustrating an example of a specific process of the test scenario output process in the test scenario generation process according to the first embodiment of the present disclosure. [Figure 4] FIG. 4 is a flowchart showing a more detailed example of the process shown in FIG. [Diagram 5] FIG. 5 is a diagram showing an example of a configuration according to the second embodiment for implementing the present disclosure. [Figure 6] FIG. 6 is an image diagram of test scenario generation according to the present disclosure. [Figure 7] FIG. 7 shows an example of a description of a verification specification and an example of a test scenario according to the present disclosure. [Figure 8] FIG. 8 is an example of a signal name comparison table in this disclosure. [Figure 9] FIG. 9 is an example of a task search condition in the present disclosure. [Figure 10] FIG. 10 is a flowchart illustrating an example of a test scenario generation process in the configuration according to the second embodiment of the present disclosure. [Figure 11] FIG. 11 is a flowchart illustrating an example of a specific process of the test scenario output process in the test scenario generation process according to the second embodiment of the present disclosure. [Figure 12A] FIG. 12A is a flowchart showing a more detailed example of the process shown in FIG. [Figure 12B] FIG. 12B is a flowchart showing a more detailed example of the process shown in FIG. [Figure 13] FIG. 13 is a diagram showing an example of a configuration according to the third embodiment for implementing the present disclosure. [Figure 14] FIG. 14 is a diagram illustrating an example of the internal configuration of the verification specification output unit 182 in this disclosure. [Figure 15] FIG. 15 is an image diagram of verification specification generation according to the present disclosure. [Figure 16] FIG. 16 is a flowchart illustrating an example of the verification specification generation process of the present disclosure. [Figure 17] FIG. 17 is a flowchart showing an example of a specific process of the verification specification statement output process in the verification specification generation process of the present disclosure. [Figure 18]FIG. 18 is a diagram illustrating a first example of a hardware configuration for realizing the functions of the present disclosure. [Figure 19] FIG. 19 is a diagram illustrating a second example of a hardware configuration for realizing the functions of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] In order to explain the present disclosure in more detail, embodiments of the present disclosure will be described below with reference to the accompanying drawings.

[0011] Embodiment 1 In the first embodiment, a configuration example for realizing a function for generating a test scenario from a verification specification will be described. In order to avoid complicating the description, the terms "data" and "information" may be omitted in the explanation when referring to electronic data or electronic information.

[0012] An example of a configuration according to the first embodiment will be described. FIG. 1 is a diagram showing an example of a configuration according to a first embodiment for implementing the present disclosure. The test scenario generating device 100A acquires verification specification data, and generates and outputs test scenario data using the acquired verification specification data. The verification specification data is electronic data of the verification specification, and in the embodiment of the present disclosure, is data including a search specification for each process in the logic design verification of a semiconductor integrated circuit. The search specification includes a verification specification string separated by distinguishing symbols, such as ",", (,), ",", and ",". The verification specification character string includes a character string capable of identifying a process related to the logical design verification, and may further include a value used in the process. The test scenario data is electronic data describing a test scenario for verifying the logic design of a semiconductor integrated circuit. The test scenario includes a test scenario description written in a hardware description language (HDL) for each process related to the logic design verification. The test scenario generation device 100A shown in FIG. 1 includes a verification specification receiving unit 110A, a condition acquiring unit 120A, a component extracting unit 130A, and a test scenario output unit 140A.

[0013] The verification specification receiving unit 110A acquires verification specification data. The verification specification receiving unit 110A acquires verification specification data describing a verification specification for each process in the logic design verification of a semiconductor integrated circuit, the verification specification including a verification specification character string separated by identification symbols.

[0014] The condition acquiring unit 120A acquires condition information. The condition acquiring unit 120A acquires condition information including information associating an identification symbol with a use condition related to the use of a verification specification string, and information associating a verification specification string with a type of processing in logical design verification.

[0015] The condition information includes information that associates an identification symbol with a usage condition related to the use of the verification specification character string. The information included in the condition information indicates, for example, a usage condition that a verification specification character string delimited by the identification symbol " " in the verification specification text is used as a signal name. The information also indicates that, for example, a verification specification character string separated by the identification symbol " " in the verification specification text is a usage condition that is used as the name of a task. The information also indicates that, for example, a verification specification character string delimited by the identification symbol ( ) in the verification specification is used as a value, which is a usage condition. In addition, the information indicates, for example, that a verification specification string separated by the identification symbol " " in a verification specification statement is a usage condition to be used as a processing range in parallel processing, repeated processing, or assumption processing.

[0016] The condition information also includes information that associates the verification specification character string with the type of processing in the logical design verification. The information included in the condition information indicates, for example, that the verification specification character string is a character string related to a type of processing, such as an external input operation in a process related to a procedure. The information also indicates, for example, that the verification specification character string is a character string related to a type of processing, such as the manipulation of an internal signal in processing related to a procedure. The information also indicates, for example, that the verification specification character string is a character string related to a type of processing, such as an operation on elapsed time in processing related to a procedure. The information also indicates that the verification specification character string is a character string related to a type of processing, such as the operation of a task (user task) in a processing related to a procedure. A user task indicates a task set by a user. Furthermore, the information indicates, for example, that the verification specification character string is a character string related to a type of processing, such as processing for obtaining an expected value of an external output signal in processing related to an expected value. Furthermore, the information indicates, for example, that the verification specification character string is a character string relating to a type of processing, such as processing for obtaining an expected value of an internal signal in processing relating to an expected value. The information also indicates, for example, that the verification specification character string is a character string related to a type of processing, such as processing by using a user task in processing related to an expected value.

[0017] The component extraction unit 130A outputs verification specification information using the verification specification data and the condition information. The verification specification information includes a verification specification character string, a use condition, and a type of processing. That is, the component extraction unit 130A uses the verification specification data and the condition information to output, for each process, verification specification information including a verification specification character string, a use condition, and a type of process.

[0018] The test scenario output unit 140A generates and outputs a test scenario using the verification specification information. The test scenario output unit 140A uses the verification specification information to refer to a database that prestores verification specification strings and test scenario strings, and outputs a test scenario that includes a test scenario string that corresponds to the verification specification string and that is generated according to the usage conditions and the type of processing. The database is a verification database having a data structure in which verification specification character strings and test scenario character strings are associated with each other so that they can be converted into each other. The test scenario character string is, for example, a character string that expresses a process related to verification in a hardware description language (HDL).

[0019] The test scenario output unit 140A shown in FIG. 1 includes a process determination unit 141A, a search unit 142A, and a process description generation unit 143A.

[0020] The process determining unit 141A determines the type of process using the verification specification information. Specifically, the process determining unit 141A determines the type of each process in the logical design verification for each piece of verification specification information of the process unit, and outputs the process type as the determination result.

[0021] The search unit 142A outputs a test scenario character string corresponding to the verification specification character string. The search unit 142A uses the verification specification information to refer to a database that prestores verification specification strings and test scenario strings according to the type of processing determined by the processing determination unit 141A, and outputs a test scenario string corresponding to the verification specification string.

[0022] The process description generating unit 143A generates a test scenario description for each process and outputs a test scenario. The process description generator 143A uses the verification specification information and the test scenario character string to generate a test scenario description for each process in accordance with the use conditions and test scenario rules according to the type of process, and outputs a test scenario including the test scenario description. The rules for a test scenario may be information that is pre-stored in the test scenario generation device 100A, or may be information that is obtained from outside the test scenario generation device 100A.

[0023] In addition to the above components, the test scenario generation device 100A may also include a control unit (not shown), a storage unit (not shown), and a communication unit (not shown). A control unit (not shown) controls the entire test scenario generation device 100A and each of its components. The control unit (not shown) starts up the test scenario generation device 100A in response to, for example, an external command. The control unit (not shown) also controls the state (operating state = start-up, shutdown, sleep, etc.) of the test scenario generation device 100A. A storage unit (not shown) stores each data item used by the test scenario generation device 100 A. For example, a storage unit (not shown) stores the output (output data) from each component in the test scenario generation device 100 A, and outputs data requested by each component to the requesting component. A communication unit (not shown) communicates with an external device. For example, if the test scenario generation device 100A does not have a display unit, communication is performed between the test scenario generation device 100A and an external device such as a display device.

[0024] The process performed by the configuration according to the first embodiment of the present disclosure will be described. FIG. 2 is a flowchart illustrating an example of a test scenario generation process in the configuration according to the first embodiment of the present disclosure.

[0025] When the test scenario generation device 100A starts the test scenario generation process, it first executes a verification specification reception process (step ST1100). In the verification specification reception process, the verification specification reception unit 110A of the test scenario generation device 100A acquires verification specification data, and outputs the verification specification data to the component extraction unit 130A.

[0026] Next, the test scenario generation device 100A executes a condition acquisition process (step ST1200). In the condition acquisition process, the condition acquisition section 120A of the test scenario generation device 100A acquires condition information and outputs the condition information to the component extraction section 130A.

[0027] Next, the test scenario generation device 100A executes a component extraction process (step ST1300). In the component extraction process, the component extraction unit 130A of the test scenario generation device 100A acquires verification specification data from the verification specification receiving unit 110A. The component extraction unit 130A acquires condition information from the condition acquisition unit 120A. Using the verification specification data and the condition information, the component extraction unit 130A outputs verification specification information including a verification specification character string, a usage condition, and a type of processing for each processing. The component extraction unit 130A outputs the verification specification information to the test scenario output unit 140.

[0028] Next, the test scenario generation device 100A executes a test scenario output process (step ST1400). In the test scenario output process, the test scenario output unit 140A of the test scenario generation device 100A obtains verification specification information from the component extraction unit 130A. The test scenario output unit 140A uses the verification specification information to generate and output a test scenario. Specifically, the test scenario output unit 140A uses the verification specification information to refer to a database that prestores verification specification strings and test scenario strings, and outputs a test scenario that includes a test scenario string that corresponds to the verification specification string and that is generated according to the usage conditions and the type of processing.

[0029] When the test scenario output process ends, the test scenario generation device 100A ends the test scenario generation process.

[0030] Here, a specific example of the test scenario output process will be described. FIG. 3 is a flowchart illustrating an example of a specific process of the test scenario output process in the test scenario generation process according to the first embodiment of the present disclosure.

[0031] When the test scenario output unit 140A starts the test scenario output process, it starts a loop process (step ST1410). The number of loops in the loop processing is the same as the number of processes described in the verification specification data (number of loops=number of processes).

[0032] Next, the test scenario output unit 140A executes a component acquisition process (step ST1420). In the component acquisition process, the test scenario output unit 140A acquires the verification specification information from the component extraction unit 130A.

[0033] Next, the test scenario output section 140A executes a process type determination process (step ST1430). In the process type determination process, the process determination unit 141A of the test scenario output unit 140A determines the process type by using the verification specification information. Specifically, the process determination unit 141A determines the process type in the logical design verification for each piece of verification specification information of a process unit, and outputs the process type as the determination result.

[0034] Next, the test scenario output unit 140A executes a processing string search process (step ST1440). In the process string search process, the search unit 142A of the test scenario output unit 140A uses the verification specification information to refer to a database that pre-stores verification specification strings and test scenario strings according to the type of process that is the result of the judgment by the process judgment unit 141A, and outputs a test scenario string that corresponds to the verification specification string.

[0035] Next, the test scenario output section 140A executes a test scenario description output process (step ST1450). In the test scenario description output process, the processing description generation unit 143A of the test scenario output unit 140A uses the verification specification information and the test scenario character string to generate a test scenario description for each process in accordance with the test scenario rules corresponding to the usage conditions and the type of process, and outputs a test scenario including the test scenario description.

[0036] Next, the test scenario output unit 140A repeats the process the same number of times as the number of processes included in the verification specification data, and then ends the loop process (step ST1460). Next, the test scenario output unit 140A ends the test scenario generation process.

[0037] The process will now be described using a more detailed concrete example. FIG. 4 is a flowchart showing a more detailed example of the process shown in FIG. FIG. 4 shows a process equivalent to the internal process (step ST1420 to step ST1450) of the loop process shown in FIG.

[0038] When the test scenario output unit 140A starts the test scenario output process, it executes a component acquisition process (step ST1501) similar to the component acquisition process (step ST1420) already described.

[0039] Next, the test scenario output unit 140A executes a process type determination process (step ST1502). In the process type determination process, the process determination unit 141A of the test scenario output unit 140A determines whether the process is related to a procedure, related to an expected value, or neither. Specifically, the process determination unit 141A first determines whether the process is related to a procedure, and then determines whether the process is related to an expected value.

[0040] When the process determining unit 141A determines that the process is related to a procedure, the test scenario output unit 140A first outputs " / / comment statement" (step ST1510). The comment statement is in the form of a verification specification statement with a comment identification symbol / / added thereto.

[0041] Next, the process determining section 141A of the test scenario output section 140A determines whether the process is an external input operation (step ST1511). When the process determining unit 141A of the test scenario output unit 140A determines that the operation is not an external input operation ("NO" in step ST1511), the test scenario output unit 140A proceeds to the process of step ST1514, which will be described later. If the process determination unit 141A of the test scenario output unit 140A determines that the operation is an external input operation (step ST1511 “YES”), the test scenario output unit 140A then searches for an external signal (step ST1512). The search unit 142 of the test scenario output unit 140A refers to the database using the verification specification character string indicating the external signal name, and acquires a test scenario character string corresponding to the verification specification character string. Next, the test scenario output unit 140A outputs “external signal=value;” (step ST1513). The processing description generating unit 143A of the test scenario output unit 140A outputs “external signal=value;” using the values ​​included in the external signal test scenario character string and the verification specification character string. When the test scenario output section 140A finishes the process of step ST1513, it ends the series of processes that are the internal processes of the loop process.

[0042] When the process determining section 141A of the test scenario output section 140A determines that the operation is not an external input operation ("NO" in step ST1511), it then determines whether the operation is an internal signal operation (step ST1514). When the process determining section 141A of the test scenario output section 140A determines that the operation is not an internal signal operation ("NO" in step ST1514), the test scenario output section 140A proceeds to the process of step ST1517 described later. If the process determining section 141A of the test scenario output section 140A determines that the operation is an internal signal operation ("YES" in step ST1514), then the searching section 142A searches for the internal signal (step ST1515). Next, the test scenario output unit 140A outputs "force internal signal = value;" (step ST1516). Specifically, the processing description generating unit 143A of the test scenario output unit 140A outputs "force internal signal = value;" by using values ​​included in the test scenario character string and the verification specification character string. When the test scenario output section 140A finishes the process of step ST1516, it ends the series of processes that are the internal processes of the loop process.

[0043] When the process determining section 141A of the test scenario output section 140A determines that the operation is not an operation on an internal signal ("NO" in step ST1514), it then determines whether the operation is an operation on an elapsed time (step ST1517). When it is determined that the operation is not an operation for elapsed time ("NO" in step ST1517), the test scenario output section 140A proceeds to the process of step ST1520 described later. When the test scenario output section 140A determines that the operation is related to elapsed time ("YES" in step ST1517), it then searches for a clock (step ST1518). Next, the test scenario output section 140A outputs "repeat (value) @ (posedge clock);" (step ST1519). When the test scenario output section 140A finishes the process of step ST1519, it ends the series of processes that are the internal processes of the loop process.

[0044] If it is determined that the operation is not an operation regarding elapsed time ("NO" in step ST1517), the test scenario output unit 140A then determines whether it is an operation regarding a task (step ST1520). When it is determined that the operation is not a task operation ("NO" in step ST1520), the test scenario output section 140A ends a series of processes that are internal processes of the loop process. When it is determined that the operation is a task operation ("YES" at step ST1520), the test scenario output section 140A then searches for the task (step ST1521). Next, the test scenario output section 140B outputs "task (value);" (step ST1522). When the test scenario output section 140A finishes the process of step ST1522, it ends the series of processes that are the internal processes of the loop process.

[0045] When the test scenario output unit 140A determines in the process of step ST1502 that the process is related to an expected value, it first outputs " / / comment statement" (step ST1530).

[0046] Next, the test scenario output section 140A judges whether the external output is an expected value (step ST1531). When it is determined that the external output is not the expected value ("NO" in step ST1531), the test scenario output section 140A proceeds to the process of step ST1534 described later. When it is determined that the external output is the expected value ("YES" at step ST1531), the test scenario output section 140A then searches for an external signal (step ST1532). Next, the test scenario output section 140A outputs “external signal_exp=(value)” (step ST1533). When the test scenario output section 140A finishes the process of step ST1533, it ends the series of processes that are the internal processes of the loop process.

[0047] When it is determined that the value is not the expected value of the external output ("NO" at step ST1531), the test scenario output section 140A then determines whether the value is the expected value of the internal signal (step ST1534). When it is determined that the internal signal is not the expected value ("NO" in step ST1534), the test scenario output section 140A proceeds to the process of step ST1537 described later. When it is determined that the internal signal is the expected value ("YES" at step ST1534), the test scenario output section 140A then searches for the internal signal (step ST1535). Next, the test scenario output section 140A outputs “internal signal_exp=(value)” (step ST1536). When the test scenario output section 140A finishes the process of step ST1536, it ends the series of processes that are the internal processes of the loop process.

[0048] When it is determined that the internal signal is not the expected value ("NO" at step ST1534), the test scenario output section 140A then determines whether it is a task operation (step ST1537). When it is determined that the operation is not a task operation ("NO" in step ST1537), the test scenario output section 140A proceeds to the process of step ST1540 described later. When it is determined that the operation is a task operation ("YES" at step ST1537), the test scenario output section 140A then searches for the task (step ST1538). Next, the test scenario output section 140A outputs "task (value);" (step ST1539). When the test scenario output section 140A finishes the process of step ST1539, it ends the series of processes that are the internal processes of the loop process.

[0049] When the test scenario output unit 140A determines that the process is neither related to a procedure nor related to an expected value (non-applicable), it outputs " / / comment text" (step ST1540). Next, when the test scenario output section 140A finishes the process of step ST1540, it ends the series of processes that are the internal processes of the loop process.

[0050] The test scenario generation device of the present disclosure is configured as follows. Test scenario generator "A verification specification receiving unit that receives verification specification data describing a verification specification for each process in a logic design verification of a semiconductor integrated circuit, the verification specification including a verification specification character string separated by an identification symbol; and a condition acquiring unit that acquires condition information including information associating the identification symbol with a use condition related to use of the verification specification character string, and information associating the verification specification character string with a type of processing in the logical design verification; a component extraction unit that uses the verification specification data and the condition information to output, for each of the processes, verification specification information including the verification specification character string, the use condition, and the type of the process; a test scenario output unit that uses the verification specification information to refer to a database that prestores verification specification strings and test scenario strings, and outputs a test scenario that includes the test scenario strings that correspond to the verification specification strings, the test scenario being generated according to the use conditions and the type of processing; A test scenario generation device comprising: As a result, the present disclosure has an effect of providing a test scenario generation device that can improve the efficiency of logic design verification.

[0051] The program of the present disclosure is configured as follows. "Computers, a verification specification receiving unit for receiving verification specification data describing a verification specification for each process in a logic design verification of a semiconductor integrated circuit, the verification specification including a verification specification character string separated by an identification symbol; a condition acquiring unit that acquires condition information including information associating the identification symbol with a use condition related to use of the verification specification character string, and information associating the verification specification character string with a type of processing in the logical design verification; a component extraction unit that uses the verification specification data and the condition information to output, for each of the processes, verification specification information including the verification specification character string, the use condition, and the type of the process; a test scenario output unit that uses the verification specification information to refer to a database that prestores the verification specification string and a test scenario string, and outputs a test scenario that includes the test scenario string that corresponds to the verification specification string, the test scenario being generated according to the use conditions and the type of processing; A program that causes the device to operate as a test scenario generation device having the above-mentioned. As a result, the present disclosure provides an effect of providing a program that can improve efficiency of logic design verification.

[0052] The test scenario generation device of the present disclosure is further configured as follows. "The test scenario output unit is a process determination unit that determines a type of the process using the verification specification information; a search unit that uses the verification specification information to refer to the database that prestores verification specification strings and test scenario strings in accordance with the type of the process determined by the process determination unit, and outputs the test scenario string corresponding to the verification specification string; a process description generator that uses the verification specification information and the test scenario character string to generate a test scenario description for each process in accordance with a test scenario rule corresponding to the use condition and the type of the process, and outputs the test scenario including the test scenario description; The test scenario generation device according to claim 1, further comprising: As a result, the present disclosure has an effect of providing a test scenario generation device that outputs test scenarios capable of executing verification corresponding to a wide variety of processes. Furthermore, the present disclosure has an effect similar to the above effect by applying the above configuration to the above program or a verification device described later.

[0053] Embodiment 2 In the second embodiment, the following will be particularly described as an addition to the configuration of the first embodiment. ·Data structure of verification specification data Test scenario data including comments using the verification specification statements from the verification specification - Configuration to display reception images Configuration to obtain condition specification data including condition information Configuration to perform validation In the description of the second embodiment, the same descriptions as those of the first embodiment will be omitted as appropriate.

[0054] An example of a configuration according to the second embodiment will be described. FIG. 5 is a diagram showing an example of a configuration according to the second embodiment for implementing the present disclosure. FIG. 6 is an image diagram of test scenario generation according to the present disclosure. FIG. 7 shows an example of a description of a verification specification and an example of a test scenario according to the present disclosure. FIG. 8 is an example of a signal name comparison table in this disclosure. FIG. 9 is an example of a task search condition in the present disclosure. The verification device 10B acquires verification specification data, generates test scenario data using the acquired verification specification data, executes verification using the generated test scenario data, and outputs a verification result. A verification device 10B shown in FIG. 5 includes a verification section 15 and a test scenario generation device 100B. The verification unit 15 executes the verification using the test scenario. The verification unit 15 executes logic design verification of the semiconductor integrated circuit using the test scenario output by the test scenario output unit 140B of the test scenario generation device 100B, and outputs the verification result.

[0055] The test scenario generating device 100B acquires verification specification data, and generates and outputs test scenario data using the acquired verification specification data.

[0056] The verification specification data is electronic data of the verification specification, and in the embodiment of the present disclosure, is data including a search specification for each process in the logic design verification of a semiconductor integrated circuit. The search specification sentence is a sentence written in a natural language, and includes a verification specification character string separated by identification symbols. For example, the identification symbols can be symbols such as ",", (,), ",", and ",", as shown in Fig. 6 (Conditions and constraints for each development <Constraints>). The identification symbols can be set as conditions and constraints for each development, and can be acquired by the test scenario generation device 100B as condition information included in, for example, condition specification data. The verification specification character string includes a character string capable of identifying a process related to the logical design verification, and may further include a value used in the process. The verification specification data has a data structure capable of holding, for each process in the logical design verification, a value indicating the processing order, a verification specification string related to the process of the procedure, and a verification specification string related to the process of the expected value. For example, the verification specification data has a data structure capable of holding a value such as a number 1010 indicating the processing order, a verification specification string 1020 related to the process of the procedure, and a verification specification string 1030 related to the process of the expected value, as shown in FIG. Specifically, in FIG. 7, as the "number, verification specification component on the procedure side, verification specification component on the expected value side" for each process, the description 1000 of the verification specification shows "Process number 1, release "power on reset" (1'b1), -", "Process number 2, -, confirm that "output reset" has been released (1'b1)", "Process number 3, after 10 cycles of "125 MHz clock" have elapsed (10), -", and "Process number 4, -, confirm that the transmission status is transmission completed "AXI read" (1'b1, 4'h0,R_TX_STAT,32'h0000_0001)".

[0057] The test scenario data is electronic data describing a test scenario for verifying the logic design of a semiconductor integrated circuit. The test scenario includes a test scenario description written in a hardware description language (HDL) for each process related to the logic design verification. The test scenario generation device 100B shown in FIG. 5 is configured to include a verification specification receiving unit 110B, a condition acquisition unit 120B, a component extraction unit 130B, a test scenario output unit 140B, an input UI command unit 150, an output UI command unit 160, and a verification database 170.

[0058] The input UI command unit 150 commands a display unit or a display device (not shown) to present a reception image. The input UI command unit 150 is a reception image presentation unit in this disclosure. The input UI command unit 150, which serves as a reception image presentation unit, outputs reception images including a verification specification reception image, which is an image for accepting verification specification data, and a condition reception image, which is an image for accepting condition specification data including condition information.

[0059] The verification specification receiving unit 110B acquires verification specification data describing a verification specification for each process in the logic design verification of a semiconductor integrated circuit, the verification specification including a verification specification character string separated by identification symbols. The verification specification receiving unit 110B acquires the verification specification data via the verification specification receiving image.

[0060] The condition acquiring unit 120B acquires the condition information. The condition acquiring unit 120B acquires condition information including information associating an identification symbol with a use condition related to the use of a verification specification string, and information associating a verification specification string with a type of processing in logical design verification. The condition acquiring unit 120B acquires condition information using the condition specification data acquired via the condition receiving image.

[0061] The condition information includes information that associates an identification symbol with a usage condition related to the use of the verification specification character string. The information included in the condition information indicates, for example, that the verification specification character string separated by the identification symbol " " in the verification specification text is used as a signal name, which is a usage condition (see <Constraint> in the Conditions and Constraints for Each Development in Figure 6). This information also indicates that, for example, the verification specification character string separated by the identification symbol " " in the verification specification text is used as the name of the task, which is a usage condition (see <Constraint> in the conditions and constraints for each development shown in Figure 6). Also, this information indicates that, for example, the verification specification string separated by the identification symbol ( ) in the verification specification is used as a value, which is a usage condition (see <Constraint> in the conditions and constraints for each development shown in Figure 6). This information also indicates that, for example, the verification specification string separated by the identification symbol " " in the verification specification text is a usage condition, such as being used as the range of processing in parallel processing, repeated processing, or assumption processing (see <Constraints> in the conditions and constraints for each development shown in Figure 6).

[0062] The condition information also includes information that associates the verification specification character string with the type of processing in the logical design verification. The information included in the condition information indicates, for example, that the verification specification character string is a character string related to a type of processing, such as an external input operation in a process related to a procedure. The information also indicates, for example, that the verification specification character string is a character string related to a type of processing, such as the manipulation of an internal signal in processing related to a procedure. The information also indicates, for example, that the verification specification character string is a character string related to a type of processing, such as an operation on elapsed time in processing related to a procedure. The information also indicates that the verification specification character string is a character string related to a type of processing, such as the operation of a task (user task) in a processing related to a procedure. A user task indicates a task set by a user. Furthermore, the information indicates, for example, that the verification specification character string is a character string related to a type of processing, such as processing for obtaining an expected value of an external output signal in processing related to an expected value. Furthermore, the information indicates, for example, that the verification specification character string is a character string relating to a type of processing, such as processing for obtaining an expected value of an internal signal in processing relating to an expected value. The information also indicates, for example, that the verification specification character string is a character string related to a type of processing, such as processing by using a user task in processing related to an expected value. By using such information, it is possible to extract the types of processing indicated in the verification specification components (procedure components, expected value components) included in the verification specification data. The information also indicates, for example, that the verification specification character string is a character string related to a type of processing, such as parallel processing. The information also indicates, for example, that the verification specification character string is a character string related to a type of processing, such as a repetitive process. The information also indicates, for example, that the verification specification character string is a character string related to a type of processing, such as a presupposition processing.

[0063] The condition information may also include information that associates a verification specification string with a search string. The search string is a string that can be obtained by searching the verification database 170 for a test scenario string. The information included in the condition information is, for example, a signal name comparison table. Moreover, the information is, for example, task search conditions. 8, for example, signal name comparison table 1100 associates signal names 1110, which are verification specification character strings, with signal names 1120, which are search character strings. Specifically, signal name comparison table 1100 associates "power-on reset" with "PREL", "output reset" with "RELO", "error LED" with "ERRLED", "WDT error" with "WDTERR", "ready signal" with "AAA.ready", "initialization completion flag" with "BBB.initend_flag", and "125 MHz clock" with "clk125m". 9, the task search condition 1200 associates a task name 1210 as a verification specification character string with a task name 1220 as a search character string. Specifically, the task search condition 1200 associates "reset release" with "reset_release;", "initial setting" with "initial_set;", "AXI write 32" with "axi_write32(port,id,addr,data);", "AXI read 32" with "axi_read32(port,id,addr,data);", "MPU write" with "MPU_Write(addr,data);", and "MPU read" with "MPU_Read(addr,data);". In the present embodiment, the condition information includes information that associates a verification specification string with a search string, but is not limited to information that includes information that associates a verification specification string with a search string when the verification specification string is a string that can be searched by referring to a database. Therefore, in the present disclosure, the verification specification string includes a search string.

[0064] The component extraction unit 130B outputs verification specification information using the verification specification data and the condition information. The verification specification information includes a verification specification character string, a use condition, and a type of processing. That is, the component extraction unit 130B uses the verification specification data and the condition information to output, for each process, verification specification information including a verification specification character string, a use condition, and a type of process.

[0065] The test scenario output unit 140B generates and outputs a test scenario using the verification specification information. The test scenario output unit 140B uses the verification specification information to refer to a database that pre-stores verification specification strings and test scenario strings, and outputs a test scenario that includes a test scenario string that corresponds to the verification specification string and that is generated according to the usage conditions and the type of processing. The database referred to by the test scenario output unit 140B is the verification database 170. The verification database 170 stores beforehand a verification specification character string (search character string) and a test scenario character string in association with each other. The test scenario character string is, for example, a character string that expresses a process related to verification in a hardware description language (HDL).

[0066] In addition, the test scenario output unit 140B outputs a test scenario including, for each process in the logical design verification, a value indicating the process order, a verification specification string separated by an identification symbol, and a comment statement including the type of process in the logical design verification, as well as a comment identification symbol added to the comment statement.

[0067] Furthermore, the test scenario output unit 140B can determine specific processes that are frequent in the processes related to the verification and include a test scenario description indicating the specific processes. The specific processing is, for example, parallel processing, iterative processing, and assumption processing. An assumed condition process is a process that is executed if a certain condition is met.

[0068] The test scenario output unit 140B shown in FIG. 5 includes a process determination unit 141B, a search unit 142B, a process description generation unit 143B, a specific process determination unit 144, and a specific process description generation unit 145.

[0069] The process determining unit 141B determines the type of process using the verification specification information. Specifically, the process determining unit 141B determines the type of each process in the logical design verification for each piece of verification specification information of the process unit, and outputs the process type as the determination result. The process determining unit 141B includes a specific process determining unit 144. The specific process determination unit 144 uses the verification specification information to determine the type of specific process, such as parallel process, repeated process, or assumption-based process, and outputs the type of process as the determination result.

[0070] The search unit 142B outputs a test scenario character string corresponding to the verification specification character string. The search unit 142B uses the verification specification information to refer to a database that prestores verification specification strings and test scenario strings according to the type of processing determined by the processing determination unit 141B, and outputs a test scenario string corresponding to the verification specification string.

[0071] The process description generator B generates a test scenario description for each process and outputs a test scenario. The process description generator B uses the verification specification information and the test scenario character string to generate a test scenario description for each process in accordance with the use conditions and test scenario rules corresponding to the type of process, and outputs a test scenario including the test scenario description. The rules for a test scenario may be information that is pre-stored in the test scenario generation device 100B, or may be information that is obtained from outside the test scenario generation device 100B. The processing description generator B includes a specific processing description generator 145 . The specific process description generating unit 145 generates a test scenario description related to the specific process according to the type of the specific process determined by the specific process determining unit 144 . The processing description generating unit B outputs a test scenario including a test scenario description relating to a specific processing.

[0072] The output UI command unit 160 issues a command to display a presentation image for presenting the test scenario output from the test scenario output unit 140B. FIG. 10 is a flowchart illustrating an example of a test scenario generation process in the configuration according to the second embodiment of the present disclosure. When the test scenario generation device 100B starts the test scenario generation process, it first executes a received image presentation process (step ST2100). In the reception image presentation process, the input UI command unit 150 of the test scenario generation device 100B outputs reception images including a verification specification reception image, which is an image for accepting verification specification data, and a condition reception image, which is an image for accepting condition specification data including condition information.

[0073] Next, the test scenario generation device 100B executes a verification specification reception process (step ST2200). In the verification specification reception process, the verification specification reception unit 110B of the test scenario generation device 100B acquires the verification specification data via the verification specification reception image. The verification specification receiving unit 110B acquires verification specification data describing a verification specification for each process in the logic design verification of a semiconductor integrated circuit, the verification specification including a verification specification character string separated by identification symbols. The verification specification receiving unit 110B outputs the verification specification data to the component extracting unit 130B.

[0074] Next, the test scenario generation device 100B executes a condition acquisition process (step ST2300). In the condition acquisition process, the condition acquisition unit 120B of the test scenario generation device 100B acquires condition information including information associating an identification symbol with a usage condition related to the use of the verification specification string, and information associating the verification specification string with a type of processing in logical design verification. The condition acquiring unit 120B acquires condition information using the condition specification data acquired via the condition receiving image. The condition acquiring section 120B outputs the condition information to the component extracting section 130B.

[0075] Next, the test scenario generation device 100B executes a component extraction process (step ST2400). In the component extraction process, the component extraction unit 130B of the test scenario generation device 100B acquires verification specification data from the verification specification receiving unit 110B. The component extraction unit 130B acquires condition information from the condition acquisition unit 120B. Using the verification specification data and the condition information, the component extraction unit 130B outputs verification specification information including a verification specification character string, a use condition, and a type of processing for each processing.

[0076] Next, the test scenario generation device 100B executes a test scenario output process (step ST2500). In the test scenario output process, the test scenario output unit 140B of the test scenario generation device 100B acquires the verification specification information from the component extraction unit 130B. Using the verification specification information, the test scenario output unit 140B refers to a database that stores verification specification strings and test scenario strings in advance, and outputs a test scenario that includes a test scenario string corresponding to the verification specification string and is generated according to the use conditions and the type of processing. At this time, the test scenario output unit 140B outputs the test scenario including a comment statement including a value indicating the processing order, a verification specification string separated by an identification symbol, and the type of processing in the logical design verification, and a comment identification symbol added to the comment statement, for each processing in the logical design verification. The test scenario output unit 140B outputs the test scenario to the output UI command unit 160.

[0077] Next, the test scenario generation device 100B executes a test scenario presentation process (step ST2600). In the test scenario presentation process, the output UI command unit 160 of the test scenario generation device 100B issues a command to display a presentation image for presenting the test scenario output from the test scenario output unit 140B.

[0078] When the test scenario output process ends, the test scenario generation device 100B ends the test scenario generation process.

[0079] Here, a specific example of the test scenario output process will be described. FIG. 11 is a flowchart illustrating an example of a specific process of the test scenario output process in the test scenario generation process according to the second embodiment of the present disclosure. When the test scenario output unit 140B starts the test scenario output process, it starts a loop process (step ST2510). The number of loops in the loop processing is the same as the number of processes described in the test scenario (number of loops = number of processes).

[0080] Next, the test scenario output unit 140B executes a component acquisition process (step ST2520). In the component acquisition process, the test scenario output unit 140B acquires the verification specification information from the component extraction unit 130B.

[0081] Next, the test scenario output section 140B executes a specific process type determination process (step ST2530). In the specific processing type determination process, the specific processing determination unit 144 in the processing determination unit 141B of the test scenario output unit 140B uses the verification specification information to determine the type of specific processing, such as parallel processing, iterative processing, and assumption condition processing, and outputs the type of processing as the determination result.

[0082] Next, the test scenario output unit 140B executes a specific processing string search process (step ST2540). In the specific process character string search process, the search unit 142B of the test scenario output unit 140B refers to the verification database 170 according to the type of specific process to obtain a test scenario character string for the specific process.

[0083] Next, the test scenario output unit 140B executes a test scenario description output process (step ST2550). In the test scenario description output process, the specific process description generation unit 145 in the process description generation unit 143B of the test scenario output unit 140B generates a test scenario description related to the specific process according to the type of the specific process determined by the specific process determination unit 144.

[0084] Next, the test scenario output unit 140B executes a process type determination process (step ST2560). In the process type determination process, the process determination section 141B of the test scenario output section 140B determines the type of process using the verification specification information. Specifically, the process determining unit 141B determines the type of each process in the logical design verification for each piece of verification specification information of the process unit, and outputs the process type as the determination result.

[0085] Next, the test scenario output unit 140B executes a processing string search process (step ST2570). In the process string search process, the search unit 142B of the test scenario output unit 140B outputs a test scenario string corresponding to a verification specification string. The search unit 142B uses the verification specification information to refer to a database that prestores verification specification strings and test scenario strings according to the type of processing determined by the processing determination unit 141B, and outputs a test scenario string corresponding to the verification specification string.

[0086] Next, the test scenario output unit 140B executes a test scenario description output process (step ST2580). In the test scenario description output process, the process description generating unit 143B of the test scenario output unit 140B generates a test scenario description for each process and outputs the test scenario. The process description generating unit 143B uses the verification specification information and the test scenario character string to generate a test scenario description for each process in accordance with the use conditions and the test scenario rules according to the type of process, and outputs a test scenario including the test scenario description.

[0087] Next, the test scenario output section 140B outputs the test scenario description for each process described in the test scenario, and then ends the loop process (step ST2590). Next, the test scenario output unit 140B ends the test scenario generation process.

[0088] The process will now be described using a more detailed concrete example. FIG. 12 (FIGS. 12A and 12B) is a flowchart showing a more detailed specific example of the process shown in FIG. 12A and 12B show processing equivalent to the internal processing (step ST2520 to step ST2580) of the loop processing shown in FIG.

[0089] When the test scenario output unit 140B starts the test scenario output process, it executes a component acquisition process (step ST2801) similarly to the component acquisition process (step ST2520) already described.

[0090] Next, the test scenario output section 140B judges whether the process is a specific process (STEP ST2802 shown in FIG. 12A). When the test scenario output section 140B judges that the process is not a specific process ("NO" in step ST2802), the test scenario output section 140B proceeds to the process of step ST2840 described later.

[0091] When it is determined that the process is a specific process ("YES" at step ST2802), the test scenario output section 140B then determines whether the process is a parallel process (step ST2810). When the test scenario output section 140B determines that the processing is not parallel processing ("NO" in step ST2810), the test scenario output section 140B proceeds to the processing in step ST2820 described later. When it is determined that the processing is parallel processing ("YES" at step ST2810), the test scenario output section 140B then outputs " / / comment statement" (step ST2811). Next, the test scenario output section 140B outputs "fork" at the beginning and "join" at the end (step ST2812). Next, the test scenario output unit 140B outputs "begin" to the beginning of the parallel processing target and "end" to the end of the parallel processing target (step ST2813).

[0092] When the process of step ST2813 is completed, or when it is determined that the process is not parallel ("NO" at step ST2810), the test scenario output section 140B then determines whether the process is a repeat process (step ST2820). If the test scenario output section 140B determines that the process is not a repetitive process ("NO" in step ST2820), the test scenario output section 140B proceeds to the process of step ST2830, which will be described later. When it is determined that the process is a repetitive process ("YES" at step ST2820), the test scenario output unit 140B outputs " / / comment statement" (step ST2821). Next, the test scenario output section 140B outputs for (loop=0; loop<value; loop=loop+1) (step ST2822). Next, the test scenario output unit 140B outputs "begin" to the beginning of the loop processing target and "end" to the end of the loop processing target (step ST2823).

[0093] When the process of step ST2823 is completed, or when it is determined that the process is not a repetitive process ("NO" at step ST2820), the test scenario output section 140B then determines whether it is a premise condition process (step ST2830). When the test scenario output section 140B determines that the processing is not the assumed condition processing ("NO" in step ST2830), it proceeds to the processing in step ST2840, which will be described later. When the test scenario output section 140B judges that the processing is a presuppositional condition processing (step ST2830), it then outputs " / / comment statement" (step ST2831). Next, the test scenario output section 140B outputs "if (condition)" (step ST2832). Next, the test scenario output section 140B outputs "begin" to the beginning of the assumption condition processing target and "end" to the end of the assumption condition processing target (step ST2833).

[0094] Next, when the process of step ST2833 is completed, or when it is determined that the process is not a presuppositional condition process (step ST2830 “NO”), the test scenario output unit 140B The process type determination process (step ST2840 shown in FIG. 12B) is executed. In the process type determination process, the process determination unit 141B of the test scenario output unit 140B determines whether the process is related to a procedure, related to an expected value, or neither. Specifically, the process determination unit 141A first determines whether the process is related to a procedure, and then determines whether the process is related to an expected value.

[0095] When it is determined in the process of step ST2840 that the process is related to a procedure, the test scenario output section 140B first outputs " / / comment statement" (step ST2850).

[0096] Next, the test scenario output section 140B judges whether the operation is an external input operation (step ST2851). When it is determined that the operation is not an external input operation ("NO" in step ST2851), the test scenario output section 140B proceeds to the process of step ST2854 described later. When the test scenario output section 140B judges that the operation is an external input operation ("YES" at step ST2851), it then searches for an external signal (step ST2852). Next, the test scenario output section 140B outputs “external signal=value;” (step ST2853). When the test scenario output section 140B finishes the process of step ST2853, it ends the series of processes that are the internal processes of the loop process.

[0097] When it is determined that the operation is not an external input operation ("NO" at step ST2851), the test scenario output section 140B then determines whether it is an internal signal operation (step ST2854). When the test scenario output section 140B determines that the manipulation is not an internal signal manipulation ("NO" in step ST2854), it proceeds to the process of step ST2857 described later. When the test scenario output section 140B judges that the operation is an internal signal operation ("YES" at step ST2854), it then searches for the internal signal (step ST2855). Next, the test scenario output section 140B outputs "force internal signal=value;" (step ST2856). After completing the process of step ST2856, the test scenario output section 140B then ends the series of processes that are the internal processes of the loop process.

[0098] If the test scenario output unit 140B determines that the operation is not an internal signal operation (step ST2854 "NO"), it then determines whether the operation is an elapsed time operation (step ST2857). If the test scenario output unit 140B determines that the operation is not an elapsed time operation (step ST2857 "NO"), it proceeds to the process of step ST2860 described later. When the test scenario output section 140B judges that the operation is related to elapsed time ("YES" in step ST2857), it then searches for a clock (step ST2858). Next, the test scenario output section 140B outputs "repeat (value) @ (posedge clock);" (step ST2859). When the test scenario output section 140B finishes the process of step ST2859, it ends the series of processes that are the internal processes of the loop process.

[0099] When it is determined that the operation is not an operation regarding elapsed time ("NO" in step ST2857), the test scenario output section 140B then determines whether the operation is an operation regarding a task (step ST2860). When it is determined that the operation is not a task operation ("NO" in step ST2860), the test scenario output section 140B ends a series of processes that are internal processes of the loop process. When it is determined that the operation is a task operation ("YES" at step ST2860), the test scenario output section 140B then searches for the task (step ST2861). Next, the test scenario output section 140B outputs “task (value);” (step ST2862). When the test scenario output section 140B finishes the process of step ST2862, it ends the series of processes that are the internal processes of the loop process.

[0100] When the test scenario output unit 140B determines in step ST2840 that the process is related to an expected value, it first outputs " / / comment statement" (step ST2870).

[0101] Next, the test scenario output section 140B judges whether the external output is an expected value (step ST2871). When it is determined that the external output is not the expected value ("NO" in step ST2871), the test scenario output section 140B proceeds to the process of step ST2874 described later. When it is determined that the external output is the expected value ("YES" at step ST2871), the test scenario output section 140B then searches for an external signal (step ST2872). Next, the test scenario output section 140B outputs “external signal_exp=(value)” (step ST2873). When the test scenario output section 140B finishes the process of step ST2873, it ends the series of processes that are the internal processes of the loop process.

[0102] When it is determined that the value is not the expected value of the external output ("NO" at step ST2871), the test scenario output section 140B then determines whether the value is the expected value of the internal signal (step ST2874). When it is determined that the internal signal is the expected value ("YES" at step ST2874), the test scenario output section 140B then searches for the internal signal (step ST2875). Next, the test scenario output section 140B outputs “internal signal_exp=(value)” (step ST2876). When the test scenario output section 140B finishes the process of step ST2876, it ends the series of processes that are the internal processes of the loop process.

[0103] When it is determined that the internal signal is not the expected value ("NO" at step ST2874), the test scenario output section 140B then determines whether it is a task operation (step ST2877). When it is determined that the operation is not a task operation ("NO" in step ST2877), the test scenario output section 140B ends a series of processes that are internal processes of the loop process. When it is determined that the operation is a task operation ("YES" at step ST2877), the test scenario output section 140B searches for the task (step ST2878). Next, the test scenario output section 140B outputs “task (value);” (step ST2879). When the test scenario output section 140B finishes the process of step ST2879, it ends the series of processes that are the internal processes of the loop process.

[0104] When the test scenario output unit 140B determines that the process is neither related to a procedure nor related to an expected value (non-applicable), it outputs " / / comment text" (step ST2880). Next, when the test scenario output section 140A finishes the process of step ST2880, it ends the series of processes that are the internal processes of the loop process.

[0105] According to the above disclosure, the test scenario generation device 100 can output a test scenario 2000 using, for example, the description 1000 of the verification specification in FIG. Specifically, verification specification information such as type = procedure, external input signal name = power-on reset = PREL, (value) = (1'b1) can be extracted from the verification specification statement data "Process number 1, Cancel "power-on reset" (1'b1), -" in the verification specification data, and the test scenario description for process 1, " / / Cancel "power-on reset" (1'b1):Set" "PREL = (1'b1);" can be generated using the verification specification information. In addition, verification specification information such as type = expected value, internal signal name = output reset, (value) = (1'b1) can be extracted from the verification specification statement data "Process number 2, -, Confirm that "output reset" has been released (1'b1)" in the verification specification data, and the test scenario description of process 2, " / / Confirm that "output reset" has been released (1'b1): Confirm", "RELO_exp = 1'b1", can be generated using this verification specification information. In addition, from the verification specification statement data “Process No. 3, after 10 cycles of the “125 MHz clock” (10), -” in the verification specification data, verification specification information such as type = procedure, elapsed time signal name = 125 MHz clock, (value) = (10) can be extracted, and the test scenario description of process 3 “ / / After 10 cycles of the “125 MHz clock” (10): setting” “clk125m→repeat (value) @ (posedge clk125m) ;” can be generated using the verification specification information. In addition, from the verification specification statement data “Processing number 4, -, Confirm that the transmission status is transmission completed “AXI read” (1'b1, 4'h0,R_TX_STAT,32'h0000_0001)” in the verification specification data, verification specification information such as type = expected value, task = AXI read, (value) = (1'b1, 4'h0,R_TX_STAT,32'h0000_0001) can be extracted, and the test scenario description of process 4 “ / / Confirm that the transmission status is transmission completed “AXI read” (1'b1, 4'h0,R_TX_STAT,32'h0000_0001): Confirm” “axi_read32(1'b1, 4'h0,R_TX_STAT,32'h0000_0001)” can be generated using this verification specification information.

[0106] The verification device of the present disclosure is further configured as follows. "A verification specification receiving unit that receives verification specification data describing a verification specification for each process in a logic design verification of a semiconductor integrated circuit, the verification specification including a verification specification character string separated by an identification symbol; and a condition acquiring unit that acquires condition information including information associating the identification symbol with a use condition related to use of the verification specification character string, and information associating the verification specification character string with a type of processing in the logical design verification; a component extraction unit that uses the verification specification data and the condition information to output, for each of the processes, verification specification information including the verification specification character string, the use condition, and the type of the process; a test scenario output unit that uses the verification specification information to refer to a database that prestores the verification specification string and a test scenario string, and outputs a test scenario that includes the test scenario string that corresponds to the verification specification string, the test scenario being generated according to the use conditions and the type of processing; a verification unit that performs logic design verification of the semiconductor integrated circuit using the test scenario output by the test scenario output unit and outputs a verification result; A verification device comprising: As a result, the present disclosure provides an effect of providing a verification apparatus capable of improving the efficiency of logic design verification.

[0107] The test scenario generation device of the present disclosure is configured as follows. "The verification specification data is data having a data structure capable of holding, for each process in the logic design verification, a value indicating a processing order, a verification specification character string relating to the processing of a procedure, and a verification specification character string relating to the processing of an expected value, The test scenario output unit includes: outputting the test scenario including, for each process in the logical design verification, a comment statement including a value indicating a process order, a verification specification character string separated by the identification symbol, and a type of the process in the logical design verification, and a comment identification symbol added to the comment statement; A test scenario generation device characterized by the above. As a result, the present disclosure has an effect of providing a test scenario generation device that outputs a test scenario that allows a user to easily check the contents of the test scenario. Furthermore, the present disclosure has an effect similar to the above-mentioned effect by applying the above-mentioned configuration to the above-mentioned program or a verification device described later.

[0108] The test scenario generation device of the present disclosure is further configured as follows. "Further comprising a reception image presenting unit that outputs reception images including a verification specification reception image, which is an image for receiving the verification specification data, and a condition reception image, which is an image for receiving condition specification data including the condition information, the verification specification receiving unit acquires the verification specification data via the verification specification receiving image, The condition acquisition unit acquires the condition information by using the condition specification data acquired via the condition reception image. A test scenario generation device characterized by the above. The present disclosure thus provides an advantageous effect of providing a test scenario generation device. Furthermore, the present disclosure provides the same advantageous effect as the above-described effect by applying the above-described configuration to the above-described program or the above-described verification device.

[0109] Embodiment 3 If a tester finds an error in the verification specification as a result of using a test scenario, the tester modifies the test scenario and performs the verification again. At this time, for example, the tester may provide feedback on the verification specification document with the details of the verification specification that should be modified. In the third embodiment, a form for realizing a function for generating a verification specification from a test scenario will be described.

[0110] An example of a configuration according to the third embodiment will be described. FIG. 13 is a diagram showing an example of a configuration according to the third embodiment for implementing the present disclosure. FIG. 14 is a diagram illustrating an example of the internal configuration of the verification specification output unit 182 in this disclosure. FIG. 15 is an image diagram of verification specification generation according to the present disclosure.

[0111] Similar to the verification device 10B already described, the verification device 10C acquires verification specification data, generates test scenario data using the acquired verification specification data, performs verification using the generated test scenario data, and outputs the verification results. A verification device 10C shown in FIG. 13 includes a verification section 15C and a test scenario generation device 100C.

[0112] Similar to the verification unit 15 already described, the verification unit 15C performs logic design verification of the semiconductor integrated circuit using the test scenario output by the test scenario output unit 140C of the test scenario generation device 100C, and outputs the verification result.

[0113] The test scenario generating device 100C is configured to generate a verification specification from a test scenario, in addition to the functions of the test scenario generating device 100B already described. The test scenario generation device 100C shown in FIG. 13 is configured to include a verification specification receiving unit 110C, a condition acquisition unit 120C, a component extraction unit 130C, a test scenario output unit 140C, an input UI command unit 150C, an output UI command unit 160C, a verification database 170C, a test scenario receiving unit 180, a second condition acquisition unit (condition acquisition unit) 181, a verification specification statement extraction unit, and a verification specification output unit 183.

[0114] The configurations of the verification specification receiving unit 110C, the condition acquiring unit C, the component extraction unit 130C, the test scenario output unit 140C, and the verification database 170C are similar to those of the verification specification receiving unit 110A, 110B, the condition acquiring unit A, 120B, the component extraction unit 130A, 130B, the test scenario output unit 140A, 140B, and the verification database 170, which have already been explained, and therefore detailed explanations thereof will be omitted here.

[0115] 13 includes a configuration for generating a test scenario using a verification specification, as well as a configuration for generating a verification specification from a test scenario, but it may be configured without the function of generating a test scenario using a verification specification. In this configuration, the test scenario generation device 100C is a verification specification generation device.

[0116] The input UI command unit 150C has the same function as the input UI command unit 150 already described. In addition, the input UI command unit 150C presents a reception image for receiving test scenario data, and outputs the scenario data to the test scenario receiving unit 180 when the test scenario data is received via the reception image.

[0117] The test scenario receiving unit 180 acquires a test scenario from an external source. The test scenario receiving unit 180 acquires, for each process in the logical design verification of a semiconductor integrated circuit, a test scenario including a comment statement including a value indicating the processing order, a verification specification string separated by an identification symbol, and a type of process in the logical design verification, and a comment identification symbol added to the comment statement.

[0118] The second condition acquiring unit (condition acquiring unit) 181 acquires condition information (second condition information) indicating an area in the verification specification where the verification specification statement should be written. The second condition acquisition unit acquires second condition information including information associating types of processing in logical design verification with areas in which verification specifications should be written in the verification specification data. For example, as shown in Fig. 15, the second condition information associates types of processing, such as processing related to a procedure and processing related to an expected value, with verification specification statement area 1020 related to processing of the procedure and verification specification statement area 1030 related to processing of the expected value in verification specification description 1000 shown in Fig. 7.

[0119] The verification specification output unit 182 outputs a verification specification for each process using the comment statements included in the test scenario. The verification specification output unit 182 outputs the comment statements identified by the comment identification symbols from the test scenarios acquired by the test scenario receiving unit 180 as verification specification statements for each process in the logical design verification.

[0120] Verification specification output unit 183 outputs verification specification data in which the verification specification output by verification specification output unit 182 is described in an area indicated in the second condition information acquired by the second condition acquisition unit.

[0121] The verification specification output unit 182 shown in FIG. 14 includes a component extractor 186 , a verification specification generator 187 , a process determiner 188 , and a verification specification writer 189 .

[0122] The component extracting section 130 extracts comment statements from the test scenario data. Specifically, the component extraction section 130 identifies and extracts comment sentences based on comment identification symbols included in the test scenario data.

[0123] The verification specification generator 187 generates and outputs a verification specification for each process using the comment and the type of process.

[0124] The process determination unit 188 uses the comment text to determine the type of process, and outputs information indicating the type of process, which is the determination result.

[0125] The verification specification writing unit 189 uses the second condition information and the verification specification to write the verification specification into an area in the verification specification included in the second condition information.

[0126] The output UI command section 160C has the same function as the output UI command section 160 already described. In addition, the output UI command unit 160C issues a command to display a presentation image for presenting the verification specification data output from the verification specification output unit 183.

[0127] An example of the verification specification generation process of the present disclosure will be described. The process performed by the configuration for realizing the function of generating test scenarios using verification specifications is similar to the process already described, and therefore a description of the process will be omitted here. Here, an example of a verification specification generation process using a configuration that realizes a function of generating a verification specification from a test scenario will be described.

[0128] FIG. 16 is a flowchart illustrating an example of the verification specification generation process of the present disclosure. When the test scenario generation device 100C (verification specification generation device) starts the verification specification generation process, first, it executes a received image presentation process (step ST3100). In the reception image presentation process, the input UI command unit 150C of the test scenario generation device 100C (verification specification generation device) presents a reception image for accepting test scenario data.

[0129] Next, the test scenario generation device 100C (verification specification generation device) executes a test scenario reception process (step ST3200). In the test scenario reception process, the test scenario reception unit 180 of the test scenario generation device 100C (verification specification generation device) acquires test scenario data via the input UI command unit 150C.

[0130] Next, the test scenario generation device 100C (verification specification generation device) executes a second condition acquisition process (Step ST3300). In the second condition acquisition process, the second condition acquisition unit (condition acquisition unit) 181 of the test scenario generation device 100C (verification specification generation device) acquires condition information (second condition information) indicating an area in which a verification specification statement should be written in the verification specification.

[0131] Next, the test scenario generation device 100C (verification specification generation device) starts a loop process (step ST3400).

[0132] Next, the test scenario generation device 100C (verification specification generation device) executes a verification specification output process (step ST3500). In the verification specification output process, the verification specification output unit 182 of the test scenario generation device 100C (verification specification generation device) outputs a verification specification for each process by using a comment statement included in the test scenario. The verification specification output unit 182 outputs the comment statements identified by the comment identification symbols from the test scenarios acquired by the test scenario receiving unit 180 as verification specification statements for each process in the logical design verification.

[0133] Here, an example of detailed processing by the verification specification output unit 182 will be described. FIG. 17 is a flowchart showing an example of a specific process of the verification specification statement output process in the verification specification generation process of the present disclosure.

[0134] When the verification specification output unit 182 starts the verification specification output process, it first executes a comment statement extraction process (step ST3510). In the comment statement extraction process, the component extraction unit 130 of the verification specification output unit 182 identifies the comment statements based on the comment identification symbols, and extracts, for each process in the logic design verification of the semiconductor integrated circuit, a comment statement including a value indicating the process order, a verification specification character string delimited by the identification symbols, and a type of process in the logic design verification. The component extraction unit 130 outputs the comment statements to the verification specification output unit 182.

[0135] Next, the verification specification output unit 182 executes a process type determination process (step ST3520). In the process type determination process, the process determination unit 188 acquires a comment text from the component extraction unit 130. The process determination unit 188 determines the process type using the comment text. The process determination unit 188 outputs information indicating the process type, which is the determination result.

[0136] Next, the verification specification output unit 182 executes a verification specification generation process (step ST3530). In the verification specification generation process, the verification specification generation unit 187 obtains a comment statement from the component extraction unit 130. The verification specification generation unit 187 also obtains information indicating the type of processing from the process determination unit 188. The verification specification generation unit 187 generates and outputs a verification specification for each processing by using the comment statement and the type of processing.

[0137] Next, the verification specification output unit 182 executes a verification specification writing process (step ST3540). In the verification specification writing process, the verification specification writing unit obtains second condition information from the second condition obtaining unit. Also, the verification specification writing unit obtains the verification specification from the verification specification generating unit 187. The verification specification writing unit uses the second condition information and the verification specification to write the verification specification in an area of ​​the verification specification indicated in the second condition information.

[0138] When the verification specification output unit 182 finishes the verification specification writing process, it ends the series of processes that are the internal processes of the loop process.

[0139] Returning to the explanation of Figure 16. Next, the test scenario generation device 100C (verification specification generation device) repeats the loop process as many times as the number of processes included in the test scenario data, and then ends the loop process (step ST3600).

[0140] Next, the test scenario generation device 100C (verification specification generation device) executes a verification specification output process (Step ST3700). In the verification specification output process, the verification specification output unit 183 of the test scenario generation device 100C (verification specification generation device) outputs verification specification data.

[0141] Next, the test scenario generation device 100C (verification specification generation device) executes a verification specification presentation process (Step ST3800). In the verification specification presentation process, when the output UI command unit 160C of the test scenario generation device 100C (verification specification generation device) acquires verification specification data, it outputs an image for presenting the verification specification data to the user.

[0142] When the test scenario generation device 100C (verification specification generation device) finishes the verification specification presentation process, it ends the verification specification generation process.

[0143] The test scenario generation device of the present disclosure is configured as follows. "A test scenario receiving unit that receives, for each process in the logical design verification, a test scenario including a comment statement including a value indicating a process order, a verification specification character string separated by the identification symbol, and a type of the process in the logical design verification, and a comment identification symbol added to the comment statement; a second condition acquisition unit that acquires second condition information including information that associates a type of processing in the logical design verification with an area in which a verification specification statement should be written in the verification specification data; a verification specification output unit that outputs a comment statement identified by the comment identification symbol from the test scenario acquired by the test scenario receiving unit as a verification specification statement for each process in the logical design verification; a verification specification output unit that outputs verification specification data in which the verification specification output by the verification specification output unit is described in the area indicated in the second condition information acquired by the second condition acquisition unit; The test scenario generation device according to claim 4, further comprising: As a result, the present disclosure has the effect of providing a test scenario generation device that can generate a verification specification from a test scenario, thereby facilitating feedback to a design department. Furthermore, the present disclosure has the effect of providing the same effect as the above by applying the above configuration to the above program or the above verification device.

[0144] The search specification generating device of the present disclosure is configured as follows. "A test scenario receiving unit that receives, for each process in a logic design verification of a semiconductor integrated circuit, a test scenario including a comment statement including a value indicating a process order, a verification specification character string separated by an identification symbol, and a type of the process in the logic design verification, and a comment identification symbol added to the comment statement; a second condition acquiring unit that acquires second condition information including information that associates a type of process in the logical design verification with an area in which a verification specification statement should be written in the verification specification data; a verification specification output unit that outputs a comment statement identified by the comment identification symbol from the test scenario acquired by the test scenario receiving unit as a verification specification statement for each process in the logical design verification; a verification specification output unit that outputs verification specification data in which the verification specification output by the verification specification output unit is described in the area indicated in the second condition information acquired by the second condition acquisition unit; A verification specification generating device characterized by the above. In this manner, the present disclosure provides an effect of providing a verification specification generation device capable of improving efficiency of logical design verification. Furthermore, the present disclosure provides the same effect as the above by applying the above configuration to the above program or the above verification device.

[0145] The program of the present disclosure is configured as follows. "Computers, a test scenario receiving unit that receives, for each process in a logic design verification of a semiconductor integrated circuit, a test scenario including a comment statement including a value indicating a process order, a verification specification character string separated by an identification symbol, and a type of the process in the logic design verification, and a comment identification symbol added to the comment statement; a second condition acquisition unit that acquires second condition information including information that associates a type of processing in the logical design verification with an area in which a verification specification statement should be written in the verification specification data; a verification specification output unit that outputs a comment statement identified by the comment identification symbol from the test scenario acquired by the test scenario receiving unit as a verification specification statement for each process in the logical design verification; a verification specification output unit that outputs verification specification data in which the verification specification output by the verification specification output unit is described in accordance with information included in the second condition information acquired by the second condition acquisition unit; A program that causes the device to operate as a verification specification generating device having the above. As a result, the present disclosure can improve the efficiency of logic design verification. This brings about the effect of being able to provide a program.

[0146] Here, a hardware configuration for realizing the functions of the present disclosure will be described. FIG. 18 is a diagram illustrating a first example of a hardware configuration for realizing the functions of the present disclosure. FIG. 19 is a diagram illustrating a second example of a hardware configuration for realizing the functions of the present disclosure. The verification device 10 (10B, 10C), the test scenario generation device 100 (100A, 100B, 100C), and the verification specification generation device of the present disclosure are each realized by hardware such as that shown in FIG. 18 or FIG.

[0147] The verification device 10 (10B, 10C), the test scenario generation device 100 (100A, 100B, 100C), or the verification specification generation device includes, for example, a processor 10001, a memory 10002, and a communication circuit 10004, as shown in FIG. The processor 10001 and the memory 10002 are installed in, for example, a computer. The memory 10002 stores the computer, verification units 15 and 15C, a verification specification receiving unit 110 (110A, 110B, 110C), a condition acquiring unit 120 (120A, 120B, 120C), a component extracting unit 130 (130A, 130B, 130C), a test scenario output unit 140 (140A, 140B, 140C), a processing determining unit 141 (141A, 141B, 141C), a search unit 142 (142A, 142B, 142C), a processing description generating unit 143 (143A, 143B, 143C), a processing execution unit 144 (144A, 144B, 144C), a processing execution unit 145 (145A, 145B, 145C), a processing execution unit 146 (146A, 146B, 146C), a processing execution unit 147 (147A, 147B, 147C), a processing execution unit 148 (148A, 148B, 148C), a processing execution unit 149 (149A, 149B, 149C), a processing execution unit 150 (150A, 150B, 150C), a processing execution unit 151 (151A, 151B, 151C), a processing execution unit 152 (152A, 152B, 152C), a processing execution unit 153 (153A, 153B, 153C), a processing execution unit 154 (154A, 154B, 154C), a processing execution unit 155 (155A, 15 3C), specific processing judgment units 144, 144C, specific processing description generation units 145, 145C, input UI command units 150, 150C, output UI command units 160, 160C, test scenario reception unit 180, second condition acquisition unit (condition acquisition unit) 181, verification specification output unit 182, verification specification output unit 183, component extraction unit 186, verification specification generation unit 187, processing judgment unit 188, verification specification writing unit 189, and programs for functioning as a control unit not shown are stored. The processor 10001 reads out and executes the program stored in the memory 10002, thereby controlling the verification units 15 and 15C, the verification specification receiving unit 110 (110A, 110B, 110C), the condition acquiring unit 120 (120A, 120B, 120C), the component extracting unit 130 (130A, 130B, 130C), the test scenario output unit 140 (140A, 140B, 140C), the process determining unit 141 (141A, 141B, 141C), the search unit 142 (142A, 142B, 142C), the process recording unit 143 (143A, 143B, 143C), the process determining unit 144 (144A, 144B, 144C), the process determining unit 145 (145A, 145B, 145C), the process determining unit 146 (146A, 146B, 146C), the process determining unit 147 (147A, 147B, 147C), the process determining unit 148 (148A, 148B, 148C), the process determining unit 149 (149A, 149B, 149C), the process determining unit 150 (150A, 150B, 150C), the process determining unit 151 (151A, 151B, 151C), the process determining unit 152 (152A, 152B, 152C), the process determining unit 153 (153A, 153B, 153C), the process determining unit 154 (154A, 154B, 154C), The functions of predicate generation unit 143 (143A, 143B, 143C), specific process judgment unit 144, 144C, specific process description generation unit 145, 145C, input UI command unit 150, 150C, output UI command unit 160, 160C, test scenario reception unit 180, second condition acquisition unit (condition acquisition unit) 181, verification specification statement output unit 182, verification specification statement output unit 183, component extraction unit 186, verification specification statement generation unit 187, process judgment unit 188, verification specification statement writing unit 189, and a control unit (not shown) are realized. Furthermore, a storage unit (not shown) is realized by the memory 10002 or another memory (not shown). Furthermore, if the verification device 10 (10B, 10C), the test scenario generation device 100 (100A, 100B, 100C), or the verification specification generation device includes the verification databases 170, 170B, 170C, the verification databases 170, 170B, 170C are realized by the memory 10002 or another memory (not shown). Furthermore, the communication circuit 10004 realizes a communication unit (not shown). The processor 10001 may be, for example, a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor, a microcontroller, or a digital signal processor (DSP). The memory 10002 may be a non-volatile or volatile semiconductor memory such as a RAM (Random Access Memory), a ROM (Read Only Memory), an EPROM (Erasable Programmable ROM), an EEPROM (Electrically Erasable Programmable Read Only Memory) or a flash memory, or a magnetic disk such as a hard disk or a flexible disk, or an optical disk such as a CD (Compact Disc) or a DVD (Digital Versatile Disc), or a magneto-optical disk. The processor 10001 and the memory 10002 or the communication circuit 10004 are connected in a state in which they can transmit data to each other. The processor 10001, the memory 10002, and the communication circuit 10004 are also connected via the input / output interface 10003 in a state in which they can transmit data to other hardware.

[0148] Or, the verification units 15 and 15C, the verification specification receiving unit 110 (110A, 110B, 110C), the condition acquiring unit 120 (120A, 120B, 120C), the component extracting unit 130 (130A, 130B, 130C), the test scenario output unit 140 (140A, 140B, 140C), the process determining unit 141 (141A, 141B, 141C), the search unit 142 (142A, 142B, 142C), the process description generating unit 143 (143A, 143B, 143C), the specific process determining unit 144 (144A, 144B, 144C), the process description generating unit 145 (145A, 145B, 145C), the specific process determining unit 146 (146A, 146B, 146C), the process description generating unit 147 (147A, 147B, 147C), the process description generating unit 148 (148A, 148B, 148C), the process description generating unit 149 (149A, 149B, 149C), the process description generating unit 150 (150A, 150B, 150C), the process description generating unit 151 (151A, 151B, 151C), the process description generating unit 152 (152A, 152B, 152C), the process description generating unit 153 (153A, 153B, 153C), the specific process determining unit 154 (154A, 154B, 154C), the process description generating unit 155 (155A, The functions of C, specific processing description generation units 145, 145C, input UI command units 150, 150C, output UI command units 160, 160C, test scenario reception unit 180, second condition acquisition unit (condition acquisition unit) 181, verification specification output unit 182, verification specification output unit 183, component extraction unit 186, verification specification generation unit 187, processing judgment unit 188, verification specification writing unit 189, and a control unit (not shown) may be realized by a dedicated processing circuit 20001, as shown in FIG. 19. Furthermore, the communication circuit 10004 realizes a communication unit (not shown). The processing circuit 20001 may be, for example, a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), an FPGA (Field-Programmable Gate Array), a SoC (System-on-a-Chip), or a system LSI (Large-Scale Integration), etc. Furthermore, the memory 20002 or another memory (not shown) implements a storage unit (not shown). The memory 20002 may be a non-volatile or volatile semiconductor memory such as a RAM (Random Access Memory), a ROM (Read Only Memory), an EPROM (Erasable Programmable ROM), an EEPROM (Electrically Erasable Programmable Read Only Memory) or a flash memory, or a magnetic disk such as a hard disk or a flexible disk, or an optical disk such as a CD (Compact Disc) or a DVD (Digital Versatile Disc), or a magneto-optical disk. Furthermore, the communication circuit 20004 realizes a communication unit (not shown). The processing circuit 20001 and the memory 20002 or the communication circuit 20004 are connected in a state in which they can transmit data to each other. In addition, the processing circuit 20001, the memory 20002, and the communication circuit 20004 are connected in a state in which they can transmit data to other hardware via the input / output interface 20003. In addition, the verification units 15 and 15C, the verification specification receiving unit 110 (110A, 110B, 110C), the condition acquiring unit 120 (120A, 120B, 120C), the component extracting unit 130 (130A, 130B, 130C), the test scenario output unit 140 (140A, 140B, 140C), the process determining unit 141 (141A, 141B, 141C), the search unit 142 (142A, 142B, 142C), the process description generating unit 143 (143A, 143B, 143C), the specific process determining unit 144 and 145 (146A, 146B, 146C), the process description generating unit 145 (146A, 146B, 146C), the process description generating unit 146 (146A, 146B, 146C), the process description generating unit 147 (147A, 147B, 147C), the process description generating unit 148 (148A, 148B, 148C), the process description generating unit 149 (149A, 149B, 149C), the process description generating unit 150 (150A, 150B, 150C), the process description generating unit 151 (151A, 151B, 151C), the process description generating unit 152 (152A, 152B, 152C), the process description generating unit 153 (153A, 153B, 153C), the process description generating unit 154 (154A, 154B, 154C), the process description generating unit 155 The functions of 4C, specific processing description generation unit 145, 145C, input UI command unit 150, 150C, output UI command unit 160, 160C, test scenario reception unit 180, second condition acquisition unit (condition acquisition unit) 181, verification specification output unit 182, verification specification output unit 183, component extraction unit 186, verification specification generation unit 187, processing judgment unit 188, verification specification writing unit 189, and a control unit (not shown) may be realized by separate processing circuits or may be realized together by a processing circuit.

[0149] Alternatively, the verification units 15 and 15C, the verification specification receiving unit 110 (110A, 110B, and 110C), the condition acquiring unit 120 (120A, 120B, and 120C), the component extracting unit 130 (130A, 130B, and 130C), the test scenario output unit 140 (140A, 140B, and 140C), the process determining unit 141 (141A, 141B, and 141C), the search unit 142 (142A, 142B, and 142C), the process description generating unit 143 (14 3A, 143B, 143C), specific process determination unit 144, 144C, specific process description generation unit 145, 145C, input UI command unit 150, 150C, output UI command unit 160, 160C, test scenario reception unit 180, second condition acquisition unit (condition acquisition unit) 181, verification specification output unit 182, verification specification output unit 183, component extraction unit 186, verification specification generation unit 187, process determination unit 188, verification specification writing unit 189, Furthermore, some of the functions of a control unit (not shown) may be realized by the processor 10001 and memory 10002, and the remaining functions may be realized by the processing circuit 20001.

[0150] In addition, the present disclosure allows free combination of the respective embodiments, modification of any of the components of each embodiment, or omission of any of the components of each embodiment.

[0151] The technique of the present disclosure can improve the efficiency of logic design verification of semiconductor integrated circuits, and is therefore suitable for use in techniques relating to logic design verification of semiconductor integrated circuits. [Explanation of symbols]

[0152] 10 (10B, 10C) verification device, 15, 15C verification unit, 100 (100A, 100B, 100C) test scenario generation device, 110 (110A, 110B, 110C) verification specification reception unit, 120 (120A, 120B, 120C) condition acquisition unit, 130 (130A, 130B, 130C) component extraction unit, 140 (140A, 140B, 140C) test scenario output unit, 141 (141A, 141B, 141C) processing judgment unit, 142 (142A, 142B, 142C) search unit, 143 (143A, 143B, 143C) processing description generation unit, 144, 144C specific processing judgment unit, 145, 145C specific process description generation unit, 150, 150C input UI command unit, 160, 160C output UI command unit, 170, 170C verification database, 180 test scenario reception unit, 181 second condition acquisition unit (condition acquisition unit), 182 verification specification statement output unit, 183 verification specification statement output unit, 186 component extraction unit, 187 verification specification statement generation unit, 188 process judgment unit, 189 verification specification statement writing unit, 1000 verification specification statement example, 1010 number (value indicating processing order), 1020 verification specification statement entry area relating to procedure, 1030 verification specification statement entry area relating to expected value, 1100 signal name comparison table, 1110 signal name string, 1120 test scenario string, 1200 task search condition, 1210 task name string, 1220 test scenario string.

Claims

1. a verification specification receiving unit for receiving verification specification data describing a verification specification for each process in a logic design verification of a semiconductor integrated circuit, the verification specification including a verification specification character string separated by an identification symbol; a condition acquiring unit that acquires condition information including information associating the identification symbol with a use condition related to use of the verification specification character string, and information associating the verification specification character string with a type of processing in the logic design verification; a component extraction unit that uses the verification specification data and the condition information to output, for each process, verification specification information including the verification specification character string, the use condition, and the type of the process; a test scenario output unit that uses the verification specification information to refer to a database that prestores verification specification strings and test scenario strings, and outputs a test scenario that includes the test scenario strings that correspond to the verification specification strings, the test scenario being generated according to the use conditions and the type of processing; A test scenario generating device comprising:

2. The test scenario output unit includes: a process determination unit that determines a type of the process using the verification specification information; a search unit that uses the verification specification information to refer to the database that prestores verification specification strings and test scenario strings in accordance with the type of the process determined by the process determination unit, and outputs the test scenario string corresponding to the verification specification string; a process description generator that uses the verification specification information and the test scenario character string to generate a test scenario description for each process in accordance with a test scenario rule corresponding to the use condition and the type of the process, and outputs the test scenario including the test scenario description; 2. The test scenario generating device according to claim 1, further comprising:

3. a reception image presenting unit that outputs reception images including a verification specification reception image that is an image for receiving the verification specification data, and a condition reception image that is an image for receiving condition specification data including the condition information, the verification specification receiving unit acquires the verification specification data via the verification specification receiving image, The condition acquisition unit acquires the condition information by using the condition specification data acquired via the condition reception image.

2. The test scenario generating device according to claim 1,

4. the verification specification data has a data structure capable of holding, for each process in the logical design verification, a value indicating a processing order, a verification specification character string related to a process of a procedure, and a verification specification character string related to a process of an expected value; The test scenario output unit includes: outputting the test scenario including, for each process in the logical design verification, a comment statement including a value indicating a process order, a verification specification character string separated by the identification symbol, and a type of the process in the logical design verification, and a comment identification symbol added to the comment statement; 4. The test scenario generating device according to claim 1, wherein the test scenario generating device generates a test scenario based on the test scenario.

5. a test scenario receiving unit that receives, for each process in the logical design verification, a test scenario including a comment statement including a value indicating a process order, a verification specification string separated by the identification symbol, and a type of the process in the logical design verification, and a comment identification symbol added to the comment statement; a second condition acquiring unit that acquires second condition information including information that associates a type of process in the logical design verification with an area in which a verification specification statement should be written in the verification specification data; a verification specification output unit that outputs a comment statement identified by the comment identification symbol from the test scenario acquired by the test scenario receiving unit as a verification specification statement for each process in the logic design verification; a verification specification output unit that outputs verification specification data in which the verification specification output by the verification specification output unit is described in the area indicated in the second condition information acquired by the second condition acquisition unit; Further equipped with 5. The test scenario generating device according to claim 4.

6. a test scenario receiving unit that receives, for each process in a logic design verification of a semiconductor integrated circuit, a test scenario including a comment statement including a value indicating a process order, a verification specification character string separated by an identification symbol, and a type of the process in the logic design verification, and a comment identification symbol added to the comment statement; a second condition acquiring unit that acquires second condition information including information that associates a type of process in the logical design verification with an area in which a verification specification statement should be written in the verification specification data; a verification specification output unit that outputs a comment statement identified by the comment identification symbol from the test scenario acquired by the test scenario receiving unit as a verification specification statement for each process in the logic design verification; a verification specification output unit that outputs verification specification data in which the verification specification output by the verification specification output unit is described in the area indicated in the second condition information acquired by the second condition acquisition unit; A verification specification generating device comprising:

7. Computer, a verification specification receiving unit for receiving verification specification data describing a verification specification for each process in a logic design verification of a semiconductor integrated circuit, the verification specification including a verification specification character string separated by an identification symbol; a condition acquiring unit that acquires condition information including information associating the identification symbol with a use condition related to use of the verification specification character string, and information associating the verification specification character string with a type of processing in the logic design verification; a component extraction unit that uses the verification specification data and the condition information to output, for each process, verification specification information including the verification specification character string, the use condition, and the type of the process; a test scenario output unit that uses the verification specification information to refer to a database that prestores the verification specification string and a test scenario string, and outputs a test scenario including the test scenario string that corresponds to the verification specification string, the test scenario being generated according to the use conditions and the type of processing; A program for causing a test scenario generating device to operate as a test scenario generating device comprising:

8. Computer, a test scenario receiving unit that receives, for each process in a logic design verification of a semiconductor integrated circuit, a test scenario including a comment statement including a value indicating a process order, a verification specification character string separated by an identification symbol, and a type of the process in the logic design verification, and a comment identification symbol added to the comment statement; a second condition acquiring unit that acquires second condition information including information associating the comment identification symbol with a position in the verification specification data where the comment should be described, and information associating a type of processing in the logical design verification with an area in the verification specification data where a verification specification statement should be described; a verification specification output unit that outputs a comment statement identified by the comment identification symbol from the test scenario acquired by the test scenario receiving unit as a verification specification statement for each process in the logic design verification; a verification specification output unit that outputs verification specification data in which the verification specification output by the verification specification output unit is described in the area indicated in the second condition information acquired by the second condition acquisition unit; A program for causing the device to operate as a verification specification generating device comprising the steps of:

9. a verification specification receiving unit for receiving verification specification data describing a verification specification for each process in a logic design verification of a semiconductor integrated circuit, the verification specification including a verification specification character string separated by an identification symbol; a condition acquiring unit that acquires condition information including information associating the identification symbol with a use condition related to use of the verification specification character string, and information associating the verification specification character string with a type of processing in the logic design verification; a component extraction unit that uses the verification specification data and the condition information to output, for each process, verification specification information including the verification specification character string, the use condition, and the type of the process; a test scenario output unit that uses the verification specification information to refer to a database that prestores the verification specification string and a test scenario string, and outputs a test scenario including the test scenario string that corresponds to the verification specification string, the test scenario being generated according to the use conditions and the type of processing; a verification unit that performs logic design verification of the semiconductor integrated circuit using the test scenario output by the test scenario output unit and outputs a verification result; A verification device comprising:

Citation Information

Patent Citations

  • Semiconductor integrated circuit test method and semiconductor integrated circuit test support method

    WO2004023554A1