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.
12. lappuse
... valid command and data sets, and the verification engineer concentrates on the behavior of the design based on the functional input stimulus. TABLE 1.1 s Examples of functional stimulus and stimulus Æ. 2 Verification engineers cannot ...
... valid command and data sets, and the verification engineer concentrates on the behavior of the design based on the functional input stimulus. TABLE 1.1 s Examples of functional stimulus and stimulus Æ. 2 Verification engineers cannot ...
28. lappuse
... valid scenarios to the design and performed all pertinent checks. This is the tape-out readiness checkpoint. Chapter 13 contains full details on the regression process. 1.6.6. Fabricate. Hardware. The design team releases the hardware to ...
... valid scenarios to the design and performed all pertinent checks. This is the tape-out readiness checkpoint. Chapter 13 contains full details on the regression process. 1.6.6. Fabricate. Hardware. The design team releases the hardware to ...
48. lappuse
... valid Outputs DUV clean_stack(0) will invalidate the entire stack pop_buf(0:1) directs the logic to pop the top 0, 1, or 2 entries from the stack the next cycle A DUV has inputs and input descriptions. This DUV has four sets of input ...
... valid Outputs DUV clean_stack(0) will invalidate the entire stack pop_buf(0:1) directs the logic to pop the top 0, 1, or 2 entries from the stack the next cycle A DUV has inputs and input descriptions. This DUV has four sets of input ...
52. lappuse
... valid instructions (op-codes) to the execution unit. When verifying HDL A by itself (macro-level hierarchy), the verification engineer needs to know all valid op-codes, and that invalid op-codes should cause exceptions and not be passed ...
... valid instructions (op-codes) to the execution unit. When verifying HDL A by itself (macro-level hierarchy), the verification engineer needs to know all valid op-codes, and that invalid op-codes should cause exceptions and not be passed ...
55. lappuse
... valid? s What is the behavior if we read and write the same cycle, and can we even do this? s FIGURE 2.12 out_buf_data1(0:8), out_buf_data2(0:8) are the requested data lines. 2.2 Strategy of Verification 55 2.2.3 Checking the Black Box.
... valid? s What is the behavior if we read and write the same cycle, and can we even do this? s FIGURE 2.12 out_buf_data1(0:8), out_buf_data2(0:8) are the requested data lines. 2.2 Strategy of Verification 55 2.2.3 Checking the Black Box.
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