• 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. Digital Implementation
  3. How to generate PinText for Chip level?

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 90
  • Views 13062
  • 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 generate PinText for Chip level?

archive
archive over 18 years ago

Hello,

I'm trying to find a way to generate  a PinText (call_text) from FE.
Until sofar I can get the locations + layer of Pads which have really Pin/Net connections. 
For example well for  'pad_VDD_IO_1' but not for 'pad_VDD_CORE ' because lacked of a net connection.
 "vddi" is a global pwnet and connected to vdd by using wildcard *.

In my netlist:

  vddi pad_VDD_CORE (  );
  vdde3v3co pad_VDD_IO_1 ( .vdde3v3(SYNOPSYS_UNCONNECTED_1) );


If you have some suggestion/advice pls send me. Thanks.


Originally posted in cdnusers.org by DN
  • Cancel
  • archive
    archive over 18 years ago

    Hi DN,

    What I did is to dump out a DEF before placement. The def has all the pad and macro, but no std cell. I then rip out all the pads statement from the def file. I then use this info to determine the bonding points. With this information, I generate three files:

    1. A TCL that will add the bond pads (addInst and placeInstance commands) and pin text (addCustomText command) to the layout
    2. Generate bonding netlist that will be needed by the assembly house
    3. Two files that voltagestorm needs to indicated the location of power and ground source.

    All the above can be scripted, and is run from encounter with something like "exec scripts/go.csh".

    Regards,
    Eng Han


    Originally posted in cdnusers.org by EngHan
    • 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