• 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. Logic Design
  3. Driving of reset line - order of magnitude difference between...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 61
  • Views 2230
  • 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

Driving of reset line - order of magnitude difference between RC & PrimeTime

archive
archive over 17 years ago

Dear all,

I am running into a weird problem with rtlcompiler on which I need some expert advice :-)

In my design I have a reset line (asynchronous) which is connected to different blocks. In every block the signal is inverted and then passed to a bunch of RN-pins. The problem that I am encountering is that rc selects the smallest available inverter to drive these pins. A timing report through the inverter does not show any problem. In the example below the inverter g1529 only adds a delay 163ps while it is loading 159 reset pins.

When performing a timing analysis with primetime the delay is found to be 6.25ns. I assume this value is correct?

When I export the net loads with write_set_load I see that the net loaded by the inverter has a load of 0. Almost all other nets (even the ones with only a couple of loads attached) have a load > 0.

Probably this is something very simple, I am quite new to rtlcompiler ;-)


Thanks,

Michael

RTL Compiler:
         Pin                   Type      Fanout  Load Slew Delay Arrival     
                                                 (fF) (ps)  (ps)   (ps)      
------------------------------------------------------------------------------
(clock virtual_clock)        launch                                    0 R   
                             latency                       +1200    1200 R   
(in_del_1)                   ext delay                     +1000    2200 F   
mem_select[0]                in port          3   6.3    0    +0    2200 F   
g519/A                                                        +0    2200     
g519/Y                       INVX1MTH         2   8.3  207  +125    2325 R   
g517/A0                                                       +0    2325     
g517/Y                       AO22X4MTH      100 119.2 1222  +878    3203 R   
g516/B                                                        +0    3203     
g516/Y                       NAND2BXLMTH     22  28.6 1340 +1163    4366 F   
cell/reset
  inst_decoder/reset
    g1529/A             <<
    g1529/Y             (i)  INVX1MTH       159   0.0    0  +163    4529 R   
    reg_IR_ID_reg[9]/RN      DFFRHQX4M                        +0    4529     
------------------------------------------------------------------------------
Timing slack :  UNCONSTRAINED
Start-point  : mem_select[0]
End-point    : cell/inst_decoder/reg_IR_ID_reg[9]/RN

rc:/> get_attribute net /designs/base/instances_hier/cell/instances_hier/inst_decoder/instances_comb/g1529/pins_out/Y
/designs/base/instances_hier/cell/instances_hier/inst_decoder/nets/n_1617
rc:/> get_attribute num_loads /designs/base/instances_hier/cell/instances_hier/inst_decoder/nets/n_1617              
159



PrimePower:
  Point                                                   Incr       Path
  ------------------------------------------------------------------------------
  clock virtual_clock (rise edge)                         0.00       0.00
  clock network delay (ideal)                             1.20       1.20
  input external delay                                    1.00       2.20 f
  mem_select[0] (in)                                      0.00       2.20 f
  g519/Y (INVX1MTH)                                       0.12       2.32 r
  g517/Y (AO22X4MTH)                                      0.89       3.21 r
  g516/Y (NAND2BXLMTH)                                    1.17       4.38 f
  cell/reset (opn_base)                                   0.00       4.38 f
  cell/inst_decoder/reset (decoder)                       0.00       4.38 f
  cell/inst_decoder/g1529/Y (INVX1MTH)                    6.25      10.63 r
  cell/inst_decoder/reg_IR_ID_reg[19]/RN (DFFRHQX8MTH)
                                                          0.00      10.63 r
  data arrival time                                                 10.63






Originally posted in cdnusers.org by denil
  • Cancel
Parents
  • archive
    archive over 17 years ago

    since RTL_compiler is a synthesis tool, it makes certain assumption and high fanout net (ideal net with no wire delay) is one of them. In this case, it treated the RESET net as a high fanout ideal net and it assumed the net will be re-buffer in the p&r tool so no buffer tree was built for the net and also it assumed a wire delay of zero. I think you can change this behaivour by some variable (control min fanout #).

    li siang


    Originally posted in cdnusers.org by lisiang
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 17 years ago

    since RTL_compiler is a synthesis tool, it makes certain assumption and high fanout net (ideal net with no wire delay) is one of them. In this case, it treated the RESET net as a high fanout ideal net and it assumed the net will be re-buffer in the p&r tool so no buffer tree was built for the net and also it assumed a wire delay of zero. I think you can change this behaivour by some variable (control min fanout #).

    li siang


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