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
6.–10. rezultāts no 78.
52. lappuse
... operations fed to the fixed-point unit. The verification of HDL B must ensure that this never occurs. Verification teams derive many checkers from properties based on the microarchitecture, or internal structures of the design, so ...
... operations fed to the fixed-point unit. The verification of HDL B must ensure that this never occurs. Verification teams derive many checkers from properties based on the microarchitecture, or internal structures of the design, so ...
54. lappuse
... operation in a register (e.g. the subtract result goes to register R7 in the figure) that the following instruction, branch if zero (BRZ), will use, then we have resource contention on R7. If the design under verification is the ...
... operation in a register (e.g. the subtract result goes to register R7 in the figure) that the following instruction, branch if zero (BRZ), will use, then we have resource contention on R7. If the design under verification is the ...
57. lappuse
... operation. The out_buf_data1 and out_buf_data2 wires should never contain valid data unless the driver performed a read and there was data in the stack. Similarly, the buf_full and buf_overrun wires should only be active when the ...
... operation. The out_buf_data1 and out_buf_data2 wires should never contain valid data unless the driver performed a read and there was data in the stack. Similarly, the buf_full and buf_overrun wires should only be active when the ...
59. lappuse
... operation and decrements it for each read. A null pointer value indicates an empty list, as would a counter value of zero. This strategy allows the checking code to quickly access the top of the stack for read operations and then remove ...
... operation and decrements it for each read. A null pointer value indicates an empty list, as would a counter value of zero. This strategy allows the checking code to quickly access the top of the stack for read operations and then remove ...
60. lappuse
... operation occurs over the course of the next few cycles, then the design would clear its erroneous behavior and the bug would go undetected. To detect this bug, the stack needs to accumulate six new entries without another clean_stack ...
... operation occurs over the course of the next few cycles, then the design would clear its erroneous behavior and the bug would go undetected. To detect this bug, the stack needs to accumulate six new entries without another clean_stack ...
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