• 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. PCB Design
  3. How to specify the pin pair in pro delay constraints

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 164
  • Views 14046
  • Members are here 0
More Content
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

How to specify the pin pair in pro delay constraints

ZhangCheng
ZhangCheng over 16 years ago

Hi all,

 In my FPGA-DDR2 design, on the net of A8, there is a pullup resistor. Please refer the attached pix for the layout on my board.

The path I need to control prop delay is from FPGA to DDR2. But in Allegro, pin pairs on this net is R-FPGA or R-DDR2, as following from information on this net:

            < NET >             

  Net Name:            DDR2_A8
  Member of Bus:       DDR2_ADDR

  Pin count:              3
  Via count:              2
  Total etch length:      1582.389 MIL
  Total manhattan length: 1652.899 MIL
  Percent manhattan:      95.73%

  Pin                     Type      SigNoise Model        Location
  ---                     ----      --------------        --------
  U2.T29                  BI        CDSDefaultIO          (5652.756 3039.055)
  P2.93                   IN        CDSDefaultInput       (6383.000 2921.728)
  RP8.1                   UNSPEC    DEFAULT_RESISTOR_PACK_4_47OHM (6899.800 2633.200)

  No connections remaining

  Properties attached to net
    LOGICAL_PATH      = @\penguin-1\.schematic1(sch_1):ddr2_a8
    FSP_NET           = DDR2_A<0>
    BUS_NAME          = DDR2_ADDR

  Electrical Constraints assigned to net
    prop delay: from AD to AR  min=1600.000 MIL  max=2200 ns
    relative prop delay: global group DDR2_ADDR_CTRL_CLK from AD to AR  delta=0.000 MIL  tol=280.000 MIL
    max parallelism: 300 MIL length at 6 MIL separation
    max parallelism: 600 MIL length at 7 MIL separation
    max parallelism: 1000 MIL length at 8 MIL separation
    max parallelism: 2000 MIL length at 10 MIL separation
    FSP_NET: DDR2_A<0>

  Constraint information:
    (Dly) RP8.1 to U2.T29  max= 2200ns  actual= 1447.605 MIL  (0.235986ns)
            (6899.800,2633.200) pin RP8.1,UNSPEC,TOP/TOP
      767.468 MIL (0.114477ns) cline TOP
            (6258.000,2898.109) via TOP/BOTTOM
      652.3 MIL (0.117235ns) cline SIG4
            (5672.440,3058.740) via TOP/BOTTOM
      27.838 MIL (0.00427453ns) cline TOP
            (5652.756,3039.055) pin U2.T29,BI,TOP/TOP

    (Dly) RP8.1 to P2.93  min= 1600 MIL  actual= 902.251 MIL
            (6899.800,2633.200) pin RP8.1,UNSPEC,TOP/TOP
      767.468 MIL cline TOP
            (6258.000,2898.109) via TOP/BOTTOM
      134.783 MIL cline BOTTOM
            (6383.000,2921.728) pin P2.93,IN,BOTTOM/BOTTOM

    (RDly) RP8.1 to U2.T29  min= 2056.43 MIL  max= 2616.43 MIL  actual= 1447.605 MIL
                   target=  (DDR2_CKE0) RP5.2 to U2.U31
            (6899.800,2633.200) pin RP8.1,UNSPEC,TOP/TOP
      767.468 MIL cline TOP
            (6258.000,2898.109) via TOP/BOTTOM
      652.3 MIL cline SIG4
            (5672.440,3058.740) via TOP/BOTTOM
      27.838 MIL cline TOP
            (5652.756,3039.055) pin U2.T29,BI,TOP/TOP

  Member of Groups:
    MATCH_GROUP     : DDR2_ADDR_CTRL_CLK
    BUS             : DDR2_ADDR
    PHYSICAL & SPACING NETCLASS: 8MIL

Can anybody give me some advice to make control on the path from FPGA to DDR2?

Thanks!

  • Prop delay constraint.jpg
  • View
  • Hide
  • Cancel
  • Mike Veal
    Mike Veal over 16 years ago

     You should be able to right click the Xnet in constraint manager and select create - pin pair.

    This might help too:

    http://www.cadence.com/rl/Resources/conference_papers/stp_cdnliveemea07_ddrconstraints_veal.pdf

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ZhangCheng
    ZhangCheng over 16 years ago

    Pin Pair can not be chosed to be desired.

    However, the document you wrote is very helpful! Thanks!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Cadence Guidelines

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