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

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.

Parents

  • Hi Paul,

    In the CDF for the component, change the component name (in the spectre simInfo) to be (for example) "cellName_netlist" (and also change it in the included subckt definition).

    Then use the hierarchy editor to create a config, and you can specify the view to use on some instances to be your stopping view, whilst other instances remain the schematic view. Those with the schematic view will get netlisted as "cellName", and those using the stopping view will get netlisted as "cellName_netlist" (i.e. using the componentName in the CDF).

    I just checked this and it worked correctly.

    Regards,

    Andrew.

Reply

  • Hi Paul,

    In the CDF for the component, change the component name (in the spectre simInfo) to be (for example) "cellName_netlist" (and also change it in the included subckt definition).

    Then use the hierarchy editor to create a config, and you can specify the view to use on some instances to be your stopping view, whilst other instances remain the schematic view. Those with the schematic view will get netlisted as "cellName", and those using the stopping view will get netlisted as "cellName_netlist" (i.e. using the componentName in the CDF).

    I just checked this and it worked correctly.

    Regards,

    Andrew.

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.