• 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. Miss VDD pin in LEF file generated with lefout command

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 91
  • Views 14916
  • 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

Miss VDD pin in LEF file generated with lefout command

weian
weian over 14 years ago

 I'm doing a bottom-up multi-level hierarchical design.On the first layer, I designed all blocks and use lefout to generate their LEF files. Everything looks fine. On the 2nd layer, I use assembleDesign to put all block designs into one single block. Then I want to use lefout command to generate the LEF file for this single block. Now the problem occurs. The generated LEF only include VSS pin but there's no VDD pin. I check the assembled layout. The VDD power stripes from each blocks are as nice and clear as the VSS stripes. I verified globalNetConnect of both VDD and VSS and couldn't find the reason.

Has anyone seen this problem before? Did I miss something? Thanks very much.

 

  • Cancel
Parents
  • Kari
    Kari over 14 years ago

     Did you try the following argument to lefOut: (along with what you already have)

    -extractBlockPGPinLayers layer_number_list

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Kari
    Kari over 14 years ago

     Did you try the following argument to lefOut: (along with what you already have)

    -extractBlockPGPinLayers layer_number_list

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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