Stats

  • Locked Locked
  • Replies 10
  • Subscribers 124
  • Views 18679
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Command for re-creating netlist

itos

Hi,


I am using Virtuoso, ADE L and and AMS together with the Simulink coupler. The coupler runs on a different computer and I execute the following command remotely to start the simulations (taken from the Simulink coupler tutorial):

echo "Matlab Current directory path is:"
pwd
setenv RUN_DIR /home/me/test/simulation/top/ams/config/netlist
cd $RUN_DIR
echo "irun will start, from this directory:"
pwd
echo "We launch runSimulation"
./runSimulation

However, it seems that this does not re-generate the netlist. Even worse, it does not throw an error (as ADE L does) when I change something but did not hit "Save & Check" or did not re-create the netlist.

What is the command to add before to recreate the netlist?

Also, based on which parameters would that happen? All settings (like design variables etc.) are stored in a certain cellview state.

Thanks!

itos

Parents

  • Thanks to both of you, great!

    Regarding the design() solution. For some reason, when I use

    design( "top" "top" "ams_tran_simulink" )

    I get

    *WARNING* (DB-270211): dbOpenCellViewByType: Failed to create cellview (top ams_tran_simulink) from lib (top) in 'a' mode because cellview does not exist, or cellview type is not recognized by dbOpenCellViewByType.
    *WARNING* (DB-270211): dbOpenCellViewByType: Failed to open cellview (top ams_tran_simulink) from lib (top) in 'r' mode because cellview does not exist, or cellview type is not recognized by dbOpenCellViewByType.

    I tried everything like opening/closing, locking/unlocking, different parameters and also dbOpenCellViewByType("top" "top" "ams_tran_simulink") in the CIW fails with the same error. I tried all possible parameters I could imagine but no luck. Clearly, library, cell and view exist and match exactly as shown in the library manager. E.g.:

    $ ls top/top/ams_tran_simulink/
    ADE_state.info  connectModules.state  disciplineSelect.state    globalSignals.state  master.tag            modelSetup.state  outputs.stateScripts  runOptInfo.state       simulatorOptions.state  turboOptions.state  waveformSetup_ws.state
    analyses.state  convergence.state     environmentOptions.state  libraryFiles.state   matlabSimulink.state  outputs.state     paramSetup.state      simulationFiles.state  solverInfo.state        variables.state

    Do you have by any chance an idea what could be going wrong?

Reply

  • Thanks to both of you, great!

    Regarding the design() solution. For some reason, when I use

    design( "top" "top" "ams_tran_simulink" )

    I get

    *WARNING* (DB-270211): dbOpenCellViewByType: Failed to create cellview (top ams_tran_simulink) from lib (top) in 'a' mode because cellview does not exist, or cellview type is not recognized by dbOpenCellViewByType.
    *WARNING* (DB-270211): dbOpenCellViewByType: Failed to open cellview (top ams_tran_simulink) from lib (top) in 'r' mode because cellview does not exist, or cellview type is not recognized by dbOpenCellViewByType.

    I tried everything like opening/closing, locking/unlocking, different parameters and also dbOpenCellViewByType("top" "top" "ams_tran_simulink") in the CIW fails with the same error. I tried all possible parameters I could imagine but no luck. Clearly, library, cell and view exist and match exactly as shown in the library manager. E.g.:

    $ ls top/top/ams_tran_simulink/
    ADE_state.info  connectModules.state  disciplineSelect.state    globalSignals.state  master.tag            modelSetup.state  outputs.stateScripts  runOptInfo.state       simulatorOptions.state  turboOptions.state  waveformSetup_ws.state
    analyses.state  convergence.state     environmentOptions.state  libraryFiles.state   matlabSimulink.state  outputs.state     paramSetup.state      simulationFiles.state  solverInfo.state        variables.state

    Do you have by any chance an idea what could be going wrong?

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. 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. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.