Home > Community > Search
Login with a Cadence account.
Not a member yet?
Create a permanent login account to make interactions with Cadence more conveniennt.

Register | Membership benefits

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

 Community Search 

Page 1 of 1 (8 items)
  • Fixing Transition violations
    1. I was trying to fix transition violation using -drv, for  a design with fences and guides. But I was in wain.  Once I removed them and recreated the encounter database with DEF, and V. The encounter was able to fix them. 2. I removed the fences and groups using encounter (from floorplan menu) and saved the database. But some ...
    Posted to Digital Implementation (Forum) by dinac123 on Mon, Jul 29 2013
  • Re: sroute + blockpin
    Sorry just found the reason.  the space inbetween ring and the block is small enough to insert the vias. But I think there should be an option to choose the via size in this case. ...  Encounter uses a default sizes.
    Posted to Digital Implementation (Forum) by dinac123 on Thu, Jun 20 2013
  • sroute + blockpin
    Trying to connect the PG aroung the block to the ring (sroute blockpins). As seen the attachment the sroute, routes only gnd on the top and vdd on the sides.  And leaves vdd on top and gnd on sides open. sroute does not leave any warnings or errors.  Thanks for your replies..  
    Posted to Digital Implementation (Forum) by dinac123 on Thu, Jun 20 2013
  • Re: create power and ground pins
    Thanks for your reply. Using version 9.13.  Yes, using createPGPin creates a Pin of type IO (and creates only one)  I wanted to create multiple PG Pin at each location of the 'physical pin' ?  but I think 'lefOut -stripePin' option would do this job. And use this lef each time when one works on the TOP.
    Posted to Digital Implementation (Forum) by dinac123 on Wed, Jun 19 2013
  • create power and ground pins
    I want create Power and ground pins at various locations in a partioned block. I succeded in creating "physical pins" by using option -create_pin 1 in addStripe. But how do I convert these "Physical Pins" object type to a normal IO Pins (add them to the netlist as IO pins).  Thanks for your replies....  
    Posted to Digital Implementation (Forum) by dinac123 on Tue, Jun 18 2013
  • Re: Prevent OptDesign in between paths
    yes, set_dont_touch would work for the nets. In my case, for example U1/a is connect with N1 to U2/a, U3/a,U4/a. I want no optimization buffers only for the path U1/a to U3/a  
    Posted to Digital Implementation (Forum) by dinac123 on Thu, Apr 11 2013
  • Re: Prevent OptDesign in between paths
    That will not work. set_false_path is only to ignore paths for the timing engine and would still add optimization buffer in the path. I think there is no option availabe to do this. For now only trick, I found is to add Fence. [ running with setOptMode -honorFence true , prevent addtion of buffer under this region, and hence force encounter to ...
    Posted to Digital Implementation (Forum) by dinac123 on Tue, Mar 5 2013
  • Prevent OptDesign in between paths
    I am trying to prevent Optimization between a path.  set_dont_touch, works only for the complete net, but not between a begin pin to a End Pin. Is there any other option to achieve this type ofcontraints? Thank You 
    Posted to Digital Implementation (Forum) by dinac123 on Mon, Mar 4 2013
Page 1 of 1 (8 items)