• 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. Error SFE-23 (undefined model or subcircuit modp and modn...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 124
  • Views 31368
  • 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

Error SFE-23 (undefined model or subcircuit modp and modn) and Error (SFE-874)

DomPaw
DomPaw over 8 years ago

Dear Cadence Community

I've got some serious problems which i need to solve as soon as possible. I'm a new Cadence user, i've tried to launch ADE and unfortunately i can't make any simulations because of those problems below.  

Error found by spectre in `uklad', during circuit read-in.
ERROR (SFE-23): "input.scs" 13: The instance `MP10' is referencing an undefined model or subcircuit, `modp'. Either include the file containing the definition of `modp', or define `modp' before running the simulation.
ERROR (SFE-23): "input.scs" 29: The instance `MN11' is referencing an undefined model or subcircuit, `modn'. Either include the file containing the definition of `modn', or define `modn' before running the simulation.
ERROR (SFE-23): "input.scs" 48: The instance `R0' is referencing an undefined model or subcircuit, `rpoly1'. Either include the file containing the definition of `rpoly1', or define `rpoly1' before running the simulation.

When I tried to fix this problem this way   Setup-->Model Library-->(added cds.lib) i've got another problem:

ERROR (SFE-874):  14: Unexpected string value "#--------------------------------------------------------------------------------".
ERROR (SFE-874): " 32: Unexpected end of line.
ERROR (SFE-874): "33: Unexpected end of line.
ERROR (SFE-874):34: Unexpected end of line.
ERROR (SFE-874):  35: Unexpected end of line.
ERROR (SFE-874):36: Unexpected end of line.
ERROR (SFE-874): 37: Unexpected end of line.
ERROR (SFE-874): 39: Unexpected end of line.
ERROR (SFE-874): 40: Unexpected end of line.
ERROR (SFE-874): "41: Unexpected end of line.
ERROR (SFE-874):  42: Unexpected end of line.
ERROR (SFE-874): "43: Unexpected end of line.
ERROR (SFE-874):  44: Unexpected end of line.
ERROR (SFE-874):  45: Unexpected end of line.
ERROR (SFE-874):  46: Unexpected end of line.
ERROR (SFE-874): " 47: Unexpected end of line.
ERROR (SFE-874):  48: Unexpected end of line.
ERROR (SFE-874):  49: Unexpected end of line.
ERROR (SFE-874): " 50: Unexpected end of line.
ERROR (SFE-874): 51: Unexpected end of line.
ERROR (SFE-874):  52: Unexpected end of line.
ERROR (SFE-874):  53: Unexpected end of line.
ERROR (SFE-874): " 54: Unexpected end of line.
ERROR (SFE-874): 55: Unexpected end of line.
ERROR (SFE-874): 56: Unexpected end of line.
ERROR (SFE-874):  57: Unexpected end of line.
ERROR (SFE-874): 58: Unexpected end of line.
ERROR (SFE-874): 59: Unexpected end of line.
ERROR (SFE-874): 60:Unexpected end of line. Expected equals sign, numeric value or string value.

(Deleted my path, just showing errors)

I tried another way, adding file input.scs in the model library then the fatal error came out :

FATAL (SFE-879): Recursive file include or library call: `/.../spectre/schematic/netlist/input.scs'.

Can anyone help me with this issue please? 

Regards,

Dominik

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

    Hi Dominik,

    Oh dear - you really do appear to be trying random things which will stand no chance of working. 

    Often design kits will set up the model path automatically to ensure the models are defined - if they don't, there's presumably some documentation with the design kit to tell you where the model files are. These are the transistor models (subckts, model statements) that need to be included so that Spectre knows the meaning of the primitive devices (modp and modn in your case). These are probably defined somewhere in a file with a ".scs" suffix (although it is possible that they're defined in SPICE syntax so they could be described differently). Without knowing what technology or design kit you're using, I doubt anyone could guess what the file is likely to be called (unless they happen to recognise the "modn" and "modp" model names).

    Including the cds.lib makes no sense; that's the definition of Virtuoso libraries (containing symbols, schematics, CDF, layouts and so on) for the Virtuoso tools to use. Virtuoso must be seeing that otherwise you couldn't draw your schematics. It's certainly not a spectre model file, hence the syntax errors.

    Including the input.scs similarly makes no sense - all the model libraries form does is specify a bunch of files to include in the input.scs that it is generating, so putting a reference to itself makes no sense (hence the error about it being recursive).

    Regards,

    Andrew.

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

    Hi Dominik,

    Oh dear - you really do appear to be trying random things which will stand no chance of working. 

    Often design kits will set up the model path automatically to ensure the models are defined - if they don't, there's presumably some documentation with the design kit to tell you where the model files are. These are the transistor models (subckts, model statements) that need to be included so that Spectre knows the meaning of the primitive devices (modp and modn in your case). These are probably defined somewhere in a file with a ".scs" suffix (although it is possible that they're defined in SPICE syntax so they could be described differently). Without knowing what technology or design kit you're using, I doubt anyone could guess what the file is likely to be called (unless they happen to recognise the "modn" and "modp" model names).

    Including the cds.lib makes no sense; that's the definition of Virtuoso libraries (containing symbols, schematics, CDF, layouts and so on) for the Virtuoso tools to use. Virtuoso must be seeing that otherwise you couldn't draw your schematics. It's certainly not a spectre model file, hence the syntax errors.

    Including the input.scs similarly makes no sense - all the model libraries form does is specify a bunch of files to include in the input.scs that it is generating, so putting a reference to itself makes no sense (hence the error about it being recursive).

    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