• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. creating pin and direction table for schematic

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 143
  • Views 16363
  • 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

creating pin and direction table for schematic

LakshmanQual
LakshmanQual over 7 years ago

Hi,

I am trying to create a list of lists for pin and corresponding direction using "Pin_And_Dir=foreach(mapcar term cv~>terminals list(term~>name term~>direction)". Its crating as below

pin1 input

pin2 input

pin3<0:1> input

pin4<3:0> output

The problem is when there is a bus for some pins. But i want them separated as below:

pin1 input

pin2 input

pin3<0> input

pin3<1> input

pin4<3> output

pin4<2> output

.....

I tried to use dbProduceMemName for pin names. But its expanding only pin names but direction is not replicating to them.

Could you please help on this to make pins and directions  as list of lists or table format?

  • Cancel
Parents
  • Marben
    Marben over 7 years ago

    Hi LakshmanQual,

    Something like these:

    cv~>terminals~>net~>signames

    Hope this help.

    Best regards,

    Marben

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • LakshmanQual
    LakshmanQual over 7 years ago in reply to Marben

    With this we can get pin names separated which can be done by "dbProduceMemName(bus)". But i was not able to get pin direction if its separated from bus.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • LakshmanQual
    LakshmanQual over 7 years ago in reply to Marben

    With this we can get pin names separated which can be done by "dbProduceMemName(bus)". But i was not able to get pin direction if its separated from bus.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Andrew Beckett
    Andrew Beckett over 7 years ago in reply to LakshmanQual

    Pin_And_Dir=foreach(mapcan term cv~>terminals foreach(mapcar termMember dbProduceMemName(term~>name) list(termMember term~>direction)))

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • LakshmanQual
    LakshmanQual over 7 years ago in reply to Andrew Beckett

    Hi Andrew, Its working fine.

    Could you please help me in making them as direct list of lists. They are coming as (((pin1 dir)) ((pin2 dir)) ((pin3<0> dir) (pin3<1> dir)) ((pin4<0> dir) (pin4<1> dir)))

    But i want them as (pin1 dir) (pin2 dir) (pin3<0> dir) (pin3<1> dir) (pin4<0> dir)..

    I want them to compare schematic and layout pins, corresponding directions..

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago in reply to LakshmanQual

    You must have mistyped what I posted (I assume you didn't cut and paste it). The first foreach should be a mapcan and I think you must have used mapcar instead (the inner loop is using mapcar, however). My code outputs:

    (
     ("a" "input")
     ("b<3>" "output")
     ("b<2>" "output")
     ("b<1>" "output")
     ("b<0>" "output")
     ("c<5>" "inputOutput")
     ("c<4>" "inputOutput")
     ("c<3>" "inputOutput")
     ("c<2>" "inputOutput")
     ("c<1>" "inputOutput")
     ("c<0>" "inputOutput")
    )

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • LakshmanQual
    LakshmanQual over 7 years ago in reply to Andrew Beckett

    Hi Andrew,

    I was mistyped the code which you mentioned. Its working good now. Thanks!!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information