Stats

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

Generating Schematic pin list

LakshmanQual

Hi Team, I am generating the pin list from schematic as

cv=geGetEditCellView()
pins=cv~>terminals~>name .

If any bus is input or output, its coming directly as a bus only like Q<3:0>. But i want them as individual pins like Q<0> Q<1> Q<2> Q<3>.

There are 10's of buses in schematic, so i want all of them to come as individual pins.

Is there any way to generate them as individual pins? I want them to compare with layout pins?

Parents
  • Andrew Beckett

    Are you asking how to create pins on the schematic, or just how to get a list of the member names? I think it's the latter you're asking for, then:

    dbProduceMemName("Q<3:0>")

    which outputs:

    ("Q<3>" "Q<2>" "Q<1>" "Q<0>")

    Regards,

    Andrew

  • LakshmanQual
    in reply to Andrew Beckett

    Hi Andrew, thanks for the reply. Sorry that the question was not clear.  I want to list the schematic pins. But using the general code, the pins were coming as bus directly.  But those pins should be separated in my list to compare them with layout pins. With the piece of code you had given, i ran that code using foreach loop on entire list which includes buses. Now my final aim reached because of your idea of "dbProduceMemName". Thank you Andrew!!!

Reply
  • LakshmanQual
    in reply to Andrew Beckett

    Hi Andrew, thanks for the reply. Sorry that the question was not clear.  I want to list the schematic pins. But using the general code, the pins were coming as bus directly.  But those pins should be separated in my list to compare them with layout pins. With the piece of code you had given, i ran that code using foreach loop on entire list which includes buses. Now my final aim reached because of your idea of "dbProduceMemName". Thank you Andrew!!!

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.