• 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. SpiceIn fails for existing symbol with bus pins

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 124
  • Views 6607
  • 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

SpiceIn fails for existing symbol with bus pins

FormerMember
FormerMember over 4 years ago

Hello,

I have SPICE netlist (also tried with CDL and spectre) with some digital gates and bus inputs/outputs, which I want to import into an existing cell. I activated the option for merging bus bits and if I do the import into an empty cell, it works fine.

Unfortunately, the CDL import, which allows specifying the pin direction in the netlist, does not find my existing cells (already asked about it in Import Netlist to Schematic with existing Cells in other Libraries ). For non-CDL netlists the pin directions are take from a symbol view, if existent. However, the import fails if the symbol contains busses with the message "Mismatch in number of ports of  symbol and subcircuit" It seems the importer does not recognize the merged pins.

I also tried to import the netlist twice. First, to generate a symbol with busses (which works) and then a second time (after deleting the schematic and without overwrite option), which fails with the message above. Also, if the override option is active, every existing view in the cell is deleted.

The only way I could get it to work is to import the netlist into a dummy cell, assign the correct pin directions and copy it to the destination cell.

Is there a way to get the import running with existing symbols and busses?

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

    Hi Paul,

    I just played with this, and I agree, it's not working very well. The merge busbits capability is fairly new (I think it was only exposed by default in IC618 ISR11), and when I tried it even without an existing symbol it appeared to be breaking the connectivity in my case. If you then try to use an existing symbol with bus pins, it fails in the way that you mention (so I suspect that hasn't been taken into account in the code).

    You should contact customer support - best to get this to R&D with a real-life subckt rather than something that I just made up for testing purposes (plus it always helps to have a real customer behind the issue).

    Thanks

    Andrew

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 4 years ago

    Hi Paul,

    I just played with this, and I agree, it's not working very well. The merge busbits capability is fairly new (I think it was only exposed by default in IC618 ISR11), and when I tried it even without an existing symbol it appeared to be breaking the connectivity in my case. If you then try to use an existing symbol with bus pins, it fails in the way that you mention (so I suspect that hasn't been taken into account in the code).

    You should contact customer support - best to get this to R&D with a real-life subckt rather than something that I just made up for testing purposes (plus it always helps to have a real customer behind the issue).

    Thanks

    Andrew

    • Cancel
    • Vote Up +1 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