Abstract: Disclosed herein is a method and a system for transaction based verification of a design under test (DUT) by a test bench. The method includes configuring the design under test with at least one configuration, the at least one configuration comprising one or more configuration values, the one or more configuration values changing during a transaction; applying at least one input to the DUT to generate at least one output, the at least one output based on a configuration value; associating a list of changed one or more configuration values with at least one abstract input transaction to generate at least one input transaction, the at least one abstract input transaction being generated by abstracting the at least one input; associating a list of changed one or more configuration values with one or more abstract output transactions to generate at least one output transaction, the one or more abstract output transactions being generated by abstracting the at least one output; determining one or more expected transactions based on the at least one input transaction using one or more transfer functions; generating an outcome as pass/fail based on comparing the at least one output transaction with each of the one or more expected transactions.
CLIAMS:We claim:
1. A method for transaction based verification of a design under test (DUT) by a test bench, the method comprising:
configuring the design under test with at least one configuration, the at least one configuration comprising one or more configuration values, the one or more configuration values changing during a transaction;
applying at least one input to the DUT to generate at least one output, the at least one output based on a configuration value;
associating a list of changed one or more configuration values with at least one abstract input transaction to generate at least one input transaction, the at least one abstract input transaction being generated by abstracting the at least one input;
associating a list of changed one or more configuration values with one or more abstract output transactions to generate at least one output transaction, the one or more abstract output transactions being generated by abstracting the at least one output;
determining one or more expected transactions based on the at least one input transaction using one or more transfer functions;
generating an outcome as pass/fail based on comparing the at least one output transaction with each of the one or more expected transactions.
2. The method of claim1, wherein each of the one or more transfer functions is based on corresponding configuration value of the changed one or more configuration values during the transaction.
3. The method of claim 1, wherein each of the one or more transfer functions is based on functional specification of the DUT.
4. The method of claim 1, further comprising storing list of changed one or more configuration values.
5. The method of claim 1, further comprising providing access to instantaneous value of the configuration to a scoreboard.
6. The method of claim 1, wherein associating list of changed one or more configuration values with the one or more abstract input transactions comprises:
adding pointers to one or more configuration values to the one or more abstract input transactions.
7. The method of claim 1, wherein associating list of changed one or more configuration values with the one or more abstract output transactions comprises:
adding pointer to one or more configuration values to the one or more abstract output transactions.
8. The method of claim 1, wherein the step of applying one or more input values to the DUT occurs independently of the step of configuring the design under test with at least one configuration.
9. A system for transaction based verification of a design under test (DUT) by a test bench , the system comprising:
a configuration interface to configure the design under test with at least one configuration, the at least one configuration comprising one or more configuration values, the one or more configuration values changing during a transaction;
a DUT having at least one input to the DUT to generate at least one output, the at least one output based on a configuration value;
a first transaction adder to:
associate a list of changed one or more configuration values with at least one abstract input transaction to generate at least one input transaction, the at least one abstract input transaction being generated by abstracting the at least one input;
a second transaction adder to:
associate a list of changed one or more configuration values with one or more abstract output transactions to generate at least one output transaction, the one or more abstract output transactions being generated by abstracting the at least one output;
a scoreboard to:
determine one or more expected transactions based the at least one input transaction using one or more transfer functions;
generate an outcome as pass/fail based on comparing the at least one output transaction with each of the one or more expected transactions.
10. The system of claim 9, wherein each of the one or more transfer functions is based on corresponding configuration value of the changed one or more configuration values during the transaction.
11. The system of claim 10, wherein each of the one or more transfer functions is based on functional specification of the DUT.
12. The system of claim 9, wherein associating list of changed one or more configuration values with the one or more abstract input transactions comprises:
adding pointers to one or more configuration values to the one or more abstract input transactions.
13. The system of claim 9, wherein associating list of changed one or more configuration values with the one or more abstract output transactions comprises:
adding pointer to one or more configuration values to the one or more abstract output transactions.
14. The system of claim 9, wherein a state aggregator stores list of changed one or more configuration values.
Dated this 11th day of March 2014
R Ramya Rao
Of K&S Partners
Agent for the Applicant
,TagSPECI:Technical Field
This disclosure relates generally to verify functionality of the design under test (DUT), and more particularly to simulation based functional verification of the DUT using transaction based approach.
| # | Name | Date |
|---|---|---|
| 1 | 1256-CHE-2014 FORM-9 11-03-2014.pdf | 2014-03-11 |
| 2 | 1256-CHE-2014 FORM-18 11-03-2014.pdf | 2014-03-11 |
| 3 | IP26608-spec.pdf | 2014-03-12 |
| 4 | IP26608-fig.pdf | 2014-03-12 |
| 5 | FORM 5.pdf | 2014-03-12 |
| 6 | FORM 3.pdf | 2014-03-12 |
| 7 | Certified copy request.pdf | 2014-03-12 |
| 8 | 1256-CHE-2014-FER.pdf | 2019-11-26 |
| 9 | 1256-CHE-2014-FORM-26 [25-05-2020(online)].pdf | 2020-05-25 |
| 10 | 1256-CHE-2014-FORM 3 [25-05-2020(online)].pdf | 2020-05-25 |
| 11 | 1256-CHE-2014-FER_SER_REPLY [25-05-2020(online)].pdf | 2020-05-25 |
| 12 | 1256-CHE-2014-US(14)-HearingNotice-(HearingDate-01-12-2021).pdf | 2021-11-10 |
| 13 | 1256-CHE-2014-POA [30-11-2021(online)].pdf | 2021-11-30 |
| 14 | 1256-CHE-2014-FORM 13 [30-11-2021(online)].pdf | 2021-11-30 |
| 15 | 1256-CHE-2014-Correspondence to notify the Controller [30-11-2021(online)].pdf | 2021-11-30 |
| 16 | 1256-CHE-2014-AMENDED DOCUMENTS [30-11-2021(online)].pdf | 2021-11-30 |
| 17 | 1256-CHE-2014-Written submissions and relevant documents [11-12-2021(online)].pdf | 2021-12-11 |
| 18 | 1256-CHE-2014-PETITION UNDER RULE 137 [11-12-2021(online)].pdf | 2021-12-11 |
| 20 | 1256-CHE-2014-IntimationOfGrant29-12-2021.pdf | 2021-12-29 |
| 21 | 1256-CHE-2014-FORM 4 [19-03-2023(online)].pdf | 2023-03-19 |
| 22 | 1256-CHE-2014-RELEVANT DOCUMENTS [20-09-2023(online)].pdf | 2023-09-20 |
| 1 | SearchStrategy_17-10-2019.pdf |
| 2 | SearchStrategy2AE_25-09-2020.pdf |