• 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. Netlist modifies itself

Stats

  • Locked Locked
  • Replies 12
  • Subscribers 124
  • Views 18958
  • 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

Netlist modifies itself

archive
archive over 18 years ago

Hello, Im trying to simulate an adder circuit which produces an output depending on an 'input offset'. That is the offset gets added to itself and whenever the addition results in an overflow it should produce an output. The adder is a 4 bit adder and so whener the sum exceeds 1111 it shud produce a carry out and the resulting sum shud substract 16 from itself and produce a new sum which would then be smaller than 1111. I hope u get the point. I made schematic for the circuit which consists of a simple 4 bit Ripple carry adder and a register driven by the clock because I want the addition to take place with the clock. The output of the adder feeds the register and the reg op feeds one of the inputs to the adder thus creating a loop structure. After doing that I create a symbol out of it and use it in a TB to see the behavior. After certain simulation trials of the Test bench i get this strange error in the spectre.out file which says that "I11 instance is an instance of an undefined model subcircuit" . Here 'I11' refers to the instance name of the symbol I created earlier. This strange error disappears when i make an exact copy of the same Test Bench schematic into another schematic. And again after a while the same error pops up and then i recreate another schematic and then it works..which is becoming kind of annoying. Does anyone have any pointers as to why is it happening? Hope to get some hints about that. Best regards, Aijaz Baig.


Originally posted in cdnusers.org by aijazbaig1
  • Cancel
  • archive
    archive over 18 years ago

    I took a quick look at the data.

    The problem is that in your config view you have:

    View List: spectre cmos_sch schematic veriloga ahdl
    Stop List: spectre cmos_sch schematic veriloga ahdl

    This means that netlisting will stop expanding when it finds a schematic - which is NOT what you want. If it stops at the schematic, it will then use the CDF to decide how to netlist it, and that indicates the component name as "subcircuit". Also, you won't get the contents of the schematic netlisted.

    The stop list should be just "spectre" in this case. I tried this (having adjusted the data slightly as I don't have "PRIMLIB" components), and it netlisted correctly. Both therm_to_bin_TB and ADC_3bit_NEW_TB config views had the wrong stop list.

    This should have been fairly clear from the hierarchy editor - because there was no expansion of the hierarchy shown there, due to each instance stopping at the schematic.

    Regards,

    Andrew.


    Originally posted in cdnusers.org by adbeckett
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 18 years ago

    Ah!!

    that is something which i was overlooking. Thanks a lot andrew!!

    I hope to learn quite a few tricks on the forums here :)

    Best Regards,

    Aijaz


    Originally posted in cdnusers.org by aijazbaig1
    • 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