Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 14801
  • 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

Delete layout terminals from database

mewi72

After a cross-view check between schematic and layout some "ghost" terminals in layout were detected. There is no pin shape in layout and no label, but the dbOpenCellViewByType function with terminals~>name attribut displays this terminals for the layout view. Now I'm looking for a function which should compare the layout and the schematic terminals and delete the "ghost" terminals from the layout view. A big problem I think is the handling of busses. Every bus pin of the layout view will described as single terminal ("A<3>" "A<2>" "A<1> and so on), the pins from a bus in schematic view together ("A<3:1>").

Do you have some ideas?

Thank you, Melanie

Parents

  • You can use the command dbProduceMemName(name) to expand the bus.

    dbProduceMemName("a<0:9:3>")
    ("a<0>" "a<3>" "a<6>" "a<9>")

    You could also get all the schematic signal names that are associated with a terminal (signal object with a memTerms attribute) with something like this:
    sigNames = setof(x geGetEditCellView()~>signals x~>memTerms)~>name

    Then:
    ghostTerms = setof(x lay~>terminals !member(x~>name sigNames))

    Derek

Reply

  • You can use the command dbProduceMemName(name) to expand the bus.

    dbProduceMemName("a<0:9:3>")
    ("a<0>" "a<3>" "a<6>" "a<9>")

    You could also get all the schematic signal names that are associated with a terminal (signal object with a memTerms attribute) with something like this:
    sigNames = setof(x geGetEditCellView()~>signals x~>memTerms)~>name

    Then:
    ghostTerms = setof(x lay~>terminals !member(x~>name sigNames))

    Derek

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.