Cadence PCB Best Practices

Constraint Compiler User Guide

Issue link: https://resources.pcb.cadence.com/i/1180274

Contents of this Issue

Navigation

Page 20 of 25

Allegro Constraint Compiler User Guide Allegro Constraint Compiler October 2019 23 Product Version 17.4-2019 © 1999-2019 All Rights Reserved. ■ Rule Set name with prefix PCS_ added to the new Physical CSet name Note: Multi-Row Header Rule= designation indicates the beginning of a Rule Set with all constraint columns included in it until another Rule= designation starts. Object Rule Specification Table The Object Rule Specification table is used to assign rules to objects in a design. Rule assignment can be accomplished by referencing group or Kind name and type classification defined in an Object table or an existing Net or XNet in the design. The primary use for the Object Rule table is to define explicit pin to pin rules of a group of objects by specifying a from- to component designation. Once these pin-pairs are defined a rule set or an existing CSet can be applied to the appropriate object level (Net Class, Net Group, and so on). You can specify one-to-many constraint expansion that propagate rules down to the lowest level while generating all supporting objects. For example, if relative propagation delay rules are defined, the compiler automatically creates the required match groups. In addition, part assignment can be driven by a mapping table to create many pin-pair relationships with associated match groups. Note: Relative Propagation Delay rules are only supported when an explicit pin-pair is specified in the table using from component to component. Specifying global or local Scope or longest pin-pair, longest driver/receiver and all drivers/all receivers are ignored.

Articles in this issue

view archives of Cadence PCB Best Practices - Constraint Compiler User Guide