Comprehensive Functional Verification: The Complete Industry CycleElsevier, 2005. gada 26. maijs - 704 lappuses One of the biggest challenges in chip and system design is determining whether the hardware works correctly. That is the job of functional verification engineers and they are the audience for this comprehensive text from three top industry professionals.As designs increase in complexity, so has the value of verification engineers within the hardware design team. In fact, the need for skilled verification engineers has grown dramatically--functional verification now consumes between 40 and 70% of a project's labor, and about half its cost. Currently there are very few books on verification for engineers, and none that cover the subject as comprehensively as this text. A key strength of this book is that it describes the entire verification cycle and details each stage. The organization of the book follows the cycle, demonstrating how functional verification engages all aspects of the overall design effort and how individual cycle stages relate to the larger design process. Throughout the text, the authors leverage their 35 plus years experience in functional verification, providing examples and case studies, and focusing on the skills, methods, and tools needed to complete each verification task.
|
No grāmatas satura
1.–5. rezultāts no 79.
14. lappuse
... sequences and internal-state machine values individually or in sequence, formal verification proves that a protocol, assertion, or design rule holds true for all possible cases in the design. The major drawback of formal verification is ...
... sequences and internal-state machine values individually or in sequence, formal verification proves that a protocol, assertion, or design rule holds true for all possible cases in the design. The major drawback of formal verification is ...
60. lappuse
... sequence of events. Over the course of a test case, enough writes to the stack need to occur so that there are exactly six entries loaded. Then, the test case must set the clean_stack and in_buf_valid signals simultaneously. At this ...
... sequence of events. Over the course of a test case, enough writes to the stack need to occur so that there are exactly six entries loaded. Then, the test case must set the clean_stack and in_buf_valid signals simultaneously. At this ...
74. lappuse
... sequence to the design. This pre-determined input sequence may be generated in a direct approach or by a random method. The test bench, or environment, is a closed system, meaning that the top level of the test bench has no inputs or ...
... sequence to the design. This pre-determined input sequence may be generated in a direct approach or by a random method. The test bench, or environment, is a closed system, meaning that the top level of the test bench has no inputs or ...
80. lappuse
... sequence with the responder. In the cache to main store example, there can be variability in the response (successful completion or failure) and in the number of cycles between command and response (if the timing is not fixed allows) ...
... sequence with the responder. In the cache to main store example, there can be variability in the response (successful completion or failure) and in the number of cycles between command and response (if the timing is not fixed allows) ...
84. lappuse
... sequence occurs. The scoreboard observes and records the initiator stimulus, sending a fetch command to the cache design. The scoreboard must observe the stimulus on the interface, rather than have the initiator stimulus component write ...
... sequence occurs. The scoreboard observes and records the initiator stimulus, sending a fetch command to the cache design. The scoreboard must observe the stimulus on the interface, rather than have the initiator stimulus component write ...
Saturs
3 | |
SIMULATIONBASED VERIFICATION | 139 |
FORMAL VERIFICATION | 437 |
COMPREHENSIVE VERIFICATION | 537 |
CASE STUDIES | 601 |
VERIFICATION GLOSSARY | 641 |
REFERENCES | 657 |
SUBJECT INDEX | 663 |
Citi izdevumi - Skatīt visu
Comprehensive Functional Verification: The Complete Industry Cycle Bruce Wile,John Goss,Wolfgang Roesner Ierobežota priekšskatīšana - 2005 |
Comprehensive Functional Verification: The Complete Industry Cycle Bruce Wile,John C. Goss,Wolfgang Roesner Priekšskatījums nav pieejams - 2005 |
Bieži izmantoti vārdi un frāzes
abstraction algorithm array assertions behavior blocks Boolean cache Calc1 Calc2 cation Chapter checker checking components chip clock command complete constraints create debug design team design under verification drive error escape analysis event-driven example execution Figure formal verification functional verification FV tools hardware hardware description language ification implementation initial input instruction stream interface language latches level of verification logic memory microprocessor monitor multiple occur on-the-fly opcode OpenVera operand operation output packet parameters performance pipeline port problem processor property specification language protocol queue random re-use reference model regression requires reset scan ring scenarios scoreboard sequence signal simulation engine specification stimulus component structure tape-out test bench tion transaction unit update valid verifica verification components verification cycle verification engineer verification environment verification plan verification team Verilog VHDL