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 95.
77. lappuse
... command bus. Up to 15 other request types may exist with different CMD(0:3) decode values. The valid bit must accompany the request, along with the tag, address, and first 32 bits of data. The next 32 bits of data follow on the next ...
... command bus. Up to 15 other request types may exist with different CMD(0:3) decode values. The valid bit must accompany the request, along with the tag, address, and first 32 bits of data. The next 32 bits of data follow on the next ...
78. lappuse
... command to the DUV. Invariably there are two ways that any design communicates availability of its resources to a requestor. The two choices are as follows: 2. The owner of the resource supplies an “available” signal to the requestor ...
... command to the DUV. Invariably there are two ways that any design communicates availability of its resources to a requestor. The two choices are as follows: 2. The owner of the resource supplies an “available” signal to the requestor ...
79. lappuse
... command, or other demand from the DUV. Continuing with the cache example, Figure 3.5 shows a main storage memory component that communicates with the cache. The memory receives either a store or fetch command from the cache and must act ...
... command, or other demand from the DUV. Continuing with the cache example, Figure 3.5 shows a main storage memory component that communicates with the cache. The memory receives either a store or fetch command from the cache and must act ...
80. lappuse
... command and response (if the timing is not fixed allows). However, in simple simulation environments, the test case writer pre-determines the timings and values. 3.1.2. Monitor. A monitor is a model that observes different aspects of the ...
... command and response (if the timing is not fixed allows). However, in simple simulation environments, the test case writer pre-determines the timings and values. 3.1.2. Monitor. A monitor is a model that observes different aspects of the ...
81. lappuse
... command sent; all others are illegal response decodes). In addition, the monitor may check for the following, depending on the environment and protocols: s The RSP(0:2) signal never is on in the absence of the RSP_VLD(0) signal ...
... command sent; all others are illegal response decodes). In addition, the monitor may check for the following, depending on the environment and protocols: s The RSP(0:2) signal never is on in the absence of the RSP_VLD(0) signal ...
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