• 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. Port order mismatch from spectre simulation

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 17944
  • 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

Port order mismatch from spectre simulation

Genas
Genas over 5 years ago

I have a case where adding the extracted netlist causes spectre to return port order mismatch.
I have compared the port order in both netlists (extracted and pre-layout) and they match perfectly.
I simulated with the extracted netlist ONLY and it completes successfully.
Similarly, with ONLY the pre-layout netlist, it completes successfully.
But combining the extracted and the pre-layout netlist causes port order mismatch error.
I will appreciate if you can provide any suggestion or clue as to the cause of this error.

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago

    Spectre itself won't report port order mismatches - because connections in spectre are by order and not by name - it wouldn't know whether they are in the wrong order.

    You also haven't said:

    1. How you are adding the extracted netlist
    2. What exactly is the error you're getting
    3. Which software versions you're using
    4. Is this happening during netlisting? If so, which ADE are you using?

    Put simply, you've not provided enough information to identify let alone diagnose the problem.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Genas
    Genas over 5 years ago in reply to Andrew Beckett

    1. Adding the extract statement via : .dspf_include '/path_to_spf.spf'

    2: Exact Error: ERROR (SFE-46): "./cell.cir" 14486: `mxihs': An instance of `hsbc' can have at most 95 terminals (but has 96).

    3. which spectre -> 'mmsim/19.10.199'

    4. Run using command line: spectre -64 -f fsdb +mt=4 +aps +lqt 0 +lqmmtoken +lorder MMSIM +spice $1 <input netlist>

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to Genas

    OK, all of that pretty important information that couldn't have been guessed from your original post. It's not in fact a port order issue at all, but a mismatch in the number of ports.

    There is an option you can add on the dspf_include line - like this:

    dspf_include "/export/home/user/support/playGPDK45/fourinv.dspf" extra_port=true

    which will tolerate a mismatch in the number of ports. Whether you really want it to do that, you'll have to decide - and check the ports to see if the port that is missing in the DSPF definition matters (in essence, your schematic has one more port than the DSPF does). Here's a description of what the extra_port option does:

    Specifies how to handle extra ports in the DSPF or schematic subcircuit definition. By default, this option is set to false, which implies that the port number in the schematic and the DSPF file needs to be the same. If not, the simulation will stop. When you set this option to true, the extra ports in the DSPF subcircuit call are changed to internal nodes. In addition, the extra ports in the schematic subcircuit definition are connected to nodes with the same name in the DSPF netlist, otherwise, they will be floating.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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