MCS | manual | tools | models | support


To run a successful MCS simulation, you must:
1) compile the necessary files
2) operate the simulator.

To assist in these tasks, we have created Compilation and Operational diagrams that will take you step by step through these processes to ensure a successful simulation.
MCS Compilation Diagram:	MCS Operational Diagram:
Below is a general sample of how to run an MCS simulation (without any visual aid).
Compiling an experiment with MCS: Create verilog file: - get "(circuit name).bench" - turn into verilog with the Bench2ver tool - this turns the bench file into "(circuit name).v" Create dee file: - turn the verilog file into a dee file using the Parse tool - this turns (verilog file) into a .dee file Create the symbol table: - get the symbol table from the dee file using the Crest tool - this makes "(circuit name).smt" from the .dee file Create the faults file: - derive all possible faults from the .dee file using any fault tool - this makes "(circuit name).fls" from the .dee file Create the waveform file: - either by using func_waveformgen, or by converting to current waveform to .dwe format - if file is .vec file, first need to make it a .dgp: open and strip off first line (# inputs) and last line ("END"), save as .dgp (just big list of waveform vectors) - second, turn .dgp into a .dws using the Tab2ws_mcs tool - third, turn .dgp into a .dwe using the Dwc_mcs tool.
Running an experiment with MCS: (numbered items represent command line entry) c e (test name) (circuit name) - create experiement with (name you make up) and (name of actual circuit) l s - load the symbol table s f 200000 - set faults to be a really big number l f (circuit name) - load the fault list s d e - set detection enabled l w (circuit name) - load the waveform r w - run the waveform d s - display statistics, or: - "d c": display coverage - "d f": display faults (big list) e - exits MCS