• 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. Import Spice generated by Tempus

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 14913
  • 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

Import Spice generated by Tempus

zaratustra
zaratustra over 9 years ago

Hello,

Before asking my questions, here follows the software versions that I'm using:

virtuoso -W:  IC6.1.6-64b.500.11

spectre - W: 13.1.1.049

tempus and voltus - W: 15.14-s048_1

This is the flow I'm using:

1) I simulated a circuit using Voltus to obtain IR-DROP profiles (OK)

2) I imported the IR-DROP profiles into Tempus (OK)

3) I exported the critical path of the circuit from Tempus to spice (with the IR-DROP profiles - Command:    create_spice_deck ...).

4) I imported the generated spice by tempus into Virtuoso using SpiceIn.

 4.1) First problem: the generated spice uses "/" and when importing into Virtuoso it stops at the first "/", so I removed all slashes "/" from the spice. It worked, however, I would like to know if this is expected or if there's another solution?

E.g.:

XStage1 U3_INST_next_reg_24_/CP U3_INST_next_reg_24_/Q U4088/A Stage1

to

XStage1 U3_INST_next_reg_24_CP U3_INST_next_reg_24_Q U4088A Stage1

4.2) The importation worked fine without the "/" and now I have the schematics.

4.3) When I try to simulate using spectre, it complains: "ERROR (CMI-2198) Waveform is not defined in V5..." also in V10...

 Analyzing these Vsources, I understood the problem, however, I still don't know the solution.

 Problem: In spice, the IR-drops were defined as a PWL: "V1 U3_INST_next_reg_24_CP 0 PWL(+ 9.99999971718e-10        0
+ 1.0049999717e-09         0.71473...)

Those PWL were translated as a "wave" parameter which doesn't exist in Vsource (analogLib), therefore the values aren't being read. I can copy manually the values to the correct parameters from Vsource (t1, v1, t2, v2...), however, I have so many voltage sources and so many circuits that it would take too long. Anyone know if is there another solution?


Thank you in advance,

Raphael

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    I've not tried importing a netlist with a PWL source like this - it may just be a limitation of the SPICE import which you'd have to report to customer support to get improved.

    However, why are you importing this into virtuoso anyway - seems a bit of an odd thing to do. Wouldn't it be simpler just to run spectre on the netlist from the command line? I can't see any significant benefit in importing it...

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    I've not tried importing a netlist with a PWL source like this - it may just be a limitation of the SPICE import which you'd have to report to customer support to get improved.

    However, why are you importing this into virtuoso anyway - seems a bit of an odd thing to do. Wouldn't it be simpler just to run spectre on the netlist from the command line? I can't see any significant benefit in importing it...

    Regards,

    Andrew.

    • 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