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 40.
54. lappuse
... operands (not specified on our example) and store the results in R7. The BRZ instruction must test the contents of R7 and branch to the target instruction address (again, unspecified in our example) if the contents equal zero. The ...
... operands (not specified on our example) and store the results in R7. The BRZ instruction must test the contents of R7 and branch to the target instruction address (again, unspecified in our example) if the contents equal zero. The ...
64. lappuse
... operands and write the results into GPR2 and GPR7. Note that the end-of-test case checks not only verify that the design writes correct instruction results to GPR2 and GPR7 but also verify that the operand GPRs remain unchanged. Figure ...
... operands and write the results into GPR2 and GPR7. Note that the end-of-test case checks not only verify that the design writes correct instruction results to GPR2 and GPR7 but also verify that the operand GPRs remain unchanged. Figure ...
66. lappuse
... operands to verify the design of the adder. The verification engineer pays special attention to creating test cases with ... operand needed to verify that the adder overflow works, a template with keywords such as OVERFLOW tells the test ...
... operands to verify the design of the adder. The verification engineer pays special attention to creating test cases with ... operand needed to verify that the adder overflow works, a template with keywords such as OVERFLOW tells the test ...
121. lappuse
Esat sasniedzis šīs grāmatas aplūkošanas reižu limitu.
Esat sasniedzis šīs grāmatas aplūkošanas reižu limitu.
122. lappuse
Esat sasniedzis šīs grāmatas aplūkošanas reižu limitu.
Esat sasniedzis šīs grāmatas aplūkošanas reižu limitu.
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 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 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 test bench components tion transaction unit update valid verifica verification components verification cycle verification engineer verification environment verification plan verification team Verilog VHDL