Stats

  • Locked Locked
  • Replies 6
  • Subscribers 144
  • Views 3898
  • 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

how to get the orientation of the terminal in "symbol"

Derek WANG

Hi All.

I'd like to get the orientation of the terminal for the "symbol" view in the cadence.

Suppose I get the cellview ID by

cv = dbOpenCellViewByType(libId~>name cellId~>name "symbol" "" "a")

and then get the first terminal by

term = car( cv~>terminals )

and how can I find the orientation for the terminal "term", or the orientation of its corresponding shape of the pin.

Thanks in advance.

Best Regards

Yi

Parents

  • Hi Andrew

    Thank you for your reply

    The motivation of the question is from the script I have written to add the "cdsTerm" into a existing "symbol".

    Although there is procedure in the cadence we can add the "cdsTerm" while creating the "symbol" from "schematic", not every designer inside the company follow such procedure. Then it ends up that there are a lot of "symbols" do not have "cdsTerm" for every pin (terminal).

    my script is to add the "cdsTerm" to each pin, when the "symbol" is already there.

    The "cdsTerm" is added based on an assumption that "input pin" is on the left side of the block, "output pin" is on the right side of the block, and "inout pin" is on the top/bottom side of the block. So after running the script, the "cdsTerm" should be added like this, take input pin for example.

     the "cdsTerm" is always at the left side of the input pin.

      unfortunately, such assumption is not sure, as some designers do put the pins in the location they want, and do not care about the pin type.

    so, we have the user case like this:

    the "cdsTerm" are overlapped on each other.

    I thought it's caused by the orientation of the pins (terminals), and I did not include such info into the script.

    So, I was thinking, if I can get the orientation of the pins (terminals), then I can use this information to put the "cdsTerm" at the right place with right orientation.

    above is my motivation to search for the orientation of the pins(terminals), hope you can help me to find an alternative.

    Best Regards


    Yi

Reply

  • Hi Andrew

    Thank you for your reply

    The motivation of the question is from the script I have written to add the "cdsTerm" into a existing "symbol".

    Although there is procedure in the cadence we can add the "cdsTerm" while creating the "symbol" from "schematic", not every designer inside the company follow such procedure. Then it ends up that there are a lot of "symbols" do not have "cdsTerm" for every pin (terminal).

    my script is to add the "cdsTerm" to each pin, when the "symbol" is already there.

    The "cdsTerm" is added based on an assumption that "input pin" is on the left side of the block, "output pin" is on the right side of the block, and "inout pin" is on the top/bottom side of the block. So after running the script, the "cdsTerm" should be added like this, take input pin for example.

     the "cdsTerm" is always at the left side of the input pin.

      unfortunately, such assumption is not sure, as some designers do put the pins in the location they want, and do not care about the pin type.

    so, we have the user case like this:

    the "cdsTerm" are overlapped on each other.

    I thought it's caused by the orientation of the pins (terminals), and I did not include such info into the script.

    So, I was thinking, if I can get the orientation of the pins (terminals), then I can use this information to put the "cdsTerm" at the right place with right orientation.

    above is my motivation to search for the orientation of the pins(terminals), hope you can help me to find an alternative.

    Best Regards


    Yi

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.