• 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. bottomup flow,how to make submodule ring and stripe can...

Stats

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

bottomup flow,how to make submodule ring and stripe can been see in top module

verysmart
verysmart over 15 years ago

in a bottomup design flow , there is a submodule,it has its own power ring and stripe,

when load the submodule to top level,   how to make toplevel  know the  submodule's ring and stripe, so when do Sroute,  top level row and stripe will hook up the subblock ring and stripe correctly.

  the submodule designed by FLAT  Encounter flow with a speical digital library,  it has IO row, POWR ring/stripe and core row.

right now I use lef2oa and oa2lef, I can see VDD and VSS pin,but I cannot see the RING and Stripe definition. 

can somebody show me how to do this

 

  

  

 

  • encounter_ring1.JPG
  • View
  • Hide
  • Cancel
Parents
  • verysmart
    verysmart over 15 years ago

    similar issue on another website:

    http://www.chiptalk.org/modules/newbb/viewtopic.php?topic_id=202&forum=2&post_id=789

     

    Hierarchical place and route with Encounter
    Hi -

    I'm trying to figure out how to place and route a hierarchy with SOC Encounter (v5.2). I must be missing something because it shouldn't be this hard! What I've done is:

    1 - Start by place and routing a core macro. This works fine. I have a vdd! and gnd! ring around the circuit. I generate DEF and Verilog and read this back in to dfII and it DRC's and LVS's just fine. I'd like to use this macro in another design as a pre-designed macro!

    2 - In SOC I use lefOut with the -stripePin option to get a lef file with vdd! and gnd! pins. I also generate a .lib file using do_extract_model. (I've also tried generating the lef file by running abstract on the layout view from dfII - same behavior)

    3 - In SOC in my top-level design I import the core.lef and core.lib files in addition to the other stuff for my top-level design. The core is instantiated in my structural verilog file. When this is imported I get a core block that I can place in the floorplan.

    4 - I can pick up and place the block, put a halo around it, etc. All seems fine...

    5 - HERE'S THE PROBLEM - when I do my power planning (rings and stripes), I can NOT get the power routing connected to this macro! I've tried with the macro as CLASS BLOCK in the lef, I've tried with the macro as CLASS RING in the lef. I've tried making the vdd! and gnd! ports also of CLASS RING. I've made sure that I'm selecting the block pins in sroute. I've even followed the convoluted power planning template flow in the dtmf tutorial included with SOC.

    NOTHING WORKS. The power routing ends up connected to the pads, connected to the standard cell rows, and the stripes are connected to the standard cells rows. But, the stripes just end before they get to my core macro. They don't connect to it!

    It seems as if the nanorouting for the signal pins also works fine. But, I can't get SOC to connect the vdd! and gnd! wires to my macro. This macro was placed and routed by SOC, and the lef and lib were also generated by SOC. It must be possible to use it in SOC!

    Help! What am I doing wrong or what am I not doing that needs to be done to make this work?

    Thanks!
    -Erik
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • verysmart
    verysmart over 15 years ago

    similar issue on another website:

    http://www.chiptalk.org/modules/newbb/viewtopic.php?topic_id=202&forum=2&post_id=789

     

    Hierarchical place and route with Encounter
    Hi -

    I'm trying to figure out how to place and route a hierarchy with SOC Encounter (v5.2). I must be missing something because it shouldn't be this hard! What I've done is:

    1 - Start by place and routing a core macro. This works fine. I have a vdd! and gnd! ring around the circuit. I generate DEF and Verilog and read this back in to dfII and it DRC's and LVS's just fine. I'd like to use this macro in another design as a pre-designed macro!

    2 - In SOC I use lefOut with the -stripePin option to get a lef file with vdd! and gnd! pins. I also generate a .lib file using do_extract_model. (I've also tried generating the lef file by running abstract on the layout view from dfII - same behavior)

    3 - In SOC in my top-level design I import the core.lef and core.lib files in addition to the other stuff for my top-level design. The core is instantiated in my structural verilog file. When this is imported I get a core block that I can place in the floorplan.

    4 - I can pick up and place the block, put a halo around it, etc. All seems fine...

    5 - HERE'S THE PROBLEM - when I do my power planning (rings and stripes), I can NOT get the power routing connected to this macro! I've tried with the macro as CLASS BLOCK in the lef, I've tried with the macro as CLASS RING in the lef. I've tried making the vdd! and gnd! ports also of CLASS RING. I've made sure that I'm selecting the block pins in sroute. I've even followed the convoluted power planning template flow in the dtmf tutorial included with SOC.

    NOTHING WORKS. The power routing ends up connected to the pads, connected to the standard cell rows, and the stripes are connected to the standard cells rows. But, the stripes just end before they get to my core macro. They don't connect to it!

    It seems as if the nanorouting for the signal pins also works fine. But, I can't get SOC to connect the vdd! and gnd! wires to my macro. This macro was placed and routed by SOC, and the lef and lib were also generated by SOC. It must be possible to use it in SOC!

    Help! What am I doing wrong or what am I not doing that needs to be done to make this work?

    Thanks!
    -Erik
    • 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