Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
System Development Suite Related Products A-Z
Cadence® digital design and signoff solutions provide a fast path to design closure and better predictability, helping you meet your power, performance, and area (PPA) targets.
Full-Flow Digital Solution Related Products A-Z
Cadence® custom, analog, and RF design solutions can help you save time by automating many routine tasks, from block-level and mixed-signal simulation to routing and library characterization.
Overview Related Products A-Z
Driving efficiency and accuracy in advanced packaging, system planning, and multi-fabric interoperability, Cadence® package implementation products deliver the automation and accuracy.
Cadence® PCB design solutions enable shorter, more predictable design cycles with greater integration of component design and system-level simulation for a constraint-driven flow.
An open IP platform for you to customize your app-driven SoC design.
Comprehensive solutions and methodologies.
Helping you meet your broader business goals.
A global customer support infrastructure with around-the-clock help.
24/7 Support - Cadence Online Support
Locate the latest software updates, service request, technical documentation, solutions and more in your personalized environment.
Cadence offers various software services for download. This page describes our offerings, including the Allegro FREE Physical Viewer.
The Cadence Academic Network helps build strong relationships between academia and industry, and promotes the proliferation of leading-edge technologies and methodologies at universities renowned for their engineering and design excellence.
Participate in CDNLive
A huge knowledge exchange platform for academia to network with industry. We are looking for academic speakers to talk about their research to the industry attendees at the Academic Track at CDNLive EMEA and Silicon Valley.
Come & Meet Us @ Events
A huge knowledge exchange platform for academia. We are looking for academic speakers to talk about their research to industry attendees.
Americas University Software Program
Join the 250+ qualified Americas member universities who have already incorporated Cadence EDA software into their classrooms and academic research projects.
EMEA University Software Program
In EMEA, Cadence works with EUROPRACTICE to ensure cost-effective availability of our extensive electronic design automation (EDA) tools for non-commercial activities.
Apply Now For Jobs
If you are a recent college graduate or a student looking for internship. Visit our exclusive job search page for interns and recent college graduate jobs.
Cadence is a Great Place to do great work
Learn more about our internship program and visit our careers page to do meaningful work and make a great impact.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
Overview All Courses Asia Pacific EMEANorth America
Instructor-led training [ILT] are live classes that are offered in our state-of-the-art classrooms at our worldwide training centers, at your site, or as a Virtual classroom.
Online Training is delivered over the web to let you proceed at your own pace, anytime and anywhere.
Exchange ideas, news, technical information, and best practices.
The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information.
It's not all about the technlogy. Here we exchange ideas on the Cadence Academic Network and other subjects of general interest.
Cadence is a leading provider of system design tools, software, IP, and services.
I've heard lots of people asking for a way to generate Makefiles for Specman code, and it seems there are some who don't use "irun" which takes care of this automatically. So I wrote this little utility to build a basic Makefile based on the compiled and loaded e code.
It's really easy to use: at any time load the snmakedeps.e into Specman, and use "write makefile <name> [-ignore_test]".This will dump a Makefile with a set of variables corresponding to the loaded packages, and targets to build any compiled modules.Using -ignore_test will avoid having the test file in the Makefile, in case you switch tests often (who doesn't?).
It also writes a stub target so you can do "make stub_ncvlog" or "make stub vhdl" etc.
The targets are pretty basic, I thought it was more useful to #include this into the main Makefile and define your own more complex targets / dependencies as required.
The package uses the "reflection" facility of the e language, which is now documented since Specman 8.1, so you can extend this utility if you want (please share any enhancements you make).
I've updated this utility a bit, to make the targets more useful. Now, even if you only loaded the file into Specman or Specview, the Makefile will have a target for compiling this with sn_compile.sh. Here's an example:First, I load a couple of files into Specman:
specman -c "load snmakedeps ; load vr_ad/e/vr_ad_top ; load vr_xbus/examples/vr_xbus_config.e ; write makefile Makefile.sn -ignore_test"
Now I use the generated Makefile.sn to incrementally compile my vr_ad_top and vr_xbus_config modules:
compile make -f Makefile.sn sncompile
This results in the executables and shared libraries that I can use with specrun/specview or ncsim.
make -f Makefile.sn stub_ncvhdl stub_ncvlog
This results in my stubs files being generated. If I already ran the "make sncompile", the stubs are generated using the compiled code, otherwise they're written using the loaded e code.
Here's an example of the Makefile.sn that's generated:
## Auto-generated Makefile for Specman - DO NOT EDIT## compiled module vr_ad_topvr_ad_top_files=\ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_ad/e/vr_ad_types.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_sets/e/vr_sets_interface.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_sets/e/vr_sets_internal_proto.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_sets/e/vr_set32_mem.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_sets/e/vr_set32_nodes.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_sets/e/vr_set32_lowlevel.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_sets/e/vr_set32_hilevel.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_sets/e/vr_set32_rnd.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_sets/e/vr_set_inf_mem.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_sets/e/vr_set_inf_nodes.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_sets/e/vr_set_inf_lowlevel.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_sets/e/vr_set_inf_hilevel.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_sets/e/vr_set_inf_rnd.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_sets/e/vr_sets_top.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_ad/e/vr_ad_api.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_ad/e/vr_ad_sequence_h.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_ad/e/vr_ad_sets.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_ad/e/vr_ad_imp.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_ad/e/vr_ad_reg_imp.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_ad/e/vr_ad_map_imp.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_ad/e/vr_ad_sequence.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_ad/e/vr_ad_vt_page_slice_patch.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_ad/e/vr_ad_vt.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_ad/e/vr_ad_predefined_seq.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_ad/e/vr_ad_macro.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_ad/e/vr_ad_mem_api.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_ad/e/vr_ad_mem_imp.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_ad/e/vr_ad_mem_obj.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_ad/e/vr_ad_mem_vt.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_ad/e/vr_ad_top.e## compiled module vr_xbus_configvr_xbus_config_files=\ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/shr_ram/e/shr_ram_main.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/shr_ram/e/shr_ram_top.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_config_h.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_types_h.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_trans_h.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_signal_map_h.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_bus_monitor_h.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_agent_monitor_h.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_agent_h.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_env_h.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_arbiter_sequence_h.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_master_sequence_h.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_slave_sequence_h.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_bus_monitor.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_agent_monitor.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_bfm.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_arbiter_bfm.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_master_bfm.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_slave_bfm.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_agent.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_env.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_protocol_checker.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_coverage.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_end_test.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_top.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/e/vr_xbus_port_config.e \ /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/examples/vr_xbus_config.elibsn_vr_ad_top.so: $(vr_ad_top_files) sn_compile.sh -exe -shlib -enable_DAC /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/util_lib/vr_ad/e/vr_ad_top.elibsn_vr_xbus_config.so: $(vr_xbus_config_files) libsn_vr_ad_top.so sn_compile.sh -exe -shlib -enable_DAC /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/examples/vr_xbus_config.esncompile: libsn_vr_xbus_config.so echo 'Recompiling e code...'# Use 'make stub_<sn_adapter_name>' to build the desired stubs file,# for example: 'make stub_ncvhdl'.stub_%: $(vr_ad_top_files) $(vr_xbus_config_files) if [ -x ./vr_xbus_config ]; then\ ./vr_xbus_config -c 'write stubs -$*'; \ else\ specman -c 'load /export/home/stephenh/Tools/IPCM08.10.004-s/ipcm/ovm_lib/erm_ex_lib/vr_xbus/examples/vr_xbus_config.e ; write stubs -$*';\ fi
In reply to StephenH:
At risk of producing a monologue that nobody is reading... ;-)
A colleague asked if I could update the generator to produce a "tarball" target, to make it easy to archive or transfer the source code.So here it is! The Specman command is unchanged, you simply have a new make target called tarball:
make -f Makefile.sn tarball
Oh,..this seems to be quite complicated..
In reply to rheychrox06:
Aww... It wasn't supposed to be complex.
Drop me an email if you'd like some help using it, maybe my forum post didn't make it very clear which bits are generated and which you have to do. Normally it should be only 1 command.