Stats

  • State Suggested Answer
  • Replies 7
  • Answers 1
  • Subscribers 161
  • Views 2311
  • Members are here 0
More Content

Match Track Lengths Across Multiple Layers

PS202410214615

Hi everyone,

I’m working with Allegro X Editor 2023 and need help matching the track lengths for a few nets. These nets span across three different layers, and simply matching the total track length is not sufficient. I want to ensure that the signal timing is controlled across all layers, so I need to match the track length on each layer individually.

I've tried using the "Total Length" and "Relative Propagation Delay Length" features, but these methods are not giving the desired results, as they take the entire length into account rather than each individual layer.

Can anyone guide me on how to achieve this?

Parents
  • 0

    Sound like you wish to match length between components pin and not full net?

    So you have to create pin pairs and constraint pin pairs instead of net.

    Net exemple:

    U1.1 U2.3 U4.11

    second net

    U1.2 U2.5 U4.6 R55.1

    if you want to match U1.1 to U2.3 with U1.2 to U2.5 you have to create two pins pairs with theses points and then put them into a matchgroup,, not the nets

  • 0 in reply to JCTEYSSIER0

    I believe an SI simulation giving you an eye diagram will help.

    A significant change in impedance along any portion of the net will cause both changes in propagation speed and result in signal reflections.  I.E. your signal transition will get there in time but the logic/voltage levels won't work. 

    I believe the only cause for propagation to be noticeably different between signal layers is stackup config related.  

Reply
  • 0 in reply to JCTEYSSIER0

    I believe an SI simulation giving you an eye diagram will help.

    A significant change in impedance along any portion of the net will cause both changes in propagation speed and result in signal reflections.  I.E. your signal transition will get there in time but the logic/voltage levels won't work. 

    I believe the only cause for propagation to be noticeably different between signal layers is stackup config related.  

Children
No Data
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.