Stats

  • Locked Locked
  • Replies 2
  • Subscribers 92
  • Views 14687
  • 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

route follow pins inside a block ring.

gops

I have a softblock in my design. I want 

1) create a block ring for the block "A" and the core  ring for other modules skipping the blobk "A". I tried to do this by creating a fence, but encounter don't exclude fence, it dumps an error to chech placement status of fence :(

2) I want to create a separate stripe for block ring

3) I want the block rings to have separate follow pins . Please tell me how I can do this without CPF.

 

thanks

gops

Parents

  • addRing -type block_rings -around <user_defined>
    addStripe -break_stripes_at_block_rings

    Just out of curiosity....................................
    Why try an isolate common power domains ? 
    Secondly why explicitly no CPF ?

    Without a proper CPF they are by definition shorted together.
    You will have to do back flips to get any of the verification tools to work.

    The only legitimate reason I can think of for block rings rather than a continuous / homogenous power grid is when mixing standard cell heights in the same module and the M1 follow pins do not lineup.

     

     Shawn

     

Reply

  • addRing -type block_rings -around <user_defined>
    addStripe -break_stripes_at_block_rings

    Just out of curiosity....................................
    Why try an isolate common power domains ? 
    Secondly why explicitly no CPF ?

    Without a proper CPF they are by definition shorted together.
    You will have to do back flips to get any of the verification tools to work.

    The only legitimate reason I can think of for block rings rather than a continuous / homogenous power grid is when mixing standard cell heights in the same module and the M1 follow pins do not lineup.

     

     Shawn

     

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.