• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. save currents in a spectre netlist, run the netlist in batch...

Stats

  • Locked Locked
  • Replies 10
  • Subscribers 126
  • Views 5945
  • 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

save currents in a spectre netlist, run the netlist in batch mode and the currents is saved as instance_name:number

ckseok
ckseok over 15 years ago

To save current into port "A" of instance "IDRIVER", I add the following line in the spectre netlist.

save IDRIVER:A

Then, I run the netlist in batch mode.

After simulation is finished, the result browser shows IDRIVER:2 instead of IDRIVER:A.

How can I make the simulator save current as Instance_name:port_name instead of instance_name:number?

Thank you.

  • Cancel
Parents
  • tenorman
    tenorman over 14 years ago

     Andrew,
       Thanks for your reply.  Looking into this a bit further, the goal for a particular circuit was to set a cellview type (i.e. schematic_extract, or even symbol) as a stop view in the heiarchy editor (so that the subcircuit definition is not defined in the netlist), include the model file for that cell at the beginning of the netlist (in the model files section of ADE), and then save the pin currents on the symbol in the test bench schematic.

    However, I noticed that if the cellview type IS NOT listed as a stop view, the SAVE statement will appear such as:
     ->     save I0.I0:2
    whereas if the cellview type IS listed as a stop view, the SAVE statment appears such as:
     ->     save I0.I0vplus
    where it appears as a netlist error, since there is no colon between the instance and the pin name anymore.  Is this a bug?  Do I have to fix something in the CDF parameters for the cell to prevent this?

    So, useterms=name works when the cellview IS NOT listed as a stop view, but how can I save these currents when defining the cellview type as a stop view instead?   Thoroughly confused,
    - Paul.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • tenorman
    tenorman over 14 years ago

     Andrew,
       Thanks for your reply.  Looking into this a bit further, the goal for a particular circuit was to set a cellview type (i.e. schematic_extract, or even symbol) as a stop view in the heiarchy editor (so that the subcircuit definition is not defined in the netlist), include the model file for that cell at the beginning of the netlist (in the model files section of ADE), and then save the pin currents on the symbol in the test bench schematic.

    However, I noticed that if the cellview type IS NOT listed as a stop view, the SAVE statement will appear such as:
     ->     save I0.I0:2
    whereas if the cellview type IS listed as a stop view, the SAVE statment appears such as:
     ->     save I0.I0vplus
    where it appears as a netlist error, since there is no colon between the instance and the pin name anymore.  Is this a bug?  Do I have to fix something in the CDF parameters for the cell to prevent this?

    So, useterms=name works when the cellview IS NOT listed as a stop view, but how can I save these currents when defining the cellview type as a stop view instead?   Thoroughly confused,
    - Paul.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information