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 85.
10. lappuse
... input combination yields the correct next state. In the case of the traffic light mentioned above, there are just 2 bits of internal latches, yielding 4 possible current states, and 5 input pins, yielding 32 possible input combinations ...
... input combination yields the correct next state. In the case of the traffic light mentioned above, there are just 2 bits of internal latches, yielding 4 possible current states, and 5 input pins, yielding 32 possible input combinations ...
12. lappuse
... input pins. Rather than verify the entire chip at once, the verification team will carve out subcomponents of the design and verify these pieces separately. Once the smaller, more manageable pieces are verified, the team stitches the ...
... input pins. Rather than verify the entire chip at once, the verification team will carve out subcomponents of the design and verify these pieces separately. Once the smaller, more manageable pieces are verified, the team stitches the ...
14. lappuse
... input scenarios 2. Flag any incorrect behavior exhibited by the design Verification engineers attack the challenge by using two fundamental methods: (1) simulation-based verification and (2) formal verification, or verifying the design ...
... input scenarios 2. Flag any incorrect behavior exhibited by the design Verification engineers attack the challenge by using two fundamental methods: (1) simulation-based verification and (2) formal verification, or verifying the design ...
43. lappuse
... input signals by pushing data into the buffer without ever popping the data. However, at the higher core level of verification, it is much harder to create this condition because the core level inputs are further from the buffer, and ...
... input signals by pushing data into the buffer without ever popping the data. However, at the higher core level of verification, it is much harder to create this condition because the core level inputs are further from the buffer, and ...
45. lappuse
... input scenarios? 2. How will I know when a failure has occurred? These tasks are separate but must work together to ... input scenarios”? Although driving all possible input scenarios is trivial with a two-latch design, it is very hard ...
... input scenarios? 2. How will I know when a failure has occurred? These tasks are separate but must work together to ... input scenarios”? Although driving all possible input scenarios is trivial with a two-latch design, it is very hard ...
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