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 74.
47. lappuse
... resetting the design. Grouping signals and busses together is important because the verification engineer will develop separate driving strategies for each set of grouped input signals. In developing a stimulus strategy, the ...
... resetting the design. Grouping signals and busses together is important because the verification engineer will develop separate driving strategies for each set of grouped input signals. In developing a stimulus strategy, the ...
48. lappuse
... reset the stack? s Do the entries get zeroed-out or just marked invalid? s What happens if a read operation occurs when the stack is empty? TABLE 2.1 s The verification team should include these scenarios. 48 Chapter 2 s Verification Flow.
... reset the stack? s Do the entries get zeroed-out or just marked invalid? s What happens if a read operation occurs when the stack is empty? TABLE 2.1 s The verification team should include these scenarios. 48 Chapter 2 s Verification Flow.
49. lappuse
... resetting it (clean_stack) Writing to the stack and resetting it (clean_stack) All bits of data Temporal cases such as writing back-to-back with a double read on the first cycle (starting with an empty stack). Writing data to the stack ...
... resetting it (clean_stack) Writing to the stack and resetting it (clean_stack) All bits of data Temporal cases such as writing back-to-back with a double read on the first cycle (starting with an empty stack). Writing data to the stack ...
56. lappuse
... reset the stack? s After a reset, are the entries zeroed-out or just marked invalid? s What if a test performs a read when the stack is empty? s Is the stack a FIFO or LIFO? s The design or architecture team produces a specification of ...
... reset the stack? s After a reset, are the entries zeroed-out or just marked invalid? s What if a test performs a read when the stack is empty? s Is the stack a FIFO or LIFO? s The design or architecture team produces a specification of ...
60. lappuse
... resets the pointers as intended but erroneously puts the data in the stack. This case only occurs when the stack has six valid entries when the clean_stack and in_buf_valid are set, as the bug is in the logic that is trying to set the ...
... resets the pointers as intended but erroneously puts the data in the stack. This case only occurs when the stack has six valid entries when the clean_stack and in_buf_valid are set, as the bug is in the logic that is trying to set the ...
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