Abbrevation
DVCon
City
San Jose
Country
United States
Deadline Paper
Start Date
End Date
Abstract

DVCon is the premier conference on the application of languages, tools and methodologies for the design and verification of electronic systems and integrated circuits&#046;The focus of the conference is on the usage of specialized design and verification languages such as Veri l og, SystemVerilog,VHDL,PSL Syste mC,e, and VERA,as well as general p u rpose languages such as C and C++&#046;Tools and methodologies include the use of te s t bench automation, hardware&#8211; assisted verification, h a rdware/ software co&#8211; verification, assertion&#8211;based and formal verification, and transaction&#8211; level system design and verification&#046;<br>Conference attendees are primarily designers of electronic systems, ASICs and FPGAs, as well as those involved in the research, development and application of Electronic Design Automation (EDA) tools&#046;Presentations are highly technical in nature, and reflect real life experiences in using these languages and tools&#046; <b>Keywords:</b> • Experience using ESL and TLM for system&#8211; level design and verification<br>• Experiences with System&#8211; on&#8211; Chip design<br>• Designing and/or verifying complex ASICs and FPGAs<br>• Using multiple HDLs and/or HVLs in a design cycle<br>• Techniques for generating constrained&#8211; random test,or other<br>automated stimulus generation methods<br>• Synthesizing transaction&#8211; level or abstract designs from high&#8211;level<br>languages such as SystemC,System Verilog or C++,to RTL<br>• Experiences with hardware/ software co&#8211;design and co&#8211; verification<br>• Experiences with mixed&#8211;signal simulation<br>• Verification techniques that really work (and what did not work)<br>• Verification process and resource management<br>• Verification methods that have achieved ze ro functional bugs in first silicon<br>• As s e rtion&#8211;based verification<br>• Coverage&#8211; driven verification<br>• Design and verification IP experiences, good and bad<br>• Measuring completeness and quality of verification: functional coverage,code coverage or other techniques<br>• Experience with formal technologies applied to verification, including the application of model checking and simulation together,or the use of dynamic formal verification tools<br>• Any topic involving the use of an HDL or HVL<br>