• 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. EMIR simulation fails with DSPF-114 code

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 125
  • Views 18417
  • 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

EMIR simulation fails with DSPF-114 code

MT13
MT13 over 6 years ago

Hi,

I am trying to run EMIR analysis on a mixed-signal design. The digital part has been verified separately, so when I did LVS in preparation for QRC extraction, I included the digital block's name in the LVS black box list (calibre --> LVS options --> LVS black box). Then did R-only extraction in QRC and chose the output format to be transistor-level DSPF.

The generated DSPF netlist has two .subckt sections; first section has the format:

.subckt dig_block [list of pin/net names]

.ends dig_block

Second section has the format:

.subckt top_level [list of pin/net names]

[extraction info]

.ends

This dspf file passes the spf checker in the EMIR analysis setup. But when I run the simulation (DC), it fails with message:

Fatal error found by spectre during circuit read-in.
    FATAL (DSPF-114): There is no Instance section in DSPF/SPF file, EMIR anlysis will not perform.

Can someone please advise on what the problem could be?  I am using virtuoso 6.1.7.

Thank you

  • Cancel
Parents
  • Saloni Chhabra
    Saloni Chhabra over 6 years ago

    Hi,

    As the error message suggests, did you check if there is an Instance section in the DSPF? Instance section contains all the devices (transistors, design resistors, design capacitors etc) and their connectivity to the nets in the design. If this section is missing, it means that your extraction setup isn't correct. For EMIR flow, you can find the required Quantus/QRC settings in the Rapid Adoption Kit for Voltus-Fi-XL.

    spfchecker looks through the first subckt definition in the DSPF which is empty in your case. Please run it again as: spfchecker -ckt top_level

    Regards,

    Saloni

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • MT13
    MT13 over 6 years ago in reply to Saloni Chhabra

    Hi Saloni,

    Thanks for the reply.

    I checked the DSPF file, and there are 2 lines that have:

    * Instance section

    The first time this occurs is within the dig_block subckt section, and it looks like:

    * instance section

    *

    .ENDS dig_block

    The second occurrence is within the top_level subckt section, and it looks like:

    * instance section

    *

    X....etc (many lines of what looks like transistor information)

    So is the problem that, as you pointed out in the last line, that the spfchecker and EMIR analysis is only looking at the first subckt, which is for the dig_block, and is empty of extracted info, and which has an empty instance section ?

    If that's the case, should I use option -ckt top_level in the highlighted field of the EMIR setup (in the attached pic)?

    Thank you very much

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Saloni Chhabra
    Saloni Chhabra over 6 years ago in reply to MT13

    Yes, you can use -ckt argument in the field you highlighted, and that will tell spfchecker which subckt to check. However, that still does not mean that EMIR analysis will work.

    You also need to add black_box="dig_top" argument in dspf_include statement in Spectre netlist. Are you including the DSPF through Simulation Files in ADE? If yes, then you can provide the black-box name as shown in snapshot below (make sure you hit apply so it becomes visible under Options column). You can also check dspf_include statement in input.scs to make sure that you've got argument there as: dspf_include "/path/to/top.dspf"   black_box="dig_top"

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • MT13
    MT13 over 6 years ago in reply to Saloni Chhabra

    Thanks a lot Saloni, that did the trick.

    Now I'm getting another error:

    Error found by spectre during circuit read-in.
        ERROR (SFE-461): "/Desktop/dig_block.scs" 7: Port number of subckt `dig_block' mismatch between schematic netlist and spf file. Port number in schematic netlist is 1249, and in spf file is 3273.

    Should I create a different topic for this?

    Thank you

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • MT13
    MT13 over 6 years ago in reply to Saloni Chhabra

    Thanks a lot Saloni, that did the trick.

    Now I'm getting another error:

    Error found by spectre during circuit read-in.
        ERROR (SFE-461): "/Desktop/dig_block.scs" 7: Port number of subckt `dig_block' mismatch between schematic netlist and spf file. Port number in schematic netlist is 1249, and in spf file is 3273.

    Should I create a different topic for this?

    Thank you

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Saloni Chhabra
    Saloni Chhabra over 6 years ago in reply to MT13

    The error message says that the number of ports found in Spectre netlist for 'dig_block' is much smaller than the ports found in the empty subckt definition in DSPF. This can happen when you run black-box extraction. To get past the error, you can try setting option 'extra_port=true'. This is available under DSPF Options in Simulation Files setup (just a row above where you specified Black Box name). Any extra ports in DSPF will be ignored and will not be driven by the testbench/design.

    That's the best I can advise without looking at the design and setup. Your simulation results should tell you if the port mismatch is causing any issues or not.

    Regards,
    Saloni

    • 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