Stats

  • Locked Locked
  • Replies 12
  • Subscribers 145
  • Views 7253
  • 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

Reading PCell Properties/Parameters using SKILL

frasheed

 Hello All,

I have a PCell that has nfet layout and I am writing a SKILL code to open the layout and label the Gate, Drain, Source and Bulk in layout. For that I need to read the parameters that where is the Gate, Drain and Sourcein layout. I tried some commands like :

pcGetParameters , pcGetParamLabelDefn, pcGetParamLabels, pcGetParamLayers but all of them are given me "Nil". Can anyone help me what's wrong ? Is it because the PCell doesn't have any properties ?

or is there any better way for labeling ?

Thanks

P.S: I didn't created that PCell and I am very beginner to SKILL.

 

Parents

  •  dbSetq(cellView~>instances~>instTerms~>term b_pin pins) is not going to work. The Virtuoso DesignEnvironment SKILL Reference IC616 is used here.

    1. The terminals pointed to by cellView~>instances~>instTerms~>term are the individual terminals inside the instance masters (Page: 1226)

    2.The instTerm jumps the hierarchy and connects the net in the current cellView (instTerm~>net) with the terminal inside the instance master (instTerm~>term). There are no pins involved, pins only mark the physical connection shapes for the cell, all hierarchical connection is done through the terminals and instTerms. In your instances, the bulk terminal has no pins and no physical connection but does have the logical connection through the bulk terminal.

    3. You cannot add a pin in the current level of the hierarchy to a terminal in the nested cellView. Connectivity does not work like that. The pin has to be a shape inside the master of the instance, not in the current level of the hierarchy.

    4. What you probably need to do, if the pin list for the terminal is nil, is either not place a label or place the label in the center of the bounding box of the instance.

    5. If the labels are supposed to stay with the instance when it is moved, transformed or deleted, either form a parent/child relationship between the instance and the labels - 5141 - (labelId~>parent = instId) or create a figGroup in IC6.x

    Ted

     

     

Reply

  •  dbSetq(cellView~>instances~>instTerms~>term b_pin pins) is not going to work. The Virtuoso DesignEnvironment SKILL Reference IC616 is used here.

    1. The terminals pointed to by cellView~>instances~>instTerms~>term are the individual terminals inside the instance masters (Page: 1226)

    2.The instTerm jumps the hierarchy and connects the net in the current cellView (instTerm~>net) with the terminal inside the instance master (instTerm~>term). There are no pins involved, pins only mark the physical connection shapes for the cell, all hierarchical connection is done through the terminals and instTerms. In your instances, the bulk terminal has no pins and no physical connection but does have the logical connection through the bulk terminal.

    3. You cannot add a pin in the current level of the hierarchy to a terminal in the nested cellView. Connectivity does not work like that. The pin has to be a shape inside the master of the instance, not in the current level of the hierarchy.

    4. What you probably need to do, if the pin list for the terminal is nil, is either not place a label or place the label in the center of the bounding box of the instance.

    5. If the labels are supposed to stay with the instance when it is moved, transformed or deleted, either form a parent/child relationship between the instance and the labels - 5141 - (labelId~>parent = instId) or create a figGroup in IC6.x

    Ted

     

     

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.