Stats

  • Locked Locked
  • Replies 2
  • Subscribers 144
  • Views 1173
  • 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

physOnly - physical only argument for terminal treation

Adrian Nistor

Hello,

It's not very clear to me what is the purpose of physical only argumen. 

If I create a PIN with Create - Pin I have the check box "Physical Only". Also in dbCreateTerminal the last optional parameter is b_physOnly. In the documentation it sais that for creatng strong connected terminales, the second and the other terminales should by physical only. But what if they are not ? 

So: What is the purpose of this option?

What test case should I try tu understend the differences of using physOnly = t and physOnly = nil ?

Thank you,

Best Regards,

Adrian

  •  I do not know if any Virtuoso tools use this attribute but it is used to designate terminals that are not represented in the logical database. For a mustConnect set of pin shapes, some of them are attached to a terminal that has the same name in the layout as the symbol. Others pin shapes which are not connected internally in the layout but are of the same internal net have to be created as pin shapes on different nets with different terminals connected to the logical terminal using dbSetTermMustJoin. These terminals do not have an identically named logical terminal in the symbol so they are "physOnly". I've used this attribute when trying when searching the pins to find the logical terminal name. VXL may use this as well.

     Ted

  • Hi Ted, thanks for the reply;

    How could I verify for a pcell which are the logical terminals and which are the physical terminals ? In otherwords, how could I test what you said ? :) It would be usefull to find the difference between physical only terminals and normal terminals in  a testcase because this way I woud have a real example and I could understend better.

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.