EDA Simulator Link™ MQ

Linking MATLAB or Simulink Software to ModelSim in ADMS

Starting ADMS for Use with EDA Simulator Link MQ

You must call vasim with all parameters manually; the configuration script available for ModelSim SE/PE is not available for ADMS.

When you call vasim, you must provide the -ms and -foreign parameters. For example,

vasim -lib ADC12_ELDO_MS -cmd 
     /devel/user/work/ams/adc12test.cmd TEST -ms -foreign matlabclient path/matlablibrary

where:

-lib ADC12_ELDO_MS

/devel/user/work/ams/adc12test.cmd

TEST

path/matlablibrary

A similar example for the Simulink link looks like this:

vasim -lib ADC12_ELDO_MS -cmd 
     /devel/user/work/ams/adc12test.cmd TEST -ms -foreign simlinkserver path/simulinklibrary

All line arguments after "ms" are sent to the ModelSim process.

See your ModelSim documentation for more about the -foreign option.

Back to Top

Using Tcl Test Bench Commands with ADMS

When you use any of the EDA Simulator Link MQ ModelSim link commands (e.g., matlabcp, matlabtb, matlabtbeval, nomatlabtb), you must precede each command with ms in the ADMS Tcl interpreter. For example:

ms matlabtb myfirfilter 5 ns -repeat 10 ns -socket 4449

All line arguments after 'ms' are sent to the ModelSim process.

Back to Top

Constraints

Setting Simulation Running Time

When running cosimulation sessions in Simulink, make sure that the runtime of the ADMS simulation is greater than or equal to the Simulink runtime.

Solaris Support

• ADMS is not supported on Solaris 64-bit, but is supported on Solaris 8, 9, 10 32-bits

• glibc errors on glnxa64 when running a cosimulation session with ADMS

  If you get the following:

  *** glibc detected *** free(): invalid pointer: 0x0000000001eeb490 ***

  The you must do this:

  setenv MALLOC_CHECK_  0

  Which says, effectively, "Do not generate an error message, and do not kill the program".

Back to Top

Adding Libraries for ADMS Support

EDA Simulator Link MQ Machine Configuration Requirements