Verilator and SystemPerl - Veripool

More documents

Recommendations

Info

Avoid Includes!• SystemC documentation suggests the bad practice ofputting SC_CTOR implementation in the header file.– If a low level module changes, you need to recompile EVERYTHING!• Instead, remove all unnecessary #includes in header files!– Move any implementation code, such as constructors to the .cpp file– Declare SubModules as just "class SubModule"– Only #include submodules in the .cpp file// FileName.hclass SubModule;SC_MODULE(Foo) {…SubModule* subcell;…SC_CTOR(Foo);};// FileName.cpp#include "SubModule.h"SP_CTOR_IMP(Foo) {…}Verilator Environment, NASCUG June 2004. Copyright 2004 by Wilson Snyder; redistribution allowed as complete presentation.12
Conclusions• With the SystemPerl and Verilator methodology we– Enable high level SystemC modeling– Write standard Verilog RTL– Can interchange Verilog SystemC on major modules– Run as fast as major simulators.– Have a license-free environment.• Multiple languages suit each team best– Faster Development, faster time to market• Free runtime is good– $$ we would have spent on simulator runtimelicenses went to computes.Verilator Environment, NASCUG June 2004. Copyright 2004 by Wilson Snyder; redistribution allowed as complete presentation.13
Page 1 and 2: Verilator andSystemPerlJune, 2004Wi
Page 3 and 4: Introduction• In 2000, we were st
Page 5 and 6: CAD FlowchartEmbeddedSoftwareTeamAr
Page 7 and 8: Example Translation• Inputs and o
Page 9 and 10: Verilator Optimizations• Verilato
Page 11: Faster SystemC Compiles• Our mode

Verilator and SystemPerl - Veripool

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?